Intermittent issue of long delays during rf2 launch

I am having issues with rf2 launch times. The times I'm citing are based on the trace file created by rf2.

A typical 'good' launch takes 60-70 seconds to get to the main menu. But there are two spots that sometime take 90 - 120 second with no log statements.

Here are those lines in a 'normal' launch:

Code:

39.04s O_AppObj.cpp 2887: Options object creation successful
39.04s JNILog.cpp     33: LoadingStatus: not loading
  

and

Code:

39.06s tire_manager 1457: Non-existent tire brand ""
51.67s plrfile.cpp  1998: Attempting to save to C:\Program Files (x86)\Steam\steamapps\common\rFactor 2\UserData\player\player.TMP

The above launch took 67 seconds to get to "Entered OSMan::Exit()".

The following launch took 256 seconds to get there and here are those two sections:

Code:

19.18s O_AppObj.cpp 2887: Options object creation successful
 168.86s JNILog.cpp     33: LoadingStatus: not loading

and

Code:

168.89s tire_manager 1457: Non-existent tire brand ""
 240.51s plrfile.cpp  1998: Attempting to save to C:\Program Files (x86)\Steam\steamapps\common\rFactor 2\UserData\player\player.TMP

Anyone know what processes are happening between these statements that aren't getting logged?

Thanks,
Joel

 

If anyone runs into this issue, while it's unlikely that you have the same situation I do, here is what appears to have helped/fixed it.

I created a monitor agent that leverages the rf2 rest api to pull state info about the sim in order to automate some processes.

I'm hitting 9 endpoints of the API ~1hz which is typically not an issue, however, during launch it seems to intermittently trigger this temporary hung state.

By changing the approach to just hitting one until it succeeds and then starting on the others, it seems to have at least greatly reduced the chance of the delays if not getting rid of them completely.

 

Which version are you using?

 

Of rf2? Current production release on Steam.

Thanks,
Joel