Is it possible to go 5 minutes without Max 2017 crashing?

[Anonymous]

I'm so over it. Doesn't matter on the job, size, what i'm doing - it will crash. I'm sending bug reports. But man I'm frustrated with this thing.
The other day it was clipping and the object was completely disappearing. I had to start a new scene and copy all the objects into the new scene so it would behave properly.
But that's the least of my frustration. Brand new job today. Very small scene. Open the layer properties -- bang! crash.

Re-doing work is growing tiresome.

[Anonymous]

Source?

[Alfred.DeFlaminis]

Thank you for the informative post @gandhics, that is interesting.  I wonder if there are two families of 970's, I use a 970 at home with Win7 and no problems at all for me, but I know others are having them.  Do you by any chance know the thread title that was coming from?  I'd like to learn more if possible.  Thank you very much for your time.

Best Regards,

[Anonymous]

Last night I had an issue when I was creating a model of a Sofa. I'd got near the end of the modelling project when I needed to create some Cushions for it. It started doing what it always does - which is the whole 3D model completely disappearing. The only way to get it back is to tap "Zoom All" continuously until it decides to show up again. This is the point in the modelling process where I know I need to use my workaround - which is to create a new scene and import all the objects I've just modelled into it. Otherwise the rest of the original scene wont be workable with all random the bugs. 

In this case, I needed to mirror an object (a cushion) - when I did that and used a cloth modifier, it started behaving erratic and the model moved at random locations whenever I selected it. I had to 'undo' the whole process and try again only for it to fail and move to another random location. Eventually, I got fed up trying to get it to behave properly and had to create a new scene and import.

[Alfred.DeFlaminis]

Hello @Anonymous,

One of the more common reasons for the zoom issue is if the system units aren't correct for the scene scale or if there is a stray vert way off in the distance on one of the parts.  If your couch is multiple parts, try Z on each part to see if one of them has a stray vert.  If you'd like I can create a private folder for you and check the file in the case it's something else and I need to log anything. 

The model moving around is entirely new to me, and I'd need to look at a file or something to really help with that.  Is that doable?  Again, I don't mind creating a private folder for you.  

Best Regards,

[spacefrog_]

---

@Alfred.DeFlaminis wrote:

Thank you for the informative post @gandhics, that is interesting.  I wonder if there are two families of 970's, I use a 970 at home with Win7 and no problems at all for me, but I know others are having them.  Do you by any chance know the thread title that was coming from?  I'd like to learn more if possible.  Thank you very much for your time.

Best Regards,

---

The general Geforce 970 issue is in my eyes a non-issue for 3ds Max. The base problem with 970's is mainly gamer related issue (slight realtime performance drop when VRAM is filled up) , as this card's upper 512MB VRAM access ( from a total of 4GB ) is simply slower due to the hardware design than the bottom 3.5 GB. This MIGHT in rare scenarios causes a drop in viewport with Max too, as soon as your VRAM really fills up that much, and might play some role if you want to use GPU rendering, but i really doubt people will notice this in 3ds Max.

There might be general problems specific to those newer cards ( 9x0, 10x0 ) and/or windows 10 and Max 2017 though

For me Max 2017 has again proofed to be rock solid ( W7, 780GTX) over the course of last weeks EXTENSIVE geo editing sessions, and Max 2017 is my favorite Max up till now. With the limitation of snapping crashes with VTX snapping in edit poly subobject mode ( happened 3-4 times over the course of this week) and some issues with vertex painting that seem to occur

I hope they fix Max 2017 to nearly perfection, this might be a version the gets used a LONG time, considering Autodesk's general attitude and the increase of maintainance sub fees , ,

[Alfred.DeFlaminis]

Thank you @spacefrog_, I see.  I appreciate the information. 

Best Regards,

[Alfred.DeFlaminis]

Hello @Anonymous,

My offer to create a private folder to check the file stands if you want it.  Please just let me know if there is anything I can do to help here.  

