VSL scripting language includes a cache system to avoid rebuilding all the scripts at each execution.
VSL cache files are generated both by the 3DVIA Studio authoring application and by the 3DVIA Studio players.
Cache files generated by the 3DVIA Studio authoring application are used during the build process and packaged directly inside the final MPBIN file. This way, when an experience is published on 3DVIA.com, the VSL cache files are also included inside the content file (Note: this only happens if VSL files have been compiled by the author/developer before publishication. Otherwise no cache is bundled).
When exiting the 3DVIA Studio application, authoring-generated cache files are kept inside the project directory (%projectDir%/Build/VSL/ directory) so as to improve compilation time next time the project is loaded. This way, cache files can be used both at runtime and during authoring for optimization purposes.
Cache files generated by the 3DVIA Studio players, on the other hand, are generated inside the windows temp directory. 3DVIA Studio has been designed so that you do not need to worry about compatibility issues between the version of the 3DVIA Studio player and the version of the 3DVIA Studio application used to build the experience.
You can disable the use of cache by checking the Preferences Dialog > Engine > VSL > “Disable cache” option combo-box.
You can also use the “Recompile” button in the VSL editor to force recompilation (ctrl+F7).
VSL compilation warnings are thrown only when no cache is present. To have the full warnings, you will have to do a clean all/compile all.