Uploaded image for project: 'Qt 3D Studio'
  1. Qt 3D Studio
  2. QT3DS-4145

Shader cache improvements

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P3: Somewhat important P3: Somewhat important
    • Qt 3D Studio 2.8
    • Qt 3D Studio 2.7
    • OpenGL Runtime
    • None
    • 24d0ffbdd7af55849d8035a6df472ed6e64adab5

      Hello,

      1. Cluster loads for the first time
      The default page configuration is loaded and the first page is active.
      exportShaderCache() API called and all available shader cache is stored into a raw partition.

      2. User customizes page configuration(added widgets) or changes the active page
      It causes some additional shaders to be used that are not in our shader cache.

      3. User performs system restart
      setShaderCacheData() API called to load stored shader cache.
      The last used page is loaded on startup.
      Shaders that are not in the saved shader cache are compiled at startup. The cluster starts slowly.
      No possibility to call exportShaderCache() to update stored shader cache due to:

      Currently void Q3DSPresentation::exportShaderCache has a limitation that says:

      Note: Exporting shader cache is only supported if no shaders have been originally loaded from a shader cache. Specifying no shader cache file or an empty or invalid shader cache file with shaderCacheFile property allows shader generation.

      I can't see any technical limitations for this. Could you please remove this limitation?

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            anmaatta Antti Määttä
            evgeniy_prikazchikov Evgeniy Prikazchikov
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved:

                There are no open Gerrit changes