-W-E-C-

Long Day Series GT1 (LS-GT1) Archer R-9 -> issues: * no animated cockpit Cavallo 570 S1 -> removed for license reasons Marisatech FMC GT4R -> removed for license reasons Newcastle Fury LS1 -> issues: * no animated cockpit * size needs checking (seems a bit narrow) Taipan LTS-R -> issues: * no animated cockpit * fix wheel arches Toro R-GT -> removed for license reasons Vulture V5-R -> issues: currently none known Vulture V6-R -> removed for license reasons Zentek Z7 LSR -> removed for license reasons...

Supercars (SC): Boxer 96 -> issues: currently none known Cavallo 360 -> issues: currently none known Deckard Conejo -> currently missing from the repo FMC GT4 -> removed for license reasons Kanagawa Z35 GT-S -> issues: currently none known Kongei KK8S -> issues: * size needs to be fixed (too broad) -> suggestions: * modell also exists in category SRW, merging with it? Lynx 220 -> issues: * no animated cockpit * maybe some geometry-update Murasama MSX -> issues: currently none known Spirit 300 ->...

i have been focusing on the existing carsets in this thread, because i would like to help with fixing models but got rather confused on what is actually needed/wanted if you think there is something that needs to be fixed with the tb70-tinder-cars, you can of course post it. if it's an issue on the model side i might be able to help, if it's about setup or problems with robots driving them i can be of no help, but maybe someone else can.

Long Day Series GT2 (LS-GT2) Bavaria G3 GTR -> removed for license reasons Bavaria NB3 LS2 -> issues: no animated cockpit currently removed from the repo because of problem with cockpit-texture Boxer 96 LS-RSR -> issues: no animated cockpit (can be adapted from coresponding sc-model) Cavallo 360-R -> issues: no animated cockpit (can be adapted from coresponding sc-model) RCM C400R -> removed for license reasons Lynx XKR -> removed for license reasons Morley R900 -> issues: no animated cockpit Sprite...

I am not sure what you mean with "fitting robot drivers". As of v2.4.0, it is possible to generate any computer-controlled driver for any car based on any of the existing robot implementations (simplix, shadow, usr or dandroid). See the attached screenshot for further reference. Since v2.4.0, the speed-dreams-data repository now only includes the car+track XML files for each robot implementation. while i was aware that you were adding the capabilty for generating drivers, i thought you kept the possiblity...

while i can understand that you would do things like that with "custom" cars submitted by users to keep things from getting muddled, i would have thought the "core"-cars (e.g. the official carsets) should kept in the repo for maintenance, keeping them updated (or at least have tickets on whats needed) and otherwise keep track of them. also, with the sc-murasama-nsx this would mean that the repo probably contains an older version, which is certainly going to cause confusion when something is to be...

thanks for the feedback. the missing codriver is "not a bug but a feature": i felt it might obstruct the view, so i put it into the driver file instead directly into the car, the kafka should have the same "issue". Is this a problem?

Thanks for taking time answering On the other hand, the canonical URL for the official assets database is https://www.speed-dreams.net/assets.json . And this is the default URL accessed by the game when entering the "Downloads" menu. where is it linked on the official poject pages (i didn't see it, only the link to the wiki on the homepage)? anyway, the motivation of poiting this topic from my side: while i am aware that the changes done due to licensing issues, afaik the wiki does reflect more or...