FreeGameDev

So, few of you said VDrift track are worst looking and should be removed.
I also have a list of SR tracks that I think are ugly - see next post, (mostly, in tracks list, all rated 1, and few with 2).

OK, so here is my list of tracks which I don't like. Click on name to view in tracks browser.
Be sure to post if you find a track here, that you don't want to be removed in next ver (except the last group).

I Definitely don't want:

virginia (deleted)
ruudskogen (deleted)
detroit (deleted)
weekend (deleted)

D9-Mud (deleted)
J4-Pipe8 (deleted)
O1-Moss (deleted)
M1-Hills (deleted)
I1-Island (deleted)

J9-Sharp (deleted)
W3-Swing (deleted)
V3-Crater (deleted)

Not sure (those Will stay):

brands
F8-Stain

J1-Curly
D2-Mntn
I2-Sandy
W6-SnowyEights

S10-PipeCurl
D13-Winding

Need renew:

I4-Sunset
W5-Circles
F3-Snail

D4-SBridge
D3-Passage
J7-Hilly

Could use some renew still:

S2-Frenzy
X3-Cloud

G1-Long
J17-JungleCanyons

V1-Dark
V2-Volcanic
W12-Peaks

F14-Maze
C3-Vast

F15-ForestTrip
J19-ShortFun

V5-Sad
T6-Sunset
O3-Air

I would be more in favour of a reduced set of awesome tracks in the official distribution, but with the possibility to retrieve the other tracks which are not included in the binary release. Maybe as some addons that could ideally be browsed and downloaded in SR. Or maybe split the stuntrally-tracks repo in two, with a new stuntrally-tracks-legacy for the old tracks you don't want to ship anymore with SR 2.4. If this could reduce somewhat the size of the stuntrally-tracks repo, it would be nice for packaging; it's easier to download several smaller packages than a big one.

Yeah well that's the issue too. I want to drop few tracks so I don't need to update them whenever sth in code changes that needs updating all tracks. Or some data like all textures lately. If I just had to deal with all tracks like before, and just not include few in release, that's really not a difference for me. Well other than size, but 10 tracks isn't much, just VDrift tracks are big.
There is no repo splitting, and even if we did that, it would be too much trouble for me too use later. I think, if we delete tracks, the download size for clone with --depth=1 will be smaller.
There was an issue about content manager but it's too big for me and we don't (and won't) have a server, so it's a dead issue.

I would investigate the STK Add Ons approach. Let people upload/maintain their own tracks.

It is all open source so you could just copy most of it and rebrand it for SR.

http://stkaddons.net/

The VDrift tracks do take a lot of space (99 MB in total). weekend is 21 MB!

The VDrift tracks could be remade with the editor, if needed. They would look better but be more demanding on the hardware (VDrift tracks are currently much lighter on the hardware than “standard” tracks).

I think the VDrift imports don’t really fit to the spirit of the game, therefore I won’t miss them. It just does not feel right to drive on these tracks in SR, because they are imports. I don’t consider to be “real” SR tracks.
As for all other tracks, keep them, please.

CryHam {l Wrote}:There was an issue about content manager but it's too big for me and we don't (and won't) have a server, so it's a dead issue.

You could ask people like TuxFamily for hosting. They can provide it for free, but rely on donations to live.

Nooo, why do you do this to the SR tracks, too?

Ah Wuzzy, the majority (and me too) decided it's best. You can still play those, just keep them in data/tracks or in your user tracks dir.
Those were the ugliest tracks, I really feel better not having them or thinking what to do to make them better.
And like Charlie said, and I agree, it's about the whole package, if we keep them then all tracks average rating will be lower.

How about releasing the deleted tracks in a seperate package, called “The Lost Tracks” maybe?

Yeah we probably can do it. Could also maybe have some other tracks from here, those not included in 2.4, but working with 2.4.

Great, that would be cool.