Strange scene behavior when material appeared in ME

[Bormax]

Hi
Strange thigs are happening with latest DBs. Please, check the attached video.
Everything is going normally until the moment when any material appeared in the ME (even if it's not assigned to objects), after that any actions with objects looks like the strength of mouse movements were multiplied by 10, and there is no more actions written in "undo" list, no way to undo anything.
I worked with corona-8-3dsmax-daily-2021-12-06 since it was published and didn't have any problems until yesterday. It just happened during the work on regular scene and after that I can't avoid this situation.
It's happening with all DBs after corona-8-3dsmax-daily-2021-09-30, with this one and older ones everything works fine.
It doesn't happen if any other renderer is chosen.

Max 2021.3

PS
Merry Christmas!

[GeorgeK]

Hi, this is peculiar I've had this issue before but not related to Corona in anyway. I can't seem to be able to reproduce this on my side with the exact same steps. Thanks for reporting this we will investigate further.

[romullus]

It happens from time to time for me too, but i struggle to see any connection with Corona. I noticed that it mostly happens after prolonged sessions with 3ds Max, when i open and close many scenes without restarting max itself.

[Bormax]

Hi

I have had same strange issue before, but those times I didn't connect it with Corona and simple restart Max helped to get rid off this behavior. But this time it's clearly connected with Corona.

I've just installed Max 2022.3 + corona-8-3dsmax-daily-2021-12-06 and everything was OK until I tried to work with the same scene I was working on before I faced this issue. Unfortunately now I have the same situation with Max 2022 :((

It seems that the starting point of this problem somewhere in that scene. I also suppose, that it might be connected with the planks objects created by Floor generator, but I'm not quite sure. I checked the scene with Prune scene and Sini Forensic, they both said that there are no virus in the scene.

Now I installed Corona 7 hotfix 1 and Max 2021 and 2022 are working fine.

I uploaded this scene to the Dropbox for you to investigate the issue. File name is 01_AH_01-2.zip

[GeorgeK]

Thank you Bormax, I am afraid I am still not able to reproduce the issue in your scene (3dsMax 2022-24.0) but there seems to be some quad setting or a bug with custom quads including the Corona IR extended viewport, that's probably related to the twitching movements, but that's just a guess. I am getting some weird twitching on the axis of objects and viewport refreshing when moving the cursor around, notice my cursor movements and what's happening (non-local axis, non-transform coordinate center, unfortunately  the viewport-glitch refresh is not captured in my gif but it can be seen in your video).

Can you please try and reset your custom quad and see if it it's reproducible?

(Report ID=CRMAX-1206)

[Bormax]

Can you please try and reset your custom quad and see if it it's reproducible?

Hi. Did you you mean quad menus? If so, I reset them, but it didn't change the situation

Also tried different viewports layouts - no result too

[GeorgeK]

Can you please try and reset your custom quad and see if it it's reproducible?

Hi. Did you you mean quad menus? If so, I reset them, but it didn't change the situation

Also tried different viewports layouts - no result too

Hi sorry I was referring to the viewport-quad configuration.  Preferably with no docked IR present. At any case we will investigate this further, can you please share your current screen resolution and if you are using any non-default windows/layout scaling?

[Bormax]

Hi
Happy New Year!

I tried different viewport layouts with no Corona IR docked in them, but didn't get positive result out of it.
Currently I work on 4K monitor with display resolution 3840x2160, text and icons scale set to 150%(recommended).
As I mentioned I have had this issue previously, that times it was with my old monitor with lower resolution.

[GeorgeK]

Hi
Happy New Year!

I tried different viewport layouts with no Corona IR docked in them, but didn't get positive result out of it.
Currently I work on 4K monitor with display resolution 3840x2160, text and icons scale set to 150%(recommended).
As I mentioned I have had this issue previously, that times it was with my old monitor with lower resolution.

Hi again and happy new year! Thanks for the provided info, can you please try to reproduce this with your ENU folder renamed? How to (keep your old ENU as backup): https://knowledge.autodesk.com/support/3ds-max/learn-explore/caas/sfdcarticles/sfdcarticles/Resetting-3ds-Max-3ds-Max-Design.html

[Bormax]

Hi again and happy new year! Thanks for the provided info, can you please try to reproduce this with your ENU folder renamed?

Hi

Done. Yes, with new ENU folder Max works normally. Does it mean that some of installed scripts/plugins is interacting with Corona this strange way?

[GeorgeK]

Highly likely that's it yes, would it be possible to provide us with a zip of your old ENU, if you can share a detailed list of 3rd party scripts/plugin you have installed? I will try and pin-point the issue.

[Bormax]

Done with Private uploader, ENU folder from Max 2022
File name 1641391785_ENU.rar

[Bormax]

Hi

Tried corona-8-3dsmax-daily-2022-01-04, the bug is still the here

[GeorgeK]

Hi

Tried corona-8-3dsmax-daily-2022-01-04, the bug is still the here

Hi and thanks for uploading the file, I am troubleshooting it in hopes of finding the offending script incompatibility.

[GeorgeK]

Please try uninstalling or removing the following and see if the issue persists:

Sergo Pogosyan-Scripts
TrackScripts (kstudio)
Wahooney Tools-ViewportAutoSnap
WickerFilms-EasyPivot
mmTransformTypeIn script

[Bormax]

Please try uninstalling or removing the following and see if the issue persists:

Sergo Pogosyan-Scripts
TrackScripts (kstudio)
Wahooney Tools-ViewportAutoSnap
WickerFilms-EasyPivot
mmTransformTypeIn script

I tried to remove the scripts mentioned by you, all of them, except the mmTransformTypeIn script. No changes in this case, the issue still persists.

Abut the mmTransformTypeIn script - I didn't find anything concerning this script in any Max 2022 folders... But it's still working in Max. So I don't know how to remove it. Could you give me some tip how to do it, please?

[GeorgeK]

mmTransformTypeIn script is from http://www.scriptspot.com/3ds-max/scripts/mmtransformtypein, please check the author links provided in script spot. In your ENU can be found as Monotone Minimal-mmTransformTypein. Please let me know if you need any more help with locating it, or if the issue still remains.

[Bormax]

mmTransformTypeIn script is from http://www.scriptspot.com/3ds-max/scripts/mmtransformtypein, please check the author links provided in script spot. In your ENU can be found as Monotone Minimal-mmTransformTypein. Please let me know if you need any more help with locating it, or if the issue still remains.

Thanks GeorgeK, but there is no such kind of files in my ENU folder... Actually this script was written by my request pretty long time ago :), and I can find mmTransformTypeIn.mcr in
 C:\Program Files\Autodesk\3ds Max 2014\scripts folder (I still have it installed on my computer), but there is no this file in any folders of Max 2021 and Max 2022...

