I recently discovered, that once i open a scene and started to render something or use the material-editor the viewport performance of max is getting bad. resulting in viewport-stuttering when rotating an object/scene or moving something around.
This behaviour only happend with corona 1.4. for now.
I’m using Max 2016 and corona 1.4 and got a Dell Firepro V7900 gpu with latest amd-driver…
currently i was not able to test this behaviour in other environments.
(Support ticket 3432)
addition_
same behavior is seen on similiar machine with an Quadro 4000 and latest driver.
Hi,
I am not observing such behavior, can you record a video showing the problem so I am in picture?
Hello Ondra,
i’ve created a video ---- usually the viewport is quite smooth… when using the mouse. After i opened the material-editor or rendered an image - the navigations withing the viewports is horrible. You kinda get that impression at the end of the video, where i didnt released the mousebutton during moving or rotation. It seems stuttering and the object jumps to a certain position where the mouse is…
Working with the scene is quite impossible.
I’ve seen that in different scenes lately, but hadn’t found the time to figure out the reason for that. I didn’t had this behavior when using vray-as render engine or merging a affected scene into a new scene - so i’m not sure if there is that original scene corrupted or if that scene got degraded over time.
I couldnt see the effect in that merged scene.
baukind_hocker.rar (5.7 MB)
I was having the same issues a little while ago and read a thread about windows update.
Ran the updates ( I hadn’t updated in months ) and everything seemed to work fine again.
Worth a try if you haven’t done so already.
as far as i know windows are up to date. on both machines…
its windows 10 by the way…
Are the textures stored in a network location (shared folder, etc)?
yes they are stored on unc network path - but usually this works with other render engines just fine. they only wait-time is, when starting rendering to collect all textures. It did not affect the performance of the UI. It was also not noticeable with corona 1.3
But maybe i will try this https://coronarenderer.freshdesk.com/support/solutions/articles/12000011862-material-editor-is-very-slow-freezing-in-corona-1-4
it seems to have similar problems…maybe the sollution will work for both.
well i tried the Microsoft Visual C++ 2015 Redistributable tip, but it didn’t changed much in the performance drop. I’m quite clueless - maybe i’ll test it on a more clean installation if i’ve some time.
Try disabling Windows Defender (completely). Or any other antivirus/firewall software you are using.
There was a very similar case where this was the solution.
Thanks for the provided scene. I took a look and there is a LOT of textures on the network drives that are accessed periodically when 3dsmax decides whether or not to refresh the material editor. It would definitely explain the slowness. My 3dsmax is completely unusable when I have the material editor open in your scene. But I have the same issue when switching to other renderers, because it does not actually happen during rendering of the previews, but before. The key question is: was this happening also in Corona 1.3, or is it new to Corona 1.4?
as far as i know this behavior was not noticable in 1.3 … it became noticable with 1.4 …
I reinstalled version 1.3 and used one of the scenes where it became very noticible (nearly unusable) with 1.4. - in 1.3 the scene handling performance was not affected and behaved like it should be / zoom, pan, everything else.
so something introduced in 1.4. slowed down usablity after started a rendering or using the material editor.
same happened here with daily build 07-29-16, also on heavy scenes some objects and proxys or even the entire scene disappear on wireframe viewports, if ou apply shademode you can see the objects, switch to wireframe or mixed wire with shade and they disappear, also when interactive is used the selection rectangle disappears from viewport, windows and max up to date.
Can you describe it and send us a scene where this happens?
https://coronarenderer.freshdesk.com/support/tickets/new
well back again on trying to resolve this.
I tried max 2017 and daily build 160918 … i also deinstalled all mscv c++ versions except the 64bit 2015 … still if i start rendering or open material editor, the scene/or viewport becomes very laggy/unusable.
I’m nut sure how to solve this - sending a max-file is probably not really helping, since the same file is behaving in max2016 with corona 1.3 very fine after material editor was opened. The only solution i can see now is to reinstall the whole machine with clean win10 and install only latest versions. But i’m not sure if that will help it.
I installed trial of 2017 3 days ago and daily, and had the same behaviour as you describe.
Super odd, because at same time, 2016 and same daily, on same computer had none of those issues.
It’s weird and reoccuring issue, but definitely tied to mat editor.
I (finally!) experienced the slow material editor recently. Everything was always working fine for me, but then I had some completely different problems with Max, so I uninstalled all MSVC++ versions, and then re-installed them one by one (proceeding exactly according to this Autodesk guide: https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/How-to-remove-and-reinstall-Microsoft-Visual-C-Runtime-Libraries.html), then I opened 3ds Max and… material editor was super slow. So I opened Windows Update, and noticed that there was no update on my PC since 2015 (oops). So I installed all available Windows Updates (required a few restarts and manually installing this https://www.microsoft.com/en-us/download/details.aspx?id=53332 since my Windows Update was stuck on “searching for updates”) and… the material editor runs super smooth again!
So it looks like basically Windows updates and MSVC++ do shit to system.
Well since I use windows10 I’m sure it is also up-to-date…
So it might be something else - but I’ll check on uninstalling C++ again and reinstalling latest C++ distributable.
Great! Good to hear you found the reason of the slow downs!!! 