ProjectedMesh layer disappears upon Blender Export

Version: 1.8.8.0

Frequency: Consistently

Severity: High

Context: When exporting a Blender ground poly/ProjectedMesh into FS2024, SU6 Beta, ProjectedMesh layer disappears.

Bug description: In the past few days I’ve been experiencing a very frustrating issue with the export of ProjectedMesh from Blender.

Previously, when exporting from Blender with an updated version of the Ground Poly I’m creating, the ProjectedMesh layer in the simulator would update in real time as soon as I pressed the Export button. I’m using the latest version of the SDK 1.7.2 with the associated Blender plugin 7.4.2.

There doesn’t seem to be anything that’s changed in my export workflow. None of the materials, exported Object names, file names or file paths have changed since I last had my normal experience.

Now, when I export the ProjectedMesh layer into the sim, as soon as the sim realises the file has refreshed, the layer disappears. I can only make it re-appear by a mix and match combination of building the project again, Closing the Project in the Project Editor, and re-opening it again. The interesting thing is, that once I manage to get it to show again, it appears just as I exported from Blender, and the updated version appears.

I get no build errors in the SDK, nor do I get any export errors in Blender. All transformations are applied as normal before I export the file, and this issue recurs upon any of the ProjectedMesh layers that are imported to the simulator, not just a certain one.

Repro steps: As above.

Attachments: https://youtu.be/K6tlkxN2PSg video showing the issue.

Hello @morganthomas757

Can you make sure you are using the “View only current package” option in the Scenery Editor “Edit” menu and try again please ?

Hi Romain,

Selecting ‘View only current package’ in the Scenery Editor ‘Edit’ tab makes no difference unfortunately, but thanks for the suggestion.

A bit of a longer video uploaded this time. Please note how the ProjectedMesh only becomes visible once I close the Package in the Package Editor. Exporting does not make the ProjectedMesh show up again, and opening the Scenery Editor makes the layer disappear. Also note that towards the end of the video, my Sim completely locked up and froze/CTD, hence I cut the recording. This happens about nearly 50% of the time currently I’d say.

Upon first glance, it seems to be a similar, if not the same issue to the one RWProfiles is having, a mixture of missing objects and sim lockups/CTDs when exporting from Blender to the sim. If this could please be looked into urgently, it would be greatly appreciated!

Hello @morganthomas757 ,

I have reproduced the problem on my side.
The bug has been logged on our side.
For the crashes, can you please send us the dump ?

Thanks for the report.

As the sim locked up, I don’t have a crash dump as such, but if it happens again, I will send it.

On a seperate note, I tried to roll back to SDK version 1.6.9, which has Blender plugin version 6.4.9, but I still have the same behaviour.

Do you know if this is a bug with the Blender Exporter or SU6 itself?

So I rolled back even further to SDK Core 1.6.6 with Blender Plugin 6.4.6, and still the same behaviour. ProjectedMeshes do not show once the Scenery is loaded in Scenery Editor, only when the project is closed in Project Editor.

This doesn’t seem to be quite the same problem as RW Profiles is having with the missing textures, as rolling back to this plugin version fixed it for him.

I will await patiently a fix to this problem, as all of my scenery work currently is concentrated on the ProjectedMesh I am creating, so can’t continue until it is fixed unfortunately.

A temporary work-around might be to separate your Projected mesh from the package, and make a separate compiled package of that PJ. Then add that to your Community folder, and a restart of the sim should show the mesh consistently. Just an idea to use until a fix is provided.

I appreciate there were no patch notes relating to it, but this issue is still present in the latest build 1.8.10.0. Just curious if a fix for the problem has been identified yet?

Hello @morganthomas757

A fix is planned for a later SU6 Beta build, likely 1.8.11.0

Regards,
Sylvain

1 Like

Thanks for the new build of SU6 Beta (1.8.11.0), and mentioning it in the changelog! It has fixed the issue so I’m a happy person! :grinning_face:

1 Like

Hello @morganthomas757 ,

The bug has been fixed in the latest build 1.8.11.0.
Make sure to apply all the transformations to the mesh before the export.
And put the origin of all the same object to the origin of the scene.

Can you confirm the fix on your side?

Hi Romain,

As above, the new build has fixed the issue for me. Many thanks for your team looking into this!

1 Like