Downloaded 511 beta to play a game. Was fine, started working on some of my own projects and playing around with client.fps.
Set client fps to a number much higher than world.fps (world.fps=10, client.fps=60), as the document suggested it was safe to do.
From that point on, my project was then subject to random app crashing, app hang ups and extreme dips in FPS(seemingly client).
Following all of this, i completely removed all traces of BYOND suite from my PC several times and re-installed 510, with no fix to the issue.
I've reinstalled several times this past week and am still suffering from massive issues with (all) my projects. I've tried every fix short of reformatting my PC. And in addition to all of those things, the files for my project seem to be corrupted as well, since a friend hosting the game experiences random dream daemon crashes.
Below is a test I have been performing for over a year.
https://www.youtube.com/watch?v=8XoXhu39kMA
As you can see here, the code runs fine despite screen capture software running to take the video as well.
An hour later, 1 second into starting the stress test, I am greeted with this screen.
![](http://puu.sh/r2m4N/65bd067f71.jpg)
Previous to DL and running of 511 my game ran comfortably with almost 0 CPU use on all fronts -- for weeks at a time.
Now it barely runs for an hour or two despite the fact that I've made no changes to warrant such an issue. (I bring all this up because apparently I lie for no reason and nothing I say can be trusted -_- )
Version control of my own projects also confirms everything I've mentioned above to be accurate as well.
I'm *only* dropping this off here to make someone aware that this is a potential issue. nothing more or less.
Does the problem occur:
Every time? Or how often? yep
In other games? yep
In other user accounts? yes
On other computers? yes
When does the problem NOT occur? pre 511 use.
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)
Not sure, seems to have corrupted earlier versions of DM as well.
Workarounds:
None that I know of, short of a formatting at this point. I've done registry cleans, defrags, system repairs,