> New features are no problem (I.e. a new type of suspension).
> If we want/need to compare TORCS-NG and TORCS, this has to be eliminated
> (because it can not be used in TORCS).
> Changed features are the reason to have different setups for TORCS and
> A great problem here: The balancing of carsets may be destroyed by changed
> So we would have to do a lot of tests to rebalance it.
> For a faster first release I would propose to keep it unchanged (in
> to TORCS 1.3.1).
> For a new TORCS release this work has to be done too and we can follow (or
> do better things).
I presume you're talking about simuv2 Wolf? I agree with what you said
When I joined NG I brought quite a few simuv3 features (suspension, diff
into simuv2 that aren't there in TORCS. New features like throttle
could probably be brought across as well - its good I think to keep simuv2
to date with simuv3 as much as possible, but at this point with all the
setups we've worked on I'd rather simuv2 in the trunk stayed frozen until
first release, with the exception of new features that don't break old
Get latest updates about Open Source Projects, Conferences and News.