Hi,
this has been happenning for quite some time with the newest release and previous one too. When IPR is on , youne basically not able to delete a node in material editor, it stay there and it makes the material creation very messy and inefficient especially with complicated materials. Can you guys please fix this?
When you go back from ipr to normal rendering mode, you can then delete the node normally.
thanks!
M
Yep we have the same issue. Very annoying. Not sure if its a max or vray thing though…
Well this is not doing when i use Corona so it looks like this one is on Chaos end.
In some cases its almost impossible to use material creation when IPR is on due to the clutter between all the used and unused nodes.
Hopefully this thread will get picked up soon by the support.
Nothing from Chaos support?
I think it’s a max thing because I have it sometimes and I don’t use IPR. What helps is minimizing and maximizing Max a few times, and show desktop a few times (windows + D). If not fixed try a few times again. I alternate a bit, most of the time it’s fixed, very strange bug though.
Same issue here. ![]()
Any news about this? It’s extremely annoying to keep tabbing in and out of the Material editor every few seconds when working on materials with IPR running. ![]()
For me even shutting down ME doesnt work
I’ll see what can be done for the Next Update 1.
Happen in IPR too, but for me reopening slate editor fix this issue immediately, dont even need to restart IPR.
Hi there,
Is this problem solved?
I am still having this issue.
I’m afraid not. It still happens for me too. Hopefully this can be resolved soon.
Yep, can confirm… also another bug, if IPR is running and a 3dsmax autosave occurs (either default or from a custom script) it crashes max after the saving is done… This only happens with Vray and no other renderer while running an IPR.
I have a similar thing happen to me, but not in exactly the same way. For me it crashes when IPR is running, an autosave happens and I close the VFB window while autosaving. I’m not sure if it’s a Vray thing though or just 3ds max being wacky as usual.
Hello! I’ve made a note in our bug-tracking system to raise the priority of the issue(internal number VMAX-7435). Regarding the the crash with auto save, I haven’t managed to reproduce it and I’ve tried with and without closing VFB. Does it happen with any scene? Could you share a crash dump and vraylog file? If it happens with specific scene, sharing a scene would be helpful as well.
I believe there is no crash dump file being created because the program just closes without a crash message window, but I’ll see if I find one when it happens. I will also send the scene.
Yes, this is annoying,
As a work around just click any where in the viewport then back to slate editor. it will work fine after that and you can delete any node.
Yes happens to me too.
Yeah, I do the same. But it is very annoying because sometimes you accidentally move objects or you have to press q all the time. It gets harder when you are making material test renders when you have to go back and forth.
Ok, so this happened again just now. I didn’t know Max was autosaving when I clicked the close button on the VFB window. Max just closed down without any error message. No crash dump file was generated.