Nice but unnecessary effect )))
By adjusting volume effect altitude you can clearly see how colors change and by scale you can see how it moving across scene.
Affected at least 2 latest versions.
Hi,
I see you are on fire.
Please keep in mind that a proper bug report includes, at least:
• Corona version used
• 3ds Max version used
• Scene where the bug can be reproduced
• Reproduction steps
Thanks.
Hi,
Corona version used - “Affected at least 2 latest versions”, so that’s 14 and 14 update 1
3ds Max version used - 2026
Scene where the bug can be reproduced, Reproduction steps - create a black plane, add corona sky to env, run interactive and play with altitude and scale. But I did that hard part for you) File in the attachment.
I combined both bugs into a single scene - the one with volume and this with pattern [https://forum.corona-renderer.com/ corona pattern possible bug ](https://forum.corona-renderer.com/ corona pattern possible bug )
Hi,
I appreciate your bug hunting, but I would appreciate more if they were more of a practical use.
3.5km above the ground for sky map’s (not volume effect’s) altitude is a possible value, but if you were more attentive, you would see that altitude has nothing to do with volume effect creating color bands. It is visible for high volume effect values even with 0 altitude value. So, this way of communication about a possible issue, specifically - “looks like you have combined the sky volume effect with thin film” and “By adjusting volume effect altitude you can clearly…” - you have actually confused and misled us. I appreciate the humor, but you sound more like your goal is to ridicule. That is not ok.
Corona version used - “Affected at least 2 latest versions”, so that’s 14 and 14 update 1
I appreciate you doing the hard part of explaining which version you used, but a release candidate is not a final build to be considered one of the latest.
It takes almost nothing to be nice and constructive with communication.
Combining bugs into a single file is ok but we would appreciate if you separate them - if you had the time to investigate separate issues, you surely have the time to save them to a file.
The bug will be reported to be considered in whole with volume effect and sky map related tasks.
Hi,
“I appreciate the humor, but you sound more like your goal is to ridicule”
there was just a bit of humor, in topic name and here “Nice but unnecessary effect )))”, absolutely no ridicule, up to this point:“But I did that hard part for you)”
And believe me, that an absolutely nice attitude in my situation.
I’m in the middle of big project and due to a bunch of bugs in corona I could not finish renders in time. As result - not received money in time and as result - didn’t paid for corona subscription in time so now it not working and I can’t check this “but if you were more attentive, you would see that altitude has nothing to do with volume effect creating color bands”.
BUT as I remember, volume effect scale produces color bands and when you change scale - color bands are moving and became less or more pronounced. But when you change altitude - the color changing. And changing color with altitude change looks very similar to how thin film changing color when you change thickness, not to mention that colors itself look like colors of thin film. So I decided that changing colors with altitude and position/pronouncing of those color bands as a result of scale change could be connected somehow, shouldn’t I?
So, this way of communication about a possible issue, specifically - “looks like you have combined the sky volume effect with thin film” and “By adjusting volume effect altitude you can clearly…” - you have actually confused and misled us
Really? Sorry for that. I understand that after reading this you opened part of code with thin film and sky, then checked if you combined them, found that it’s not the case and realised that I misled you (sarcasm)
But what happened in reality - you did nothing, not even opened max, added plane, corona sky with volume effect to check it. Did I mentioned some conditions to reproduct it so you need the scene? Instead you required that I waste my time by doing that for you.
And another POSSIBLE bug I reported - corona pattern with on/off texture. Same - did I mentioned some conditions to reproduct it? Pattern mod ->disable rendering of base object → add on/off texture → base object visible. Did you checked that? But why waste your time on this if you already know that it is expected? (and I expected that this may be the limitaion, that why I wrote POSSIBLE bug). But it much funnier if I’ll waste my time to do the 3-click scene for you so you can say it’s expected.
And no, I didn’t saved scene with some bug that happens each time in a clean scene with a kind of “default” setup.
I appreciate your bug hunting, but I would appreciate more if they were more of a practical use
While rendering masterplan view volume effect producing some weirdo results for years already.
Now the volume effect produce some werid color banding. I din’t noticed it at start, as it a big desert scene and reddish band were on top of reddish rocks, but then I noticed green/blue/purple colors depends on camera postion. And had to stop work and investigate WTF is happening.
Thanks, I’ll tell client that this have no practical use. But I’m afraid my client will not share your opinion on this.
After converting bitmaps to corona bitmap I have to open each texture in external viewer to check how it looks and then switching between different color primaries to find one of them are closer to original texture, because behaviour look absolutely random for me. That a very convenient workflow and what is more important - fast.
Out of core not working or I don’t understand what it’s needed for as I have to rescale textures manually, consider I’m creating mipmaps instead of out of core feature.
But thanks again, now I see that fixing of this will have no practial use. So no need to fix. Nice.
As for now insead of using volume effect, I used volume material. And guess what? Another bug (or even 2, but not sure, maybe second is a limitation). But I didn’t reported it yet, as it more complex and I have to prepare scene for you, unlike the case with volume effect and pattern, which could be easily recreated on clean scene in few clicks.
So, within one scene I got 5 bugs and 2 limitations, or 6 bugs and one limitation, didn’t finished part of the renders it in time, didn’t received money in time, have corona license suspended, so can’t work until I got payment. And you say I need to waste my time to create one plane scene (instead of the job I get paid for) because you don’t want to do 5 clicks and check what I reported (I guess this is the job you get paid for) and that all those bugs have no practical use? That’s a great example of being “nice and constructive with communication”.
V.P., not offense but you sound like someone I’d avoid having to interact with if you have a complaint.
Just imagine being with the support staff, having tens of reports daily to go through, new and old ones, documenting them, checking with devs, reporting back to users, internal stuff to deal with etc.
Of course, I too would prefer to have a scene prepared by you since I probably wouldn’t have time to setup 10 scenes a day and try to reproduce user issues, especially if you have a good repro case in your hands to who me the issue to begin with.
The support staff are at work just like you, with deadline in their necks, support cases to take care of and their own lives. Sarcasm is not going to improve your interaction in any way.
no offense,
but just to clarify - as I remember I always trying to provide scene and steps to reproduce problem if there any conditions for such bug.
Like I said in post you anwsered to - I have 2 more bugs, but I didn’t reported them yet, as I need to prepare scene. Those have more specific conditions, so scene with it should be added.
But what is the reason for creating simple scene with default corona sky and enabled volume effect? Is there any specific steps you need to follow? Is there any conditions, I don’t know, like certain sun scale/positon in combination with some specific settings? Just add corona sky and enable volume effect. That’s all.
Or like with corona pattern - add pattern modifier->disable rendering of base object->add on/off texture ->base object visible on render.
Should I?
Ok, I did it. Is there any time saved?
Let’s try to imagine difference in with and without scene:
No scene: open max->open environment settings->add corona sky->open material editor->drag corona sky map->enable volume effect->add dark plane to see effect better->render
Scene: download scene->open max->open scene->open material editor->check settings of corona sky->render
How much time saved here? Skipped “open environment settings->add corona sky->”,“drag corona sky map->”,“add dark plane to see effect better”, but added download+open, which would take more time than what is skipped. And added some time on my side.
Same for pattern. What changed between send us the scene and this is expected? You can see settings? Settings were in report. Result? Result were in report. It’s a limitation of this feature. Why not said this at start?
What if tomorrow there will be a bug, when you enable denoiser for interactive and it’ll not work. Should I save the scene for it? Or if you add corona sky and in will render pure white?
I appreciate your bug hunting, but I would appreciate more if they were more of a practical use
and probaly this one triggered me the most - you reporting useless things. You’re wasting our time.
Creating two separate, proper bug reports with scenes is definitely faster than writing this forum post (no sarcasm). It saves both your and our time.
Please check [this thread for how to report bugs to us](https://forum.corona-renderer.com/ How to report bugs to us ).
After some thought, I have to admit you were right and I was wrong.
I was too tired, too nervous and too emotional when the problems with this project reached a critical point. I decided to report problems during work in hope that some of them could be fixed till I’m working on this and thought that a bit of humor was what I needed. And although I didn’t intend to, I turned the whole thing into a damn circus.
Sorry guys and especially you, Aram.
Won’t happen again.
Thanks for your message and for the courage you put into it.
Such things happen to all of us, remember that they are temporary.
I hope our forums help you and other users not only technically but also bring up mentally when needed.
Wishing you and all forums users great weekend!
This issue has been fixed in the newly-released Corona 16 preview build and the fix will be included in the final Corona 16 release: Chaos Corona 16 for 3ds Max - Previews (Daily Builds) Changelog - #4 by AramAvetisyan
Please try it and let us know if everything is working as expected. Thanks!