Race Sim Central
Rec.Autos.Simulators Archive

(core.ini) who has control

4 posts by 3 people · 18 Jul 1999 - 18 Jul 1999

As a server, I'll assume that he has control over every line in the core.ini with the word "server" in it.. ie "net_mdm_server_send_every = 3". What about the clients? do they work with only the lines that have "client" in them.. ie "net_mdm_client_send_every = 3". Or, does the server do everything in it's core file as well as send the client the info to send it's stuff when the server tells it to? What I want to know... Who has control over what in the core.ini file? I checked over the stuffs listed in [link lost in import: /;There] is some good info there but it's layed out chaotically as to my question. I'll re-read it all and try to make sence of it. In the mean time does anyone know who has cantrol of each line in the core? Mike Barlow -- ========================================= Mike Barlow of Barlow Racing? ========================================= Member of R.O.R. 1999 http://w3.ime.net/~marknjess/ror.html ========================================= Racing online with the help of...... Mark Seery ***sports [link lost in import] Sim Racing Mag http://www.simracingmag.com/ Race Communications Association http://members.xoom.com/RCA/toc.html Holodyne Engineering Mystic Music (have Your !!Name/Address!! placed here) mikeba.vcf < 1K Download
Bart Westra 18 Jul 1999#481228
<snip> Point taken. I plan to redo the pages next month when I am off duty for 4 weeks. And get them up to date with 1.1 as well. This is the piece concerning your question: "When connecting via TCP/IP, the values for net_use_mdm_bandwidth_for_tcp_ip must be the same on the server and the client. If not, a bandwidth mismatch will be reported when trying to connect. The client uses its local client_send_every setting to determine the send frequency of the local car data, the server uses its local server_send_every setting for the send frequency of the surrounding cars data. The server uses its local server_send_size setting to determine the size of the packets it sends to the clients. If a client has a smaller value for server_send_size in its core.ini, a bandwidth mismatch will be reported when trying to connect. The client_send paramaters are ignored on the server. " The last remark may not be true for GPL 1.1. The client_send parameters on the server may play a role in the reported connection quality. Bart Westra
% As a server, I'll assume that he has control over every line in the % core.ini with the word "server" in it.. ie "net_mdm_server_send_every = % 3". What about the clients? do they work with only the lines that have % "client" in them.. ie "net_mdm_client_send_every = 3". % Or, does the server do everything in it's core file as well as send the % client the info to send it's stuff when the server tells it to? % What I want to know... Who has control over what in the core.ini file? % I checked over the stuffs listed in % http://people.a2000.nl/bcwes/gplol.htm. There is some good info there % but it's layed out chaotically as to my question. I'll re-read it all % and try to make sence of it. In the mean time does anyone know who has % cantrol of each line in the core? I am still awaiting the official word on v1.1 of GPL from Randy Cassidy. However, this is the information he posted in r.a.s. regarding v1.0: Both :-) The host uses the server_send values to determine how much and how often it can send data to each client. The host uses the client_send values to determine how much and how often it should expect to see data from each client. (Note that the sizes are maximums - frequently it won't be necessary to send that much data, so smaller packets will be sent (ever notice that your modem lights glow brighter while in a race with several cars than when selecting parameters for the race?)) Similarly, the client uses the client_send values to determine how much/often it can send to the server, and the server_send values to determine how much/often it can expect to see from the server. It's critical that the client_send_size on the client be no greater than the client_send_size on the host. If this is not the case, the client may send a packet to the host that is larger than the host believes is possible, and this will cause the host to disconnect the client. Similarly, it is critical that the server_send_size on the host be no larger than the server_send_size on the client. Otherwise the client may see a packet from the server that is larger than it believes is possible, and disconnect from the server. It's best to have the send_every's match, but it's not critical. A GPL host will disconnect a client if it receives less than 50% of the number of packets it expects to see from that client (that'd be a pretty crappy connection). But, if the client had a client_send_every of 3, and the server had a client_send_every of 2, then with a perfect connection the server would only be seeing 67% of what it was expecting to see from the client. This doesn't leave much margin for packet loss before the server dumps the client. (This also works in reverse - if a client isn't getting 50% of the number of packets it expects to see from the server, it will disconnect from the server). -- **************************** Michael E. Carver ************************* Upside out, or inside down...False alarm the only game in town. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=<[ /./. [- < ]>=-=-=-=-=-=-=-=-=-=-=-=-=-=
Thanks :) That answered the question. I'd assume that anything that says "client" in the core.ini would be controlled by the client. A suggestion... List each and every line in the core.ini. Below each line give a description of what it is, what it's used for, what values are valid, and what the benefits and downfalls are for changing the values. Thanks, Mike barlow -- ========================================= Mike Barlow of Barlow Racing? ========================================= Member of R.O.R. 1999 http://w3.ime.net/~marknjess/ror.html ========================================= Racing online with the help of...... Mark Seery ***sports [link lost in import] Sim Racing Mag http://www.simracingmag.com/ Race Communications Association http://members.xoom.com/RCA/toc.html Holodyne Engineering Mystic Music (have Your !!Name/Address!! placed here) mikeba.vcf < 1K Download

Sponsors

Affiliate Links

Sim Gaming Expo MOZA Racing Sim-Lab Fanatec TrakRacer Asetek Internet Privacy From NordVPN Dreamhost Capital One Credit Card Application Fanatical CDKeys Amazon Amazon UK Project Motor Racing iRacing Get your racing gloves, boots and more from Demon Tweeks. Enlist at Roberts Space Industries, developers of Star Citizen and Squadron 42


Back from the ashes since July, 2019. First created in 2001 with the merger of Legends Central (founded 1999) and simracing.dk.

A site by a sort of sim racer, for sim racers, about racing sims. News and information on both modern and historic sim racing software titles.

All products and licenses property of their respective owners.


Facebook Threads Bluesky Twitter Mastodon Instagram YouTube Tiktok Twitch Reddit Google News Apple News Subscribe via WordPress Flipboard eBay

Race Sim Central © 1999-2026 | Some links pay RSC a commission. Advertising does not equal endorsement.Cookie Policy