End - 128=1552 64=6340 32=700 16=0 8=0 4=0 2=0 1=0
I don't get fps lag as such, I do because my computer is terrible, I am not whinging about that. The game freezes for 1-2 seconds when playing, watching demos back or spectating players I don't have it happen. When I am riding I was keeping an eye on the times it was happening and it seems to happen at exactly every five minutes so 5, 10, 15, etc.
Actually looks like the new snapshot is performing better than the old one, or at least similarly. I don't mean to be insulting, but are you certain you have threaded optimization disabled from the control panel. Or have you tried disabling hyper threading through the bios all together.
All opinions expressed by this account are unofficial, and should be taken with a grain of salt
End - 128=1552 64=6340 32=700 16=0 8=0 4=0 2=0 1=0
I don't get fps lag as such, I do because my computer is terrible, I am not whinging about that. The game freezes for 1-2 seconds when playing, watching demos back or spectating players I don't have it happen. When I am riding I was keeping an eye on the times it was happening and it seems to happen at exactly every five minutes so 5, 10, 15, etc.
Do you have demo recording turned off? Some systems freeze when it writes the demo file. That might explain why it doesn't happen when playing back demos.
With the 5 minute intervals it sounds a lot like it's a background process scheduled to do something every 5 minutes.
Josh Vanderhoof
Sole Proprietor jlv@mxsimulator.com
If you email, put "MX Simulator" in the subject to make sure it gets through my spam filter.
After speaking about the issue with Jay, it has something to do with sequence files in the tracks (apparently), however it only started happening since this latest update so I am confused as to why..?
I have demo recording turned on, I have never turned it off.
I had the CPU monitor up and it isn't spiking at all so I am really confused
I haven't downloaded anything new or changed anything on my pc other than doing Nvidea driver updates..
stocksy129 wrote:After speaking about the issue with Jay, it has something to do with sequence files in the tracks (apparently), however it only started happening since this latest update so I am confused as to why..?
I have demo recording turned on, I have never turned it off.
I had the CPU monitor up and it isn't spiking at all so I am really confused :lol:
I haven't downloaded anything new or changed anything on my pc other than doing Nvidea driver updates..
I can definitely do something to limit the size of sequence files. Maybe I'll cap the max width/height to 256.
Josh Vanderhoof
Sole Proprietor jlv@mxsimulator.com
If you email, put "MX Simulator" in the subject to make sure it gets through my spam filter.
I was able tom make the sequence file on Hangtown null and I only had the freeze once which was only for a split second barely noticeable, afterwards I didn't have a problem at all, I did 20minutes and not one freeze frame. so maybe limiting them would be good, worth a shot.
What else has sequence files besides the flags? I replaced the crowd with a blank alpha image to help a little (at least I'm pretty sure it helped , I don't think the transparency antialiasing will do anything to a full alpha image right?)
TeamHavocRacing wrote:If I had a nickel for every time someone asked for this, I would have a whole shitload of nickels.
That's all I could find with a sequence file, I am now noticing my offset spikes to 300-400 each time the frame freezes. Not sure if that information changes anything.
JLV, I was wondering if this could possibly be a culprit to some of the FPS issues people have been experiencing.
Myself and Kyle Robb both have 980ti graphics cards along with similar more than sufficient CPU's 6700k and 5820k. With my computer I have no issues with FPS or experience frame skips. Kyle experiences frame skips along with FPS drops. We both run identical advanced settings in nVidia Inspector/Control Panel so that should all be the same. We ended up finding this by accident today when we were overclocking with MSI Afterburner. My GPU will run close to my boost clock which is 1485 mhz. His GPU with the same overclock or stock like shown will only run at base clock and will not boost in MXS other than at startup it will go up a touch then go back down to 1013mhz constant. This issue only occurs in MXS for him he has no boosting issues in other games. Any idea what could be causing this?
A GTX 980 should easily have enough processing power without overclocking. If I were having problems with hitches or stutters one of the first things I'd try is going back to the non-overclocked settings.
Josh Vanderhoof
Sole Proprietor jlv@mxsimulator.com
If you email, put "MX Simulator" in the subject to make sure it gets through my spam filter.