[GeorgeK]

mmTransformTypeIn script is from http://www.scriptspot.com/3ds-max/scripts/mmtransformtypein, please check the author links provided in script spot. In your ENU can be found as Monotone Minimal-mmTransformTypein. Please let me know if you need any more help with locating it, or if the issue still remains.

Thanks GeorgeK, but there is no such kind of files in my ENU folder... Actually this script was written by my request pretty long time ago :), and I can find mmTransformTypeIn.mcr in
 C:\Program Files\Autodesk\3ds Max 2014\scripts folder (I still have it installed on my computer), but there is no this file in any folders of Max 2021 and Max 2022...

Hi again, you can find the file on the provided ENU folder \ENU\usermacros\Monotone Minimal-mmTransformTypein, but I can't imagine this remnant can be so impactful. Hmmm, I will look bit more deeper on your UI ENU settings it's the next possible thing.

I am assuming starting over with a clear ENU is not an option.

[Bormax]

Hi again, you can find the file on the provided ENU folder \ENU\usermacros\Monotone Minimal-mmTransformTypein, but I can't imagine this remnant can be so impactful. Hmmm, I will look bit more deeper on your UI ENU settings it's the next possible thing.

Thank you! I don't know how I didn't noticed this script there, and why 'search' didn't find it either, but you're right, it was located in ENU\usermacros folder.

I deleted it, but unfortunately with no positive news this time either...

I am assuming starting over with a clear ENU is not an option.

Actually this is what I'm going to do for Max 2022 when I have more time (maybe on this weekend), and I hope I'll find the script/pluging or maybe some interface setting which has some conflict with Corona's latest DBs. I'll let you know if I find something

[GeorgeK]

Please keep me posted, I will be digging through a bit more, it would be nice to identify the cause for this.

[Bormax]

Hi again.

