Welcome, Guest
Username: Password: Remember me

TOPIC: Multiplayer server configuration (for admins)

Multiplayer server configuration (for admins) 04 May 2019 15:17 #337321

  • sps
  • sps's Avatar
  • OFFLINE
  • alter Hase
  • Sascha Sullivan
  • Posts: 949
Offizielle Posts von KS Dev. Minolin zum Thema Server Konfiguration, inkl. Ratings, dynamisches Wetter

- configuration.json
- event.json
- settings.json
www.assettocorsa.net/forum/index.php?thr...server-admins.54830/

Beispiel:
- TrackMedalsRequirement goes from 0 to 3 and will ensure that drivers have the corresponding track medal unlocked (on the track you are offering on the server)
- the safetyRatingRequirement goes from -1 (disabled) to 99
- weatherRandomness is 0 for disabled, 1 (or 2) for realistic weather - up to 10 for chaos and insanity





- Dynamic weather
- Multiplayer Rating requirements
www.assettocorsa.net/forum/index.php?thr...s-event-notes.55894/














With 0.6, the configuration of ACC multiplayer servers will change quite a bit. Let us go through it.
Unlike before, the configuration is split to 3 different json files.

configuration.json
Code:
{
"udpPort": 9600,
"tcpPort": 9600,
"maxClients": 30,
"configVersion": 1
}
Is the very technical description of a server, and will most likely never change. The reason for this file is that this may be in the responsibility of a server hoster like Rackservice, and it would be a good idea to let users not even edit this. As customer, this would mean you find this file readonly in your ftp folder (or similar).

Content wise just make sure the ports are unique on the system, and to have inbound firewall rules.

settings.json
Code:
{
"serverName": "ACC Server with a cool name",
"password": "1234",
"adminPassword": "4321",
"trackMedalsRequirement": 3,
"safetyRatingRequirement": -1,
"configVersion": 1
}
The settings contain specific things you will most likely want to stick to (once you found a good setup).
You already see server name and the passwords, expect this to be extended to spectator settings, rating requirements and so on.

event.json
Code:
{
"track": "zolder",
"eventType": "E_3h",
"preRaceWaitingTimeSeconds": 15,
"sessionOverTimeSeconds": 120,
"ambientTemp": 26,
"trackTemp": 30,
"cloudLevel": 0.3,
"rain": 0.0,
"weatherRandomness": 1,
"configVersion": 1,
"sessions": [
{
"hourOfDay": 9,
"dayOfWeekend": 1,
"timeMultiplier": 1,
"sessionType": "P",
"sessionDurationMinutes": 7
},
{
"hourOfDay": 18,
"dayOfWeekend": 1,
"timeMultiplier": 1,
"sessionType": "Q",
"sessionDurationMinutes": 10
},
{
"hourOfDay": 14,
"dayOfWeekend": 2,
"timeMultiplier": 1,
"sessionType": "R",
"sessionDurationMinutes": 10
}
]
}
The last file contains the plain event., reduced to what you actually want to configure. The file also is a standalone description of a race weekend - so you can easily flip this in and out without the need to manage server name / ports.

Remarks
You will notice that we for now stripped down the configuration as much as possible. With the time, we will again add the interesting options in terms of assists, realism, gameplay and track/condition options. But for this release, the quest is to make sure the multiplayer works fine.
Handing out too many options will bring us many reports like "no grip in MP", where we would waste lots of time to find out that this is possibly only a certain condition setting - or the user is used to SC but it was turned off on that server.

Also we will as usual deliver a default configuration and an up-to-date readme.txt with explicit documentation.

I will try to keep this topic updated on further changes. Feedback, questions and requests here are appreciated, but it has to be totally focused on the way to configure servers (that means no talk about possible future features, no troubleshooting).

==========
0.7
Remarks
- please make sure you have fully read and understood this post: www.assettocorsa.net/forum/...rating-mul...s-event-notes.55894/
- the trackMedalsRequirement goes from 0 to 3 and will ensure that drivers have the corresponding track medal unlocked (on the track you are offering on the server)
- the safetyRatingRequirement goes from -1 (disabled) to 99
- weatherRandomness is 0 for disabled, 1 (or 2) for realistic weather - up to 10 for chaos and insanity

Additionally, we have the first admin commands available. You elevate to admin once by chatting
/admin 4321 (pw according to "adminPassword" in settings.json)

then you can use
/next
/kick <racenumber>
/ban <racenumber>

Kick will prevent the victim to join again during the rest of this race weekend; the ban will be as long as the server is up.
No, there won't be a perma-ban file, that's what an integrated SA system is for. Make sure to use it.

