Announcement
Collapse
No announcement yet.
RT GPU - Titan XP - crash
Collapse
X
-
Originally posted by John_Do View PostHello guys,
I just got my new GPU and it seems that V-Ray doesn't like it, RT GPU systematically crashes. I have installed the latest nVidia drivers ( 373.06 ).
What is wrong ?
Thank you for the post.I am not sure but it is a possible problem with drivers. Can you uninstall the existed drivers r373.06 and reboot PC to complete a process. Download a new one from http://www.nvidia.com/download/drive...x/107563/en-us (372.90), install it and run RT GPU.
BR BoyanBoyan Nalchadjiiski | QA Engineer @ Chaos |
E-mail: boyan.nalchadjiiski@chaos.com
-
Another issue, can't find the cause despite my trials.
I have a simple V-Ray material which works fine in the Shader Tree, with the three V-Ray engines ( RT CPU/GPU/prod). But when I setup it to work in the Schematic View, the glossiness isn't the same in RT GPU, see below ( prod/RT CPU / RT GPU ) :
At first I thought it was the Inverted setting which was not supported in Schematic View but it's supported. The gloss map seems to work since inverting it of modifying the gamma does something. But the gloss value is wrong. Is there is something that I should be aware of ?
EDIT : haha, I have just inverted the map in Photoshop and test RT GPU, it works..I spoke too quickly ! BTW please fix itLast edited by John_Do; 18-10-2016, 03:02 PM.
Comment
-
.I spoke too quickly ! BTW please fix it
I don't understand what the issue is exactly.
Greetings,
Vladimir NedevVantage developer, e-mail: vladimir.nedev@chaos.com , for licensing problems please contact : chaos.com/help
Comment
-
You had Texture Color R connected to glossiness, instead of Texture Value.
I don't think it's the invert option that's broken, but rather the combination with using one of the RGB output channels.
Do the connection as shown, and it seems to work the same in CPU and GPU, with or without invert.
I will log the issue.
Greetings,
Vladimir NedevVantage developer, e-mail: vladimir.nedev@chaos.com , for licensing problems please contact : chaos.com/help
Comment
-
Yeah thats irritating. Value is actually a bit like black white map, so in theory both should work. At least that was the case in 3dsmax. However in Modo its split up, which makes no always sense with V-Ray. In a perfect world V-Ray would be able to use both, converting a Value to a b/w RGB map or a RGB to a Value without asking the user.. but I guess its quite difficult to code.
Comment
-
In a perfect world V-Ray would be able to use both, converting a Value to a b/w RGB map or a RGB to a Value without asking the user.
When you drag a color output to a value(scalar) input, MODO connects the R channel output.
It would be more logical to have a warning appear that lets you choose the value(scalar) output instead.
When you drag a value(scalar) output to a color input, MODO connects to the R channel input.
It would be more logical to connect the value to all three channels automatically or give you a warning.
You need to ask The Foundry to make these modifications to the Schematic UI.
Btw, the value output is computed as the luminance of the output color ( 0.3*r + 0.59*g + 0.11*b ).
Greetings,
Vladimir NedevVantage developer, e-mail: vladimir.nedev@chaos.com , for licensing problems please contact : chaos.com/help
Comment
-
Originally posted by vladimir.nedev View PostThat's a problem with the MODO UI, not V-Ray for MODO...
Sorry for the MODO rant on the Vray forum...just agreeing.
Comment
Comment