+- Forums (https://www.vdrift.net/Forum)
+-- Forum: Project (https://www.vdrift.net/Forum/forumdisplay.php?fid=4)
+--- Forum: Development (https://www.vdrift.net/Forum/forumdisplay.php?fid=9)
+--- Thread: Fixed car parts naming and customization (/showthread.php?tid=2201)
Fixed car parts naming and customization - NaN - 11-28-2015
Currently we have a fixed set of car components (engine, wheels, ...) but also allow additional arbitrary named parts.
I've been wondering if it would be better to have a fixed set of parts. It would make car files easier to read/modify and eventually allow to add tuning functionality, by adding car part lists.
Something like:
Code:
glass
interior
seat f/r fl/fr/rl/rr
steering
body
hood
trunk
fender fl/fr/rl/rr
door fl/fr/rl/rr -> do we need this?
bumper f/r
spoiler f/r
light f/r
transmission
engine
differential f/c/r
wheel f/r fl/fr/rl/rr
tire ...
suspension ...Other parts I am missing?
RE: Fixed car parts naming - NaN - 11-28-2015
The parts lists would be loaded from an optional parts.txt/ini file in the car directory.
Looking like this maybe:
Code:
[spoiler.f.1]
#spoiler definition here
[spoiler.f.2]
...
[hood.1]
...
[wheel.fl.1]
...
[tire.fl.1]
...
[brake.fl.1]
...All part options would be explicit, to be able to limit tire/rim selection for example. The default parts would use the reserved index zero (hood.0).
RE: Fixed car parts naming - NaN - 11-28-2015
Thinking about it. It would be nice to have trim options (preselected parts configurations), maybe saved in a trim_levels.txt/ini (or variants.txt/ini) file.
The user would be able to select the default variant (parts zero) or other predefined variants (think of the different LE and ATT variants we have now) and modify them creating a custom variant.