It'll automatically do the exact same erode sequence.aeffertz wrote:Will it erode the same as it did in the server? Do I need to adjust my .exe commands at all?Wahlamt wrote:They do erode the track.
2019-04-21 snapshot
Re: 2019-04-21 snapshot
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.
Sole Proprietor
jlv@mxsimulator.com
If you email, put "MX Simulator" in the subject to make sure it gets through my spam filter.
Re: 2019-04-21 snapshot
I tried racing the erode test tonight and had some of the worst stutter ever, i was stuttering as soon as i left the gate and couldnt even play the game.
#1 All Time 250 RF NA Motocross Winner
#1 All Time 250 RF EU Winner
16th overall on the RF Gaming All Time Wins List
#1 All Time 250 RF EU Winner
16th overall on the RF Gaming All Time Wins List
Re: 2019-04-21 snapshot
jlv wrote:Just in case anyone missed this:jlv wrote:If you're getting the stutter, two things would be helpful.
Type "/fpshist", do whatever makes the stutter happen, and type "/fpshist" again. Post the numbers. (It'll be in the lastlog so you can cut and paste it from there.) If you can do it with a demo it'd be better for the sake of repeatability.
Type "/reportstutter .25" in the chat screen, make the stutter happen, and post the lastlog file if it hits anything. If it doesn't say "Stutter in x - x seconds", you need to use a lower value. If you want, just post the fpshist numbers and I'll tell you a good value to use.
TeamHavocRacing wrote:If I had a nickel for every time someone asked for this, I would have a whole shitload of nickels.
-
- Posts: 109
- Joined: Thu Sep 15, 2016 8:42 pm
- Team: MV Films
- Location: Kentucky
Re: 2019-04-21 snapshot
This was about 6 or so min of riding from the erode test going on tonight. Using "/reportstutter .10" My stutters are every 2ish seconds and is normally a small hit rather than a longer freeze. AMD Ryzen 5 1600, RX580 8gb and 16gb ddr4. Have demo as well if needed.
Re: 2019-04-21 snapshot
These are the exact same stutters i was getting, JLV PLEASE HELPgarrettolver wrote:This was about 6 or so min of riding from the erode test going on tonight. Using "/reportstutter .10" My stutters are every 2ish seconds and is normally a small hit rather than a longer freeze. AMD Ryzen 5 1600, RX580 8gb and 16gb ddr4. Have demo as well if needed.
#1 All Time 250 RF NA Motocross Winner
#1 All Time 250 RF EU Winner
16th overall on the RF Gaming All Time Wins List
#1 All Time 250 RF EU Winner
16th overall on the RF Gaming All Time Wins List
Re: 2019-04-21 snapshot
Hello I was doing the first outdoor erode test I was stuttering on the first moto then the second was fine. I saved the demo from the moto 2 and started to stutter on lap one I was use the code "/reportstutter .10" and here are the numbers I got. I run a i5 8300u 1050gtx 3gb 8gb 1tb hard drive.
[445:51:40.06] Stutter threshold set to 0.100000
[445:51:42.99] lil p connected
[445:51:43.02] lil p disconnected
[445:52:45.25] Juan Vasquez | Meta connected
[445:53:04.11] Stutter in tic - 0.105000 seconds
[445:53:06.13] Stutter in tic - 0.103000 seconds
[445:53:08.15] Stutter in tic - 0.104000 seconds
[445:53:12.18] Stutter in tic - 0.101000 seconds
[445:53:13.45] Juan Vasquez | Meta is ready
[445:53:17.70] Erode queue full!
[445:53:25.05] Motorcrosser: ?
[445:53:29.20] tommy bickles: lol
[445:53:30.32] Stutter in tic - 0.106000 seconds
[445:53:34.36] Stutter in tic - 0.109000 seconds
[445:53:48.46] Stutter in tic - 0.104000 seconds
[445:53:52.49] Stutter in tic - 0.102000 seconds
[445:54:06.61] Stutter in tic - 0.105000 seconds
[445:54:08.62] Stutter in tic - 0.105000 seconds
Here are my graphics in game:
https://gyazo.com/6e1f40fa0501bb10f8fc2b03f58f79b2
I didn't get these stutters on the old snapshots but once I switch over to the new latest snapshots I started stuttering. PLZ JLV
[445:51:40.06] Stutter threshold set to 0.100000
[445:51:42.99] lil p connected
[445:51:43.02] lil p disconnected
[445:52:45.25] Juan Vasquez | Meta connected
[445:53:04.11] Stutter in tic - 0.105000 seconds
[445:53:06.13] Stutter in tic - 0.103000 seconds
[445:53:08.15] Stutter in tic - 0.104000 seconds
[445:53:12.18] Stutter in tic - 0.101000 seconds
[445:53:13.45] Juan Vasquez | Meta is ready
[445:53:17.70] Erode queue full!
[445:53:25.05] Motorcrosser: ?
[445:53:29.20] tommy bickles: lol
[445:53:30.32] Stutter in tic - 0.106000 seconds
[445:53:34.36] Stutter in tic - 0.109000 seconds
[445:53:48.46] Stutter in tic - 0.104000 seconds
[445:53:52.49] Stutter in tic - 0.102000 seconds
[445:54:06.61] Stutter in tic - 0.105000 seconds
[445:54:08.62] Stutter in tic - 0.105000 seconds
Here are my graphics in game:
https://gyazo.com/6e1f40fa0501bb10f8fc2b03f58f79b2
I didn't get these stutters on the old snapshots but once I switch over to the new latest snapshots I started stuttering. PLZ JLV
-
- Posts: 109
- Joined: Thu Sep 15, 2016 8:42 pm
- Team: MV Films
- Location: Kentucky
Re: 2019-04-21 snapshot
Here is the demo. http://www.mediafire.com/file/2v3986323 ... xdemo/filegarrettolver wrote:This was about 6 or so min of riding from the erode test going on tonight. Using "/reportstutter .10" My stutters are every 2ish seconds and is normally a small hit rather than a longer freeze. AMD Ryzen 5 1600, RX580 8gb and 16gb ddr4. Have demo as well if needed.
Re: 2019-04-21 snapshot
Thanks for that info! The "Erode queue full" message is a big hint. Does the stutter happen in a demo played back in "playback only" mode? If it's what I think is happening I'd expect it not to stutter in that situation.
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.
Sole Proprietor
jlv@mxsimulator.com
If you email, put "MX Simulator" in the subject to make sure it gets through my spam filter.
Re: 2019-04-21 snapshot
The stutter doesnt happen when in warmup mode and watching the demo, it happens when playing while in the racejlv wrote:Thanks for that info! The "Erode queue full" message is a big hint. Does the stutter happen in a demo played back in "playback only" mode? If it's what I think is happening I'd expect it not to stutter in that situation.
#1 All Time 250 RF NA Motocross Winner
#1 All Time 250 RF EU Winner
16th overall on the RF Gaming All Time Wins List
#1 All Time 250 RF EU Winner
16th overall on the RF Gaming All Time Wins List
Re: 2019-04-21 snapshot
DP It also happens when doing race against in demo mode.mx201 wrote:The stutter doesnt happen when in warmup mode and watching the demo, it happens when playing while in the racejlv wrote:Thanks for that info! The "Erode queue full" message is a big hint. Does the stutter happen in a demo played back in "playback only" mode? If it's what I think is happening I'd expect it not to stutter in that situation.
#1 All Time 250 RF NA Motocross Winner
#1 All Time 250 RF EU Winner
16th overall on the RF Gaming All Time Wins List
#1 All Time 250 RF EU Winner
16th overall on the RF Gaming All Time Wins List
Re: 2019-04-21 snapshot
Thanks again. That confirms my guess about what's causing it.mx201 wrote:DP It also happens when doing race against in demo mode.mx201 wrote:The stutter doesnt happen when in warmup mode and watching the demo, it happens when playing while in the racejlv wrote:Thanks for that info! The "Erode queue full" message is a big hint. Does the stutter happen in a demo played back in "playback only" mode? If it's what I think is happening I'd expect it not to stutter in that situation.
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.
Sole Proprietor
jlv@mxsimulator.com
If you email, put "MX Simulator" in the subject to make sure it gets through my spam filter.
Re: 2019-04-21 snapshot
Here's mine from that demo with a couple fps checks as well. In race against, I get the same 2 second tics. In playback only, I don't get any. If I use the volume up/down buttons on my keyboard in race against/online, it will also cause a huge tic.
Code: Select all
[388:13:32.52] Alex Effertz | Bucky Husky is ready
[388:13:32.52] Still waiting on: 908(27s)
[388:13:32.52] Jeremy Brady |Motographix Co connected
[388:13:32.52] Jeremy Brady |Motographix Co disconnected
[388:13:32.52] Still waiting on: 908(60s)
[388:13:32.52] snozzle:
[388:13:32.52] Still waiting on: 908(56s)
[388:13:32.52] Still waiting on: 908(50s)
[388:13:32.52] Trevor Spencer | JMC Motorsports is ready
[388:13:32.52] Setting working set range to 1073741824 - 2113929215
[388:13:32.52] Working set successfully updated
[388:13:32.52] Priority successfully set to high
[388:13:38.29] Bobby Desselle: alright boys can we not die on the start
[388:14:01.29] Bryan Kelly | Privateer connected
[388:15:07.02] Bryan Kelly | Privateer Timed out
[388:15:16.96] Foregrounded and locked
[388:15:16.96] WM_SIZE message 1920x1080
[388:15:16.97] LockSetForegroundWindow failed
[388:16:07.95] WM_SIZE message 0x0
[388:16:49.30] Foregrounded and locked
[388:16:49.30] WM_SIZE message 1920x1080
[388:16:49.31] LockSetForegroundWindow failed
[388:16:54.06] WM_SIZE message 0x0
[388:16:56.50] Foregrounded and locked
[388:16:56.51] WM_SIZE message 1920x1080
[388:16:56.51] LockSetForegroundWindow failed
[388:16:59.57] 128=25256 64=350 32=10 16=19 8=2 4=14 2=0 1=2
[388:17:01.74] WM_SIZE message 0x0
[388:17:04.08] Foregrounded and locked
[388:17:04.08] WM_SIZE message 1920x1080
[388:17:04.09] LockSetForegroundWindow failed
[388:17:18.90] Bryan Kelly | Privateer connected
[388:17:30.10] Isaiah Dickerson | MV Films disconnected
[388:17:38.75] Bryan Kelly | Privateer is ready
[388:17:41.76] Erode queue full!
[388:17:54.19] 128=5611 64=837 32=11 16=7 8=20 4=0 2=0 1=0
[388:18:28.03] WM_SIZE message 0x0
[388:18:29.55] Foregrounded and locked
[388:18:29.55] WM_SIZE message 1920x1080
[388:18:29.56] LockSetForegroundWindow failed
[388:18:36.45] WM_SIZE message 0x0
[388:18:38.60] Foregrounded and locked
[388:18:38.61] WM_SIZE message 1920x1080
[388:18:38.61] LockSetForegroundWindow failed
[388:18:39.86] Stutter threshold set to 0.100000
[388:18:43.80] Nathan James | looking for team : omg lol
[388:19:25.22] WM_SIZE message 0x0
[388:19:47.38] Foregrounded and locked
[388:19:47.39] WM_SIZE message 1920x1080
[388:19:47.40] LockSetForegroundWindow failed
[388:19:51.68] Stutter threshold set to 0.010000
[388:19:53.25] Stutter in tic - 0.062000 seconds
[388:19:53.27] Stutter in sound - 0.010000 seconds
[388:19:55.26] Stutter in tic - 0.066000 seconds
[388:19:57.29] Stutter in tic - 0.072000 seconds
[388:19:57.30] Stutter in sound - 0.010000 seconds
[388:19:59.30] Stutter in tic - 0.072000 seconds
[388:20:01.32] Stutter in tic - 0.079000 seconds
[388:20:01.34] Stutter in sound - 0.011000 seconds
[388:20:03.34] Stutter in tic - 0.083000 seconds
[388:20:03.36] Stutter in sound - 0.011000 seconds
[388:20:05.35] Stutter in tic - 0.072000 seconds
[388:20:05.37] Stutter in sound - 0.010000 seconds
[388:20:07.37] Stutter in tic - 0.075000 seconds
[388:20:07.38] Stutter in sound - 0.010000 seconds
[388:20:09.38] Stutter in tic - 0.069000 seconds
[388:20:11.39] Stutter in tic - 0.072000 seconds
[388:20:11.41] Stutter in sound - 0.010000 seconds
[388:20:13.41] Stutter in tic - 0.071000 seconds
[388:20:15.43] Stutter in tic - 0.069000 seconds
[388:20:17.44] Stutter in tic - 0.070000 seconds
[388:20:17.46] Stutter in sound - 0.010000 seconds
[388:20:19.45] Stutter in tic - 0.068000 seconds
[388:20:19.47] Stutter in sound - 0.010000 seconds
[388:20:20.35] Stutter in draw - 0.019000 seconds
[388:20:21.48] Stutter in tic - 0.071000 seconds
[388:20:23.49] Stutter in tic - 0.070000 seconds
[388:20:25.51] Stutter in tic - 0.081000 seconds
[388:20:25.53] Stutter in sound - 0.010000 seconds
[388:20:27.53] Stutter in tic - 0.078000 seconds
[388:20:29.55] Stutter in tic - 0.081000 seconds
[388:20:29.57] Stutter in sound - 0.011000 seconds
[388:20:30.78] Austin Jones connected
[388:20:30.88] Austin Jones disconnected
[388:20:31.57] Stutter in tic - 0.087000 seconds
[388:20:31.59] Stutter in sound - 0.012000 seconds
[388:20:33.58] Stutter in tic - 0.080000 seconds
[388:20:33.60] Stutter in sound - 0.011000 seconds
[388:20:40.47] WM_SIZE message 0x0
[388:20:40.49] Stutter in processmessage - 0.027000 seconds
[388:20:40.52] Stutter in update - 0.027000 seconds
[388:20:40.54] Stutter in processmessage - 0.018000 seconds
[388:20:47.09] Foregrounded and locked
[388:20:47.09] Stutter in processmessage - 0.014000 seconds
[388:20:47.10] WM_SIZE message 1920x1080
[388:20:47.11] LockSetForegroundWindow failed
[388:20:47.11] Stutter in getmessage - 0.010000 seconds
[388:20:47.19] Stutter in processmessage - 0.048000 seconds
[388:20:59.06] Deallocating bikes
[388:20:59.06] Finished deallocating bikes
[388:20:59.06] Deallocating track
[388:20:59.08] Finished deallocating track
[388:20:59.08] Freeing memory (1)
[388:20:59.18] Closing input devices
[388:20:59.18] Closing audio
[388:20:59.18] Writing config files
[388:20:59.19] Freeing memory (2)
[388:20:59.19] Freeing memory (3)
[388:20:59.19] Freeing file list
[388:20:59.19] Freeing memory (4)
[388:20:59.19] Deleting textures
[388:20:59.19] Deleting models
[388:20:59.20] Deleting OpenGL context
[388:20:59.21] Closing input devices
[388:20:59.21] Killing Controller(Xbox360WirelessReceiverforWindows)
[388:20:59.21] Timestamp adjustment was 2
[388:20:59.21] Destroying window
[388:20:59.25] Window shutdown complete
Re: 2019-04-21 snapshot
Is this better?
Windows: http://mxsimulator.com/snapshots/mx-2019-04-30-1498.exe
Linux: http://mxsimulator.com/snapshots/mxbin-2019-04-30-1498
Windows: http://mxsimulator.com/snapshots/mx-2019-04-30-1498.exe
Linux: http://mxsimulator.com/snapshots/mxbin-2019-04-30-1498
The volume keys are probably starting up a mixer app. I can't do anything about that.aeffertz wrote:Here's mine from that demo with a couple fps checks as well. In race against, I get the same 2 second tics. In playback only, I don't get any. If I use the volume up/down buttons on my keyboard in race against/online, it will also cause a huge tic.
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.
Sole Proprietor
jlv@mxsimulator.com
If you email, put "MX Simulator" in the subject to make sure it gets through my spam filter.
Re: 2019-04-21 snapshot
That fixed it for me! The volume buttons also now don't cause any sort of tics or spikes.jlv wrote:Is this better?
Windows: http://mxsimulator.com/snapshots/mx-2019-04-30-1498.exe
Linux: http://mxsimulator.com/snapshots/mxbin-2019-04-30-1498
The volume keys are probably starting up a mixer app. I can't do anything about that.aeffertz wrote:Here's mine from that demo with a couple fps checks as well. In race against, I get the same 2 second tics. In playback only, I don't get any. If I use the volume up/down buttons on my keyboard in race against/online, it will also cause a huge tic.
Re: 2019-04-21 snapshot
That fixed it for me when i did the playback race!, no stutters at alljlv wrote:Is this better?
Windows: http://mxsimulator.com/snapshots/mx-2019-04-30-1498.exe
Linux: http://mxsimulator.com/snapshots/mxbin-2019-04-30-1498
The volume keys are probably starting up a mixer app. I can't do anything about that.aeffertz wrote:Here's mine from that demo with a couple fps checks as well. In race against, I get the same 2 second tics. In playback only, I don't get any. If I use the volume up/down buttons on my keyboard in race against/online, it will also cause a huge tic.
#1 All Time 250 RF NA Motocross Winner
#1 All Time 250 RF EU Winner
16th overall on the RF Gaming All Time Wins List
#1 All Time 250 RF EU Winner
16th overall on the RF Gaming All Time Wins List