scottdmilner / dungeon-pipeline

Pipeline for BYU Animation's Class of 2025 capstone film
BSD 3-Clause "New" or "Revised" License
6 stars 4 forks source link

Dungaya crashes when trying to open file #200

Open scottdmilner opened 1 month ago

scottdmilner commented 1 month ago

Issue submitted via PipeBot Reporting user: Erik Bostrom


Trying to open previs scene file that was working yesterday and it just closes itself. Diego also had a crash when trying to build a new anim scene.

scottdmilner commented 1 month ago

Something about the instancers we're using for the coins is causing a division by zero error that's crashing Maya whenever we try to open that layout file. Blocking loading on those instancers is a temporary fix

BigRoy commented 1 month ago

If you have a reproducable crash case - this would be great to share with Autodesk support team for them to investigate.

Also, I'd like to mention that 'crashing' on scene open usually goes with debugging steps like:

Also - with crashes like these it'd be best to share the crash .log and .dmp files that often get generated in the %TEMP% with Autodesk too.

scottdmilner commented 1 month ago

Thanks for the tips @BigRoy!

I've narrowed the crash down to a specific asset that is being brought in as part of a set via a USD Stage. This particular asset has a point instancer in it and something in there is causing the crash. I've determined that the assets being instanced by the instancer aren't the issue, so Maya really doesn't like something about the instancer itself. The instancer works fine in Solaris (where it originated).

Currently trying to strip down the asset with the instancer to get an MWE that will trigger the crash

scottdmilner commented 1 month ago

Hmmm this may be an instance of this issue: https://github.com/PixarAnimationStudios/OpenUSD/issues/2149

scottdmilner commented 1 month ago

That is indeed the issue. Ensuring that each variant of the asset uses all of the instancer's prototypes fixes the problem. Will test in Maya 2025 as the issue should be fixed there.