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.
looks like they need highlight compression ..?.. Exactly.
Transparency always comes with a cost. Look how drastically rays/s gets reduced in second render - from 4,5M to 2,8No, I don't use any bitmaps in opacity, only a procedural Falloff, from white to very light grey.. but thanks for this piece of info :)
If you're using bitmap in opacity slot, you should take special care in what format you choosing, as there might be a huge difference in performance: https://forum.corona-renderer.com/index.php/topic,4249.0.html
No no no, yes :D i could be more explanatory here is the link https://forum.corona-renderer.com/index.php/topic,1012.0.html
What i want to say to you, by looking your material, your white is too white...
Basically nothing is white 255.255.255 so if you make bunch of materials in your scene too white it will make your render times higher. So instead using 255 for white you should use 170.170.170 or use 255.255.255 and set level for diffuse to 0.7.
What are you referring is albedo element it is used just so it make it easier for you observing what has high albedo by showing it in red(you can switch to it in corona VFB)
Please read about it as it is well explained in forums.
Also this is just as starting point and one possible reason of your high render times and it is reasonable to expect render times going up when you use translucency, caustics or scene with more complex GI or materials.
Yo mate, please search "AlBEDO" on forum, things will be much clearer after.Wow.. I'm more confused now :D .. can you give me a little bit more direct information.
I don't like this licensing model at all. Yes, it's new and innovative, and supposedly the super-duper-Saas model is very fair to the final users. But in my humble opinion it's not. The first licensing proposal had to be completely redone, because it was so completely unfair for the box model and heavily biased towards the Saas model. And even now, after the changes (thanks guys for at least including payed updates in the box model...) still is.
I look at the Box model and think about Corona as a render engine in it's baby stage, a very promising baby by the way. But let's not forget that there are a ton of features that haven't been implemented yet. I'm very sure the development team is going to do a great job, and give us a full fledged render engine, no doubt about it. But come on... the baby 1.0 version, is the same price as the competition (Octane v2.x is 459€ and Maxwell v3 is 446€), and if you're not lucky enough to get the promo discount you're either left with no updates, or paying 100€ more. Those are way more developed versions, tried and true... those are grown ups compared to Corona. Doesn't seem so fair right?
So then I look at the Saas model, supposedly the fair option. But to me it's just a neat way to get you hooked into the system. Very easy to step in, affordable at the beggining and "you are always free to take the door and leave". Of course you are.... and then in 2 years time, when all your libraries are converted to Corona, all your workflow is optimized for Corona, all your work has been done in Corona, and all the time you have spent in mastering Corona ... are you gonna leave? After two years, when the licensing costs are starting to get equal and you see your mighty Saas slowly overtaking the box model costs, will you want to leave and be left with nothing? I guess not... You're going to be hooked with no way to step out, cause once you stop paying for the Saas you're left with just a crippled demo version. And nobody wants that. That's when the money leak starts, and you wish you had bought the Box version.
If only the Saas model would give us the chance of owning the software once the box model price was met, meaning you could really step out of the game and at least keep a usable piece of software you have paid for... I would see it fair. But right now it just doesn't add up. We're either blind-buying the baby-box model at a higher cost than the competition, or stepping into the leaky Saas model.
sorry, I did not supouse that you don't have photographic exposure checked on!NVM, I really appreciate your help :)
If you want to use "photographic" exposure controls, then you definitely need to have use photographic exposure checked. OTOH, why do you want "photographic" controls if you don't have a clue what it does? Use arbitrary exposure control (EV) - it's much easier to understand.
p.s. you really don't need to touch film width control, unless you know what you're doing.
Do you mind that f-stop for example does no changes in Relation to the Film-width or f-stop does No changes at all?No, it doesn't change at all, I may send you 2 renders with different F-stop values, OR ISO values with everything else is constant, but sending them won't make any difference as they are EXACTLY the same.
