Improve OSL performance when controllers animate parameters

[Anonymous]

The title of this suggestion is perhaps quite self-explanatory. OSL is a great addition to 3ds max, but when it comes to animating parameters OSL's performance is horrible.

For example, FPS in a scene with a simple textured plane primitive drops from 440-400fps down to 1-3fps when one single OSL parameter is animated.

Animation of texture parameters is an essential part of most CGI pipelines. Such monstrous performance hit for just one animated parameter is not acceptable and makes OSL almost useless for any professional pipeline.

I expect the products I pay for to be reliable and efficient. Let's make OSL reliable and efficient.

[Anonymous]

It should be added that it's not all parameters that cause significant slowdown.

Mainly it's when bitmap sequences are connected with the OSL Numbered File Name and frame number is linked to some kind of controller. Perhaps it's more to do with string parsing that needs to be optimized.

Since I work a lot with bitmap sequences and OSL gives me more control with the playback, I see fixing this performance issue as an essential thing.

[pyroskat]

I will expand that to: Get realtime image sequences/animated textures on viewport.  Can be done loading in ram all sequences until a certain amount. I will love to get more realtime feedback even with complex shaders. We have ram, lets use it!