If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Exciting News: Chaos acquires EvolveLAB = AI-Powered Design.
To learn more, please visit this page!
New! You can now log in to the forums with your chaos.com account as well as your forum account.
It depends on where you set the gamma. If you set it in the V-Ray color mapping options, then the results should be the same (but it depends on your other color mapping settings as well). If you change the 3ds Max output gamma, then they will be different.
I think we found an issue in Vray 2.2.02. We've noticed strange happenings when using Composite maps fed into the texture slot of Vray Area lights in use with RT (CPU). It's difficult to reproduce though. With bitmaps or standard maps fed into layer input slots of a composite map and others feeding into their mask inputs, when you adjust the opacity slider in that composite map, RT will sometimes freeze or return black in those lights. I've been trying to build a scene to post here but this issue is crashing max completely.
Ok I've pin pointed the issue. The problem: RT (CPU) using a composite map in the texture slot of a vray area light and lowering the opacity to zero on the bottom layer of that composite map, will cause the entire light to go black in Vray RT (CPU) 2.20.02. The bottom layer's opacity seems to effect all layers above it. I've linked a simple scene here that demonstrates the problem. If you run RT (CPU) and adjust the composite map layer opacity on layer 01 you will see the issue.
Ok I've pin pointed the issue. The problem: RT (CPU) using a composite map in the texture slot of a vray area light and lowering the opacity to zero on the bottom layer of that composite map, will cause the entire light to go black in Vray RT (CPU) 2.20.02. The bottom layer's opacity seems to effect all layers above it. I've linked a simple scene here that demonstrates the problem. If you run RT (CPU) and adjust the composite map layer opacity on layer 01 you will see the issue.
I don't have 2.2.3 here (still running 1.5sp5) but can anyone confirm massive crashes to desktop with particle flow toolbox#2 and it's particle skinner (that allows for ripping and tearing) and changing topology? In particular when this changing topology mesh is cached with SuperMesher at any given sub frame sampling quality.
I don't have 2.2.3 here (still running 1.5sp5) but can anyone confirm massive crashes to desktop with particle flow toolbox#2 and it's particle skinner (that allows for ripping and tearing) and changing topology? In particular when this changing topology mesh is cached with SuperMesher at any given sub frame sampling quality.
Comment