[TL1] Converting boss models for pets

• [TL1] Converting boss models for pets
  Posted by Lord Nyriox on 08 Mar, 2017 23:10
• SOLVED:
  
  Disable "hardware skinning" in the options to enable these pets to work. 
  
  

  ---

  Original Post:
  
  Next time I need to be a little more thorough in my testing prior to posting… 
  
  Primarily I want to know how to make the Ordrak ("bosses\ordrak\ordrak") model from TL1 and the Vyrax ("bosses\boss_dragonlive\tower_dragon") model from TL2 both load as TL1 pets. 
  
  I am getting a "crash to desktop" at the main menu whenever I try to load either of those as pets. 
• 
  
• #1 Reply
  Posted by Anarch16sync on 09 Mar, 2017 15:57
• There may be some difference in the ogre mesh version, like TL2 using an updated version of ogre than TL1... I haven't checked, but since you can't make it work that may be the issue. If you want to check you can convert the models to .xml and open them in a text editor to see the version difference.
• 
  
• #2 Reply
  Posted by Anarch16sync on 10 Mar, 2017 16:06
• For 3, just remove the collision mesh line in the unit data. Pets shouldn't have collision meshes since it bugs (crash to desktop) skills with collision detection.
  If that doesn't work then 1 may be an issue, the game has a soft limit to vertex count, if you use models with a  high poly count the games bugs in weird ways. TL2 should have a higher vertex limit, since most models have more poligons than the TL1 models.
• 
  
• #3 Reply
  Posted by Kva3imoda on 10 Mar, 2017 17:22
• Quote from: Lord Nyriox on 08 Mar, 2017 23:10

  but whenever I try to make a pet use any vanilla mesh from the "Bosses" directory—even if I move the model to the generic monster model directory—the game crashes the instant it tries to render the pet.
  

  You mean these models?
  
  
  
  This all works fine as pets. I think the problem is in the *.material files.
  It should look like this:
  Alric.material
  

  Code: [Select]

  material Alric
{
technique
{
pass
{
ambient 0.588 0.588 0.588
diffuse 0.588 0.588 0.588
specular 0 0 0 0
emissive 0.4 0.4 0.4
scene_blend alpha_blend
alpha_rejection greater 5
texture_unit
{
texture alric.dds
}
}
}
}
  
• 
  
• #4 Reply
  Posted by Phanjam on 11 Mar, 2017 06:36
• Hey Nyriox. I also can't seem to get Vyrax to work as a pet! Tho I got him to work as a monster - so it can't be the model files...  Will keep digging...
  
  

  Spoiler (hover to show)

  
  
• 
  
• #5 Reply
  Posted by Lord Nyriox on 11 Mar, 2017 11:10
• Hi Phanjam! 
  
  It's really awesome you are helping out, because I am having no luck with either Ordrak or Vyrax (they both crash the same way, so I have been testing them side by side with the same methods). 
  
  There are a few commonalities I would like to note between them, regarding their model data: 
  
  

  • They both have vertex and polygon counts in the thousands. 
  • They both have more than five "Special_" animations for their unique skills. 
  • They both have dedicated non-"Special" animations for alternative methods of locomotion (Turn left/right for Ordrak; "Soar" for Vyrax). 
  • They both have more complex animations involving fine-grained motion (fingers, tail, wings, arms/legs, head/neck, et cetera). 
  • They both use a dedicated collision mesh. 
  • They both naturally spawn underground, or at least with underground lighting.  (Therefore some shortcuts might have been taken with regards to rendering support above-ground.) 
  • EDIT:  They also both have default textures at 1024x1024 pixels (unlike the more conventional 256x256 or 512x512).  Given the suddenness of the crash it could be an "out of memory" error. 

  
  There are a few other commonalities, like the fact that they're both bosses (I was entertaining a theory for a while that boss models might be flagged in some way and forbidden from being used for pets), and they're both dragons (lore-wise, dragons are an endangered species). 
  
  As for testing, could you forward me your spawnclass for the Vyrax model?  I would like to see if spawning Vyrax in the "Upper Wilds" area of Emberfiend crashes the game (if so, number 6 is the cause; the "Upper Wilds" area uses above-ground lighting, like the town and main menu). 
  
  EDIT 2:  Also, I see that you're using my "Dragonkin Overlord" pet in the screenshot.  What do you think of him so far? 
  
  Thanks again,
  - Lord Nyriox
  
  
  
  
  
