CGPress uses technology like cookies to analyse the number of visitors to our site and how it is navigated. We DO NOT sell or profit from your data beyond displaying inconspicuous adverts relevant to CG artists. It'd really help us out if you could accept the cookies, but of course we appreciate your choice not to share data.
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
The technical storage or access that is used exclusively for statistical purposes.
The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
I was hoping that all the memory leak fixes would be the end of all the crashes and freezing for me but after about 5 minutes I created a spline circle and like so many times before max 2016 freeze while I click and drag to make the spline. I’ll try some other stuff next week (I only work part time at the moment and no more this week) to see if some or all of the other crashes are there, like the orbit the camera [CRASH], entering sub object mode [CRASH] or the best one; having max running and I’m working on some papers and [CRASH] max goes down even though I’m not doing anything at the moment. It’s far from all the time but enough so that I run 2015 on the same computer for all production work and I have no problems what so ever with that version.
Well – this is certainly not normal behavior. Max 2016 as been pretty solid too me, even more so with SP2 which finally fixed that threatful memory leaking bug with the nitrous viewport. It looks like there’s something wrong with your 3ds Max 2016 configuration, or with the system..
BTW: you are not the REAL Marcus Persson i presume ?