Sweet! Thank you!
Colludium - do you just move everything from the Node-Webkit 32 bit folder to the NW 32 bit folder? I just want to make sure I understand you. And yes - thanks!
Colludium - that sounds like the best approach I've heard so far. Does it export flawlessly? Can you chose the 32 bit export option?
Thank you both for addressing this.
Ancillary
Excellent! Thank you.
Yes, I have read that. As R0J0hound said, I think this bug has already been reported.
Develop games in your browser. Powerful, performant & highly capable.
jobel - the latest NW.js I used was working well on my game. I have read many including Auriel say that 10.5 works the best for them. Some report lots of jank with recent NW.js'. Also, thanks for the tip on changing the version in the caproj.
I saw where someone said they had to revert to C2 version 192 to successfully export to PC/Steam with NW 10.5. Is that true and, if so, how would one get their game saved with the latest C2 to work with version 192? Is that possible?
Kyatric - Ashley - any idea what this error could mean?
Ancillary - I don't use any arrays so it must be something different in my project, eh?
It also seems that it isn't disabling collisions as I am instructing it too after it overlaps the target sprite.
lucid - I made a collision rectangle in one of my Spriter animations. When I destroy the collision rectangle on overlap, it actually seems to destroy all of my sprites and the spriter object for the character that includes it.
R0J0hound - Thank you. I think the only containers I use are my spriter objects. The error must be there somewhere.
Ancillary - I don't use any arrays and, yes, I find that after I close the error window, the game keeps playing correctly. I do use many Spriter objects in my game so I'm wondering if they might be involved. I understand that IIDs are generated automatically so it does make me wonder what the problem is. R0J0hound - thank you. If I can get my google drive to work, I'll PM you a link.