Open nebulazorua opened 4 months ago
seems to be related to it firing one last time after its meant to be released
Seems related to the timer being recycled without .object being set again?? this was with a trace at the top of flickerProgress Unsure why this is happening here but not in the compiled game, esp. since I'm using the shit from hmm
flicker seems to be destroyed erroneously? (the "Fuk u" is traced in destroy)
so it seems to be that its getting a new flicker, and getting the same flicker?? which is then released, but the timer is still going so it fucks everything up. No clue why FlxPool is returning the same flicker
this is, infact, whats happening. Strange
Seems to have been fixed in 0.3.3, I'm not getting the crash anymore.
Please check for duplicates or similar issues, as well performing simple troubleshooting steps (such as clearing cookies, clearing AppData, trying another browser) before submitting an issue.
If you are playing the game in a browser, what site are you playing it from?
If you are playing the game in a browser, what browser are you using?
What version of the game are you using? Look in the bottom left corner of the main menu. (ex: 0.2.7, 0.2.1, shit like that)
0.3.2
Have you identified any steps to reproduce the bug? If so, please describe them below in as much detail as possible. Use images if possible.
Yeah go play stress lol
Please describe your issue. Provide extensive detail and images if possible.
When compiling, Stress crashes after a Tankman dies cus of Line 171 in FlxFlicker "Called from flixel.effects.FlxFlicker::flickerProgress flixel/effects/FlxFlicker.hx line 171"
crash log here crash-2024-05-09-00-33-35.log
Only edits I've made shouldn't affect this as they don't touch FlxFlicker. I ran hmm install etc exactly as said in the compiling docs
If you're game is FROZEN and you're playing a web version, press F12 to open up browser dev window, and go to console, and copy-paste whatever red error you're getting