Szark…it is two separate dashes (minus sign, twice) between the shaderdl.exe and the recompile-sdl bit…
The sahders are recompiled on the fly - without the source code that’s the only option.
No, the—recompile-sdl option will PERMANENTLY recompile the shader, not ‘on the fly’ but actually write it to disk. Overwriting the original, if there is no other shader folder set in the 3delight.ini (which DS doesn’t use).
True, but I meant the net result is the same - though without having to wait for the recompile each time, I suppose. It isn’t, so far as I know, a substitute for getting a new version of the shaders prepared specifically for the new version of 3delight.
And that is the bit that confuses me ... I thought these shaders (the pw ones) had been updated for DS4.5.
That was to get them to work originally…in the beta there was another update to the 3Delight core…so they may need it again (and from the info message being seen so often, that’s a given).
I did run a test render on my glass shader, before the recompile with it being recompiled on the fly it was taking about 15 minutes to render a scene. After the recompile, it dropped to 12. But it wasn’t a completely fair test…I did include the -O3 flag on the recompile (not from source, I’ll have to do that later), so some of the speed increase could have come from the higher level of optimization.
Adding the higher level of optimization to other shaders isn’t really recommended, because it’s hard to tell what exactly may happen and without a fallback it’s not worth the risk.
One of the other tests for timing was to render to a RIB and then recompile all the shaders in the RIB folder…it took about a minute to do that, so you can figure about a minute of the time spent rendering/waiting for the render to start was 3Delight running the ‘on the fly’ recompile of the shaders…