You're the host, you decide. Force a restart if you feel it's necessary. Forcing a restart while others are still racing is generally not a good idea, but it's your decision. If you want your server to offer immediate restarts as soon as anyone wants one, fine. If you want to be a kind and understanding admin, be one. If you want to be the bastard operator from hell, go ahead. etc.
While hosting from in-game (starting a new game from the multiplayer menu), voting for a restart or end will immediately be treated as a completed vote, so you can't really vote normally. To be able to cast normal votes, you'll need to run the dedicated server.
Cute event, great racing with FEL in the rallycross and some tight laps on Cadet. Sorry to Sp3c and Alt for outbraking myself in the second chicane of cadet on one of the first laps.
Made some stats and uploaded the replays to FLP's website, here.
A database dump would make some stuff simpler for sure, maybe a dump exluding detailed race results could work? I'm thinking about writing something to show statistics on overall team progress, with FLP's meager 6 members it'll still be hundreds of queries.
I could live with such a thing being tarpitted an entire week.
Getting a dump of all players in <team> would also be great if a complete one isn't happening.
Really impressive, great video / commentary / coverage.
Only thing i didn't like was the alternative (high res?) textures on the short bits from Aston, combined with low resolution and compression they sort of turn into a single-color featureless surface.
Turn one to chicane. You slow down too fast and turn in too soon. There's still some space to your left. Chicane should easily be taken flat out if tyres are up to temperature. You loose about .8 of a second to split 1.
Turn four, right-hander after back straight. You've got loads of space to your left here, making the turn much narrower then necessary. You loose grip and slide thru the corner loosing time.
Turn five, S into uphill and split 2. You lift off too soon, you can carry more speed into the turn-in. You loose about .6 of a second to split 2.
Turn eight (last), you don't use the extra bit of road to your right, making the turn narrower and loosing speed. You loose about .5 of a second to s/f line.
I've got a H-shifter which i basically never use, i've also got a second wheel / pedals for clutch which i basically never use. At first i thought i'd go for the g25 right away but i think i'll properly wear out the DFP first.
Pretty strange race in pool 3, most of the grid seemed to disappear during the first 2 or 3 laps. I had a slight crash which sort of inverted my camber on right front, not really ideal for fe1r.
There's not really that much to document, the source isn't meant to be a finished program and i wouldn't know what else to add besides the comments in the configuration files.
The streamed mpr is always late, you can fast forward until you're about 20-30 seconds behind but any closer then that the replay will probably stop. The mpr isn't constantly written to by LFS and thus it's not constantly streamed either, it depends on the amount of action in the race, amount of racers, etc.
How to automatically deal with wrong way drivers is specified by the server option /autokick, which can be set to yes, no (kick), ban or spectate. The option is set in the configuration file for a dedicated server or thru chat/command /autokick in server console or in-game as admin.
ie. /autokick=yes in config, /autokick yes in chat/console.
There is a server option for disabling car resets but it doesn't seem to actually be implemented yet. Scripting to disable or penalize car resets would be extremely sketchy and prone to mistakes, which is probably why there are no such scripts or applications yet.
The splash screen text is to be grabbed from a .txt file, controlled by the server setting /welcome.
Could you add something like a frequency offset, perhaps a configuration file like an .ini or something? I would really want to tweak the 'center' frequency for BF1 / XRT since the sounds are so out of tune when mixed with LFS' engine notes.
I also think your program deserves a thread of its own
It should be enough to extract the archive wherever you'd like to put it and by method of choice run "path/to/php.exe path/to/script.php". You can also add "path/to/php" in your environment variable PATH to have php available from command line anywhere. You could also probably just drag 'n drop the script onto php.exe. Or use file association. etc.
Since the scripts are sort of sketchy you may need to use absolute paths in the script configs. (server.cfg/client.cfg).
One good example for demonstrating that PHP doesn't rely on a webserver might be that it's relatively simple to write a decent webserver in PHP.
It's tricky to make a PHP webserver fully support PHP though.
I have 81 hotlaps, i like it, my vote goes to starting from pits with ambient temps. The useless skill i've wasted so much time practicing has actually been very useful in super pole or other short forms of qualifying.
I tie ID and username to nickname and store ID and username under nickname. Sort of cross-referenced i guess, works really well. List simply gets updated whenever there's a packet holding relevant information.
I'm going nuts with insim relays/proxies/gateways.
My app couldn't connect to Companion, to connect it sends the ISI packet, a VER request and waits for the VER response, which never arrived. Companion works fine thru my relay though.
It's incredible how complicated this simple thing is, for example,
dedilink -> my relay: ok.
dedilink -> racemanager gateway: fails.
dedilink -> my relay -> racemanager gateway: ok.
lfsworld insim relay -> my relay: fails.
Since it doesn't work with lfsworld it's obviously broken, but it works so well in other situations. :tired:
Anyway, </offtopic>. The bits of Companion 0.5 i've tried so far have worked really well and your list of features is starting to look scary.
I tried connecting to companion's relay and got the message "relayed client desires MSS .. ", and i guess companion doesn't respond to my app any further since it sees this as a problem? If this is the case, i don't think you need to drop/not respond to the connection. For my app, missing MSS packets would still allow a whole lot of functionality, nothing breaks because of MSO, some stuff just won't get triggered.
NLP vs MCI might be a real problem, but i think you could allow apps wanting MSS.