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.


Messages - dj_buckley

Pages: 1 2 3 [4] 5 6 ... 59
46
[Max] Feature Requests / VFB Curves Histogram
« on: 2024-02-01, 14:47:15 »
If you add curves to the tonemapping stack the histogram is only effected by the operators above it and not the curves operator itself.  To the see the effect of the curves operator on the histogram you need to add another curves below it which seems pretty counterintuative.

Repro steps:

Start IR
Add curves operator at bottom of tonemapping stack
Adjust curves and observe histogram not changing

I appreciate this is how the curves adjustment layer works in PS, but you also have a separate histogram in PS that shows the effects of changes made to said adjustment layer

47
[Max] I need help! / Re: wxWidget Debug Error
« on: 2024-01-30, 15:32:29 »
I've never experienced it with Corona 10.  It's only since upgrading to 11 and now 11 hf1.  It's all scenes and it isn't consistent.  It doesn't happen every time.  It's random

48
[Max] I need help! / Re: wxWidget Debug Error
« on: 2024-01-30, 14:37:20 »
11 and now 11 Hotfix 1

49
[Max] I need help! / Re: wxWidget Debug Error
« on: 2024-01-30, 14:29:42 »
Any news on this at all, it's still happening

50
3. Furthermore, I have logged a feature request to provide a way to selectively color correct a hue range using Corona color correct map (Similar to Color Correct OSL). (Internal ID=1292062353)

Thanks Avi - this would be ideal, not just for the Sky.


51
2. Regarding the slight shift in clouds' pink tint when using Corona Sky with Corona Color Correct, I'm not able to reproduce this issue on my end. In my testing, using Corona Sky with or without Corona Color Correct maintains consistent results. Please ensure that all settings are applied correctly, and if the issue persists, feel free to provide additional details or share specific settings for further investigation.

Not quite, the shift happens when you increase the ColourCorrect saturation to say 0.25,  this boosts the blues and brings that nice blue back, but it completely messes up the clouds.

52
Here's the scene and the steps.

- Open File (note sun position in relation to camera etc etc)

- Start Interactive from Camera View

- All looks ok but the sky is very pale and not desirable - this is default settings (the only change is setting Cirrus Amount to 0)

- Change ColourCorrect saturation to 0.25 to get some blue back into the sky - YIKES where did that pink come from in the clouds.

- Change ColourCorrect saturation back to 0 to restore some normality

- Increase VFB saturation to 1 - YIKES that's where it's coming from, although they don't look like it at default settings the clouds are indeed carrying a pink hue which is clearly demonstrated when we increase the VFB saturation.

- Put VFB saturation back to 0

- Change ColourCorrect saturation to 0.25

- Reduce turbidity to 1.7 - nope still pink, this can be verified again by setting VFB saturation back to 1

- Increase altitude to 350m - eek, the clouds look slightly less pink but now the grounds gone pink, what's happening?

The point being, as soon as you plug the Corona Sky into a ColourCorrect to boost the blues, the clouds go all sorts of wrong because although they don't look pink with default settings, they are indeed carrying a pink tone which becomes really exaggerated with any saturation adjustments

53
Hi Avi

Maybe I'm missing something here but here goes ...

A).  Throughout your video from the start to the end, your clouds are clearly pink.  Even with your turbidity at 1.7, they're pink.

B).  Your ColourCorrect is set at default, so of course there will be no change, try bumping the saturation in your CC node to 0.25 as i explained in my initial steps.

C).  Test it without the saturation in the VFB at 1.  I only did this to exaggerrate the effects after my initial tests.

D).  I have ACES OT turned on in my tonemapping stack.

I'll send a scene over shortly.

54
Just wondering if this ever got solved?

55
Trying to get my head around using the built in clouds and so far I'm not impressed.  They only seem to work if you leave the sky at defaults for everything.

As soon as you put the sky in a CC node it's game over.

I'll set the scene.  This is a sunny afternoon shot (2.30pm) in the Caribbean (or it's meant to be).  The sun is infront of the camera and off to the left (about 45 degrees)

Image 1 - this is the default Corona Sun and Sky with Clouds off.  It's way too pale (but there are plenty threads about that).

Image 2 - this is default Corona Sun and Sky with Clouds turned on.  Clouds look okay'ish.

Image 3 - this is default Corona Sun and Sky with Clouds off, plugged into a CoronaColourCorrect to boost the saturation of the sky a bit (0.25 Sat)

