Since its latest update, @EchoRed, @pascal76680, @PayDay and I from Phoenix Interactive started using the new version of HODOR 2.0. Unfortunately, we’re having issues with our models, and our content doesn’t work anymore.
Basically, the main issue is that HODOR can’t locate the SHADER.MAP entry for innateSS - MAT[hw2Shader]_SHD[innateSS].
Here’s the full log:
-- Scan Path: D:\Program Files (x86)\Steam\steamapps\common\Homeworld\HomeworldR M\Data\subsystem\tau_research_module DAE->HOD: Loading D:\Program Files (x86)\Steam\steamapps\common\Homeworld\Homewo rldRM\Data\subsystem\tau_research_module\DAE\tau_research_module.DAE DAE->HOD: Creating Homeworld2 Multi Mesh File - Version 512 Parsing SHADERS.MAP DAE->HOD: Unable to locate SHADER.MAP entry for innateSS - MAT[hw2Shader]_SHD[in nateSS] - using generic! DAE->HOD: Creating STAT[hw2Shader] with Shader[innateSS] DAE->HOD: Generating Scene Data LOD DAE->HOD: Generating Animation Channels XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Scan Complete!
HODOR doesn’t crash but the game encounters an issue with the new .HOD files, which results in a CTD.
Starting Level: DATA:\LevelData\Multiplayer\demoSSC\2p_abydos.level HOD Trace: data:SubSystem\TAU_RESEARCH_MODULE\TAU_RESEARCH_MODULE.hod HOD Trace: data:SubSystem\TAU_MIDWAY_SHIELD\TAU_MIDWAY_SHIELD.hod Unknown mesh group type (1) -- FATAL EXIT -- basicmesh/602:! --stack trace-- Display: (0, 0, 100, 100) - (8, 31)
As you can see, the game doesn’t recognize the “mesh group type”. We could probably philosophy on the meaning of this haha, but in all seriousness we have the same issue each time we use HODOR to port our content.
PS: Of course, our DAEs are not corrupted