Hi-Rez/Satin

MSL resource files?

ccworld1000 opened this issue · 2 comments

Why are MSL resource files not integrated into 'Group' files, but packaged in the form of resource drops? Are there any subsequent situations to be considered in the design? Or is the original intention of such a design in consideration of aspects?

They are not in groups because they are copied into Satin's resources, this is so shaders / pipelines can be assembled at runtime. If there is another way around this, please let me know.

The idea is good, but Apple uses a sandbox mechanism.

With the following references, I'm not sure if it's feasible (smile)
1 separate the built-in MSL variables.
2. There is MSL + header file reuse in OC. Maybe swift can also be used? If you can't, just add a bridge.