Image 4 - this is the same as Image 3, but with the Clouds on again.  The clouds are clearly pink.

The second column of images is the same as the first column but with PS Saturation set to 100.  This is to serve 2 purposes.  A).  It demonstrates just how pale the default CoronaSky is and B)  It demonstrates the very obvious magenta tint to the clouds.

Not only that but when turning on clouds the entire sky goes darker so the blues become a differnt colour.  Why is this?  It's almost as if enabling clouds gives the rest of the sky a grey wash.  My clouds amount is set to 0.25.

I appreciate I'm kinda looking towards the sun here so I'm not expecting an ultra saturated blue sky but even so, the default sun and sky looks so grey with a very subtle hint of blue.  I can deal with the colour though, it's the clouds that fully ruin everything.

Last note - there's another thread on here at the minute about banding in the sky.  This banding is evident in my screenshots too.

56
[Max] General Discussion / Re: Price Increase
« on: 2024-01-24, 17:39:34 »
Every time anyone tinkers with and adds to code of a program it creates the possibility of Nth amount of issues.

This is what I was talking about.  Last few releases have resulted in something breaking from the previous release, that was originally working absolutely fine.

57
[Max] General Discussion / Re: Price Increase
« on: 2024-01-24, 15:12:42 »
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 get what you're saying but that £20 a month is what paid for the Corona we have today.  It funded development so it's not as simple as comparing the two like for like in that way.  And it really isn't £10 more.  The maths/increases have been explained multiple times over.  For some it's close to 1000% more than it was back then.

The other way to look at it is, with increased prices today, you'd expect more groundbreaking features and faster development, as more money is being injected into it in with the higher prices in theory.  But that doesn't seem to be the case.  As you said, we're literally paying more less, I'd even settle with paying more for the same, but the expectation naturally would be paying more for more.

58
[Max] General Discussion / Re: Price Increase
« on: 2024-01-24, 14:37:37 »
And be mindful that those legacy deals with 3 render nodes will not last forever. Nothing does. Just business, nothing personal.

Appreciate that but if we go back to my original question - this was all part of why a lot of us went with Corona in the first place.  Taking things like that away contirbute to taking away Coronas edge over the competition.  My original question that started the thread was basically "Why am I using Corona these days and not something else?"

I was looking for USP's and so far nobody has been able to give me one really.

I don't know anyone that's happy with paying more for less.  Where else does that happen in the world?  I can't think of anything that I pay for currently that has increased the price and at the same time taken benefits away.  It's akin to my phone service provider telling me the price is going up but at the same time telling me I'll be losing my data limit, but I can buy it back as an addon if I want.  You'd switch providers immediately or I would anyway.

59
[Max] General Discussion / Re: Price Increase
« on: 2024-01-24, 14:00:06 »
I+ VRay is the flagship product and it will always get more attention: you are paying less for less. Fair deal.

What a tag line, Corona wouldn't have existed at all if this was the case from the start imo

60
[Max] General Discussion / Re: Price Increase
« on: 2024-01-24, 13:52:33 »
I would suggest to take a step back for a moment (mid 2010's I guess if you value precision).
Archviz crowd fell in love with Corona exactly for the reason of it having less features than VRay.
If you do not need all the Premium "gimmicks" but would happily enjoy some of VRay's features: VRay Solo being priced exactly as Corona Premium might be the option for you. Again: fair deal.

We also fell in love with it because it was cost effective and independent and development was fast etc etc

With regards the 'Solo' option - this is the whole point, we would then lose render nodes and floating licence, so it becomes much more expensive than Premium if you want those features back ...

A lot of us indie's have more than one PC that we use for DR or with Pulze etc so the render nodes that we got as part of our monthly subs back in the day are essential.  Also, as an indie, by nature you can work from anywhere, it's great having Corona installed on your main PC, but then having a floating licence so you can also pick up your laptop and go work from wherever whenever.  You lose both of these things with Solo.  So you're forced to take the Premium option because it's cheaper than Solo + Render node + Render node etc, but then you're paying for premium and the price of premium includes Cosmos and all that Jazz. 

There's no middle ground.  We need a middle option for Floating Licence plus Render Nodes minus Cosmos, Phoenix etc etc.  Call it Solo Plus or whatever you want.

Pages: 1 2 3 [4] 5 6 ... 59