+- Sim Racing System (https://www.simracingsystem.com)
+-- Forum: Sim Racing System (https://www.simracingsystem.com/forumdisplay.php?fid=1)
+--- Forum: Bugs & Troubleshooting (https://www.simracingsystem.com/forumdisplay.php?fid=3)
+--- Thread: Could not joint race, lods.ini for different car was missing? (/showthread.php?tid=6763)
Could not joint race, lods.ini for different car was missing? - Stefan Bader - 08-26-2019
Hi,
couldn't join the tatuus Spa race because the lods.ini for "austin_mini_cooper" was missing.
See picture attached.
Creating a singleplayer-event (practice, hotlap, etc.) with the tatuus in spa worked fine.
Whilst i couldn't connect i quickly downloaded both the "Austin Mini Cooper S Fia App.K Spec 1.0" and "BMW Mini JCW F56 V2.0".
I still couldn't join
.edit: weirdly enough: joining via the server browser and manually search for the simracingsystem server worked... (1 minute before qualy was over)
RE: Could not joint race, lods.ini for different car was missing? - Fr.dr.k S.d.rst.dt - 08-27-2019
solutions:
1. download the mini cooper
2. delete launcher data
3. join from the server browser, search "simracingsystem" and join.
RE: Could not joint race, lods.ini for different car was missing? - Stefan Bader - 08-28-2019
@Fredrik: as i wrote in my initial post: i already downloaded the mini cooper mod
Just tried joining the tatuus spa event and it worked this time.
Maybe i just needed to restart content manager after installing the mini cooper mod.
RE: Could not joint race, lods.ini for different car was missing? - Russell Sobie - 08-28-2019
I always start CM before every race. I get this error probably 50% of the time when trying to join using the Join button on the registration page (if I can even see it without refreshing the page).
Just skip down to the bottom of Fredrik's list and join using the Online menu. That works 100% of the time, first click.
RE: Could not joint race, lods.ini for different car was missing? - Borre Verdoes - 09-01-2019
I've had this error a few times and everytime the error was gone after restarting Content Manager.