Even though there's such a theoretical range of combinations to get to a PB on (every car x every track) it seems I'm not alone in wanting
something fresh and new. What have been the macro changes to the game of late? When patch S came out we got the improved physics and the BF1. We got the improved sounds in V/W, and X has brought pre-load clutchpack and false starts. Sure, there have been a squillion other improvements but not in any area that broadly affects the user experience - and these changes span a development time of 14 months (not including the dev time
for patch S).
We're all going crazy for something fresh and new, and it seems to me that we could be easily appeased with new
content, and so we'd STFU to allow Scawen to work on the core game engine (collisions, engine damage, weather...). I've previously thought that user-contributed material would be a great way to go, but only if:
- Quality was controlled by a central authority (e.g. Scavier), to whom all content would have to be submitted, and may go through several iterations for testing, suitability to the game, playability etc. There would probably be a closed beta-testing group for this (beta testing an alpha product? You know what I mean....)
- Downloading content was integrated into the game engine, e.g. with the patch auto-updating. No hunting for patches, no worrying about new content integrity.
- Strict versioning control was implemented. E.g. think about the two Brands Hatch in GPL. Cosmetic differences would not be the end of the world (e.g. the SO City graphical updates) but any layout changes would be crucial to ensure every driver is using the exact same circuit. I can imagine LFS having all sorts of hideous sync errors as well if this wasn't managed properly (e.g. your version of Brands has incorrect elevation, so my car's reported position appears to be tunnelling through the solid track to you....)
- There was an agreed and committed release schedule. It could be as meagre as one car every six months, and one track per year. Oversaturation would be unhealthy and unnecessary. But having something - anything - we could count on to look forward to with a reasonable degree of certainty would be such a refreshing change
- Certainly there would be a number of keen amateurs who would jump in and have a go at submitting content. But I suspect that there are a few genuinely talented members of the community who excel and thrive at producing the desired content, and most of the hard work would come from them. So I don't think inferior quality would be an issue so long as the QA process was built in, and well documented and understood. Also the required quality would soon become evident with comparison to the stock cars and tracks plus any newly accepted material. I.e. don't even bother submitting content until it's of the same level as Blackwood
- This could allow LFS to further develop into its own niche, which right now feels like track-day specials and somewhat obscure regional circuits. So new cars like the DP1 would fit right in. I seriously doubt whether we would ever see our Ferraris and Porsches shipping with the stock game (although anything could happen over time, particularly if LFS' popularity continues to grow).
- There remains a big question about licensing. Clearly the devs can't blatantly ignore licensing issues, but possibly one workaround would be to implement various 'repositories' of content. There could be three: "core" (all the content we know and love right now), "official" which would contain community addons approved by the devs (e.g. a community created and approved fantasy track, where there are no license issues, or officially blessed ones like the DP1), and the "community" repository which is a link to only a single content source where community members can QA and approve content for download. This would have a big fat disclaimer like 'any content downloaded form the community repository is not endorsed by Scavier etc etc' but would allow us to develop things like our own Nordschleife, or the GT3RSR. Crucially, QA control, download management, versioning etc as listed above would have to be applied fiercely to this community repository as otherwise we'd be straight in to rFactor territory. Some lucky volunteer would have to step up and 'be' that community repository host, and we'd also have to appoint a QA committee to perform those tasks, as we could hardly ask Eric to adjudicate whether my copy of the Karrussel was up to the game's high standards.
If I felt I had even one iota of success in persuading Scavier to adopt this, I'd start talking about the positive reasons for doing so - that the community goodwill and patience is a finite resource and that this would be a really cheap and empowering way of further reinforcing our borderline-obsessive feelings about LFS, and that you can't ignore a certain degree of exasperation even among the die-hards that we never know what we're going to get, and when we get it, it doesn't materially affect the game we love so much. I think the model I've described would work, but who am I kidding? I can't see it ever being adopted so I'll just sit back and wait for improved GTR textures (that
we can already download) and improved AI (that I don't need), and keep driving GTR at AS National along with the 5,000 others (in
broad daylight).
Rakhsh