So I've started from new MAX 2022 ENU folder and installed most of the scripts and made UI setting from scratch. This time I didn't install some of Sergo Pogosyan's scripts, but if you remember, I tried to remove them previously and it didn't help to solve the problem.
Max still works normally, I even worked with the scene, which as I supposed has problem point, but still didn't get this issue. So no clue where this problem was hidden. I'm happy that I can continue to work with the latest Corona builds, but maybe would be wise to understand what caused this Max behavior. If you need I can send you my new ENU folder, so you can compare it with the old one.

[pokoy]

The perpetual ENU folder mystery...
FWIW, you could try to reset the UI and see if it helps, or just reset the ribbon UI - this one helps with some quirks with the UI too.

From what I understand, even people at Autodesk don't really know why the ENU folder gets mangled sometimes. Most of the people who worked on the UI and older components are either long gone or work in other teams now so they probably would need time to understand what the code does before they can attempt to fix it. Resources are scarce at Autodesk and UI problems in particular don't get enough attention as long as the 'magic potion' of deleting the ENU folder works.

[GeorgeK]

Hi again.

So I've started from new MAX 2022 ENU folder and installed most of the scripts and made UI setting from scratch. This time I didn't install some of Sergo Pogosyan's scripts, but if you remember, I tried to remove them previously and it didn't help to solve the problem.
Max still works normally, I even worked with the scene, which as I supposed has problem point, but still didn't get this issue. So no clue where this problem was hidden. I'm happy that I can continue to work with the latest Corona builds, but maybe would be wise to understand what caused this Max behavior. If you need I can send you my new ENU folder, so you can compare it with the old one.

Please do I am interested.

[Bormax]

Done.
With Private uploader, file name is 1641934894_ENU-new-Max2022.rar

[GeorgeK]

Done.
With Private uploader, file name is 1641934894_ENU-new-Max2022.rar

Thanks again, looking into it.

[Bormax]

Hello again!

Do you have any progress with fixing this issue? I continue to use Daily Builds and have the same issue pretty often. Replacing a broken ENU folder solves the problem, but it doesn't work for a long time.
Overall it looks like this:
Max works normally and I work on some scene. At some point I get this issue, I replace ENU folder with the one which is working fine, Max again works normally but not for a long time with the same scene. Somehow this scene breaks Max again and again.
I still didn't find any specific object/setting/material which leads to this Max behavior, but I can tell that it happens mostly during the work on exterior scenes. I would say that the main difference between components of my exterior and interior scenes is the amount of proxy objects (I use a lot of them for trees, plants, grass, stones) and the use of Forest Pack for scattering the elements of a greenery.

Would be nice to get some solution better than Replacing a broken ENU folder - it's pretty annoying and brakes the workflow

[GeorgeK]

Hello again!

Do you have any progress with fixing this issue? I continue to use Daily Builds and have the same issue pretty often. Replacing a broken ENU folder solves the problem, but it doesn't work for a long time.
Overall it looks like this:
Max works normally and I work on some scene. At some point I get this issue, I replace ENU folder with the one which is working fine, Max again works normally but not for a long time with the same scene. Somehow this scene breaks Max again and again.
I still didn't find any specific object/setting/material which leads to this Max behavior, but I can tell that it happens mostly during the work on exterior scenes. I would say that the main difference between components of my exterior and interior scenes is the amount of proxy objects (I use a lot of them for trees, plants, grass, stones) and the use of Forest Pack for scattering the elements of a greenery.

Would be nice to get some solution better than Replacing a broken ENU folder - it's pretty annoying and brakes the workflow

Hi Bormax, is it possible to share an archive of that scene with us?

[Bormax]

Hi Bormax, is it possible to share an archive of that scene with us?

Hi
Yesterday morning I've updated Corona to DB Mar 11 2022 and Forest pack to 7.3.1. During the day I tried to reproduce this issue with different scenes which "were broken", but didn't succeed with that, so (fingers crossed) hope this update solved the problem. But if it will come back I'll send you the scene

[GeorgeK]

Hi Bormax, is it possible to share an archive of that scene with us?

Hi
Yesterday morning I've updated Corona to DB Mar 11 2022 and Forest pack to 7.3.1. During the day I tried to reproduce this issue with different scenes which "were broken", but didn't succeed with that, so (fingers crossed) hope this update solved the problem. But if it will come back I'll send you the scene

Interesting, thanks for the update I hope it's addressed but should it re-surface please let me know.