Right. I agree. Thanks EP for sharing your view on this topic.
Also BTW yes, getting any track version from git is possible, anyone who cloned tracks repo can checkout to any commit hash in history and have tracks in that date, it could mean though some data will be missing or so.
I think we should only "renew" original tracks, so modify them keeping their look, e.g. adding horizon, objects, a few new assets if they fit, maybe a fluid, replacing outdated assets to newer, etc.
Other reason like now is replacing old skies (which we need to anyway).
I can handle fixing sky issues (brightness, not matching fog) this but IDK when.
I will restore Cross, MadMntn, Islands, etc to original SR3 look, and keep recent modified versions in new folders. So will add them as CrossLoop, MadMntn2, IslandsNight, etc.
I think it's the right way, although I'm not too happy about this, as I personally don't really like track mods as much as new tracks. And this adds some data (few MB) to repo, and adds tracks to list that aren't that different.
But yeah for 3.0 I think it's okay. if we someday will have
content manager in game Gui (that can browse and download tracks) this won't be an issue. But its implementation needs time. And it's lower priority for me than restoring still missing things from 2.7.
This also makes me think about starting another topic for track removal later, e.g. for those with 2-3 rating.