• 
  
• #6 Reply
  Posted by Lord Nyriox on 11 Mar, 2017 21:50
• To avoid duplicating test results, I'll provide a summary of my proposed tests on the potential model issues listed above.   
  
  

  Quote from: Lord Nyriox on 11 Mar, 2017 11:10

  Spoiler (hover to show)

  • They both have vertex and polygon counts in the thousands. 
  • They both have more than five "Special_" animations for their unique skills. 
  • They both have dedicated non-"Special" animations for alternative methods of locomotion (Turn left/right for Ordrak; "Soar" for Vyrax). 
  • They both have more complex animations involving fine-grained motion (fingers, tail, wings, arms/legs, head/neck, et cetera). 
  • They both use a dedicated collision mesh. 
  • They both naturally spawn underground, or at least with underground lighting.  (Therefore some shortcuts might have been taken with regards to rendering support above-ground.) 
  • EDIT:  They also both have default textures at 1024x1024 pixels (unlike the more conventional 256x256 or 512x512).  Given the suddenness of the crash it could be an "out of memory" error. 

  
  For numbers 2, 3, and 5, I can confirm that removing excess animations and/or meshes from the model directory does not solve the problem.  The crash occurs same as always. 
  
  For numbers 1 and 4, I have neither the tools nor the experience to test with any confidence.  Someone with more experience working with mesh/skeleton data should handle that. 
  
  For number 6, testing should be easy.  Simply spawn either Ordrak or Vyrax in an outdoor area.  As I mentioned above, the "Upper Wilds" area from Emberfiend could be used as a testing ground. 
  
  For number 7, I will downscale the Ordrak and Vyrax textures to 256x256 tomorrow for testing. 
  
  Thanks again,
  – Lord Nyriox,
  Necromancer of Torchlight
  
  
• 
  
• #7 Reply
  Posted by Phanjam on 12 Mar, 2017 04:32
• Quote from: Lord Nyriox on 11 Mar, 2017 11:10

  ...could you forward me your spawnclass for the Vyrax model?  I would like to see if spawning Vyrax in the "Upper Wilds" area of Emberfiend crashes the game (if so, number 6 is the cause; the "Upper Wilds" area uses above-ground lighting, like the town and main menu).
  

  Here you go...
  https://drive.google.com/open?id=0B2aVtkeuHrtcVE5La3FwUndaN2c
  
  "Vyrax as replacement for the dog" is in there too, just disabled; I was trying to test him (unsuccessfully so far) as a pet...
  
  About the commonalities...
  

  Quote from: Lord Nyriox on 11 Mar, 2017 11:10

  Spoiler (hover to show)

  Quote from: Lord Nyriox on 11 Mar, 2017 11:10

  • They both have vertex and polygon counts in the thousands. 
  • They both have more than five "Special_" animations for their unique skills. 
  • They both have dedicated non-"Special" animations for alternative methods of locomotion (Turn left/right for Ordrak; "Soar" for Vyrax). 
  • They both have more complex animations involving fine-grained motion (fingers, tail, wings, arms/legs, head/neck, et cetera). 
  • They both use a dedicated collision mesh. 
  • They both naturally spawn underground, or at least with underground lighting.  (Therefore some shortcuts might have been taken with regards to rendering support above-ground.) 
  • EDIT:  They also both have default textures at 1024x1024 pixels (unlike the more conventional 256x256 or 512x512).  Given the suddenness of the crash it could be an "out of memory" error. 

  If these are what is causing the crashes, then they should do so whether you are spawning them as pets or as enemy monsters.  The fact that they can spawn as monsters but not as pets leads me to believe these are not the cause.
  
  

  Quote from: Lord Nyriox on 11 Mar, 2017 11:10

  I see that you're using my "Dragonkin Overlord" pet in the screenshot.  What do you think of him so far? 
  

  LOL! He is so OP Zipping around killing anything that moves, and I just casually walk over to pick up whatever loot is lying around