There is also a /restart, but this isn't safe to use in certain conditions - make sure to use this only during the real session time, where the time is ticking down.
Last Edit: 04 May 2019 15:25 by sps.
The administrator has disabled public write access.

Multiplayer server configuration (for admins) 04 May 2019 15:46 #337322

  • sps
  • sps's Avatar
  • OFFLINE
  • alter Hase
  • Sascha Sullivan
  • Posts: 949
Tracknamen bzw. deren Schreibweise:

misano
nurburgring
paul_ricard
hungaroring
zolder
Monza
Last Edit: 04 May 2019 15:47 by sps.
The administrator has disabled public write access.

Multiplayer server configuration (for admins) 27 May 2019 19:01 #337581

  • sps
  • sps's Avatar
  • OFFLINE
  • alter Hase
  • Sascha Sullivan
  • Posts: 949
Dieser Beitrag passt überall und nirgendwo, aber die wichtigsten Features betreffen die Adminspielzeuge, denke ich?!

ACC Blog Multiplayer & Rating - 1.0

www.assettocorsa.net/forum/index.php?thr...er-rating-1-0.57088/

1) Competition Rating & Competition Servers
2) Competition Rating unlocks with Racecraft Rating
3) Quick Access Multiplayer Menu
4) Car limits by server restrictions
5) Server defined entry lists
6) (Multiplayer) driver swaps
7) Spectator mode
8) Race director commands
9) Return of the broadcasting API
10) Preparation phase countdown in Menu


TL;DR;
1) Competition Rating is now active, and introduce a new "Competition Server" type. Given quite high SA requirements, you can join those servers to compete with other users in more serious races.
2) The Competition Rating (CP) now unlocks with Racecraft Rating (RC), no need to grind 50 RC in order to compete in the new Competition servers.
3) New "Quick Access Multiplayer Menu" - Quickjoin into Public Multiplayer, enter the Competiton servers - or advance to the old server list.
4) Max server capacity changed: It now linearily depends on rating requirements set up for this server. 45 SA equals 24 cars, 70+ SA can run 30 cars.
5) Entry list options for server admins and leagues.
6) Teams and corresponding driver swaps can now be configured by server admins.
7) Specator mode is now active: Server admins can setup spectatorSlots and the password to use, which joins a server without car.
8) First Race director commands.
9) Broadcasting API is active again. www.assettocorsa.net/forum/index.php?thr...-users-thread.53828/
10) Better information about session and countdown during race preparation phase.
Last Edit: 27 May 2019 20:24 by sps.
The administrator has disabled public write access.

Multiplayer server configuration (for admins) 02 Jun 2019 10:52 #337646

  • sps
  • sps's Avatar
  • OFFLINE
  • alter Hase
  • Sascha Sullivan
  • Posts: 949
"Public beta" 1.0.1 - Build 3877818
About Hotfix 1 and the "public beta" branch



"We are testing a candidate build that will especially solve the crash occuring in Multiplayer. The full test cycle takes longer, as we also need to verify all the other parts. Also we want to keep the public v1.0 as it is, to not interfere with the SRO E-Sport event currently undergoing at Paul Ricard. On the other hand, we want you to participate in this fix as early as possible as soon as possible and offer you a more stable multi. We decided to release this first Hotfix candidate on a "public beta" branch."

Enter the code for the public beta: accBetaBranch

www.assettocorsa.net/forum/index.php?thr....57636/#post-1056762
The administrator has disabled public write access.

Multiplayer server configuration (for admins) 10 Jun 2019 11:00 #337732

  • sps
  • sps's Avatar
  • OFFLINE
  • alter Hase
  • Sascha Sullivan
  • Posts: 949
Last Edit: 10 Jun 2019 11:01 by sps.
The administrator has disabled public write access.

Multiplayer server configuration (for admins) 28 May 2020 14:21 #340826

  • sps
  • sps's Avatar
  • OFFLINE
  • alter Hase
  • Sascha Sullivan
  • Posts: 949
Ein interessantes Tool zur Rennauswertung:

www.assettocorsa.net/forum/index.php?threads/acctracker.64306/
The administrator has disabled public write access.

Multiplayer server configuration (for admins) 09 Jun 2020 20:24 #341030

  • sps
  • sps's Avatar
  • OFFLINE
  • alter Hase
  • Sascha Sullivan
  • Posts: 949
Vielleicht ist diese live-timing platform was?

www.assettocorsa.net/forum/index.php?thr...lable-for-acc.64812/

pitwall.live


upload_2020-6-8_20-41-50.jpg
Last Edit: 09 Jun 2020 20:26 by sps.
The administrator has disabled public write access.

Multiplayer server configuration (for admins) 11 Jun 2020 09:29 #341047

  • Meraculix
  • Meraculix's Avatar
  • OFFLINE
  • Administrator
  • ACC / R3E
  • Posts: 2562
ja das sieht gut aus B)
was jetzt noch klasse wäre, wenn man da noch infos zum eigenen bzw gemeinsamen auto bekommen würde wie z.b. sprit verbrauch, ( runde, gesamt, aktuell, verbrauch im schnitt ) und / oder stint länge und aktuelle fahrzeit des fahrers wie oft man schon an der box war, wie oft man reifen gewechselt hat usw.

könnten wir dann für die kommenden langstreckenrennen nutzen :whistle:
Ihr habt eine lange anreise zum Simulantentreffen ??

12500km mit 32,5h Reisezeit, von La Paz( bolivien) direkt zum Ring !

Ich war da, budentreffen 2015 !
The administrator has disabled public write access.

Multiplayer server configuration (for admins) 11 Jun 2020 11:20 #341050

  • sps
  • sps's Avatar
  • OFFLINE
  • alter Hase
  • Sascha Sullivan
  • Posts: 949
Erstmal implementieren und testen wäre ein Anfang...
The administrator has disabled public write access.

Multiplayer server configuration (for admins) 18 Jan 2021 10:32 #343033

  • sps
  • sps's Avatar
  • OFFLINE
  • alter Hase
  • Sascha Sullivan
  • Posts: 949
Thema Wetter, dynamisch aber ohne Gewitter und Platzregen:



1: "anything can happen" with high chance of variation:
"cloudLevel": 0.2-0.35,
"rain": 0.1-0.2,
"weatherRandomness": 5-7,
"simracerWeatherConditions": 1,

2: conservative variation with potential rain
"cloudLevel": 0.2-0.5,
"rain": 0.05-0.1,
"weatherRandomness": 4,
"simracerWeatherConditions": 1,

3: guaranteed overcast (no rain, only changing clouds)
"cloudLevel": 0.6-1.0,
"rain": 0.0,
"weatherRandomness": 2-3,

4: guaranteed sunny (only minor cloud changes)
"cloudLevel": 0.0-0.4,
"rain": 0.0,
"weatherRandomness": 2-3,

5: overcast with occasional light-medium rain
"cloudLevel": 0.6-1.0,
"rain": 0.0,
"weatherRandomness": 4-7,
"simracerWeatherConditions": 1,

6: guaranteed light-medium rain all weekend
"cloudLevel": 0.6-0.8,
"rain": 0.1-0.2,
"weatherRandomness": 1-3,
("simracerWeatherConditions": 1,) - optional

7: guaranteed medium-heavy rain
"cloudLevel": 0.6-1.0,
"rain": 0.45-0.6,
"weatherRandomness": 3,
("simracerWeatherConditions": 1,) - optional

Your weekend setup, the proximity (and continuity) of sessions inside the weekend will still be a major factor. Also, the highest randomness settings (5-7) do what they advertise, being highly random and thus less predictable.


Ambient temp sets the average daily mean temperature and the dynamic track calculation does the rest based on cloud level and time of day.
Also, the minimum daily mean temperature you can set is 11. This can go down to 2-5 during the night depending on cloud level (more cloud, warmer night).

I would generally recommmend setting the sessions to Saturday (day 2) when trying to achieve variable weather, because with high randomness you can hit a weather drift that moves the cycle away from the baseline by the 3rd day, and it becomes more unpredictable than you'd like.
I would recommend setting FP on day 1 and Q and R one after the other on day 2. With this you get an idea about general weather movement (based on how FP might be different from Q), and then Q and R should be pretty linear to not make the race conditions a total surprise. Still, with anything above 4 randomness, I don't recommend Sunday sessions.

These tips combined with the simracer conditions should produce good results.
Siehe Anhang




www.assettocorsa.net/forum/index.php?thr...page-51#post-1179422
&
www.assettocorsa.net/forum/index.php?thr...page-28#post-1173096

+ Download WetterMatrix Excel-Tabelle
aus diesem Thread:
www.assettocorsa.net/forum/index.php?thr...ndbook-thread.58245/



W.jpg
Attachments:
  • Attachment This attachment is hidden for guests. Please log in or register to see it.
  • Attachment This attachment is hidden for guests. Please log in or register to see it.
Last Edit: 18 Jan 2021 10:35 by sps.
The administrator has disabled public write access.
Time to create page: 0.054 seconds
Go to top