Sidney Schwartz
Resource contributor
- Messages
- 514
- Country

I have a SU model I may want to add one or two LODs to. I much prefer to make my own LODs rather than use the auto function in MCX. There's not much in the way of instruction, though, on importing LODs.
1. The LOD import function seems to give the same file type choices that the regular import function does. Does this mean I can import an unprocessed dae as an LOD?
2. How do the textures work? Let's say my main model is TERMINAL. It's been processed by MCX and the textures are named TERMINAL0.BMP, TERMINAL1.BMP, etc. I then modify TERMINAL and export it as TERMINALLOD40.dae. What now? Can I open TERMINAL in MCX and import TERMINALLOD040.dae as is, or do I first have to convert TERMINALLOD040.dae to an mdl? If have to convert it to an mdl before importing as an LOD for TERMINAL, do I have to rename the textures so they are the same as those used by TERMINAL?
Any clues would be appreciated. If there are already step-by-step instructions somewhere for doing this, it sure would be nice to have some.
1. The LOD import function seems to give the same file type choices that the regular import function does. Does this mean I can import an unprocessed dae as an LOD?
2. How do the textures work? Let's say my main model is TERMINAL. It's been processed by MCX and the textures are named TERMINAL0.BMP, TERMINAL1.BMP, etc. I then modify TERMINAL and export it as TERMINALLOD40.dae. What now? Can I open TERMINAL in MCX and import TERMINALLOD040.dae as is, or do I first have to convert TERMINALLOD040.dae to an mdl? If have to convert it to an mdl before importing as an LOD for TERMINAL, do I have to rename the textures so they are the same as those used by TERMINAL?
Any clues would be appreciated. If there are already step-by-step instructions somewhere for doing this, it sure would be nice to have some.
