So few things I’ve noticed now, but don’t remember if it was always like this: (Max 2026, Corona 14.1, legacy gamma settings)
I can’t click on map to load it as different gamma just like I can easily do with MaxBitmap. Yes I can add another node but that complicates simple shaders for which I rarely use Slate on.
It doesn’t prompt load screen even when adding as new (so can’t set gamma even first time). I remember it did this though?
When converting from bitmap which was loaded as 1.0 override to CoronaBitmap, the new CoronaBitmap has primaries as “Custom” (Color space: sRGB) and no longer 1.0 override thus. Renders as regular 2.2.
That seems like plenty of issues :- / I wanted to try CoronaBitmap to save memory but looks like I won’t be adopting it in meantime again.
Hm, i have almost exact configuration - Max 2026.3, Corona 14.1 RC1, legacy gamma and i don’t experience any of these issues with Corona bitmap. Maybe there’s something wrong with your Max installation? Maybe refreshing ENU folder could help to solve them?
I can’t click on map to load it as different gamma just like I can easily do with MaxBitmap. Yes I can add another node but that complicates simple shaders for which I rarely use Slate on.
Work as expected. For new and re-loading of bitmaps. Clicking first on the image, changing to override and specifying gamma of 1.0 works the same for Max and CoronaBitmap. Maybe you have a “special” bitmap?
It doesn’t prompt load screen even when adding as new (so can’t set gamma even first time). I remember it did this though?
I guess you are adding a CoronaBitmap not in material editor but in e.g. environment menu? This is a known bug. The load dialog appears when you drag-drop the node into material editor or sometimes during material editor open.
When converting from bitmap which was loaded as 1.0 override to CoronaBitmap, the new CoronaBitmap has primaries as “Custom” (Color space: sRGB) and no longer 1.0 override thus. Renders as regular 2.2.
Works as expected, renders before and after conversion are identical.
Quietmode actually can negatively affect many things, its usually a good idea to turn it back off after you use it for a specific task/script.
I can take a look for you when I’m not busy but we should be able to adjust it so that once the scene is fully loaded then it can turn itself off. Not exactly sure why its only affecting CoronaBitmap in this case so i’ll leave that question for the devs.
One question, you keep this persistent so that it doesnt bug you for when you file open/drag drop new scenes into 3dsmax, or just the first time opening 3dsmax?
I open a lot of very big scenes (2GB+) that often take 5 minutes to do so let’s say, and sometimes I forget to check while I do other task or move away from desk and realize the opening paused (some warnings let scene load continue, like missing bitmaps, but others pause it) because “Connecter integration has update! PLZ install”. Having 3ds Max just open the damn scene gives me so much more peace. If there was any actual important issue it would show up during render-time anyway, or Corona would warn me (funny that one isn’t silenced, but CoronaBitmap dialog is, odd no?).
I had it in start-up scripts folder, so I presume it stays persistent? I never open new scene from 3ds Max itself though, just habit I guess. It’s always from desktop (I also feel it’s faster unless the Max is empty and less prone to issues).
Not sure, while scripting ive found Quietmode can break things randomly so out of good habit I switch it back off after doing a specific function. I say randomly because I dont know what specific things are/are not affected so maybe something in QT or whatever specific prompt is affected by Quietmode, if that makes sense. On my second coffee give me a moment to gather my brain lol. Devs probably have a better response.
Ok good to know, I’m asking because it will affect how the script works. So yes its persistant currently because all that script does is turn on quietmode before the scene loads, then stays on. However we can adjust it so that once that scene is fully loaded it can switch it off, but that will also be persistant for that session.
If you were to then say file → load then we would need to adjust the script to switch back on again, then repeat. If you just open a new max then that doesn’t need to be accounted for.
I started using this script while I was still using a lot both 3dsMax 2023 and 2026 at same time, and it would endlessly need to inform me about different version of… everything while loading down-saved max version :- ).
I mean it does warn about breaking things but the alternative was breaking my patience :- ).
In general both Max and Corona are informing me about too much stuff. I would love snooze button on that.
When 3ds Max quiet mode is enabled,Corona Bitmap starts misbehaving - the “load image” dialog doesn’t pop up once it’s added to the material editor and clicking “load map” in its UI doesn’t work.
