Well...
guys, I got the impression that your attitude towards customers is drifting in the wrong direction.
I'm using corona more then 10 years and there a lot of not fixed bugs, but each time it was like yeah, there is a problem, we'll fix that (but not always happens obviously).
But for some time it looks like a gaslighting.
Almost a year ago I reported problem with tyflow and got anything but fix: questions why do I use it that way, advices with a workaround, and then a cool stories that it's a 3dsmax problem(no), tyflow problem(no) and that all renders work that way(no) - I had to spent time to do videos for you just to read - don't believe your eyes, it's not what it looks... and silence after - it's my problem from then.
Now I've got this problem, with old scene I decided to
rerender in my free time. For me it was resolved in 5 min, as soon as I found which set of object causing "not memory leak, but wrong scene set up". They been added for certain camera which I deleted later and forgot to delete those objects. I could easily delete them.
But I thought - what if it'll happen to someone less lucky than me (or even for me in future) during work on tight schedule, when there is no time for those investigations?
So I spent time (now it looks like I just wasted time) to narrow it down from 120 object to 2 and send it to you, so you can fix it. I gave you a scene with a rare hard to catch bug that happens under certain conditions and instead of investigating and fixing it I see some childish and a rude approach - "You are a fool yourself"
before "diagnosing" something as memory leak
diagnosing in quotes? You mean than I'm incompetent to call it memory leak? You are right - I'm not one of corona devs so I can't say that))) Just corona sucked memory in 2 boxes scene so fast that when I saw memory usage growing like 30Gb/s in task manager I had no time to click cancel. Max crashed without any messages, and not only max but some other app and windows became completelly unresponsible. But no, than't not memory leak, as it well known that memory leak can happen only with default settings and if you change those settings within allowed values - it called bad scene setup. If it looks like a duck, swims like a duck, and quacks like a duck, then it probably
is a duck bad scene setup:)
There is no leak, your scene is set up to eat up memory
If so, can you reproduce such setup in a clean scene? I mean setup that will eat all memory with few simple objects with simple materials. Can you? Because I can't.
they all seem to be related to the Legacy Mtl
Exactly, I wrote about that in first post.
Also, if you isolate either of the objects, it renders fine (even with the "wrong" materials and render settings)
This too. That's why I said interesting and hard to catch bug. And even more - it depends on camera position, object postion and rotation. By rotating camera or moving/rotating objects we can get absolutely normal ram usage, or 1-2 GB more than should be, or slowly growing or instant crash.
should not be used, sounds like Fresnel IOR was 100 and the scene's Max Depth was 100
Should I add link to your official support.chaos.com where we can see IOR up to 999 without any warning that it may cause
crash/memory leak "bad scene setup"? Or max depth's tooltip whis says that it affects performance only?
I'm using different non default settings for GI/AA balance, max ray depth and max intensity in different scenes depening on how it affects result and up to now there was no problems with "scene setup".
And before saying that there is nothing broken except idiot behind keyboard who can't even set up scene, you should took that into attention:
I decided to rerender old scene
Rerender means it rendered not for the first time. And guess what? There was no problem with scene setup earlier, it perfectly WORKED back then but NOT WORKING now. Which means that something was broken in Corona between "then" and "now".
A bit of feedback based on some of reported bugs. Let's be honest, if you don't have time to fix something or not top priority or simply don't want to - just say that and it'll be ok. No need to say that all working as intended, working nice, "we're winning winning winning"© and gaslight person who reported bug.
Based on this bug and tyflow bug your attitude perfectly match gaslighing definition, as in both cases something wrong with corona, not me.
The American Psychological Association defines gaslight as: To manipulate another person into doubting his or her perceptions, experiences, or understanding of events.
Show Posts