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 - Ludvik Koutny

Pages: 1 2 [3] 4 5 ... 171
31
News / Re: Corona Renderer 1.7 for 3ds Max Daily Build
« on: 2017-09-20, 11:00:01 »
Would be great if you could override the exposure with the new Corona Cam. Hope this will be implemented.

It's right there, in the Tone Mapping rollout. It's true that tone mapping is not directly related to exposure, so maybe it needs better place in the UI.

32
[Max] Daily Builds / Re: Daily Builds 1.7
« on: 2017-09-19, 17:13:42 »
No Ondra, i don't have any volumetric effects in this scene. I can send it to you if want.

Edit: I've send it to you through Private Uploader.

Go go go :)

Use the private uploader link in Ondra's signature :)

33
[Max] I need help! / Re: VFB saturation produce noise
« on: 2017-09-18, 13:03:48 »
It's not expected, it's probably just an order of operations issue. It should be fixable, but the fix could possibly introduce issues somewhere else.

34
[Max] Daily Builds / Re: Daily Builds 1.7
« on: 2017-09-11, 12:11:41 »
I'd also vote for option to install LUTs optionally, in the same manner as material presets. Of course, I would still make the option to install both of these ON by default, so new users who don't know what they do yet won't miss out on it.

Specifically for LUTs, I would probably always include Dubcats trio of Photographic LUTs, regardless of if the LUT package is selected or not.

35
There may be some problem with the new sampler maybe... not having the static pattern in places where it should. I would recommend you to upload the scene here https://corona-renderer.com/upload and report the problem in the bug reporting section along with the name of the scene.

This is the best way to ensure developers will take a look at it and make sure whatever is happening will be fixed in 1.7. Since I see that your noise pattern is static on most of the images, but moving in the glass parts, it's probably a bug at a lot lower level, which users can not work around in any way.

36
The good thing would be the dirt - vray material or even the Fs today is definitely better developed than Cr.
enRich dirt support - doing a great job .. AO in CR. It has far less potential than its neighbors

http://www.enrichpro.com

What exactly doesn't CoronaAO do that V-RayDirt does? Last time I checked, they were nearly the same. V-RayDirt has some legacy stuff like reflection occlusion and environment occlusion back from the days when people used to fake GI with AO, but when it comes to procedural material creation, both have pretty much same feature set.

37

Yes, but I mean DomeLight does not do that either.

If you switch Camera and want to change environment with it, then in V-Ray, you have to disable current DomeLight and enable another one, and in Corona, you have to replace current environment map with another one. It's about the same amount of clicks.

I uncheck render hidden lights in the render panel. Then I name the layers based on the cameras. That way I can turn on and off the lighting rigs with layers, which are recorded in state sets eventually

I still don't get it... State Sets record state of the map in the environment slot too... :|

38
Quote from: Rawalanche link=topic=17249.msg108232#msg108232


Eh... Just drag and drop another map into environment slot...?

yes i do that now. but when you have a max file with 30 cameras, you need to rotate or completely change the hdr based on that view. it would be SUPER DOOPER cool if somehow we didn't need to reassign those custom settings every time you switch cameras. Know what i mean?

Yes, but I mean DomeLight does not do that either.

If you switch Camera and want to change environment with it, then in V-Ray, you have to disable current DomeLight and enable another one, and in Corona, you have to replace current environment map with another one. It's about the same amount of clicks.

39

There's nothing that V-Ray's DomeLight can store that environment map in environment slot can not.


copy your dome light and chose a different hdr. now your scene has two hdrs that you can turn on and off for different renders. how do you replicate this workflow in corona? assign the hdr to a non renderings object? save different max files just for different hdr's? you cant? Please let me know!

Eh... Just drag and drop another map into environment slot...?

40
about DomeLight, I don't have longer experience with vray but what I understand is it is a feature which gives user a room to store custom lighting options, am I right?
if ondra doesn't want it because of it could hurts corona's simplicity but in other hands users really need custom lighting options (including me sometimes).
then .. what about integrate custom lighting inside the CoronaCamera? :)

DomeLight's primary use in V-Ray is not to store different custom lighting options, but just to make image based lighting work in the first place. Without it, HDRI illumination does not work correctly.

There's nothing that V-Ray's DomeLight can store that environment map in environment slot can not.

Multiplier of DomeLight is equal to RGB Level value of Bitmap or CoronaBitmap in the environment slot, rotation of the DomeLight is equal to U offset in Bitmap or horizontal rotation in CoronaBitmap, Visibility, and reflection/refraction multipliers are equal of using environment overrides in Corona.

In general, switching multiple environments with DomeLights is not faster or slower than doing so in the environment slot.

41
it should be scriptable - some simple UI where you drag&drop few maps and there is one switch controling which one is used. Somebody can try writing it ;)

Drop a Color Correct or Output Map into the environment slot. Drop 4-5 hdri into the slate material editor next to the previous mentioned map. Takes 1 hot key and a simple drag of a node to switch between multiple hdris. This is how i do it and it works great.

I haven't read that this would be put in anywhere, but I would like to see the Corona Toolbar found over in the Corona Goodies forum to be installed by default (Which is something Vray does).

You should use Output map, or CoronaOutput, or some light map like that. Autodesk's ColorCorrection is still, even after some fixes, unnecessarily slow map :)

42
https://labs.chaosgroup.com/index.php/rendering-rd/cg-garage-podcast-137-ondrej-and-vlado-corona-and-v-ray/

Here's some more behind the scenes info, which I hope should probably clear some more doubts ;)

43
Regarding DomeLight requests - adding DomeLight would not resolve Corona's inability to store multiple environments for LightMix. That's a completely separate and more complex problem. What introduction of DomeLight would do is just making IBL setup in Corona more confusing and less straightforward.

Then there should be another solution for the cases when need to keep 2 and more different environments in one scene with easy access, control and switching. Not everyone works with the slate material editor to keep separate tab with different environment maps, so this is not the solution.

You don't need slate, you can have it in the compact material editor. For example create CoronaMultiMap, call it "Environments", and into each slot, add environment bitmap you want. Then when you need to switch them, just drag a new environment map and instance it into environment slot.

As far as complexity goes, it's about the same number of input actions:

DomeLight:
1, Select current DomeLight
2, Click checkbox to turn it off
3, Select another DomeLight
4, Click checkbox to turn it on

Environement slot:
1, Hit hotkey to open material editor
2, Hit hotkey to open environment window
3, Drag environment map from editor
4, Drop environment map onto environment slot

I am still wondering why do people keep requesting DomeLight. It does not add any new functionality, ease of use or speed. A practical example where DomeLight does something more or does it faster would be much appreciated.

44
Maybe this is already possible, in that case ignore this post.
A way to save the GI, or at least the most computationally expensive calculations.
This would be useful for animation rendering, if the scene doesn't have moving objects.
And not only for animation, but even for stills, if one already waited for an hour for a render to finish and he decided the still came out great, but he wants to re-render again with a slightly higher resolution, would be great to just save the calculation to a file, and re-render again from that file. And now the renderer needs to calculate mostly antialiasing and reflections, but not the lighting.

I think Vray has something similar to that.

I know Corona is suppose to only use modern techniques, and baking lighting is old technology, but I think many many years need to pass until a full quality still frame takes between 1 and 10 minutes where the baking point becomes moot.

Corona does this already for UHDcache. To do it for primary GI bounce would require something like Irradiance Map, and that's probably not going to happen.

Regarding DomeLight requests - adding DomeLight would not resolve Corona's inability to store multiple environments for LightMix. That's a completely separate and more complex problem. What introduction of DomeLight would do is just making IBL setup in Corona more confusing and less straightforward.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------

As for my vote, definitely being able to see refraction in masking and texmap render elements. It's a long overdue already for such an important feature. V-Ray does that well :)

45
[Max] Daily Builds / Re: Daily Builds 1.7
« on: 2017-08-27, 16:36:46 »
Hello,

Is there any way I can go back to the old image sampler now that Corona is not backwards compatible anymore? Something is wrong with this one, I don't really have any speed improvement and I get a lot more reflective noise than I had before. I haven't had the time to properly test it, but this is how it feels. I made the huge mistake of working on my projects while updating to 1.7

Where there major changes to the sampler between Version 1.5- Version 1.6 as well ? Because so far I felt 1.5 to be the best.


Thank you,

It would make a lot more sense to send that scene and get that bug fixed, rather than revert two versions back.

Pages: 1 2 [3] 4 5 ... 171