Messages - Gr100

For several weeks I have been working on a new machine that I have made myself. The rendering engines I mainly use are v-ray and of course corona. Vray benchmark definitely satisfies me, unfortunately the corona benchmark is a total failure. My score on stock settings is 47 seconds. My second weaker computer has a score of 42 seconds. In addition, when comparing both of these computers in other benchmarks, they show that the set with AMD is much better, but the corona does not confirm it. What is the reason for this?My computer composition is:

Thats crazy, im running the same system here pretty much. Discouraging after paying $6300 CAD for it. On the flip side, im able to render out a pretty heavy exterior scene at 4K in about 45 mins with about 2% noise level. About to run the bechmark to see what i get.

after an internal discussion, we decided to handle the beta situation ASAP for every paying customer. After all, you are not the first customer in need of the older versions. If you want, you can send me a PM here on the forums and we'll make sure that you can get back to your project as soon as it's possible.

But thats why its not working. If you havent paid for a license how do you expect to use it after the initial demo has run out? Its not a 45 day demo, every 45 days!! If you paid for a license then surely you could use the beta's that you were using previously? I can use previous versions going all the way back to 1 for 3ds max, but you obviously have to pay for that privalege.

Hey ArtisticPixel, I have the FairSas Lic. Whenever I try to install an older Beta Version of Corona, I get a message saying this older build has expired and that it won’t work (and it doesn’t). I think Corona did it that way so as to block users from continually using those free version since the full version has been released. That’s fair enough but we need to get this to the attention of the Developers to allow computers that are running a valid license version of Corona to run any older versions as well. And if that’s too hard to implement then send me the fille directly, even if it runs for only 45 days like a trial version does, myself and anyone else who’s been inconvenienced by this situation would appreciate it.

Thanks Artisticpixel for your help but I’m aware of this link. These builds pose the same problems with instancing and proxies. My viewports are brough to almost a complete halt when working with these. 2 hours our work becomes 16 hours and still nothing accomplished. I will post my system specs later but it’s defin not my systems. I’ve worked with Corona since 2015 and had way better experience with the plugin. I think as a License customer I should have access to all the Beta tests that we’ve been using especially in a situation like this so we can at least meet our obligations. I was under the assumption that when we purchase a license we’d be able to utilize all the older builds for flexibility. We ditched Vray in 2015 and committed to Corona because it’s a great plugin. We don’t doubt that Corona will get it right, we just need a way out right now.Corona is way underpriced as it stands. Perhaps they should increase the price and get more developers in there to iron these things out.

Guys can you please release the older versiona of corona for use please!!!!! We bought the license and everything went downhill, we havent been able to do any work at all for 3 + weeks, im not going to explain our situations again becuase we havnt get any worthwhile solutions, we havnt been able to produce any work in 3 + weeks, we are running a business just lik the guys who use 3ds max, we have clients work / contracts that we're not fulfilling because of problems with the plugin... Please, we have a license, atleast give us the chance of using an older version like alpha 5/ 6 because the most recent build are a headache. Please underdtand this is extemely frustrating... Give us something jesus christ!!!

We've sent all those details directly including the files that was being worked on. Its been 2 weeks and no solid response. My concern is; what do in the meantime if older versions don't work either. Everyone in the field should know how it is when you can't deliver the projects to clients adhering to deadlines. It cost us all money but most of all reputation. We've been patient all along the alpha testing. We just felt the final release would be less of a headache. Quite frankly, we've had less problems with older builds than we do with this new release. Left in the dark also means; i have no idea when theses problems will get fixed.

Happy I came here to know that this problem isn’t only happening to me. My computer maxes out right away no matter the resolution of the rendering. Power usage, CPU and RAM are through the roof. Computer Locks up and crashes. Sometimes the rendering doesn’t even start. A project that was done and ready to render out took me an additional weak just playing around to find ways to lower the file size etc. Files was only 35 MB.

I experience almost the same issues with RAM usage in Teamrender. Except my RAM usage while rendering a high resolution still image with teamrender is almost instant at max. While rendering the same scene on my workstation only just uses around 3 to 4GB of RAM (see attached screenshots). Also nearly all my teamrender-clients crash while teamrendering this project. Unfortunatly without creating a bug report. The Teamrender client just quits.

Having this very same problem. Using Carbon Scatter to populate my scenes with grass and trees and Corona only renders a few of the scattered objects. Last 3 projects I had to us e 2D grass textures, sad.

I'm not sure if I'm doing something wrong but it has been going on for some time now and that is that my viewport freezes for a while when I have corona porxies in my scene.It only happens when I switch from perspective view to top view and not vice versa. With one proxy with a 250MB file inside it freezes about 4 seconds. With 8 of those it freezes about 32 seconds. Makes no difference if I use "Cache in RAM" or not, neither what visualisation method. I use a 4 view panel and i switch between them with the F-keys.So everything goes smooth when proxies are loaded, no problem at all. It's only when I switch from perspective view to top view but that happens quite often unfortunately :(