To help and consolidate this issue i'm linking out to a post I made this morning on the Aximmetry Facebook group with some vision/examples to help diagnose :

https://www.facebook.com/groups/240516383914797/permalink/760117231954707/

Hi,

Do you have the Use Io Store Project Setting enabled?:

If turning this on doesn't fixes it, does this happen with the newest version of Aximmetry (non beta unreal)?

Warmest regards,

Hi Eifert,

I can say that setting is on in my UE5 (non Beta) and the issue is present (as shown in your Facebook group posts i link to)

I also posted a mention that in UE5.1 (preview1) there's a recommendation/requirement for SM6 support for Nanite whereas in your UE5 I can't Cook Content with that SM6 setting enabled (so i go back to the SM5 default setting)

The videos I show on the post show the sticky behaviour where performance drops when the camera moves (Nanite streaming) but settles back to a decent frame rate once the camera stops (Nanite streaming isn't active)

Hi Renbry,

The SM6 will be fixed in the next version.

We are investigating the issues with Nanite including the performance one.

Warmest regards,

Amazing!

I'm happy to stay on the Beta program, if it continues. I'm not in a commercial environment yet, so I can easily upgrade to newer and newer betas. Meanwhile I'm building out a huge library of Nanite/Lumen heavy scenes as you may have scene with the Alley Way which has ~6x 40million mesh buildings (Nanite) and ~60x 8k textures (Virtual Textures) which is the heaviest of my datasets so far.

Matt Hermans

Hi, just to check in on this one, as experiencing it no a project today. IO Store is enabled within the project packaging settings, was on by default. Any updates? (Using latest broadcast version, not beta)

Hi,

Unreal Editor for Aximmetry has been upgraded to Unreal 5.1 in Aximmetry 2023.1.0: https://aximmetry.com/learn/software-version-history/#%E2%96%BA-latest-2023-1-0

The above issues should no longer happen in the new version. If you are still experiencing them after upgrading, please report them here.

Warmest regards,

Hi Eifert,

Thank you for the update. I can confirm the nanite-related performance bugs seem to have gone from the initial testing I've done. That's great news! 

Hi folks.

We are experiencing the same nanite-related issue in Aximmetry v 2023.2.2. Exact same performance warning and serious frame drops when the camera moves, rendering the virtual set unusable for production. Io store is enabled in the settings.

We are experiencing this with a new virtual set utilizing assets, blueprints, and architecture bought from the Epic Store. Other virtual sets with nanite enabled work fine. Any way to resolve this?

Hi,

You should try cooking again after enabling Use Io Store.

You could try using DirectX12 and only SM6 in Unreal Editor's Project Settings:

And never select the ES3.1 options.

If this does not help, we might be able to tell what is going wrong if you share your Unreal Project Settings. Unreal Project Settings is saved into this file: ...YourProject'sFolder\Config\DefaultEngine.ini

Warmest regards,

Hi Eifert,

Thanks for the prompt response. I went into the level blueprint and deleted everything that came with the scene I bought on Epic Games and kept only Aximmetry triggers and blueprints. That resolved the issue - nanite didn't like something in the level blueprint, not sure what it was. 

Will keep the above in mind if we run into the same issue. Thanks again, cheers.