• 
  
• #8 Reply
  Posted by Lord Nyriox on 12 Mar, 2017 09:47
• Quote from: Phanjam on 12 Mar, 2017 04:32

  If these are what is causing the crashes, then they should do so whether you are spawning them as pets or as enemy monsters.  The fact that they can spawn as monsters but not as pets leads me to believe these are not the cause.
  

  
  That depends on whether te game loads models for different types of units differently.  I have no idea if that's the case, but it is a possibility. 
  
  Also, have you tried to load Vyrax or Ordrak in town (or at least in an area with sky exposure)?  Until you have, #6 is a possibility. 
  
  

  Quote from: Phanjam on 12 Mar, 2017 04:32

  LOL! He is so OP :D Zipping around killing anything that moves, and I just casually walk over to pick up whatever loot is lying around 8)
  

  
  Yeah, that part does annoy me a little bit.  It's turned into a competition between my Vindicator character and my Dragonkin Overlord pet to see who kills enemies the fastest.  My Vindicator usually wins, but only because monster/pet AI sucks, meaning I notice enemies faster.  (I've been considering adding advanced AI to monsters based on the discussion in https://forums.runicgames.com/viewtopic.php?f=6&t=6187#p145189, because I find monster lemmings so boring.) 
  
  Thanks again,
  ~ Lord Nyriox
  
  
• 
  
• #9 Reply
  Posted by Lord Nyriox on 13 Mar, 2017 07:40
• Huh. This is interesting.
  
  I don't know how exactly you managed to summon "vyraxtest", but I tried to use the console to do it (I don't really know any other method).
  
  I typed in

  Code: [Select]

  vyraxtest into the console in the mines, and—BAM—the exact same crash-out I get loading Ordrak and Vyrax at the menu.
  
  Just a reminder, the console command I typed would have placed the dragon right where I was standing.
  
  Which makes me wonder: perhaps pets somehow start out rendering with their coordinates at the exact same place as the player. 
  
  If so, then we just need to figure out why these models in particular crash the instant it happens, even though no other models do. 
  
  Just a thought,
  – Lord Nyriox
  
  
• 
  
• #10 Reply
  Posted by Phanjam on 13 Mar, 2017 09:33
• Hmmm, yes I spawned him the same way (typed in "vyraxtest" in the console), but I got him into the game 
  
  About the spawn-point; could the collision.mesh file have something to do with the crashing? If the unit is spawning in the exact same location as you and the collision mesh is saying "noooooooooo!!!!!" Just a thought (I need some sleep right now see you in a bit!)
• 
  
• #11 Reply
  Posted by Lord Nyriox on 13 Mar, 2017 13:43
• Quote from: Phanjam on 13 Mar, 2017 09:33

  could the collision.mesh file have something to do with the crashing?
  

  
  See my prior comment:
  

  Spoiler (hover to show)

  Quote from: Lord Nyriox on 11 Mar, 2017 21:50

  For numbers 2, 3, and 5, I can confirm that removing excess animations and/or meshes from the model directory does not solve the problem.   
  

  
  Removing the "collision.mesh" file was one of my earliest tests, as was removing excess animations.  Neither solved the problem for me. 
  
  But actually, what I was thinking was that the models themselves might have been designed with external collision in mind. 
  
  Given that they are both unique models designed exclusively for use as bosses, all sorts of shortcuts could have been taken with regards to their design.
  
  Then again, it might be just the fact that I tried to type it at level 1, right after entering the mines for the first time.  ;} 
  
  – Nyriox
  
  
• 
  
• #12 Reply
  Posted by Matthew Lefferts on 16 Mar, 2017 12:37
