Severity:High
(Low - quality of life, workflow optimization, rare enough to not impact production, etc…
High - critical but workarounds are available, important feature not working as expected, frequent enough to impact production
Blocker - prevents from working on the project, prevents from releasing the product)
Bug description:The Built Airport with the Beacon Object inserted is displaying the Beacon well above the position it was placed in the scenery editor. The height above the ground is also slightly different with only the project loaded, but not the Scenery Editor.
**Repro steps:
Create 1ft x 1ft cube in Blender. Set at 0.5ft above ground. Name Mesh “BeaconX”
Place Object in Scenery using Scenery Editor and set vertical height to 100ft or 30-31m.
Set “Has Beacon” and mesh name BeaconX.
Set to Airfield Civilian.
Build**
You have defined a single LOD with minSize set to 0 on the object you attach the beacon to.
With LOD restrictions, your object is only loaded when the camera is very close to it.
If not, your object is not loaded, and the node is not found.
If the node the beacon is attached to is not found in the scene, the beacon will be placed 30 meters above ground level. This is the default behavior inherited from previous versions of Microsoft Flight Simulator.
What you want to do is create proper LODs for your object, and make sure the node you want to attach the beacon to is present in all LODs.
If you don’t want any geometry in your object and are only interested in the beacon, you might want to consider using SimPropContainer lights instead, street lights in particular:
@FlyingRaccoon Does this mean the beacon location is not re-evaluated once the “attachment-node” appears in the scene as the camera is getting closer and the LOD containing the node is rendered?
No it is, and will be “snapped” to the node as soon as it appears.
And then the position is kept in memory so if the model is unloaded, the beacon will keep its position.