Rigs Of Rods Monster Truck Pack

Posted : adminOn 2/23/2018

So I downloaded a few trucks from the site. This one: The other one was this: To rule out any issues in 0.4.5.1, I tried both vehicles in 0.39.5. It seems that the spawning problems aren't caused by bugs in RoR. The authors haven't included all the dependencies in their.zip files, therefore the trucks cause a crash.

Rigs Of Rods Monster Truck PackRigs Of Rods Monster Truck Pack

This is probably my best work in Rigs of Rods to date, and I couldn't have done it without a great team of people behind me! DanDon (textured by Mark Colineri) Pedals Model/Textures - acdcfan56 Shocks Model/Textures - Sim-Monsters V4 Pack Makers (modified by DanDon), Coconutmen Tire Model/Texture - RockCrwlr. View Current Tournament Report. View Upcoming Tourneys TPWD Home TPWD Records-Lake Mexico Lakes Report TPWD Reports. FLT Flash Fishing Report! Dead Can Dance Anastasis Rar Extractor there.

For example, the BadHabitTrophy.truck. RoR crashed because a flare material was not found: OGRE EXCEPTION(5:ItemIdentityException): Could not find material GraveDiggerredflare in BillboardSet::setMaterialName at C: data ror-trunk dependencies src Ogre ogre_src_v1-7-3 OgreMain src OgreBillboardSet.cpp (line 312) Commented out the flare, another error popped up that crashed RoR: OGRE EXCEPTION(5:ItemIdentityException): Unable to derive resource group for SIR4wsouter.mesh automatically since the resource was not found. In ResourceGroupManager::findGroupContainingResource at C: data ror-trunk dependencies src Ogre ogre_src_v1-7-3 OgreMain src OgreResourceGroupManager.cpp (line 1782) Commented out the 4 mesh files, another error that crashed RoR: OGRE EXCEPTION(5:ItemIdentityException): Unable to derive resource group for OR4wsLower.mesh automatically since the resource was not found. In ResourceGroupManager::findGroupContainingResource at C: data ror-trunk dependencies src Ogre ogre_src_v1-7-3 OgreMain src OgreResourceGroupManager.cpp (line 1782) Commented out the 2 mesh files, another error that crashed RoR: OGRE EXCEPTION(5:ItemIdentityException): Unable to derive resource group for OrangeDshaft.mesh automatically since the resource was not found. In ResourceGroupManager::findGroupContainingResource at C: data ror-trunk dependencies src Ogre ogre_src_v1-7-3 OgreMain src OgreResourceGroupManager.cpp (line 1782) Fearing to get stuck in an endless loop I stopped.

Checked the log and found some more errors: BIO ERROR BadHabitTrophy.truck:0012 globals Material 'GravediggerBand' used in Section 'globals' not found! We will try to use the material 'tracks/transred' instead. Can't assign material GravediggerBand to SubEntity of wheelobj-t32-0 because this Material does not exist. Have you forgotten to define it in a.material script? OGRE EXCEPTION(6:FileNotFoundException): Cannot locate resource Chassis_Colors.png in resource group General-Reloaded-2 or any other group. In ResourceGroupManager::openResource at C: data ror-trunk dependencies src Ogre ogre_src_v1-7-3 OgreMain src OgreResourceGroupManager.cpp (line 753) Error loading texture Chassis_Colors.png.

Texture layer will be blank. Loading the texture failed with the following exception: OGRE EXCEPTION(6:FileNotFoundException): Cannot locate resource Chassis_Colors.png in resource group General-Reloaded-2 or any other group. In ResourceGroupManager::openResource at C: data ror-trunk dependencies src Ogre ogre_src_v1-7-3 OgreMain src OgreResourceGroupManager.cpp (line 753) OGRE EXCEPTION(6:FileNotFoundException): Cannot locate resource rkmradiator.png in resource group General-Reloaded-2 or any other group. In ResourceGroupManager::openResource at C: data ror-trunk dependencies src Ogre ogre_src_v1-7-3 OgreMain src OgreResourceGroupManager.cpp (line 753) etc... Will not waste space posting all the errors (very many missing textures). Noticed similar issues with the other vehicle.

So the issues are caused by messy modding practice, for which we cannot blame RoR's code. Thanks for investigation. Unfortunately, due to lack of proper tools and fault-ignorance of pre-0.4.5 parser, most trucks are messy. But we're stuck with them, so we need to handle them the best we can.

For one thing, missing resources should never crash RoR. If they're critical, they should only cancel the loading, showing an error dialog like 'Spawning failed; critical errors in the vehicle. See spawner log'. If the resources are non-critical, the vehicle should load anyway with a warning dialog like 'Missing resources in the vehicle, it may not look correctly. See spawner log.'