Which OSL Textures are supported/not supported, whichever list is shorter?

[Morne]

Hi Team

For GPU, which OSL maps are supported or not supported. The docs just says "Some OSL maps are not supported yet."

[ikomitov]

Hello Morne,

Any shaders with string outputs will not work. In general, shaders which involve string operations may not function as expected, since V-Ray GPU has very strict limitations with respect to string handling. So here is a list of the problematic 3ds Max shaders. These will not work because they return strings:

• GetNodeName.osl
• SetFile.osl
• SetFilename.osl
• SetString.osl

These will skip the automatic gamma correction (the gamma is determined by the file extension):

• HDRIEnviron.osl
• OSLBitmap.osl
• RandomBitmap.osl / RandomBitmap2.osl
• UberBitmap.osl

The following do not work because the object picking is not implemented yet (applies to CPU as well):

• CameraProjector.osl
• ObjectProjector.osl
• SphericalProjector.osl

GetParticleAge.osl does not work because the paLife attribute is not supported (applies to CPU as well).

In case you are interested in the language details, this is what GPU-friendly shaders are allowed to do:

• string initialization with a string literal, e.g., string a = "foo";
• string initialization with another string, e.g., string b = a;
• string assignments, e.g., a = b; b = "foo";
• equality checks: a == b; a != b;
• passing strings as arguments to function calls, e.g., string a = "foo"; bar(a);
• returning a string from a function, e.g. string bar() { return "bar"; }

Using any other string operations and string routines may lead to undefined behavior.

I hope this gives you some answers about what kinds of shaders the GPU can execute.

Best regards,
Ivan

[Morne]

Awesome, thanks Ivan
Would be good if this can be added to the docs