Chaos Corona Forum
Official Stuff => News => Topic started by: Ondra on 2015-07-29, 15:00:08
-
Displacement
Physical camera
3dsmax atmospherics
Multimap improvements
bugfixes
and more. No cake this time.
https://corona-renderer.com/blog/corona-renderer-1-2-for-3ds-max-released/
Update: hotfix 1 is out, at the same URL. It fixes crashes some users experienced when opening older scenes with CoronaSun
-
Very cool! Tnx!
-
Super cool, really nice features. Was waiting for that displacement modifier. I only hope you guys have kept the original sun gizmo, I really like it :-)
-
Thanks for those improvements and bug fixes, can't wait to test it out!
However my colleague wanted to open a 1.1 scene with 1.2 and it crashes before starting with the Error Report of death:
"An error has occurred and the application will now close.
Do you want to attempt to save a copy of the current scene?"
After reinstalling 1.1 everything works fine again.
Is it maybe due to trying to convert 1.1 objects like the old Corona Sun to 1.2?
key data of the scene:
- Corona Sun
- ForestPack
- VertexPaint map
Maybe this helps. I you want a screenshot just ask.
BR Ben
-
can you provide us with the scene and/or the minidump?
-
Hi, we have installed 1.2 and testing the displacement modifier we have seen that checks Adaptive and Keep Edges Together are missing, as you can see in the picture... Is that correct?
In the movie of your page they are...
-
we have removed the checkboxes since, to make the UI lean and clean. Both features are now always enabled and there is practically no reason to disable them.
-
I actually wanted to test it on my own workstation (to reduce file size for uploading) and I was able to open the file without problems. Everything was converted correctly.
My colleague then opened an empty scene and merged the file into it, without problems as well. Seems to have been a glitch on his workstation's side..
We will observe it further in the future.
BR Ben
-
we have removed the checkboxes since, to make the UI lean and clean. Both features are now always enabled and there is practically no reason to disable them.
OK, thank you
-
Congrats with release!
Does physical camera 100% supported? And if not, which features are left? I've took a look at description of new camera in max 2016, that's a nice set of features - very temting to test it.
And WOW, CoronaBlend for 1.3! Looking forward to it very much.
Still no word about uv space anisotropy though...
-
Biased primary GI seems to be missing from the roadmap, any info guys?
-
Biased primary GI seems to be missing from the roadmap, any info guys?
It used to be included in old versions of Corona before
I think adding it will make Corona more and more similar to V-Ray, in my opion
However, hope to see Adaptive image sampling soon :)
-
all improvements very good! butt why change the sun ? the angle and rotation parameters are just perfect and precise using it combined with hdri, now it is just a crap like vray sun.
-
i also think the previous sun was better... with the angle and rotation parameters (more precise control)... or better implement checkbox , if the user wants a targeted sun then disable the angle and rotation... but overall great improvement...
-
How come .exr output does not include all channels in one file as it used to be?
It was handy and it was only one file with lets say 70 MB, now I have 10 files with ~500MBs
-
all improvements very good! butt why change the sun ? the angle and rotation parameters are just perfect and precise using it combined with hdri, now it is just a crap like vray sun.
You can read about this one here:
https://forum.corona-renderer.com/index.php/topic,7239.195.html
-
Still no word about uv space anisotropy though...
Is there a reason why nobody from the team is commenting on the implementation of UV space anisotropy?
It's seeming like more and more of a strange omission now given the other advancements since 1.0.
It was hinted at for 1.1 also. Could we have another estimate please if it's deemed too unimportant to make it into the roadmap?
-
I've put it on my TODO for 1.3...
-
Whattt! is this true? a bug or what??
thats not doable for me at the office, guess what it looks like 10 or so renders with all the passes on the folders....
How come .exr output does not include all channels in one file as it used to be?
It was handy and it was only one file with lets say 70 MB, now I have 10 files with ~500MBs
-
I think there are no related changes, it could be random. A bug report would be appreciated.
-
I've put it on my TODO for 1.3...
That would be great. Thanks for the info.
-
Regarding EXR channels, it was new Photshop CC 2015 that doesn't support reading all channels.
-
I´m getting severe lag in Max viewport after installing Corona 1.2 and opening any old scene that used to work before. Is this a (known) issue with Corona? I suspect it is because I haven´t done any other changes. Max reserves one CPU even when nothing is being worked on, and my whole desktop lags to a point where I need to close Max even to use a browser. I´m on a i7-4930K with 32G RAM.
EDIT: Ok seems like the issue occurs with Max 2016 but is not present in 2015.
-
Damn, I knew I am right with hesitating about 2016. I have the trial on my laptop but the layers issues, now lag. Hmm.
-
Damn, I knew I am right with hesitating about 2016. I have the trial on my laptop but the layers issues, now lag. Hmm.
Yeah not too impressed with it so far but to be fair this lag isn´t Maxs´ fault, I guess, since it worked just fine before.
-
still can be - the usually change something under the hood silently, without telling us, and it turns out something that worked before suddenly stops working and we are left to figure out which of the 20 thousand lines is causing the problem.
-
Just amazing work on this new update. The displacement features are really powerful.
But since alpha 7 i'm longing for the CoronaBlendMtl. Too bad it takes so long.
Also when can we expect the region render feature in CoronaFB?
-
Hi there, I'm still waiting impatietly for the hair and skin shader ( and it need to have the support for hairfarm and ornastrix to make it usable, since no one use crappy hair and fur in max.. ) Any idea whn it will come out ? It was supposed to be this summer.. but by checking the roadmap...
-
3d max 2016 crashes when i change inverse gamma settings in VrayHDRI from 1,0 to another value. It happens on different hdri maps. Both interactive and standart mode have this. Previous Corona version works fine..
-
Report bugs and crashes to appropriate section, please.
-
Report bugs and crashes to appropriate section, please.
It makes sense to have a discussion re: the current version in the very thread created for it, though? If you look at how many views topics in the Bug Reporting get vs this one for example you´ll notice this has already gotten more than 10 times the views of any bug report thread. When in hurry I´d rather take my chances on a popular thread where more people might have suggestions or a straight solution. Bear in mind we´re not only reporting bugs but working on paying projects and sometimes need answers sooner than later.
-
You can rest assured that devs monitors bugs reporting section as well as this topic. But it's much easier for single reports to be lost in a sea of irrelevant posts. You can still discuss them here, though.
-
You can rest assured that devs monitors bugs reporting section as well as this topic. But it's much easier for single reports to be lost in a sea of irrelevant posts. You can still discuss them here, though.
That´s besides the point which was the more views a problem gets the more likely I get an answer quick. I didn´t mean to imply I´d use the news section as a substitute for bug reporting :) Of course if I track down a clear bug I´ll report it but in cases like the one I asked about earlier I´d prefer checking out if it´s a known thing already before starting a whole new topic.
-
Has that issue with the IOR set to 999 been resolved yet? I remember seeing the temporary solution was to use a coronacolormap with RGB each set to 100,000 to obtain the correct falloff, but I wasn't sure if this was still a problem.
**EDIT**
The issue was mentioned here: https://forum.corona-renderer.com/index.php/topic,8214.0.html
-
I am also interested in steyin's question.
-
great stuff!
one thing...;
I'm going to argue that until adaptive displacement is sped up it would be really useful to be able to turn it off.
My scene with lots of displacement has used to take 10sec for geometry to cook. now it takes 20 minutes and most of the time crashes the machine.
-
have you tried decreasing displacement quality?
-
There is a new version of Corona that should fix the sun crashes/problems. Get it here:
https://corona-renderer.com/download/
-
Ondra - yes I have but it doesn't look nearly as nice. This is lots of craggy old architecture. . I have displacement at 1px and it wasn't slow at all. 87 million primitives.
Geometry took 10-20 seconds to cook.
With the new adaptive displacement. closer to 20 minutes.
Seems wrong that I should have to lower the quality of displacement with 1.2.
loving other improvements BTW. The fixed edges on displacement is huge.
-
Hi guys - one question about new displacement - does the geometry have to be turbosmoothed or quadified cause I have some shape drawn with splines and displacement is bugging me