|
i'm not too knowledgeable about vamos. but i've sorta been thinking about some ideas with regard to the car loading process. so i'll apologize in advance if this is not what you were looking for as input. with the decoupling it might be cool to have a more free-form .car file. idk, maybe it's already like this.
==
maybe something like you could make as many [bracketed] headings as you want. and call them whatever you want. then write whatever parameters you want under them*, so as more data gets found for the car it can be incorporated into the .car file regardless of whether the physics system supports it yet or not.
then the .car parser would seek out the [engine] heading and read what it can from that. under it you could insert values for bore, stroke, cylinder count, cam count, block material, head material. and maybe eventually there will be tuning options for boring out the engine so it could take into account the stock bore.
suspension has been talked about allot. maybe, for suspension it could default to a fixed, hard suspension unless you signify a type of suspension. (mcpherson, leaf-spring, super-strut, etc.) and then each of those could have totally different parameters that the physics engine would be able to interpret given the context.
downside is that you'd have to document what parameters are recognized by the game and which ones affect which designs.
i'd really like to see each heading get a position and weight by default though. and if each one had a mesh as well it would be a good foundation for a full in-game tuning system. just to have each car as a big laundry list of parts, some with serious performance effects like changing suspension designs or engine swaps, others with mild weight reductions like removing passenger seats and window motors. and still others would be extra parts that would affect performance like spoilers, strut tower braces, and roll-cages.
|