• Hey hey folks!
  
  I'm Matt Lefferts, lead animator over at Runic. 
  Obviously it's been a while since I've worked first hand on TL1 or TL2, but the animation count, or the complexity like having fingers animated, shouldn't be an issue.
  
  When your game runs, it should generate an "Ogre Log" file in the same general location as your save folder, or where screen shots are stored.  (see the attached image).
  
  Run the game and get it to crash in the same way, then check the Ogre log file, all the way at the very bottom.  Post up that information so we can see what it says.  This is one way that I debugged a lot of stuff when working on the game.
• 
  
• #13 Reply
  Posted by Lord Nyriox on 16 Mar, 2017 16:31
• @Matthew Lefferts:   
  
  Steps to reproduce: 
  

  • Modify a pet's .DAT file to point to the model directory and mesh file of Ordrak or Vyrax.
  • At the character selection screen, click on the button for the pet that was modified.
  • Swear like a sailor as the game INSTANTLY crashes to the desktop with "Torchlight game executable stopped working".

  
  Note that the problem does not occur when using these models for a normal monster.  The crash only affects pets that use them. 
  
  Entire content of the Ogre.log file afterwards: 
  
  

  Spoiler (hover to show)

  10:03:30: Creating resource group General
  10:03:30: Creating resource group Internal
  10:03:30: Creating resource group Autodetect
  10:03:30: SceneManagerFactory for type 'DefaultSceneManager' registered.
  10:03:30: Registering ResourceManager for type Material
  10:03:30: Registering ResourceManager for type Mesh
  10:03:30: Registering ResourceManager for type Skeleton
  10:03:30: MovableObjectFactory for type 'ParticleSystem' registered.
  10:03:30: OverlayElementFactory for type Panel registered.
  10:03:30: OverlayElementFactory for type BorderPanel registered.
  10:03:30: OverlayElementFactory for type TextArea registered.
  10:03:30: Registering ResourceManager for type Font
  10:03:30: ArchiveFactory for archive type FileSystem registered.
  10:03:30: ArchiveFactory for archive type Zip registered.
  10:03:30: FreeImage version: 3.10.0
  10:03:30: This program uses FreeImage, a free, open source image library supporting all common bitmap formats. See

  The FreeImage Project

  freeimage.sourceforge.net

  for details
  10:03:30: Supported formats: bmp,ico,jpg,jif,jpeg,jpe,jng,koa,iff,lbm,mng,pbm,pbm,pcd,pcx,pgm,pgm,png,ppm,ppm,ras,tga,targa,tif,tiff,wap,wbmp,wbm,psd,cut,xbm,xpm,gif,hdr,g3,sgi,exr,j2k,j2c,jp2
  10:03:30: DDS codec registering
  10:03:30: Registering ResourceManager for type HighLevelGpuProgram
  10:03:30: Registering ResourceManager for type Compositor
  10:03:30: MovableObjectFactory for type 'Entity' registered.
  10:03:30: MovableObjectFactory for type 'Light' registered.
  10:03:30: MovableObjectFactory for type 'BillboardSet' registered.
  10:03:30: MovableObjectFactory for type 'ManualObject' registered.
  10:03:30: MovableObjectFactory for type 'BillboardChain' registered.
  10:03:30: MovableObjectFactory for type 'RibbonTrail' registered.
  10:03:30: Loading library .\RenderSystem_Direct3D9
  10:03:30: Installing plugin: D3D9 RenderSystem
  10:03:30: D3D9 : Direct3D9 Rendering Subsystem created.
  10:03:30: D3D9: Driver Detection Starts
  10:03:30: D3D9: Driver Detection Ends
  10:03:30: Plugin successfully installed
  10:03:30: Loading library .\Plugin_ParticleFX
  10:03:30: Installing plugin: ParticleFX
  10:03:30: Particle Emitter Type 'Point' registered
  10:03:30: Particle Emitter Type 'Box' registered
  10:03:30: Particle Emitter Type 'Ellipsoid' registered
  10:03:30: Particle Emitter Type 'Cylinder' registered
  10:03:30: Particle Emitter Type 'Ring' registered
  10:03:30: Particle Emitter Type 'HollowEllipsoid' registered
  10:03:30: Particle Affector Type 'LinearForce' registered
  10:03:30: Particle Affector Type 'ColourFader' registered
  10:03:30: Particle Affector Type 'ColourFader2' registered
  10:03:30: Particle Affector Type 'ColourImage' registered
  10:03:30: Particle Affector Type 'ColourInterpolator' registered
  10:03:30: Particle Affector Type 'Scaler' registered
  10:03:30: Particle Affector Type 'Rotator' registered
  10:03:30: Particle Affector Type 'DirectionRandomiser' registered
  10:03:30: Particle Affector Type 'DeflectorPlane' registered
  10:03:30: Plugin successfully installed
  10:03:30: Loading library .\Plugin_CgProgramManager
  10:03:30: Installing plugin: Cg Program Manager
  10:03:30: Plugin successfully installed
  10:03:30: Loading library .\Plugin_OctreeSceneManager
  10:03:30: Installing plugin: Octree & Terrain Scene Manager
  10:03:30: Plugin successfully installed
  10:03:30: Loading library .\ParticleUniverse
  10:03:30: Installing plugin: ParticleUniverse
  10:03:30: MovableObjectFactory for type 'PUParticleSystem' registered.
  10:03:30: MovableObjectFactory for type 'BoxSet' registered.
  10:03:30: MovableObjectFactory for type 'SphereSet' registered.
  10:03:30: ParticleUniverse: Particle Renderer Type 'Billboard' registered
  10:03:30: ParticleUniverse: Particle Renderer Type 'Box' registered
  10:03:30: ParticleUniverse: Particle Renderer Type 'Sphere' registered
  10:03:30: ParticleUniverse: Particle Renderer Type 'Entity' registered
  10:03:30: ParticleUniverse: Particle Renderer Type 'RibbonTrail' registered
  10:03:30: ParticleUniverse: Particle Renderer Type 'Light' registered
  10:03:30: ParticleUniverse: Particle Emitter Type 'Point' registered
  10:03:30: ParticleUniverse: Particle Emitter Type 'Line' registered
  10:03:30: ParticleUniverse: Particle Emitter Type 'Box' registered
  10:03:30: ParticleUniverse: Particle Emitter Type 'Circle' registered
  10:03:30: ParticleUniverse: Particle Emitter Type 'SphereSurface' registered
  10:03:30: ParticleUniverse: Particle Emitter Type 'Vertex' registered
  10:03:30: ParticleUniverse: Particle Emitter Type 'MeshSurface' registered
  10:03:30: ParticleUniverse: Particle Emitter Type 'Position' registered
  10:03:30: ParticleUniverse: Particle Emitter Type 'Slave' registered
  10:03:30: ParticleUniverse: Particle Affector Type 'Dummy01' registered
  10:03:30: ParticleUniverse: Particle Affector Type 'LinearForce' registered
  10:03:30: ParticleUniverse: Particle Affector Type 'Gravity' registered
  10:03:30: ParticleUniverse: Particle Affector Type 'ParticleFollower' registered
  10:03:30: ParticleUniverse: Particle Affector Type 'Vortex' registered
  10:03:30: ParticleUniverse: Particle Affector Type 'Randomiser' registered
  10:03:30: ParticleUniverse: Particle Affector Type 'Line' registered
  10:03:30: ParticleUniverse: Particle Affector Type 'Scale' registered
  10:03:30: ParticleUniverse: Particle Affector Type 'GeometryRotator' registered
  10:03:30: ParticleUniverse: Particle Affector Type 'TextureRotator' registered
  10:03:30: ParticleUniverse: Particle Affector Type 'TextureAnimator' registered
  10:03:30: ParticleUniverse: Particle Affector Type 'Jet' registered
  10:03:30: ParticleUniverse: Particle Affector Type 'Align' registered
  10:03:30: ParticleUniverse: Particle Affector Type 'FlockCentering' registered
  10:03:30: ParticleUniverse: Particle Affector Type 'CollisionAvoidance' registered
  10:03:30: ParticleUniverse: Particle Affector Type 'VelocityMatching' registered
  10:03:30: ParticleUniverse: Particle Affector Type 'Colour' registered
  10:03:30: ParticleUniverse: Particle Affector Type 'SineForce' registered
  10:03:30: ParticleUniverse: Particle Affector Type 'Dummy02' registered
  10:03:30: ParticleUniverse: Particle Affector Type 'SphereCollider' registered
  10:03:30: ParticleUniverse: Particle Affector Type 'PlaneCollider' registered
  10:03:30: ParticleUniverse: Particle Affector Type 'BoxCollider' registered
  10:03:30: ParticleUniverse: Particle Affector Type 'InterParticleCollider' registered
  10:03:30: ParticleUniverse: Particle Affector Type 'PathFollower' registered
  10:03:30: ParticleUniverse: Particle Observer Type 'OnExpire' registered
  10:03:30: ParticleUniverse: Particle Observer Type 'OnEmission' registered
  10:03:30: ParticleUniverse: Particle Observer Type 'OnCount' registered
  10:03:30: ParticleUniverse: Particle Observer Type 'OnEventFlag' registered
  10:03:30: ParticleUniverse: Particle Observer Type 'OnCollision' registered
  10:03:30: ParticleUniverse: Particle Observer Type 'OnVelocity' registered
  10:03:30: ParticleUniverse: Particle Observer Type 'OnTime' registered
  10:03:30: ParticleUniverse: Particle Observer Type 'OnPosition' registered
  10:03:30: ParticleUniverse: Particle Observer Type 'OnClear' registered
  10:03:30: ParticleUniverse: Particle Observer Type 'OnQuota' registered
  10:03:30: ParticleUniverse: Particle Observer Type 'OnRandom' registered
  10:03:30: ParticleUniverse: Particle EventHandler Type 'DoExpire' registered
  10:03:30: ParticleUniverse: Particle EventHandler Type 'DoFreeze' registered
  10:03:30: ParticleUniverse: Particle EventHandler Type 'DoPlacementParticle' registered
  10:03:30: ParticleUniverse: Particle EventHandler Type 'DoStopSystem' registered
  10:03:30: ParticleUniverse: Particle EventHandler Type 'DoEnableComponent' registered
  10:03:30: ParticleUniverse: Particle EventHandler Type 'DoAffector' registered
  10:03:30: ParticleUniverse: Particle EventHandler Type 'DoScale' registered
  10:03:30: ParticleUniverse: Particle Extern Type 'Gravity' registered
  10:03:30: ParticleUniverse: Particle Extern Type 'SphereCollider' registered
  10:03:30: ParticleUniverse: Particle Extern Type 'BoxCollider' registered
  10:03:30: ParticleUniverse: Particle Extern Type 'Vortex' registered
  10:03:30: ParticleUniverse: Particle Behaviour Type 'Slave' registered
  10:03:30: Plugin successfully installed
  10:03:30: *-*-* OGRE Initialising
  10:03:30: *-*-* Version 1.6.4 (Shoggoth)
  10:03:30: Path for saving is ... C:/Users/Solkona/AppData/Roaming/Runic Games/Torchlight/SAVE
  10:03:30: Setting YRatio Init - 1.40625
  10:03:54: CreateViewports AspectRatio message - 1920 x 1080
  10:03:54: CreateViewports AspectRatio message AR - 1.77778
  10:03:54: GAMEUI AspectRatio message - 1920 x 1080
  10:03:54: GAMEUI AspectRatio message AR - 1.77778
  

  
  That is the entire content of the file.  I have no idea if that is helpful or not. 
  
  Thank you for your support,
  - Lord Nyriox
  
  
• 
  
• #14 Reply
  Posted by Matthew Lefferts on 16 Mar, 2017 16:43
• Dang.  Nothing shows up in the Ogre Log that suggests where the problem occurred.
  
  We've been thinking about it on our end and the first thing I would try is stripping out Ordrak's skills, one by one.  In theory he may have a skill that specifically tries to target the player or summon things it can't find, and that's what's causing the issue.
  
  It's also highly likely that characters like Ordrak exceed the bone count for hardware skinning, so if you have any flags in there for that it would cause it to crash.
•