DOCS The Server Admin Handbook thread

Thanks Minolin as always.

I wonder what we get if we choose zolder_2019 or zandvoort (signifying 2018 version)

Do we somehow get warped to an alternate dimension, like below?

 

@Minolin does endurance mode for qual works now? Maybe, can you give an example for correct server config?

 

@Minolin It appears that if you use the postQualySeconds and postRaceSeconds . you can no longer use the admin /next .. we set at ten minutes and would skip if all drivers are ready before the 10 minute period. By design?

Also . should we be using a newer server exe.. ie deleting and verifying to get a newer version?

 

I'd noticed admin commands not working, but hadn't pinpointed to postQualySeconds and postRaceSeconds - just from previous to current versions it's stopped working...
Glad to hear it's not just me.

 

It does work, but I had to spam /next cause even the postqualyseconds (and race) are treated as a session as well as every other instance where things are moved "forward". From free practice to free practice its at least 20 "/next" commands

 

would at least be easier if there was the possibility to use the up-arrow to repeat the earlier command, or that the chat line stays active after sending a message so you can just copy/paste spam

and while i'm at it: i noticed that in the scenario where I am streaming, i cannot enter the admin password on the server. maybe there is a way to automatically transform anything behind the /admin command to: ******

 

Code:

{
   "preRaceWaitingTimeSeconds":90,
   "sessionOverTimeSeconds":140,
   "postQualySeconds":90,
   "postRaceSeconds":120, 
}

Yesterday and the day before, we used the above "event.json" on one of our servers and I try several times the "/next" command without problems.

 

Im fairly sure what is happening after you use skip or even restart command in a qualy or race session, this doesnt take effect until after the postQualy and postRace seconds have expired. If you use skip command in a practice session there is no big delay and thats the only session without these delays.

"postQualySeconds": 30,
"postRaceSeconds": 110,
"sessionOverTimeSeconds": 110,

Not sure if it also uses session overtime but if you could make the admin command bypass these then I think this should work out the same as in current practice sessions.

 

@Minolin could you take a look at single session qualy or practice servers being set to day 3 always starting on a green track.

Here is the session setup I am using.
{
"track": "zolder_2019",
"eventType": "E_6h",
"preRaceWaitingTimeSeconds": 100,
"postQualySeconds": 30,
"postRaceSeconds": 110,
"sessionOverTimeSeconds": 110,
"ambientTemp": 22,
"cloudLevel": 0.05000000149011612,
"rain": 0.0,
"weatherRandomness": 0,
"sessions": [
{
"hourOfDay": 15,
"dayOfWeekend": 3,
"timeMultiplier": 1,
"sessionType": "Q",
"sessionDurationMinutes": 30
}
],
"configVersion": 1
}

This is for a league qualifying server where I want static conditions and optimum track. This never has worked for me but if I add an extra session of 1 min practice then skip to qualy I can get optimal grip for the qualy session.

Here is what the log says at the start of the session.

Code:

20028: No drivers around, resetting session
20028: Resetting race weekend
20028: Empty Leaderboard - will skip the json dump
20028: Resetting weekend to friday night
20028: ==ERR: Track services ERROR target time is more than 2 days 226800, is 0
20028: SessionManager::randomizeGreenFlagTriggers: s:0.970972 e:0.000000 r:0.976583
20028: Detected sessionPhase <session> -> <waiting for drivers> (Qualifying)

I don't know if the track services ERROR is the issue but no idea what that means. Is there a way to setup a server with static optimum grip levels? also can time scale be 0. If it starts optimum will the track still keep gripping up so we should keep a short session to avoid it getting faster if more join in and run lots of laps.

 

I found adding an extra practice session of 1 minute ahead of this gives me the optimum track next session.

Code:

{
    "track": "zolder_2019",
    "eventType": "E_6h",
    "preRaceWaitingTimeSeconds": 10,
    "postQualySeconds": 5,
    "postRaceSeconds": 5,
    "sessionOverTimeSeconds": 100,
    "ambientTemp": 22,
    "cloudLevel": 0.05000000149011612,
    "rain": 0.0,
    "weatherRandomness": -1,
    "sessions": [
        {
            "hourOfDay": 11,
            "dayOfWeekend": 2,
            "timeMultiplier": -1,
            "sessionType": "P",
            "sessionDurationMinutes": 1
        },
        {
            "hourOfDay": 15,
            "dayOfWeekend": 3,
            "timeMultiplier": -1,
            "sessionType": "Q",
            "sessionDurationMinutes": 30
         }
    ],
    "configVersion": 1
}

Also timeMultiplier -1 does keep time static which is what I wanted. WeatherRandomness -1 seems to work too.

Not sure why a single qualy session always starts out green still. That is a workaround, it just means people that join first need to skip the practice or wait a minute.

Ambient temp is also starting at 26c on this session even with dynamic off and 22 set in the config.

 

Hi,

Im trying to setup ACC server, here is my session order:
FP, Q1, Q2, R1, R2

But for both racers the grid is ordered by results from Q1, results from Q2 are useless. Do you know how to fix this? Is this a known issue?

Regards,
SF

 

It's a known issue.

 

Current workaround is use FP Q1 R1 Q2 R2 this is working correctly in 1.1.2

 

