EVS Presentations (.EVSP) provide a single file deliverable which allows our customers to provide versions of their Earth Volumetric Studio (EVS) applications to their clients, who can then modify properties interactively.
For example, an EVS Presentation can allow your clients to:
- Choose their own plume levels
- Change Z-Scale and/or Explode distance
- Move slices or cuts through the model
- Draw their own paths for (cross section) cross-sections
This works by creating a restricted version of an EVS application, saved as an EVS Presentation (.evsp file).
The file will have all of its data stored as packaged files, always work in Presentation Mode, and prevents the application from being modified. In addition, only the Application Favorite properties can be modified, so the author of the Presentation needs to determine which properties are critical for the Application to modify in advance.
This functionality results in a single file deliverable which can allow unlimited changes to critical application properties, and is usable without and EVS license by your clients.
C Tech's EVS Presentations (EVSP) are single-file deliverables that allow you to share interactive versions of your Earth Volumetric Studio (EVS) appl
Creating Presentation Applications
The development of EVS Presentations (EVSP) from EVS Applications will nearly always require modification to your EVS application. The key steps are: Save your application (ideally under a new name, as you will be modifying it for the process of making an EVSP). Replace Disallowed Moduleswith acceptable replacements, if applicable. See Disallowed Modules and Replacements for specifics on which modules need to be replaced. Note: Not all Disallowed Modules have replacements which can be included in EVS Presentations. For example, many 3d exporters must just be removed altogether. Modules which create a model (gridding and horizons, 3d estimation, etc) must be removed. This is done by saving an EF2 file (using write evs field) of their output, and then using that EF2 file in read evs field as a replacement of the network portion doing the model creation. Packageall data files referenced in any modules. There cannot be any externally referenced data files. Some modules cannot be packaged and are automatically replaced by the packaging process. These include: import vector gis import cad import wavefront obj Best if you don’t do this step sooner. See Packaged Files and Packaging Data Into Your Applications for details on the process. Add all desired module properties to Application Favorites, so they can be accessed once the application is saved as an EVS Presentation. EVS Presentation files do not allow access to module properties unless they are added to the Application Favorites. Backup your application as an EVS application to serve as an editable backup. This is essential, should you wish to add additional module properties later. Convert the application to an EVS Presentation (.evsp file). This is not a reversible process, which is why you want the backup from step 5. Convert To Presentation The option to convert your current application to an .EVSP file is not a reversable process. To access this, choose Show Menu in the Main Toolbar: