Modified core.ini

U

User 3639

In two leagues it is already used new core.ini. Whether it is planned GNL transition yg new core.ini? C new characteristics it is possible to conduct more dense struggle?
Here endurances from other leagues:
FAQ:
Why change netcode settings?
Remember racing offline, hitting an AI and they're solid as a brick? That's what it will be like racing online with these new settings if you hit another car - it still doesn't stop some things "operator behind the wheel" related but it does improve door to door and bumper to bumper contact - the car position is updated to all players at twice the datarate of normal and so it's easier to go side by side in a corner with someone without warping into them. The new code allows for closer racing, it doesn't give you a license to go banging and beating on the guy or girl in front, the same physics still apply so most contact will still result in at least 1 car crashing.

Is it mandatory?
Yes, not making the change places additional strain on the server which can compromise everybody elses connections.

Why fix what isn't broke?
To be frank, the netcode is broke, this game was designed to run on 56k modems NOT broadband connections, there a way too many cautions caused by bumps that would with this code result in no accident, there is a known fix, so why shouldn't we at least try it? If you have raced at ASCORS then you know why we're trying this.

What about racing on other servers?
You will likely need to change the values back, the only known servers running this code are ASCORS and V8Thunder.

I made the changes, entered the server, clicked drive and was disconnected - why?
You or the updater hasn't applied the changes correctly, please check the path is correct for the updater or double check your core.ini file and make sure the last line has a value of 0 if it has a value of 1, then this is what causes you to be disconnected, regardless of whether the other values are correct, if the last line is incorrect you game is limited to a 56k speed connection to the server and this is why you got disconnected.

If you experience this, DO NOT continue to connect, click drive, disco, connect, click drive etc. etc. this puts massive strain on the server and compromises everybody elses' connection, if you are disconnected once after clicking drive, rejoin the server and contact the in-race admin for assistance.
Hello,

For at least the ASCORS Pre-Season Testing we are running a few new settings to try things out, all in the interest of improving the racing here. What this new ini change does is, remember how whenever you raced offline, the AI cars were a solid brick? Well with these changes turned on, every car you race here, will feel just like an AI car when you hit it, quite incredible.

Basically NR03 was designed to run for 56k, that's why we have all those netcode contacts and wrecks from that. This basically uses some more bandwidth, and provides for some more stable racing. We had about 22 people try it out last night, and we had everyone hooked up with no issues.

Before you do anything BACK UP YOUR CORE.INI, AND PUT IT SOMEWHERE OUT OF THE WAY, SO YOU DO NOT GET THE INI'S MIXED UP. You can backup your core.ini in several ways, you can copy and paste one onto your desktop, you can do whatever you want, just make sure you have two copies of it. One for the changes, and one with your original core.ini settings.

With one of your core.ini's, you will change the following lines:

net_lan_client_send_every=1
net_lan_server_send_every=1
net_use_mdm_bandwidth_for_tcp_ip=0

(Just a note, if something goes wrong with your backup or something: Those lines you changed to 1, used to be 2).

* One of the reasons I said to backup your original ini, if you race ANYWHERE, and I mean anywhere else, you will have to switch back to the original core.ini, otherwise it will not let you race with your different settings. This shouldn't be too big of an issue if you stay organized, it takes 2 seconds to swap a file in and out.
 
U

User 490

Sounds interesting, but I'm even more interested in what Volker has to say about that. ;)
And is there a replay available, where all drivers changed this settings?
 
U

User 490

oh_rly.jpg
 
U

User 312

The 3rd setting is already recommended to be set to 0 by VR (see all cars on replay instead of like 12 in front)

Without knowing much about it, the "....server...." setting, by name it refers to running a server, so it should be switched to 1 on the VR Servers.

The "....client....." setting would probably affect everyones computers behaviour, probably just sending more packets, sounds pretty logical to set that to 1 on everyones machine.
 
U

User 768

The 3rd setting is already recommended to be set to 0 by VR (see all cars on replay instead of like 12 in front)

yes.

Without knowing much about it, the "....server...." setting, by name it refers to running a server, so it should be switched to 1 on the VR Servers.
IF we decided to use those settings, it would be necessary to do so, yes ;) . I'm not sure, though, if the client side not also had to set the ...server... settings. We could try, but we also could simply do it and avoid troubles.

The "....client....." setting would probably affect everyones computers behaviour, probably just sending more packets, sounds pretty logical to set that to 1 on everyones machine.
No, if the setting were not the same as on the server, the server would not accept the client - you could not connect (iirc).

One of the main problems with that setting is that the clients would need an even more stable connection and low pings, otherwise it would not make too much sense. And I'm not sure what will happen, if a client capable of "[...]send_every=2" but not being able to fullfill a "[...]send_every=1" tries to run these settings. The package loss could lead to even more severe situations than a little "stuttering" in the line. And we already encounter the later with the "softer" setting of 2 (meaning 18 updates per second, while 1 means 36 updates per second). Of course also the total traffic load would double. I'm not sure about server-replay size, though. And the server would be even more vulnerable to variations in system load, which can lead to nasty lags as we all know from past experience.

Klaus
 
U

User 3205

Verrät mir hier auch mal jemand das mysteriöse Geheimnis der Eulen?^^

Was soll mir das sagen?:)
 
U

User 3205

Mach Sachen8o

:rolleyes:

LOL L33t ist nicht mehr so mein Ding, u know, G33k?^^ 2 old a s o...
 
U

User 3205

Manchmal glaube ich, Dieser Google steht Dir sehr nahe :gruebel:

..Immer diese modernen schreibweisen...eine seltsame Welt ist das geworden....:vogel:
 
U

User 1180

Okay zurück zur ini änderung. Ich schlage vor wir probierens mal in einem mittwoch trainings rennen. Dann lassen wir die Rookies am Montag drüber fahren, dann müssen die GNOSler herhalten und dann kommt es in die DOM
 
U

User 3257

Okay zurück zur ini änderung. Ich schlage vor wir probierens mal in einem mittwoch trainings rennen. Dann lassen wir die Rookies am Montag drüber fahren, dann müssen die GNOSler herhalten und dann kommt es in die DOM

Find Ich gut. Also zumindest das im Training testen.

Wiederstand ist übrigens zwecklos :D

orly_owl-strogg.jpg
 
Oben