bdbssb

Thank you again for a great tutorial/information.

It would be better if I could get a link to the full mod so I can test it though.

Ok I’ll try to take a look. The turning radius can be changed as well I believe.

If it has a capacity then density/mass can be disabled too. I would have to look at the xml. Do you have a link?

And welcome to the site. Thank you for posting. We need to use the forum more.

When you say turn better. You mean it’s just pulling hard? The down force can be lowered. That would be easier than adding a 3-point.

So I have had a couple of people working with vehicle type and specialization and I wanted to pass on how the game engine handles these attributes. So every vehicle has a type name at the top of the xml. Example below. <?xml version="1.0" encoding="utf-8" standalone="no" ?> <vehicle type="carFillable"> <annotation>Copyright (C) GIANTS Software GmbH, All Rights Reserved.</annotation> The "carFillable" tells the game engine to look for specific attributes in the xml. I do not know the specific name however this is how I refer to this process. I will attach a file called FS19_vehicleTypes.xml that will come in helpful and what I will be referring to. So when I search "carFillable" in the file we will see this <type name="carFillable" parent="baseDrivable"> <specialization name="fillVolume" /> <specialization name="dischargeable" /> <specialization name="trailer" /> <specialization name="tensionBelts" /> <specialization name="foldable" /> </type> The xml is telling the game load vehicle type "carFillable" which has the specializations listed below of fillVolume, dischargeable, trailer, tensionBelts, foldable. But then you see parent with the name "baseDrivable" so we need to search the xml for "baseDrivable", be sure to go to the top of the document to find the actual type "baseDrivable" not a listing of a parent like above. You want to see this <type name="baseDrivable" parent="base"> <specialization name="ikChains" /> <specialization name="wheels" /> <specialization name="crawlers" /> <specialization name="slopeCompensation" /> <specialization name="speedRotatingParts" /> <specialization name="enterable" /> <specialization name="fillUnit" /> <specialization name="motorized" /> <specialization name="drivable" /> <specialization name="aiVehicle" /> <specialization name="aiImplement" /> <specialization name="articulatedAxis" /> <specialization name="lights" /> <specialization name="attacherJoints" /> <specialization name="powerTakeOffs" /> <specialization name="suspensions" /> <specialization name="connectionHoses" /> <specialization name="honk" /> <specialization name="wipers" /> <specialization name="frontloaderAttacher" /> <specialization name="bunkerSiloCompacter" /> </type> As you can see there are many more specializations in this vehicle type but we also have a parent of "base" so lets search for base. <type name="base" className="Vehicle" filename="dataS/scripts/vehicles/Vehicle.lua" > <specialization name="baseMaterial" /> <specialization name="tipOccluder" /> <specialization name="foliageBending" /> <specialization name="washable" /> <specialization name="wearable" /> <specialization name="dynamicallyLoadedParts" /> <specialization name="animatedVehicle" /> <specialization name="dashboard" /> <specialization name="cylindered" /> <specialization name="mountable" /> </type> As you can see there is no parent listed so there is no need to reference any further. Now if we simply look at all the referenced specializations we have this list. <specialization name="baseMaterial" /> <specialization name="tipOccluder" /> <specialization name="foliageBending" /> <specialization name="washable" /> <specialization name="wearable" /> <specialization name="dynamicallyLoadedParts" /> <specialization name="animatedVehicle" /> <specialization name="dashboard" /> <specialization name="cylindered" /> <specialization name="mountable" /> <specialization name="ikChains" /> <specialization name="wheels" /> <specialization name="crawlers" /> <specialization name="slopeCompensation" /> <specialization name="speedRotatingParts" /> <specialization name="enterable" /> <specialization name="fillUnit" /> <specialization name="motorized" /> <specialization name="drivable" /> <specialization name="aiVehicle" /> <specialization name="aiImplement" /> <specialization name="articulatedAxis" /> <specialization name="lights" /> <specialization name="attacherJoints" /> <specialization name="powerTakeOffs" /> <specialization name="suspensions" /> <specialization name="connectionHoses" /> <specialization name="honk" /> <specialization name="wipers" /> <specialization name="frontloaderAttacher" /> <specialization name="bunkerSiloCompacter" /> <specialization name="fillVolume" /> <specialization name="dischargeable" /> <specialization name="trailer" /> <specialization name="tensionBelts" /> <specialization name="foldable" /> This seems like a lot to take in but honestly just take the time to search and follow the names. Now if you have a vehicle you are building and you cannot find a default vehicle with the specializations you want then you need to add a custom vehicle type in your modDesc. You would add these lines in your modDesc file. I use a customized vehicle type in my Factory pack but below is an example of the lines you would need to add. <vehicleTypes> <type name="fuelTrailer2" parent="baseFillable" filename="$dataS/scripts/vehicles/Vehicle.lua"> <specialization name="fillTriggerVehicle" /> <specialization name="dischargeable" /> <specialization name="waterTrailer" /> </type> </vehicleTypes> It is important that you use a type name that is not used as a default type or the game will simply load the default vehicle type. The easiest way to do this is to search for your new name in the FS19_vehicleTypes.xml and be sure it is not found. Next you would put "fuelTrailer2" in the vehicle's xml type name and it would be adding the 3 specialization's listed along with every specialization loaded from parent "baseFillable" as I showed how to do above. Hope this helped and please feel free to respond with any questions or suggestions. FS19_vehicleTypes.xml

