Japster
Member
Hi guys - I'm not sure if any of you have submitted bug reports yet, but I took the (quite substantial) time to thoroughly document a game-crippling bug I discovered in the HTML5 target on the later run-times, put the EXACT release that it stopped working properly in, and the one it worked in, 1 release prior. Added my project file, gave full logs and instructions on how to reproduce it in FIVE SECONDS flat. In short, everything needed to quickly investigate and hopefully fix this bug ASAP.
I've now waited WEEKS, no (as in, none-automated auto) email, no response, etc, and my project is now sat in limbo (and yes, it's ready to release other than this) while I wait for a response even.
I did originally get by via switching to the old runtime, but now even this isn't working - for some reason, switching to the older runtime now makes the game crash on launch (for EVERY target build, HTML5 and Windows included), as even though the rooms are still showing as being in the correct order, with my splash screen the first (and this works with the newer (broken) runtime), NOTHING I do, other than deleting my entire 'problematic' room and re-creating it (not even copying and deleting it), makes the project launch using the correct starting room (which also sets up the variables etc....)
Even trying to force a room change at the start, is completely ignored - GMS2 wants to start with that bloody room, and nothing will stop it from doing so! even checked room creation code etc, nothing - GMS2 completely ignores any attempt to reset the room, even setting another room to start, then resetting, doesn't work. If anyone has seen this issue, and knows how to possibly resolve it, I would be hugely appreciative!
As it stands, I'm trying to help YoYo AND myself, by submitting a literally game/engine-breaking HTML5 bug with EVERYTHING needed to more easily track it down and revert it to it's (previously) perfect behaviour, and feel like I'm being COMPLETELY ignored, AND losing money....
Oh, and that latest bug - the one where half of the time, the HTML5 Neon Jam entries were not even accepting any mouse buttons or key presses? - I noticed if you have an active button (seemingly random buttons) on a page, and click it, it sometimes starts accepting input as normal. Another 'quirk' that's been around for way too long - reading on the forums about hacks and tricks to try and get focus - surely by now this should also be fixed?! - As it stands, one of the known 'fixes' (workarounds) for this is....
...yep... ...build with that older runtime that works for my dual-mouse button presses - "2.3.0.401" - ironic, no?... Doesn't this show that issues occurred in the release immediately following this one?
I know that YoYo are busy guys, but really, stuff like this makes me want to re-assess my opinion of the quality of support provided, and is frustrating as hell...
I've now waited WEEKS, no (as in, none-automated auto) email, no response, etc, and my project is now sat in limbo (and yes, it's ready to release other than this) while I wait for a response even.
I did originally get by via switching to the old runtime, but now even this isn't working - for some reason, switching to the older runtime now makes the game crash on launch (for EVERY target build, HTML5 and Windows included), as even though the rooms are still showing as being in the correct order, with my splash screen the first (and this works with the newer (broken) runtime), NOTHING I do, other than deleting my entire 'problematic' room and re-creating it (not even copying and deleting it), makes the project launch using the correct starting room (which also sets up the variables etc....)
Even trying to force a room change at the start, is completely ignored - GMS2 wants to start with that bloody room, and nothing will stop it from doing so! even checked room creation code etc, nothing - GMS2 completely ignores any attempt to reset the room, even setting another room to start, then resetting, doesn't work. If anyone has seen this issue, and knows how to possibly resolve it, I would be hugely appreciative!
As it stands, I'm trying to help YoYo AND myself, by submitting a literally game/engine-breaking HTML5 bug with EVERYTHING needed to more easily track it down and revert it to it's (previously) perfect behaviour, and feel like I'm being COMPLETELY ignored, AND losing money....
Oh, and that latest bug - the one where half of the time, the HTML5 Neon Jam entries were not even accepting any mouse buttons or key presses? - I noticed if you have an active button (seemingly random buttons) on a page, and click it, it sometimes starts accepting input as normal. Another 'quirk' that's been around for way too long - reading on the forums about hacks and tricks to try and get focus - surely by now this should also be fixed?! - As it stands, one of the known 'fixes' (workarounds) for this is....
...yep... ...build with that older runtime that works for my dual-mouse button presses - "2.3.0.401" - ironic, no?... Doesn't this show that issues occurred in the release immediately following this one?
I know that YoYo are busy guys, but really, stuff like this makes me want to re-assess my opinion of the quality of support provided, and is frustrating as hell...
Last edited: