query "scene:path" context var in OSL Expression node

[JeremyBooks]

Hey All,

From your docs etc, I assume it should be possible to query the scene path in an Expression node using OSL. I wrote this expression in Python with no issues, but converting to OSL to test speed, I am having some issues.

In short:

string scenePath = context( "scene:path", "defaultString"); printf("%s\n", scenePath);

results in the default value being printed for each location in the DAG. the Python equivalent scenePath = context.get("scene:path", "defaultString") works perfect!

Is this something that is not actually supported in the Expression Node?

[johnhaddon]

As you suspect, retrieving scene:path isn't currently supported in OSL expressions, but is supported in Python expressions. The reason is that scene:path is actually an array of (interned) strings, and we haven't implemented support for those in OSL. If there are no limitations in OSL itself (I haven't looked yet), we may be able to fix this if you'd like to open an issue.

[JeremyBooks]

As far as i can tell OSL has no issues with string arrays, I can certainly create an issue for this. I can imagine using OSL expressions for these situations that require all paths in the scene to be faster than python.