What are your Gridmap load times?

I'm curious.

1. Open BeamNG.drive
2. Go to Freeroam and double-click on Gridmap
3. Wait for the level to load to the point where you can drive the truck.
4. Upload your beamng.log (located at Documents\BeamNG.drive\beamng.log)
5. Feel free to brag about your hardware specs - only after you've uploaded a log or at least correct timestamps.

For the purposes of this excercise I consider the "load time" to be the time between two specific time stamps: because "loading scren shown": and the final Sent bindings to everybody (in xxms) because "keys app" (note that "send settings to everybody" happens multiple times and the (in xxms) part is displaying a variable so it can change. The easy way to find this entry is to go to the bottom of the log and search "Up" for "keys app".)

Here is an example where we have a driveable truck in approximately 8s using a Samsung 840 Evo 1TB :

Code:

 12.51595|I|t3dlua.|Sent bindings to everybody (in 31ms) because "loading scren shown": { keyboard0 = 81, mouse0 = 2, xinput0 = 19}
 20.28462|I|t3dlua.|Sent bindings to everybody (in 31ms) because "keys app": { keyboard0 = 81, mouse0 = 2, xinput0 = 19}

 

Code:

  8.39271|I|t3dlua.|Sent bindings to everybody (in 15ms) because "loading scren shown": { keyboard0 = 82, mouse0 = 2}
17.86459|I|t3dlua.|Sent bindings to everybody (in 15ms) because "keys app": { keyboard0 = 82, mouse0 = 2}

9.47188 seconds.
Old 80GB Seagate HDD.

 

Thanks, as you may have guessed HDD load times is really what I wanted to know about. <10s is impressive w/ an old 80GB HDD (to me at least). Just to be sure, that's the first "sent bindings to everybody" after the "Mission loaded" line, right?

 

I just did what you said. I just searched up from the end of the log for "keys app".
Here's a second run, this includes all "keys app" messages:

Code:

  8.74081|I|t3dlua.|Sent bindings to everybody (in 31ms) because "loading scren shown": { keyboard0 = 82, mouse0 = 2}
 16.90532|I|t3dlua.|Sent bindings to everybody (in 15ms) because "keys app": { keyboard0 = 82, mouse0 = 2}
 17.04394|I|t3dlua.|Sent bindings to everybody (in 31ms) because "keys app": { keyboard0 = 82, mouse0 = 2}

8.30313 seconds.

I looked up what model the HDD is. It's a Seagate ST380815AS.

 

Thanks, I know that wasn't what I posted in the OP. Just wanted to make sure we were on the same page.

This should have come as no surprise to me, oops. I'm (now) guessing that the game is CPU bound in creating the level. Hopefully someone with some slower components will chime in.

 

Code:

11.98249|I|t3dlua.|Sent bindings to everybody (in 31ms) because "loading scren shown": { keyboard0 = 82, mouse0 = 2, xinput0 = 19}
19.96425|I|t3dlua.|Sent bindings to everybody (in 15ms) because "keys app": { keyboard0 = 82, mouse0 = 2, xinput0 = 19}
Edit:
 17.93731|I|t3dlua.|Sent bindings to everybody (in 32ms) because "player #0 switched from <none> to pickup": { keyboard0 = 82, mouse0 = 2, xinput0 = 19}

7.982 seconds on Corsair MX100 512GB.

Edit: that would change the time to 5.955 seconds