LODs
LODs
Some cars, when importing to zModeler after being unlocked, have some weird texture bugs, like on this car, L0 has white taillights, while L1 hast red taillights, i tried exporting all but highest but it still has L0 and L1 with the same texture bug, is there any way, to move the L1 to L0 within the taillights hierarchy?
Re: LODs
Unlocking models is a bad idea on its own. Models are locked to prevent someone editing the models.
Concerning the LODs in your question, I'm not quite sure what exactly is wrong or what do you mean there. You can manage LODs manually on every part. In particular, you can disassemble compound object (taillight) to get geometry objects for every LOD stored there; then you can manage these geometries (copy, if needed) and assemble compound again by assigning geometries for every LOD you need. For example, if the geometry for some LOD is a correct one, you can extract it, duplicate and assign it as a geometry for L0 and L1. It's up to you to decide what exactly you need.
If your top hierarchy element has "_hi" in name, an exporter will consider that this model has highest LOD in scene (L0). An export to "*****_hi.yft" file will export L0 components from compound elements. An export to "******.yft" will export L1..L4 lods and omit L0 states. These are "Export highest" and "Export all but highest" modes respectively. This is the exact behavior of exporter when LODs: "Autodetect" mode is used.
Concerning the LODs in your question, I'm not quite sure what exactly is wrong or what do you mean there. You can manage LODs manually on every part. In particular, you can disassemble compound object (taillight) to get geometry objects for every LOD stored there; then you can manage these geometries (copy, if needed) and assemble compound again by assigning geometries for every LOD you need. For example, if the geometry for some LOD is a correct one, you can extract it, duplicate and assign it as a geometry for L0 and L1. It's up to you to decide what exactly you need.
If your top hierarchy element has "_hi" in name, an exporter will consider that this model has highest LOD in scene (L0). An export to "*****_hi.yft" file will export L0 components from compound elements. An export to "******.yft" will export L1..L4 lods and omit L0 states. These are "Export highest" and "Export all but highest" modes respectively. This is the exact behavior of exporter when LODs: "Autodetect" mode is used.
Re: LODs
I have a hard time explaining so bear with me.
L0 has white tail lights
L1 has red tail lights
I've tried the same procedure when creating LODs for optimization, copied the texture, dismiss it, renamed the 2 textures L0 and L1 and reassigned each one to the respective LOD, HOWEVER, the L0 went to L2 and the L1 went to L3, what im asking is, is there any way to remove the L0 which has the white tail lights, and replace it with the L1 which has the red tail lights?
L0 has white tail lights
L1 has red tail lights
I've tried the same procedure when creating LODs for optimization, copied the texture, dismiss it, renamed the 2 textures L0 and L1 and reassigned each one to the respective LOD, HOWEVER, the L0 went to L2 and the L1 went to L3, what im asking is, is there any way to remove the L0 which has the white tail lights, and replace it with the L1 which has the red tail lights?
Re: LODs
I've managed to get around this problem, but now i tried to add extra pieces to the front bumper and this happend. https://imgur.com/HnJ2pJI
Re: LODs
if you make any changes in hierarchy, you have to update both model.yft file and model_hi.yft file. Perfectly, these should be exported from one scene as specified above and mind to export and put into the game both files each time you make changes.