If you have ever added a wheel to a part that folds then you have probably ran in to the issue of the wheel moving but the wheel collision not? If you figured it out great, if not here ya go. The issue is the wheel has to be called out in the moving tool area. I am going to copy some lines in from a plow that thumper was having issues with. I helped him via a dm in discord. So the key here is to know the part that is moving in the animation and the wheels that are in that part. If you are using cylinder parts or not it will matter as well. In the example the first 2 parts have cylinder parts (parts that move with a reference). The last part is just a moving part with the wheels inside it. It matters because the lines are closed off differently. As a guide I used the krone forager to figure out how move the collisions. They are invisible wheels. The forage heads will pivot, they don't lock like a harvester header. So here is the animation lines I looked at. <animations> <animation name="folding"> <part node="leftWing" endTime="15" startTime="0" startRot="0 0 0" endRot="0 0 114.4"/> <part node="rightWing" endTime="15" startTime="0" startRot="0 0 0" endRot="0 0 -114.4"/> <part node="leftArm" endTime="15" startTime="0" startRot="0 0 0" endRot="0 0 -114.4"/> <part node="rightArm" endTime="15" startTime="0" startRot="0 0 0" endRot="0 0 114.4"/> <part node="leftSupport" endTime="15" startTime="0" startRot="0 0 0" endRot="0 0 114.4"/> <part node="rightSupport" endTime="15" startTime="0" startRot="0 0 0" endRot="0 0 -114.4"/> </animation> <animation name="lowerAnimation"> <part node="bottomSupport" startTime="0" endTime="2.5" endRot="-20 0 0" startRot="0 0 0"/> <part node="topSupport" startTime="0" endTime="2.5" endRot="-20 0 0" startRot="0 0 0"/> <part node="swivel" startTime="0" endTime="2.5" endRot="20 0 0" startRot="0 0 0"/> <part node="assistCylinder" startTime="0" endTime="2.5" endRot="-16.5 0 0" startRot="0 0 0"/> <part node="assistRam" startTime="0" endTime="2.5" endTrans="0 0 -0.978" startTrans="0 0 -0.894"/> </animation> </animations> The leftWing and rightWing are where the first and second set of wheels are. The second set are in the swivel. <cylindered> <movingTools> <movingTool node="leftWing" playSound="true" wheelIndices="1"> <dependentPart node="leftCylinder"/> </movingTool> <movingTool node="rightWing" playSound="true" wheelIndices="2"> <dependentPart node="rightCylinder"/> </movingTool> <movingTool node="swivel" wheelIndices="7 8 9 10"/> </movingTools> <movingParts> <movingPart node="leftCylinder" referencePoint="leftJointHyd" referenceFrame="0" isActiveDirty="true"> <translatingPart node="leftRam"/> </movingPart> <movingPart node="rightCylinder" referencePoint="rightJointHyd" referenceFrame="0" isActiveDirty="true"> <translatingPart node="rightRam"/> </movingPart> </movingParts> <sounds> <hydraulic template="DEFAULT_HYDRAULIC_SOUND"/> </sounds> </cylindered> As you can see the leftWing and rightWing have cylinder parts, the swivel does not. That is why they are closed off differently. The swivel line would not normally be there but it had to be added to call out the wheel indices. As you can see all that had to be done was to add the wheelIndices comand in so that the game engine knows that there are wheels inside the moving part. When indexing indices you start with 1. So simply wheel 1 is in the leftWing, wheel 2 is in the rightWing, and wheels 7 8 9 10 are in the swivel. I know this would probably be better explained in a video however I wanted to add it here quick to help those that may have had an issue.