Modular aircraft not responding correctly to model.cfg

[MSFS 2024] Questions & Community Discussions Aircraft
1

Hello,

I have a modular aircraft setup, exterior + interior separate models.
One unique variant
empty helper on my common folder.

My exterior model is attached to the helper via attached_objects.cfg located inside my variant/config folder. Interior model is attached to helper via the same file

[sim_attachment.0]
attachment_root = "SimObjects\Airplanes\dev\attachments\dev\aircraftname_ext"
attachment_file = "model/aircraftname.xml"
attach_to_model = "exterior"
attach_to_model_minsize = 0
always_execute_associate_js = 1
always_execute_model_behavior = 1
alias = "Exterior"

[sim_attachment.1]
attachment_root = "SimObjects\Airplanes\dev\attachments\dev\aircraftname_int"
attachment_file = "model/aircraftname_interior.xml"
attach_to_model = "interior"
always_execute_associate_js = 1
always_execute_model_behavior = 1
; Should be named "Interior" if you only have 1 Variant without Livery Selection Requirments (Otherwise Use Tag from Attachments.cfg)
alias = "Interior"

My model.cfg is on common/model. I have all 4 options set to true

The issue comes when I compile and load the aircraft into the sim. In Internal camera I cannot see external model, and ext camera I can’t see the internal. Completely ignoring my model.cfg. This also causes issues when entering and exiting the aircraft, as you would only see the cockpit floating, though sometimes both are visible - its really inconsistent.

My workaround was to attach both interior and exteriors models to the interior and exterior helpers. That way I have both always visible (and I can use specific LOD submodels). However, this is probably not ideal, and I have a feeling I’m missing something here.

1st party aircraft @FlyingRaccoon

1 Like
2

Two things may be happening here:

  • Make sure your model.cfg in the common folder (helper) is correctly setup for your specific aircraft requirements.
  • Make sure it’s not an LOD culling issue. In dev-mode, open the LOD Debug Tool and Force LODs to LOD 0 and see if the sim is culling your models. If they are, you need to optimize your LODs further using the new documented LOD Selection System.
2 Likes
3

Forced active LOD - none of my interior models will render on the external camera, no matter which LOD I force it to.

And as far as I understand, I have my helper correctly setup.

[model.options]
withExterior_showInterior=1
withExterior_showInterior_hideFirstLod=1
withInterior_forceFirstLod=1
withInterior_showExterior=1

[models]
interior = interior.xml
exterior = exterior.xml

I have both interior.xml and exterior.xml on the same folder, both look like this

<?xml version="1.0" encoding="utf-8"?>
<ModelInfo>
	<LODS>
		<LOD ModelFile="Helper.gltf"/>
	</LODS>
</ModelInfo>

And my attached_objects.cfg

[sim_attachment.1]
attachment_root = "SimObjects\Airplanes\dev\attachments\dev\aircraftname_int"
attachment_file = "model/aircraftname_interior.xml"
attach_to_model = "interior"
always_execute_associate_js = 1
always_execute_model_behavior = 1
; Should be named "Interior" if you only have 1 Variant without Livery Selection Requirments (Otherwise Use Tag from Attachments.cfg)
alias = "Interior"
4

Did you resolve this?

5

Not quite. LODs are very inconsistent on Modular Builds with large aircraft, and we don’t get the results we wanted. Abandoned the modular build temporarily.

1 Like