Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
If I remember correctly Corona's subscription started from 20/month. I do not recall the version number but I'm sure you wouldn't trade current Corona for the old one to save 10/month. You are getting more than you used to get. You might not like the things you are getting (Cosmos) but the value is there. Check car prices in Europe from the year Corona introduced subscription model to get some ideas about things getting expensive.
Regarding the USP? It is simply not there for you anymore most likely. But also look around and, if possible, show us a better deal from Chaos' competitors.
I regret my words in this post below in 2021 when complaining about the same this thread is complaining about.Vray costs $700/year for the whole ecosystem.
Corona costs $360/year for a fraction of the services and development.
I don't get it.
I don't use scatter, cosmos, corona materias, scans or anything else other than core Corona. If the price increases were for the "ecosystem", I don't think it's justified for most of professional archviz artists.
The biggest gripe for me is that most of the "new features" of late, are half baked or experimental and have been for some time. Rather than just a fully featured fully working new feature, they either don't work as epected or come with workarounds, exceptions and disclaimers. And they never seem to make it out of that phase. The focus of the last few releases seems to be around new users. Experienced long time users of Max let alone Corona, don't need Power Tools or anything like that. I can't see anyone that uses Forest Pack switching to Scatter when Forest Pack is about 10 years ahead in terms of development and isn't particularly expensive considering what it offers. Never gonna please everyone I suppose.
I don't understand the 6 monthly release cycle anyway. That alone has a rushed feeling about it. Personally think the release cycle should be as follows:
Big Release - Exciting New Feature(s)
6 months later - Hotfix that fixes anything that was experimental/half baked in the Big Release
6 months later - Big Release
Rinse and repeat.
So you're getting a big release every year and then a smaller bug fixer in between that addresses ALL of the issues from the previous release.
I guess at the end of the day, for customers to be okay with price increases they need to feel like they're getting value for their money. And of late (last few releases) it doesn't feel like that. Higher Cost + Less Features = Sour Taste.
It should be like that if you used your formula previously as you mention in your first post. And Corona should do conversion correctly both ways unless there is bug. (Only exception is when you reach 99999 value)
Example I just quickly tried:
Light A: 100cm x 5cm 5000 Lumen = 46 W/srm2
Light B: 200cm x 5cm 46 W/srm2 = 10000 Lumen
Works as expected. Watts per surface stay constant, Lumens as direct total luminosity adjust accordingly.
After setting initial amount in Lumens, change to Watts. It will convert the value and the Watts are measured per square area so the total intensity will scale up & down with size change.Perfect, thank you. BUT.. when I go into the light lister and change from lumens to default it changes every single light to 69.9 W no matter the lumens, if I change it back it still shows the correct lumens- should this be the case ?
Well, there were no changes to DR in this release, so this one is unlikely to be a bug. More likely to be an installation or firewall issue. Here are the guides:
https://coronarenderer.freshdesk.com/support/solutions/articles/12000002056-distributed-rendering-stopped-working-after-the-installation-of-newer-version
https://coronarenderer.freshdesk.com/support/solutions/folders/12000000629
Let us know if anything there resolves the issue, ty!
Anyone having any issues with DR? everything has worked perfectly up until the latest build and now it keeps parsing the scene in DR and then comes up red with connection failed? Both machines see each other but keeps timing out. Never had this before. Any ideas?
Just to ask the obvious and make sure - did you update Corona and DR on all the slave machines so they have exactly the same version of Corona installed? Also, by "latest build" do you mean "Final released version"? And other thought, be sure firewalls are set to allow the connections through (not impossible there's been an update to the firewall, or that the updated Corona needs some sort of update to your settings depending on how it was set up to let it through).
