3DS Max 2019 crashes when selecting objects in Scene explorer

[Anonymous]

Finding this issue present in 3ds Max 2019 - how is this still an issue 3 years later, I don't understand.

Your comment has been made into a new thread by @hagen.deloss: here is the original thread

[hagen.deloss]

Hello @Anonymous

Thanks for posting this issue in the forums! I have a few questions so we can hopefully narrow down the problem. 

Do you find that it crashes when you select anything in the scene explorer, or just objects? Do you have any other selection issues, such as selections in the viewport crashing, or another part of the UI crashes when you select it?

I look forward to hearing back from you!

[Anonymous]

The issue occurs in a scene where I have 1000 objects specifically the objects 535-599 (ish) seem to crash the scene when I select them in the scene view - my suspicion was that it is down to the modifiers on those objects, as the majority of the 1000 objects were generated by a script.

Selecting the troublesome objects in the scene viewport also caused it to crash

What was interesting though, was that if I used 'H' to open the object selection menu, and selected the objects, it wouldn't crash and the modifiers on the objects were fine. But alas, selecting them again in the scene view would cause the program to hang indefinitely.

I am happy to provide the scene for checking, or if there is an editor log that I could provide if at all helpful - have attached it with this response, shouldn't need any texture maps or dependancies to crash either, have checked on another PC here.

It was rather frustrating as I needed to select the objects to delete them! My workaround for now is to use the 'H' key selection menu then right clicking and deleting them in the scene view.. 

Rob

[Anonymous · Accepted solution]

This crash has nothing to do with SceneExplorer. There`s something going on with Object_Part_537 in your scene.

Unlike the other objects in your scene it has a specific modifier setup.If you select this specific object the scene crashes.It doesn`t matter how you select it.

[brentscannell]

Great investigation work @Anonymous!

Regardless of what's making it crash..a crash is a crash and its bad. @Anonymous Can you share the details about the script creating this object? Was in crashing in previous versions of 3ds Max? Did you send in a CER report, and if so, do you have the report number handy or can you direct message me your email address so that I can look it up?

[hagen.deloss · Accepted solution]

Hi @Anonymous

Thanks for sending me the scene! it was super helpful in figuring out *some of whats going on. I encountered the same crash as you in the scene you attached, so I loaded it up and narrowed it down to one object, Object_Part_537. So i saved out everything in the scene besides that object, and then merged it into a new scene. I haven't experienced any crashes in the new scene!

I did notice that the object was right before Object_Part_534....looks like there is 2 missing objects in that sequence. I'm not sure what script you used to create this mesh, I just wanted to point out that discrepancy, I'm sure there is a correlation between the missing numbers and selection issue.

I hope this helps with the issue! You may also need to re-simulate this if the issue persists. Let me know how you decide to proceed 😄

Please select the Accept as Solution button if a post solves your issue or answers your question.

[hagen.deloss]

@Anonymous

You figured it out! How did you get the modifier stack to show up before it crashed on you? 

[brentscannell]

So on my machine, I tried to reproduce and see if I can get my own CER..it did indeed freeze like crazy (I was able to see the modifier stack)..however I left the app to go do other things while waiting to see if a CER window popped up..and when I got back to 3ds Max a few minutes later..it was unfrozen and now I can select/deselect it it as much as I want without freezing or crashing. Strange..

[Anonymous]

@Anonymous I was midway through deleting problematic objects before sending you the file, the missing parts of the object list were deleted by me as they were causing a crash, they definitely had the same modifier stack.

[Anonymous]

Hi @brentscannell
I have attached the scripts (unless they aren't allowed to attach) I used to generate the objects - fracture voronoi (http://www.scriptspot.com/3ds-max/scripts/fracture-voronoi) to generate a set of fragments up to 1000. Noticed no problems there. I then used Fragnoiser (http://www.scriptspot.com/3ds-max/scripts/fragnoiser) to add some noise to specific faces on the fragments to add some variation to them, I didn't notice any problems on the one fragment I tested but the script wasn't very handy - I saw it added the noise modifier to fragments. I then gave up using fragnoiser and added the noise modifier to a few of the fragments, while using the vol select modifier. Didn't notice anything unusual at the time and saved the file.

Coming back to it the other day,  I was group selecting the fragments and adding materials to them - however it always crashed when selecting through the range of 500-600 which was annoying. That led to me identifying which objects caused the crash and inidividually deleting a few before sending the file over to this forum post.

I have only used this scene in 3ds Max 2019, could try in 2016 if you want me to as I have that installed also - recently updated all the machines here to 2019. I don't have a CER bug report to add here, I've only posted this here for investigation.

[hagen.deloss]

Hi @Anonymous

It sounds like the Fragnoiser script was still on some residual chunks of your scene, have you tried running the simulation again without Fragnoiser applied to any of the objects?

If you would like to try this out in 201, but I think we can still get the same effect in Max 2019. 

Did you want to explore some other ideas to emulate what the Fragnoiser script does?

[hagen.deloss]

Hello @Anonymous

I wanted to check in with you @brentscannell and @Anonymous to see if anything else was discovered on this issue, or if you felt as though a post or posts helped resolve the issue.

If so, it would be super helpful to other folks if you could mark the post as a solution, that way the rest of the community can benefit from the knowledge in this thread.

If I can help you with anything else, let me know! I'm happy we found the geometry that was causing your scene issues 😄