2019-06-17 snapshot

[Atom6246]

I'm just saying, if you can repeat it, do the reportstutter tool and maybe JLV can find what's causing it. The proof of frame drops is nice but I think he needs more to go off.

I see what you're saying but thing for me is I was streaming. So I would have to fire up my stream just long enough to re-race it then end it, which I do not like to do. Or re-race it twice off stream but that doesn't sound too convenient.

If JLV needs me to do it I guess I will.

[jlv]

Do you have the demo? Race against the demo on each snapshot and see if there’s a difference.

I do, but don't feel it's necessary considering I linked a gyazo from the actual race on Wednesday night with substantial evidence of frame drops. As well as others noticing the same.

The reason I ask for demos and stuff isn't because I don't believe you. To fix things I need to understand why they're happening. If something reliably happens and is repeatable it's easy to fix. If there's an error or warning message, that can lead me in the right direction. If all I have is a vague report that something's going wrong I have no chance of fixing it.

With that said, I did get a bad lag incident on WW ranch which didn't show up in the demo. I did have a lot of stuff running in the background so it might have been that but it is a little suspicious. If someone manages to catch it with reportstutter that'd be helpful.

[TeamHavocRacing]

How reliable are the people reporting as far as admitting what's running at the time. How clean of a boot is it and are they using a VPN with no streaming or Discord etc. etc. etc.

[Jeremy150]

Just did some testing.

The only snapshot that does not stutter for me is 4-21. When you put out the 4-30 snapshot, it fixed most people's games that were stuttering, but everyone who didn't stutter with 4-21, had stutters with 4-30.

I tried racing moto 1 this week with 6-17, but I was getting very bad stutters so I reverted back to 4-21, and I was fine for the race.

When playbacking the demo, no stutters happen on 6-17, but when I race against the demo the stutters happen again.

Report Stutter won't catch them, because instead of my FPS dropping below 4, my FPS drops to around 15-20, which gives the same effect.

Here is the demo from the Pro 450 Moto 1 from WW Ranch
https://drive.google.com/open?id=1B0x4J ... Lbjh-LQL08

Let me know if I need to test anything else or if I'm missing critical information.

i7 8700k
RTX 2080 ti
32Gb Memory
1TB m.2 ssd

[Atom6246]

The only snapshot that does not stutter for me is 4-21. When you put out the 4-30 snapshot, it fixed most people's games that were stuttering, but everyone who didn't stutter with 4-21, had stutters with 4-30.

^

Report Stutter won't catch them, because instead of my FPS dropping below 4, my FPS drops to around 15-20, which gives the same effect.

I only did 2 laps in the demo but this is all I got.



i7 7700k
RTX 280
16gb ram

[jlv]

Might be tough to fix if it's in getmessage. The most likely cause for that would be another process preempting mx.exe. (getmessage/processmessage is where the game collects input. It's not doing any intensive work there but getmessage is a task switching point for Windows.)

I'll do some more testing and see if it's happening anywhere else. Jeremy, is that demo a sure way to trigger it? If you want reportstutter to show dips below 20 fps use "/reportstutter .05" (i.e. 1/20).

[Jeremy150]

Yes that demo I posted is the one I have been testing with.
I had to drop reportstutter to .01 to get it to report them

Code: Select all

[105:40:36.65] Stutter in tic - 0.010000 seconds
[105:40:37.40] Stutter in tic - 0.011000 seconds
[105:40:37.42] Stutter in tic - 0.010000 seconds
[105:40:37.43] Stutter in tic - 0.010000 seconds
[105:40:37.44] Stutter in tic - 0.010000 seconds
[105:40:38.14] Stutter in tic - 0.010000 seconds
[105:40:39.09] Stutter in tic - 0.010000 seconds
[105:40:39.11] Stutter in tic - 0.011000 seconds
[105:40:39.15] Stutter in tic - 0.011000 seconds
[105:40:39.19] Stutter in tic - 0.011000 seconds
[105:40:39.22] Stutter in tic - 0.010000 seconds
[105:40:48.78] Stutter in tic - 0.010000 seconds
[105:40:48.79] Stutter in tic - 0.010000 seconds
[105:41:22.73] Ackie Rush | AUS connected
[105:41:24.68] Devin Ryan | AektivCo connected
[105:41:27.63] Stutter in tic - 0.011000 seconds
[105:41:28.22] Stutter in tic - 0.011000 seconds
[105:41:38.87] Ackie Rush | AUS is ready
[105:41:45.35] Roy Mitchell | Whipstyle disconnected
[105:41:45.84] Roy Mitchell | Whipstyle connected
[105:41:46.34] Connor Wells | BFD disconnected
[105:41:49.00] Layne Wofford disconnected
[105:41:51.48] Roy Mitchell | Whipstyle is ready
[105:42:07.09] Devin Ryan | AektivCo is ready
[105:42:24.25] Stutter in tic - 0.012000 seconds
[105:42:24.26] Stutter in tic - 0.011000 seconds
[105:42:24.29] Stutter in tic - 0.011000 seconds
[105:42:24.30] Stutter in tic - 0.010000 seconds
[105:42:24.38] Stutter in tic - 0.011000 seconds

[jlv]

Yes that demo I posted is the one I have been testing with.
I had to drop reportstutter to .01 to get it to report them

It's doing it for me. Had to be in "race against" mode for it to happen. Thanks!

[MotoDad183]

Just realized it but somehow after install I lost all my 2018 bikes? the newest bike is a 13. Should I just try and re download it?

[MotoDad183]

Just realized it but somehow after install I lost all my 2018 bikes? the newest bike is a 13. Should I just try and re download it?

never mind I fixed it.