Hello, could you upload the .json to confirm how you have it?

 

this is not from our league server but I found you can even stack 3 races and I have had no issues with it,

Code:

{
    "track": "zolder_2019",
    "eventType": "E_6h",
    "preRaceWaitingTimeSeconds": 90,
    "postQualySeconds": 30,
    "postRaceSeconds": 100,
    "sessionOverTimeSeconds": 100,
    "ambientTemp": 22,
    "cloudLevel": 0.050000000149011612,
    "rain": 0.15,
    "weatherRandomness": 3,
    "sessions": [
        {
            "hourOfDay": 16,
            "dayOfWeekend": 1,
            "timeMultiplier": 4,
            "sessionType": P",
            "sessionDurationMinutes": 20
        },
        {
[LEFT][FONT=Georgia][COLOR=rgb(20, 20, 20)]            "hourOfDay": 8,
            "dayOfWeekend": 2,
            "timeMultiplier": 4,
            "sessionType": "Q",
            "sessionDurationMinutes": 10
        },
        {[/COLOR][/FONT][/LEFT]
            "hourOfDay": 10,
            "dayOfWeekend": 2,
            "timeMultiplier": 4,
            "sessionType": "R",
            "sessionDurationMinutes": 15
        },
        {
            "hourOfDay": 15,
            "dayOfWeekend": 2,
            "timeMultiplier": 4,
            "sessionType": "Q",
            "sessionDurationMinutes": 10
        },
        {
            "hourOfDay": 16,
            "dayOfWeekend": 2,
            "timeMultiplier": 4,
            "sessionType": "R",
            "sessionDurationMinutes": 15
        },
        {
            "hourOfDay": 20,
            "dayOfWeekend": 3,
            "timeMultiplier": 4,
            "sessionType": "Q",
            "sessionDurationMinutes": 10
        },
        {
            "hourOfDay": 23,
            "dayOfWeekend": 3,
            "timeMultiplier": 4,
            "sessionType": "R",
            "sessionDurationMinutes": 15
        }
    ],
    "configVersion": 1
}

The server will post this error.

Code:

0: ==ERR: Detected Q after R(1)
0: ==ERR: Detected Q after R(2)
0: SessionManager::randomizeGreenFlagTriggers: s:0.890000 e:0.950000 r:0.901380
0: Track zolder_2019 was set and updated
0: Event changed
0: ==ERR: Detected Q after R(1)
0: ==ERR: Detected Q after R(2)

But it has worked without issues on Open and private servers for me in 1.1.x builds. PQQRR now just uses Q1 for the grid of both races though that worked in earlier versions.

 

I remember being able to run the PQRQR (but not the PQQRR) well before patch 1.1.
I would have to try with PQRPQR when I have time.

 

Has ACC allowed to add ballast to player yet?

 

Hi everyone, I updated the config in my server with PQRQR but the log show this:

Code:

0: Joining during race is allowed
0: maxCarSlots 30 exceeds the allowed slots by Rating requirement (26). Add Track Medal and Safety Rating Requirements to gain up to 30 slots (3 TM + 70 SA)
0: ==ERR: Detected Q after R(1)
0: SessionManager::randomizeGreenFlagTriggers: s:0.890000 e:0.950000 r:0.920050
0: Track nurburgring_2019 was set and updated
0: Event changed
0: ==ERR: Detected Q after R(1)
0: SessionManager::randomizeGreenFlagTriggers: s:0.890000 e:0.950000 r:0.891793
0: Significant change detected, updating lobby (1|1)
0: maxCarSlots 30 exceeds the allowed slots by Rating requirement (26). Add Track Medal and Safety Rating Requirements to gain up to 30 slots (3 TM + 70 SA)
0: Resetting weekend to friday night
0: SessionManager::randomizeGreenFlagTriggers: s:0.890000 e:0.950000 r:0.906546

Spoiler: event.json

{
"track": "nurburgring_2019",
"eventType": "SP",
"preRaceWaitingTimeSeconds": 120,
"postQualySeconds": 30,
"postRaceSeconds": 100,
"sessionOverTimeSeconds": 120,
"ambientTemp": 10,
"trackTemp": 16,
"cloudLevel": 0.8,
"rain": 0.0,
"weatherRandomness": 2,
"sessions": [

{
"hourOfDay": 14,
"dayOfWeekend": 1,
"timeMultiplier": 4,
"sessionType": "P",
"sessionDurationMinutes": 30
},

{
"hourOfDay": 9,
"dayOfWeekend": 2,
"timeMultiplier": 4,
"sessionType": "Q",
"sessionDurationMinutes": 15
},

{
"hourOfDay": 14,
"dayOfWeekend": 2,
"timeMultiplier": 4,
"sessionType": "R",
"sessionDurationMinutes": 25
},
{
"hourOfDay": 10,
"dayOfWeekend": 3,
"timeMultiplier": 4,
"sessionType": "Q",
"sessionDurationMinutes": 15
},

{
"hourOfDay": 14,
"dayOfWeekend": 3,
"timeMultiplier": 4,
"sessionType": "R",
"sessionDurationMinutes": 45
}
],
"configVersion": 1
}

 

Guys a question.
How to set up track grip? (green, fast, and others)
I can't set it on the server
Thanks a lot