Best Regards,

[nastev]

@Anonymous

Next time when you get issues with disappearing objects in your scene - you could try to Reset Xfrom for your objects and see if that fix the issue.

I had problems twice for 2 different scenes, when I model objects and at some point - I got issue with viewing them - they just disappears and no way to get them back in current view. Adding Reset XForm to objects fix issue for me in current scene.

You could try that, may be it will help, may be not in your case.

Best!

Nik

[Anonymous]

Dear Sir

I can't found mental ray in my Assign renderer file in 3ds max 2017 can you please tell  me how can i install it ? 

[Alfred.DeFlaminis]

Hello @Anonymous and welcome to the community.   I have moved your message to a new thread located here and it would be my pleasure to help you with this there.  Thank you.  I am working on a reply now.  

Best Regards,

[Anonymous]

Cheers mate. But it's not one object in particular. It's all of them. So I only have to rotate the viewport for all objects to disappear...

[Anonymous]

Cheers Alfred. I've created a new scene (very light)  and it's doing it again. Would you mind downloading the attachment and taking a look at it please.

[nastev]

Understood.

In my scenes there was many objects also. and when one of them go with problems - it sucks the whole objects to disappears.

When I fix that single object - viewport start working fine again.

May be it was a different problem, I don't know, but it is very similar.

I have opened your config.max scene and so far everything looks fine and no disappearing happened here.

I'm with latest Nvidia drivers and 1070 on Win10.

Best!

Nik

[Alfred.DeFlaminis]

Hello @Anonymous,

Thank you for the sample file.  I was able to replicate what you were describing.  The problem here is that the system units are too small for the scene itself.  The system units are in mm, but the scene is a hundred thousand times bigger than that.  My advice is to open Max, change your system units to Inches then open the scene and select "Rescale the File Objects to the System Unit Scale".  Problem was instantly resolved for me when I did that.  In Inches, the scene is only 1000 times bigger than the system unit.  I have more information here about unit settings if it's helpful.  

If your entire scene took place as a carving in the side of a pencil or something like that then mm would be a decent system unit.  For this scene, feet or inches should be fine.  The general rule is use a system unit that represents the smaller details, in your case the squares sides of these boxes which are 96 inches square.  Can you please try the above for me?  Thanks!

Best Regards,

[Anonymous]

Wow! Thanks for that Alfred.
So for us Metric users, can I use cm instead?
I'll give this a go when i get home tonight. If this works and solves my issue - I'll buy you a bloody slab of beer. Because this problem has been a thorn in the side of my **** leg!
The crashes I can deal with, but this is one issue that has been making my blood boil...
Can't wait to try it out!

[Alfred.DeFlaminis · Accepted solution]

Hello @Anonymous,

Of course, you can use cm or maybe even meters in this case because of the small sides of the boxes being roughly 8 feet or so.  (2.4ish meters.)  Please let me know if you have any problems!

Best Regards,

[Anonymous]

I believe this may have fixed my issue with clipping. I won't know until the weekend when I do some vigorous work but so far so good. It's not spazzing out on me like it normally would simply by selecting something so fingers crossed. Thanks Alfred!! You are a god amongst men!

[Alfred.DeFlaminis]

You're too nice to me @Anonymous!    Thanks for the kind words.  😉

Best Regards,

[Anonymous]

@Alfred.DeFlaminisSorry Alfred to dig up an old thread but I'm having the same old issue as previously mentioned.
I've adopted the CM unit scale as suggested but it's still doing it. It's so bad at the moment that I can't even continue on with this project (which I'm running out of time on) Would you mind checking out the project file and giving me some clues how to fix this?

[Alfred.DeFlaminis]

Hello @Anonymous,

I'm not seeing any problems in here, and the viewports are rotating pretty well here.  Which orbit mode are you using?  (I use OrbitSubObject)

Best Regards,