@Ashley Like I said before. Not all issues can be recreated with a smaller capx. I can't make a capx of someone else having the game crash on them. Or for the fact that I mentioned in a previous post that all C2 dev'd games and prototypes I give to this person crash randomly for them while they have no problems running anything else. Stuttering frame rates on computers faster than mine? I can't make a capX of these issues for you - in a big game that has issues that randomly happen, how do I even know what part of the engine is messing up? How do I make a capX - I'd basically be recreating the whole game until I figured out what was going wrong.
All of the issues we've had with C2 aside of not being able to update the version of C2 we are using for Insanity's Blade, I have developed work arounds for - or simply found alternate ways to do the thing that should work the way I'm already doing it. One thing I've always liked about C2 (and well programming in general) is the fact that I can always find multiple ways to get the same end result.
But for us, it's simply the instability and unpredictability of the end result. Which again, we have no control over. No matter how complex or simple of a creation I make with this software, the end result will always be the same - unpredictable. And you can't simply blame the state of say Node Webkit for it's faults either as it was your choice to use it as an exporter.
And I also know you have no control over HTML5. And it would seem that the people who develop have no control either
And the updates they make must have some toll on how C2 runs.
Anyhow, I'm not here to argue. I only want this thing to get better. And to me, the announcement of C3 when C2 feels unfinished has made me worry.