Hyomoto
Member
Well, it finally happened. GM2 broke and it doesn't seem I can fix it any more. Or at least, I have no idea what I can do to fix it other than start a new project since it seems localized to my project. Here's the bug in action:
Here's some context, you are looking at a 94x38 pixel room with two objects, and yet, despite a real_fps of ~10,000, it cannot seem to maintain a frame rate of 48. I just have no idea any more. I mean, it's just my project. If I start a new one it works fine, this one however is apparently garbage. I tried clearing the cache, I tried restarting the computer, I tried even changing the way this stuff is rendered to the screen and then ... it went up to 44. Still not 48, but better? So I changed everything back. 44. Started the program: it was running at 44 instead of 32. So now it runs at 44 instead, despite actually having changed nothing. I mean, maybe if I keep this up it'll get back to 48?
I just want to find some way to isolate what is happening. I have more than 200 hours in project right now and for a bug like this to bring it all grinding to a halt is just maddening. I mean, is there NO logs I can check, NO numbers I can view? Nothing I can do to see why THIS project is so afflicted by this bug but other ones are unaffected? I'm clearly in the minority here but damn it, there has to be SOMETHING I CAN DO TO HELP GET THIS FIXED. Some troubleshooting step. Some output to read or submit. Right now I have no idea if it will ever go back to 48 ( I -could- set the program speed to 60 or so and then it would be about 48, since the slowdown seems comparative, not absolute, but that's not really a solution, is it?).
So I restarted my computer again aaaand, yup. Framerate back to 32. I have my Surface with me and a I strongly suspect it will have the same issue since this has been a problem for quite some time now. However, I guess the next best option is if it IS permanently borked, at least now it's reproducable to file a useful bug report. Hopefully it happens on your machines as well, though based on my prior interactions with the bug tracker, unless I can isolate 'the offending bit of code' there's no point. Unless the offending code is the forty lines or so that's running in that gif, I think I've pretty much isolated most of my work out of the equation.
Here's some context, you are looking at a 94x38 pixel room with two objects, and yet, despite a real_fps of ~10,000, it cannot seem to maintain a frame rate of 48. I just have no idea any more. I mean, it's just my project. If I start a new one it works fine, this one however is apparently garbage. I tried clearing the cache, I tried restarting the computer, I tried even changing the way this stuff is rendered to the screen and then ... it went up to 44. Still not 48, but better? So I changed everything back. 44. Started the program: it was running at 44 instead of 32. So now it runs at 44 instead, despite actually having changed nothing. I mean, maybe if I keep this up it'll get back to 48?
I just want to find some way to isolate what is happening. I have more than 200 hours in project right now and for a bug like this to bring it all grinding to a halt is just maddening. I mean, is there NO logs I can check, NO numbers I can view? Nothing I can do to see why THIS project is so afflicted by this bug but other ones are unaffected? I'm clearly in the minority here but damn it, there has to be SOMETHING I CAN DO TO HELP GET THIS FIXED. Some troubleshooting step. Some output to read or submit. Right now I have no idea if it will ever go back to 48 ( I -could- set the program speed to 60 or so and then it would be about 48, since the slowdown seems comparative, not absolute, but that's not really a solution, is it?).
So I restarted my computer again aaaand, yup. Framerate back to 32. I have my Surface with me and a I strongly suspect it will have the same issue since this has been a problem for quite some time now. However, I guess the next best option is if it IS permanently borked, at least now it's reproducable to file a useful bug report. Hopefully it happens on your machines as well, though based on my prior interactions with the bug tracker, unless I can isolate 'the offending bit of code' there's no point. Unless the offending code is the forty lines or so that's running in that gif, I think I've pretty much isolated most of my work out of the equation.
Last edited: