Messages

106

[Max] Resolved Feature Requests / Being able to see lightmix in IR extended viewport.

« on: 2018-01-29, 10:58:01 »

Hi guys

I would love the option to choose which render element the extended IR viewport should be showing. Especially when using the interactive lightmix. It just defaults to the beauty pass which makes it rather useless for lightmix use.

There was an earlier post regarding render elements here: https://forum.corona-renderer.com/index.php?topic=15778.msg99805#msg99805

107

[Max] I need help! / Re: Lighting interior - uniform/diffuse lighting

« on: 2018-01-01, 16:06:20 »

Already looks better and yeah, all the little details adds up to making a more realistic image. It's hard (if not impossible) to nail great lighting in a scene like that. I would advice you to always test lighting on a complete scene. The light will behave and look very differently on a full scene.

In your reference, it is however mostly a wooden clad interior. So you probably need to tweak that wood material until you get something pleasing (don't be afraid to cheat a little to get the look you are after). But know, that a lot can still be tweaked in photoshop ;)

Have fun :)

108

[Max] I need help! / Re: Lighting interior - uniform/diffuse lighting

« on: 2017-12-29, 11:54:25 »

I'm wondering why you are getting that extreme red/purple glow coming from the back on the edges of your image. Do you have an object there with a vray material or something else that will give that bright red glow?

Also, don't be afraid to tweak your materials to get the result you are after. You could put in a color correction node on some of them and desaturate the diffuse map.

Same thing with your light source aka the sun and sky. Play with the light temperature on both of them, you can even desaturate the sky a little.

You can also use the inverse color picker in the "color tint" option in the framebuffer, click around your image to try and get a better balance temperature wise.

Show us what you end up with :)

109

[Max] I need help! / Re: [solved] Opacity map doesn't ignore reflection on mesh backside.

« on: 2017-12-19, 17:31:48 »

sorry about that Maru, deadline later today and thought I'd better report before moving on to a new project. I can confirm there is no problems if I set refrac value to 0 or tick the "thin" option. But I agree. There shouldn't be any refraction at all. Was a vray mat an 1 click convert, only added the correct translucency map manually as it seems to get rid of them when converting.

110

[Max] I need help! / Re: Opacity map doesn't ignore reflection on mesh backside.

« on: 2017-12-19, 10:19:44 »

Uploaded scene with just the tree, awnings and a bright environment color. (It still happens in this scene when awning/canopy material has a reflection value).

Yes, leaves have a translucency map and a value of 0.6. If I set this to 0, there is no change at all. Only thing that helps seems to be removing refl. value on awning material.

111

[Max] I need help! / [solved] Opacity map doesn't ignore reflection on mesh backside.

« on: 2017-12-19, 09:12:26 »

Hi

I'm experiencing the attached result when rendering on 1.7 RC2. Scene was done in this version, so I don't know if it has always behaved like this. It doesn't matter if I have DR enabled or not.

It seems like the opacity map doesn't ignore the reflections cast on the mesh backside.

Here I have some simple shop awnings behind street trees. If the material on the awning is reflective, it will bounce the light on the backside of the tree leaves mesh and produce the attached result.

I'm just removing the reflection on the awning material as a quick fix for the project, but I don't think it should behave like this right?

112

Hardware / Re: Workstation advice

« on: 2017-11-23, 10:16:15 »

What model is your current i7 CPU? You can type it in on the benchmark site and compare the performance to the X5550 Xeons you would get in that ebay build:

https://corona-renderer.com/benchmark/cpu/X5550

113

[Max] General Discussion / Re: Corona 1.7 - CMasking netrender error

« on: 2017-11-18, 12:46:30 »

"Masking/other render elements coming out mixed with some other kind of image - like focus sampling mask or beauty"

To all users experiencing this:

1) Make sure you are not using V-Ray cameras in your scene, or any other part of V-Ray or other renderer. In case you are using a V-Ray camera, or any other non-native 3ds Max/Corona object, please remove it, and see if the issue persists.
2) Is V-Ray installed on your render node(s)? If so, please try re-installing V-Ray, and see if the problem persists. If it does, please try uninstalling V-Ray completely on the workstation and on the node(s). Then see if it helps.
3) If none of this is helping, please contact us here https://coronarenderer.freshdesk.com/support/tickets/new with a description of the problem, example image of what you are getting, and all DR logs - here is how to get them: https://coronarenderer.freshdesk.com/support/solutions/articles/12000002065

Just a note: we are not sure if this has anything to do with V-Ray, but it seems that in at least two cases the solution was to either re-install V-Ray, or to stop using V-Ray camera. It could as well be a false trail, but in such case maybe we will be able to find the correct one.

Another idea:
Make sure there are no leftovers from an older version of Corona on your PCs - go to Windows "Programs and Features" list, uninstall Corona Renderer, and then install 1.7 again. Make sure 1.7 is installed on all computers taking part in DR, and make sure that you are using DR server 1.7 on all of the nodes.

This happens with both phys and corona cam. Wasn't an issue prior to 1.7. Has been like this since the daily builds and still persist after clean 1.7 final build on both workstation and rendernode.  Images renders fine when just using workstation or the node via backburner (no DR). Will try and send you some DR logs.

114

Hardware / Re: Curved Monitors?

« on: 2017-11-09, 10:07:51 »

Just as an FYI for anyone reading this thread at a later date I eneded up getting two Dell 34" U3417W's.  They're basically a slightly newer version of the U3415W's.  They have a sharper curve (better for dual I thought) less backlight bleed, better speakers (not a biggie but nice), thinner bezel, etc.

Anyway...so far, loving them.  They come pre-calibrated like other Ultrasharps, each with their own 'calibration report.'  The color seems to be very true and also the monitors very closely match each other, which is nice.  The curve is also good...nothing I notice day-to-day but I bet I'd miss it if it were gone.  Especially with dual screens.

Anyhow, love them and would recommend them.  The only issue I have so far is that on a fresh boot they don't show a signal with Display Port, only HDMI.  This seems to be kind of a common issue with 1080 Ti cards though...might just end up using HDMI.

Cheers,
Daniel

Wait, so you have two 34" curved monitors next to each other? So this is basically you during a workday yes?:



Also, yeah I'm having the same signal issue on boot when using display port on nvidia cards. It definitely prioritizes the other ports.

115

[Max] General Discussion / Re: Corona 1.7 - CMasking netrender error

« on: 2017-11-04, 20:06:01 »

I'm also getting weird results with the CMasking_ID and CShading_SourceColor pass when using DR in 1.7. No matter the scene and both with phys+corona cam. All works good if I only render locally or on the node via backburner. So it's a DR problem for sure.

Main PC = single xeon
Node = dual xeon

116

[Max] Daily Builds / Re: Daily Builds 1.7

« on: 2017-10-26, 12:49:38 »

I'm getting weird results in my CMasking_ID render element when I have DR enabled. Happens in all my scenes with RC7 Build and DR enabled. All is fine without DR. Think it was there in RC6 too, but figured it must've been a specific scene. Not the case. (haven't tried RC8 yet). See attached :)

I'm still getting a weird result with the CMasking_ID and CShading_SourceColor pass when using DR. Using the final 1.7build nothing has changed here. No matter the scene. All works good if I only render locally or on the node via backburner. So it's a DR problem for sure.

Are you able to reproduce this? Screenshots are in org. reply in this thread (reply #770)

117

[Max] Daily Builds / Re: Daily Builds 1.7

« on: 2017-10-22, 17:40:53 »

Hi Jens. This looks like the "light leak" issue, that has been discused several times on this forum. In most of these cases the problem occurred because the walls had no thickness, and the solution was to ad thickness, for example by using a shell modifier.

Is this the same in your case?

Thank you PROH! This was indeed the case :)

118

[Max] Daily Builds / Re: Daily Builds 1.7

« on: 2017-10-22, 15:47:10 »

Have any one experienced this issue with white noise in corners? Never seen it before in earlier versions, but it happens constantly now. Albedo pass is fine, all values good.

(I'm still on RC7 due to the many reports of how unstable and buggy the newer versions are).

119

[Max] Daily Builds / Re: Daily Builds 1.7

« on: 2017-10-14, 18:54:22 »

I'm getting weird results in my CMasking_ID render element when I have DR enabled. Happens in all my scenes with RC7 Build and DR enabled. All is fine without DR. Think it was there in RC6 too, but figured it must've been a specific scene. Not the case. (haven't tried RC8 yet). See attached :)

120

[Max] Resolved Feature Requests / Re: Instancing with Forest Pack and Rail Clone - status?

« on: 2017-10-07, 10:11:51 »

Is this something that will be partially possible to do in 1.8 roadmap with the "Multimap - randomization by mesh elements"?

If so, I hope it won't continue it's implementation ETA from 1.6->1.7->1.8->1.9 ;)