Diablo 3 sometimes starts with max FPS - why?

[AngelsHalo]

Anyone know? Seems random. Diablo 3 will load (manually, YAR, doesn't matter) with FPS unlimited, even if the setting is ticked correctly. I just have to close the client and reopen it to fix the problem, but it can get annoying. Really puts a big load on one of my project rigs.

 

[yura]

same with me

 

[Job2k9]

I used to use Apoc's d3 starter and I'd randomly get them starting with the fps cap ignored fairly often. This was back when D3's would crash every few hours and I had a macro setup to relaunch them when I was away. Usually resulted in me finding 3 or 4 running at full fps when I returned home, which really taxed my pc far more than needed. Very frustrating and I never did find a fix.

 

[IGG]

I've got the same problem. My guess that this issue could happen due to high hdd\ssd load when staring multiple clients, because I get this thing more often when starting a lot of cients at once.

This FPS problem has got an easy solution - a plugin (or relogger additional code) or integrated db FPS check - that will check game fps a the beginnig of a profile and if fps are over the limit, restart the game or smth. Maybe we need to ask devs if such thing is possible. I noticed that unlimited fps on just one client affects a lot productivity of other bots, they get massive lags

 

[AngelsHalo]

I've got the same problem. My guess that this issue could happen due to high hdd\ssd load when staring multiple clients, because I get this thing more often when starting a lot of cients at once.

This FPS problem has got an easy solution - a plugin (or relogger additional code) or integrated db FPS check - that will check game fps a the beginnig of a profile and if fps are over the limit, restart the game or smth. Maybe we need to ask devs if such thing is possible. I noticed that unlimited fps on just one client affects a lot productivity of other bots, they get massive lags

Yeah that seems like a logical solution. I thought it was just one of my computers that was acting up at first, but now that I've had multiple project rigs (2 different PCs, and 2 laptops) to fool around with botting, I've noticed all of them have the same issue, so it must be something within D3 itself. Its not too much of an issue since I don't run max loads, but my Intel 3770k runs 11 and even if a couple get the FPS bug its still ok. My AMD FX-8320 project, however, is running on pretty high load even with 8 bots. If one of them the FPS bug, then everything slows down (lots of pauses in the other bots).