I updated the PDF with recent updates that have been accumulating in the Steam guide:
- Corrected description of initial fuel, damage, and repair points for trucks.
- Added reference information for US trucks.
- Added information about how to hand-edit the navigation map.
- Added summary icons throughout the custom features sections to indicate when changed XML properties are applied and which color channels are used by XML properties that specify a color or texture.
- Added more information regarding IsClampV.
- Added more detail regarding all types of model shadows.
So i've almost finished creating a custom plant but I can't get the tree to stay grounded and unmovable. Do you guys know what code needs to be put in the xml files to lock down my custom tree?
Sorry for the late response. I'm still not used to the notification system here.
The standard way is to give Mass="0" to the body at the base of your body hierarchy. This will prevent it from moving at all.
You could also put a constraint on the base body, e.g. with Type="Fixed". This constraint is implicitly attached to the world. The fixed constraint allows a bit of spring, but no large-scale movement. In this case, a higher mass will reduce the spring movement.
@tattoo Yes, under "Select Truck Components", "Choose the Truck Type":
"In the truck selection dialog you can choose to select a trailer instead of a truck. If you select a trailer this way (instead of the usual trailer selection below), the trailer is parked by itself as if it is a truck. Logs can be loaded on this trailer as described in the addons section below."
@tattoo Nope, there's no protection for a distribution coming through a model. You have to go around all your models clearing the distribution density or changing the material to keep grass and plants out. (My maps tend to end up with a few custom materials just so that I can do this.)
The ModelMaterial tag is a child of the Material tag (in the mesh XML).
Last night I added notes to all of the WheelTracks and IsWheelTracks properties to make it clear that they're not the same thing. You might need to refresh the BBMMM page if you've had it open since then.
And from the little I played with lights on my loop, InnerCone and OutterCone describes the top and bottom of a cone. Inner would be the small, upper part and Outter would be the large, bottom part of the cone created by the light. There's also a length setting but it's been a while since I messed with em and don't remember. I'd have to experiment more. Sorry.
I got the InnerCone figured out and documented. It's not quite how you describe, but it all makes perfect sense now.
this is amazing... one request.. for reference sections on xml, can you provide a full example of a completed xml file for the different elements? I like to see what a working xml looks like to help validate my entries. thanks!
This is why the guide points to examples in the built-in assets. They are your completed examples!