Home Forums Mistika VR Features Request file system structure

This topic contains 2 replies, has 3 voices, and was last updated by  Javier Moreno 3 weeks, 6 days ago.

  • Creator
    Topic
  • #36819

    joe.pitts
    Participant

    Hi,

    That’s it!!!

    Can anyone explain all the folders and structures that are created for each project?

    thx

    joe

Viewing 2 replies - 1 through 2 (of 2 total)
  • Author
    Replies
  • #39516

    susanne
    Participant

    Yes, I’d like to have an explanation as well. The creation of projects is not exactly intuitive.

    #40407

    Javier Moreno
    Moderator

    Hi, here is some information:

    Base folders:

    During the installation (and also in the initial dialog appearing when opening Mistika VR) two base folders are defined:

    – Work:  This is the base folder where all the projects are created.

    – Material: This is the base folder where the rendered media files are created.

    You can change them at any time, in the Paths dialog appearing when opening Mistika VR

    Project folders:

    When you create a new project it will  contain several sub-folders. Most of them are not relevant for Mistika VR, but they need to be there so different SGO products (Mamba, Mistika Ultima…) can work with the same project.

    The relevant project folders and project  files for Mistika VR are only these:

    ProjectName/DATA : This is where your sequences are saved., including all the stitch information.  All the work you do to a sequence is saved in a .vrenv file.

    Then, a same project can have several .vrenv files (as many as you create with the  “File->Save as” menu). This permits to have multiple sequences of a complex production,  or multiple versions of a same stitch

    – ProjectName/DATA/RENDER

    This point is for advanced users and for programmers. Most users will not need to use these files, but it is documented here as a reference:

    Every time  you render (or when you use the “Add to render queue” button),  a render job file ( .rnd file) is created under the DATA/RENDER/RenderName folder for each shot, and they contain all the information that is passed to the renderer.   A .rnd file is like the .vrenv file, but split into shots (one .rnd per shot).

    A .clp file is also created with each .rnd file. It contains the metadata of the new media file that will be created when rendering the .rnd file.

    In those files you will find all the render metadata that was not defined in the .vrenv , including  the render resolution, render path, and render format.

    You can use the .rnd files in two ways:

    * Command Line Interface (CLI). The “mistika -r” CLI permits to launch the background render as a command line (  mistika -r PathToRnd )

    * The “Add to render queue” permits to create the rnd files and then call a user scripts for each one passing the rnd and some other metadata to them. For example,  the integration with Smedge and other render farms use those files to submit the render jobs.

    Note: All the files mentioned above are text files, you can find their syntax in the corresponding article in the knowledge base.

    Global settings ( VR-ENV folder ) and camera presets folder.

    – The software also needs a global folder to save global settings that do not depend on a specific project.  This is the VR-ENV folder in your user account (on Windows, it is located in %UserData%/VR-ENV ).  Most of the files inside are not intended for direct user manipulation, but there is one interesting folder that you may need to be aware, which is the VR-ENV/etc/CameraPresets folder. It contains the camera presets describing all the known camera rigs.  Sometimes SGO or  Mistika VR users publish new camera presets  before they appear in new releases, and you can install them by simply placing them in this folder.

     

     

     

    1 user thanked author for this post.
Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.