I tinker with Racer when I have time, usually happens on Sundays since its the only real day off I have. My new job has kept me busy (doesn't help that I probably spend 2 hours in my car driving there and back).
I tend to stick with RC4 myself, mostly because I felt it worked best for network play. So that said i think agreeing on which version to use as a community version would be the first thing to figure out, If RC5c works well on the network side, I'd say it could be the one to go with.
I have a few cars I could still release here, most obviously its my Ranger (seriously just waiting for Silver to get around to making 2d gauges for it), the other car needs more work first, parts of it are good, just needs more polish in spots. And actually just thought, I still haven't released my Omni GLH-Turbo, guess that thing should be looked at as well at some point here. I'd be willing to put in any of my content that I've created, just name it. I can also look into older cars being updated to a newer version of Racer (I actually got the Supra going pretty nicely, and even the Golf R32 looking good)
As for Raven 2, tell me what you think it needs, I kind of want to get the car/track listings in a better order (right now they go off of folder name, would prefer vehicle name). Granted some features are going to be harder to add than other features (nothing like a good challenge though).
I've not looked back at RC4 yet, but I have this feeling there were a few physics bloopers in there that made it not so useful.
That period was a high point, but still interspersed with the odd deal breaker in the occasional version.
RC5c seems to work ok here when I've played with Cosmo, almost all problems we ever had were firewall related. Racer itself seemed to play ok.
The only issues I think we had were things like resetting and scripts interfering with each other. Actually running Racer off a server with clients joining might alleviate some issues there, and the scripts may be more robust simply by figuring out decent scoping and doing some thorough testing.
Knowing we're aiming at one specific version of Racer at least means we can just figure it out and then run with a consistent approach.
I can then target all my shaders and PBR stuff at that version, and example skies/values, and we can then work out with great base content and upgrade everything slowly to meet those standards we slowly set and define as 'being the best'
I know Stereo and Cosmo put a lot of time and effort into bug finding and shaders stuff around this time, so we have lots of reason to use a vintage around that point as the last known good version to build some decent content up from.
Has anyone here ever run a Racer server and had a multiple remote (over internet) client session?
As per Raven, I'm thinking more a trusted batch running system maybe? So it kinda does a bit like what the Lambo Gallardo config tool does.
If it can also elegantly manage many different car folders but the same 'car' underneath, so that network players can see different coloured cars and so on, that'd be cool.
So it'd mean Raven somehow dealing with primary car folders (a base install), and then deploying the 'variants' into the car root folder with appropriate names for the car folders.
I'm not sure how it'd all work, but raven variants just meant huge disk space, but everyones cars were still the same colour if they picked the same one.
Letting Raven actually make the variants actual car folders to choose from, but without the user needing to download 20 different cars, would be really cool.
Dave
And I could update a few cars.
