If the component folder cannot be found and a previous steam command returned not 0, this indicates that the steam download failed.
steamcmd does not handle large (> 1GB) workshop items well. They tend to abort after some time.
You see such an message as the last message in the logfile, no subsequent lines visible
Aug 03 12:03:56 reciever.py:366 INFO : We did not manage to extract any vehicle definitions. Check the used version.
Use a different version!
Under some circumstances, the key get's invalidated. This is an ongoing issue and is being montiored. Until a fix is available, follow following steps.
To make sure the key get's updated, select “clear” from the server key field.
Save the server, without a pending action.
Open the server again and refresh until the server key is present again. Click on the link to download the key file and follow the instructions on https://forum.studio-397.com/index.php?threads/how-to-hosting-with-steamcmd-and-paid-content.57209/.
Upload the unlock file to the “Server unlock key” field. APX will collect the key. If the unlock is successfull, the field will be cleared.
If this fails, repeat the steps, but on the step clearing the server key select the action “start”.
Check the bandwith settings of the event.
This issue often comes with a missing key.
Background: The initial setup downloads the reciever from GitHub and the server froms steam. Both download can fail at some points. If downloads are working, the server will start for a brief moment to create all the folders and files within UserData/. After that the server is being killed. It can happen that the server does not start in time, causing the server to be installed without having a UserData folder. On deployment, when APX tries to utilize that file to add the wanted values, it will fail.
This can have following issues:
You have following options:
If your installation is stuck at this step, this means the download failed. Check your network connection and if your installed version is still supported.
Something went wrong while creating the folders, downloading the server of steamcmd. Consider trying the steps from this guide.
If the grip is not used and you see following message in the log file, check the definition of thet rack within the component. There might be a track layout required wich is not included within the component.
No properties could be extracted from the track. Make sure you are using a correct layout description for this component.
If not, you may be affected by this issue, which is an ongoing task https://github.com/apx-simracing/issues/issues/45
Check for following message within your logfile of the server:
Aug 22 10:44:06 steam.py:121 INFO : Found 0 files as vehicle definition in C:\Users\chm\AppData\Local\Temp\tmpv88hde1l
Check your logfile for following messages:
Aug 28 18:14:47 steam.py:163 INFO : Found 0 files in C:\Users\chm\Documents\rfactor-server\steamcmd\steamapps\workshop\content\365960\1453463528 Aug 28 18:14:53 reciever.py:366 INFO : [WinError 3] Das System kann den angegebenen Pfad nicht finden: 'C:\\Users\\chm\\Documents\\rfactor-server\\server\\Installed\\Vehicles\\Radical_SR3-RSX_2017'
This can have several issues:
You will see such a message in your logfile:
Sep 24 19:49:13 deploy.py:859 INFO : We don't found the desired layout in the gdb layout list. Falling back to old method. Desired layout name is Blackwood GP, track list is ['Blackwood GP (classic) // shows up in rFactor2 as the subfolder.', 'Blackwood GP [reverse] (classic) // shows up in rFactor2 as the subfolder.', 'Blackwood GP // shows up in rFactor2 as the subfolder.']
Check that the desired layout matches the Key “EventName” from the GDB file.
This _should_ be the name of the layout displayed in the game. This must match EXACTLY.
This is a bug https://github.com/apx-simracing/issues/issues/48 as the server overwrites the ini file controlling the track filter
You might see following message in the log file:
We will choose the first VEH file as a template: xy
You need to specifiy a suitable class in the entry page. The field name is “base class”. Otherwise the first VEH file from the mod will be used.
If everything is working, you will see this message:
We will choose the VEH file as a template: XYZ.veh as it suits the BaseClass string "example": example class
If you have a global Python installed and you see APX commands to fail, use following workaround:
Add the full path to the “cli” to the file python39._pth:
python39.zip . reciever import site C:\path\to\the\cli\folder