With JetStream Roamer you can open a wide variety of native 3D CAD file types without having to have the CAD application on your machine. See for more detailed information on these file formats and their options. File management all happens with the File menu and the Standard toolbar.

The File menu includes the following items:
This option resets JetStream and closes existing files.
To create a new file
Go to File, New
or
Click New
on the Standard
toolbar.
When working in JetStream, it is possible that others may be working on the CAD files you are currently reviewing. For example, if you are coordinating various disciplines on a project, then you may have an overall .nwf file referencing numerous design files. During the iterative stages of the project, any member of the design team could potentially be modifying their CAD files. To ensure the data you are reviewing is current, JetStream provides a refresh function to reload any files that have been modified since commencing the review session. This feature does not reload all of the files you have loaded, merely those modified since last opening them.
To refresh your scene with the latest versions of the currently loaded model files
Go to File, Refresh...
or
Click Refresh
on the Standard
toolbar.
With JetStream Roamer you can open a wide variety of native CAD file types without having to have the CAD application on your machine. See for more detailed information on these file formats and their options. To open a model file
Go to File, Open...
or
Click Open
on the Standard
toolbar.
The standard Open dialog use of Shift and Control keys allows multiple files to be selected and appended to the current set of models.
JetStream enables you to build up a complex scene from smaller models by appending, or uniting, multiple model files together, which can be of any type that JetStream Roamer supports. (See for more detailed information on these file formats and their options).
Each file has its own units and when appending more files to the scene, each file is automatically scaled to match the units of the first file loaded into the scene. Each file type has a default unit associated with it that it uses when loading files of that type. You can change this associated unit in the Units tab of the Global Options dialog (see for more detailed information). However, once a file is loaded, you can change its unit scaling using the Edit, File Units and Transform function. See for more information.
The combined set of models may be published as a single JetStream .nwd file using the JetStream Publisher plugin. These models can then be viewed with NavisWorks Freedom free viewer. See for more information.
You can also save the combined set of models as an .nwf file. No geometry is saved in this format, but a list of appended files, along with their path relative to the .nwf file is saved, along with any overrides, comments, redlines, viewpoints or other JetStream specific information. See for more information on saving files.
To append a file
Go to File, Append...
or
Click Append
on the Standard
toolbar.
The standard Open dialog use of Shift and Control keys allows multiple files to be selected and appended to the current set of models.
When merging multiple .nwf files, that each comprise the same reference files, JetStream will only load a single set of the combined models, along with all review markup (such as tags, viewpoints or comments) from each .nwf file. Any duplicate geometry or markup will be removed when merged. See for more information on .nwf files.
To merge a file:
Then
Go to File, Merge...
or
Click Merge
on the Standard
toolbar.
Finally
Browse to and select the file, or files, to be merged.
The standard Open dialog use of Shift and Control keys allows multiple files to be selected and merged with the currently loaded model.
If a TimeLiner license is available, and two or more merged files contain TimeLiner data, limited merging can be done with this data. Three scenarios are handled.
If the two TimeLiner data sets are identical, then merging of files can occur without issue.
If the two TimeLiner data sets are completely unrelated, merging of data in this context will not be successful
If the two TimeLiner data sets contain the same Primary link then the data set with the most recent link (i.e. the newest file date) is chosen over the other. If the Primary links are different, then the data set with the highest number of tasks will be used, and links will be re-attached wherever possible.
For more information on TimeLiner, see the TimeLiner book.
When you have finished reviewing a model or a set of models and are exiting JetStream, you are prompted to save. When saving to a JetStream .nwf file, only a list with pointers to the files currently loaded is saved, along with the scene's environment, the current view, clash results (if available) and viewpoints. If you want to take a snapshot of the scene, including all geometry, then you need to publish an .nwd file. See for information on how to do this.
Go to File, Save
or
Click Save
on the Standard
toolbar.
Enter a name and location for the file, if you wish to change the existing name.
Click Save to save the file or Cancel to return to JetStream without saving.
This is exactly the same as the Save function (see , but it gives you the opportunity to rename the file that you are saving.
Go to File, Save As...
Enter a new name and location to store the file.
Click Save to save the file or Cancel to return to JetStream without saving.
Publishing a NavisWorks .nwd file takes a snapshot of the current scene that cannot then be changed (i.e. files cannot be deleted from a published .nwd file). The file can also be used with the NavisWorks Freedom free viewer. This command is only available if you have the JetStream Publisher plugin.
You can print a hard copy of the current viewpoint to any printer or plotter.
When the print option is selected it prints the current viewpoint scaled to fit and centered on the page.
Go to File, Print...
or
Click Print
on the Standard
toolbar.
Check the printer settings are as required and click OK to print the viewpoint or Cancel to return to JetStream without printing anything.
The maximum image size is 2048x2048 pixels.
The Properties button controls printer-specific ink and paper settings.
Before you print out a copy of the model you are working on, you may wish to see how it will appear.
Go to File, Print Preview...
Use Zoom In and Zoom Out to do just that with the preview image.
Click Print, OK to confirm and print the image, or click Close to return to JetStream.
This option enables the setting up of paper size and orientation options.
Go to File, Print Setup...
The print setup dialog box is displayed.
Make changes as required to the paper, orientation and click on Properties to change printer-specific settings.
Click OK to print the image, or click Cancel to return to JetStream.
This command deletes the selected files from the scene. It is only available when more than one file is appended in the scene.
You cannot delete files from within a "published" NavisWorks .nwd file (see . You can only delete appended files, whether they were appended manually, or within an .nwf file.
To delete a file
Go to File, Delete File
It is not possible to undo this command.
JetStream is a communication tool and the Send feature makes it easy for you to send your current model along with its viewpoints. The Send command uses your current mail exchange service and will prompt you to set one up if it cannot find one.
Sending a mail will first save the current working file, so you are guaranteed to always send the latest review.
To send a file by email from within JetStream
Go to File, Send...
or
Click Send
on the standard toolbar.
This accesses your mail package and sends the current file as an email attachment.
If an .nwf file is received, JetStream will search for the appended files first using the absolute path that the sender originally saved the file with. This is useful if a team is on a local network and the files can be found using the Universal Naming Convention (UNC). Otherwise, a team not sharing a server can organize a project using the same file hierarchy and drive letter and JetStream can find the files this way.
If JetStream is unable to find the files, then the recipient can save the attached .nwf in a directory where all the appended files are located. The .nwf can then look for these files relative to its own location.
This way, you are able to move a whole sub-directory from your projects directory to a completely new location. Save the .nwf file in this new place and it will be able to search for the files from here.
The import option inputs Intergraph PDS review data, including:
It is also possible to import data that has been exported from previous JetStream sessions, including:
Clash Test XML (.xml)
See for more information on exporting data from JetStream.
Clash test .xml files can only be imported if you have a valid license for the Clash Detective plugin. See the Clash Detective user guide for more information on importing clash test criteria.
Tag information from Intergraph PDS contains a unique ID, saved viewpoint and corresponding comments. Tag information created in JetStream may also be exported to be used in Intergraph PDS. See for more information.
From the File menu, choose Import, PDS Tags...
The Import dialog is displayed:

Locate and Open the .tag file to import the PDS tag data, or click Cancel to return to JetStream without importing a file.
Display sets from Intergraph PDS contain detailed criteria, defining item selections. When imported into JetStream, .dst files create search sets in the Selection Sets control bar. See for more information on search sets.
From the File menu, choose Import, PDS Display Sets...
The Import dialog is displayed:

Locate and Open the .dst file to import the PDS display sets, or click Cancel to return to JetStream without importing a file.
Viewpoints can be imported into JetStream via an .xml file, enabling you to bring viewpoints into the current scene from another model file. For example, if you are working on different versions of the same model, you can save viewpoints in one version of the file, export them and then import them into the other version. See for more information on saving viewpoints and for more information on exporting viewpoints to an .xml file.
From the File menu, choose Import, Viewpoints XML...
The Import dialog is displayed:

Locate and Open the viewpoints .xml file to import the viewpoints, or click Cancel to return to JetStream without importing a file.
Search criteria can be imported into JetStream which populates the Find Items control bar. The search can then be run on the current model, finding any items that match the specific criteria. See for more information on searching the model for items based on their properties.
From the File menu, choose Import, Search XML...
The Import dialog is displayed:

Locate and Open the search .xml file to import the search criteria into the Find Items control bar, or click Cancel to return to JetStream without importing a file.
Search sets can be imported into JetStream which populates the Selection Sets control bar with pre-defined search sets. Selecting an imported search set will define the current Find Items criteria and search the current model accordingly. See for more information on searching the model for items based on their properties.
From the File menu, choose Import, Search Sets XML...
The Import dialog is displayed:

Locate and Open the search sets .xml file to import the search sets into the Selection Sets control bar, or click Cancel to return to JetStream without importing a file.
The export option outputs the current viewpoint in one of four ways:
Rendered image formats (various)
Rendered image files can only be exported if you have a valid license for the Presenter plugin. See the Presenter user guide for more information on exporting rendered images.
It is also possible to export an animation, or a TimeLiner sequence to:
Or, as a sequence of individual frames to:
TimeLiner sequences can only be exported if you have a valid license for the TimeLiner plugin. See the TimeLiner user guide for more information on exporting TimeLiner sequences.
The export option additionally outputs a variety of review data, including:
Clash Test XML (.xml)
Clash test .xml files can only be exported if you have a valid license for the Clash Detective plugin. See the Clash Detective user guide for more information on exporting clash test criteria.
The export option outputs a number of additional review file types:
From the File menu, choose Export, Piranesi EPix...
Use the Browse... button to locate a destination and enter a new filename to export, if you wish to change from the existing filename and location.
Select the sizing options for the file to be exported. (See for more details).
Click Save to export the file, or Cancel to return to JetStream.
With the view to be exported in the main navigation window, from the File menu choose Export, Image...
The Image Export dialog box is displayed:

Select the format of the image you wish to export:
Windows Bitmap
Portable Network Graphics (PNG)
Select Interlacing and Compression options from the PNG Options dialog box:

JPEG
Select Compression and Smoothing options from the JPEG Options dialog box:

Select the sizing options for the file to be exported. (See for more details).
Click OK to continue, or click Cancel to return to JetStream without exporting an image.
Enter a new name and location to store the file.
Click Save to export the file, or Cancel to return to JetStream.
With an animation selected, from the File menu, choose Export, Animation...
The Animation Export dialog box will be displayed:

Select the Source from which you wish to export the animation.
This can either be the Roamer default, Current Animation (the currently selected animation), or, provided that you have a valid license for the TimeLiner plugin, a TimeLiner Simulation
Select the Renderer with which you wish to render the exported animation.
This can either be the Roamer default, OpenGL , or, provided that you have a valid license for the Presenter plugin, Presenter
Select the Format in which you wish the output to be exported in:
Windows AVI
Click Options... to select the Video Compression you require.
Clicking Compression will open a standard Windows dialog box that allows you to choose which >codec to use, as well as its configuration. Only those codecs currently installed will be shown and the PC that the .avi file will be run on will also need the same codec installed.
JPEG (sequence of static images, taken from individual frames)
Click Options... to set the Compression and Smoothing levels you require.
PNG (sequence of static images, taken from individual frames)
Click Options... to set the Interlacing and Compression levels you require.
Windows Bitmap (sequence of static images, taken from individual frames)
Select the sizing options for the file to be exported. See for more details.
For animations, you should also enter the number of frames per second (FPS) you require.
Click OK to continue, or Cancel to return to JetStream.
Enter a new name and location to store the file(s).
For image sequences, the name will contain the first integer of a 'counter', e.g. 001. Subsequent frames will be automatically incremented by one, e.g. 002, 003, 004 and so on.
Click Save to export the file(s), or Cancel to return to JetStream.

The size of the exported image/animation can be set in various ways:
Explicit allows you full control of the width and height (the dimensions are in pixels).
>Aspect Ratio allows you to set the height, and the width is automatically calculated from the aspect ratio of your current view.
Current View takes the width and height of your current view.
>Anti-Aliasing smoothes the edges of the exported images. The higher the number, the smoother the image, but the longer they take to export. 4x should be adequate for most situations.
There is a maximum size of 2048 x 2048 pixels, for Roamer OpenGL output.
From the File menu, choose Export, PDS Tags...
Enter a new filename and location, if you wish to change from those suggested.
Click Save to export the .tag file, or Cancel to return to JetStream.
Viewpoints can be exported from JetStream to an .xml file. These viewpoints contain all associated data, including camera positions, sections, hidden items and material overrides, redlines, comments, tags and collision detection settings.
Once the viewpoint data is exported to this text-based file format, it can either be imported into other JetStream sessions, or it can be accessed and used in other applications. For example, you may want to set up the same viewpoints in your CAD application.
From the File menu, choose Export, Viewpoints XML...
Enter a new filename and location, if you wish to change from those suggested.
Click Save to export the .xml file, or Cancel to return to JetStream.
The search criteria specified in the Find Items dialog box can be exported to an .xml file. This can then be imported into other JetStream sessions. For example, if you have specified a complicated search criteria, containing various logic statements, that relates to all projects you work on, then this feature allows you to specify it once and use it on all projects.
From the File menu, choose Export, Current Search XML...
Enter a new filename and location, if you wish to change from those suggested.
Click Save to export the .xml file, or Cancel to return to JetStream.
Saved search sets can be exported from JetStream as an .xml file. These can then be imported into other JetStream sessions and re-used. For example, if you have a number of generic searches that you perform on all of your projects, this feature allows you to specify the searches once and use them on all projects.
From the File menu, choose Export, Search Sets XML...
Enter a new filename and location, if you wish to change from those suggested.
Click Save to export the .xml file, or Cancel to return to JetStream.
An .html file can be exported containing a JPEG of all of the saved viewpoints and associated data, including camera position and comments.
To customize the appearance or layout of the html file, you will need to edit the viewpoints_report_lang.xsl file, where lang is a code representing your language. The installed file is located in the stylesheets subdirectory of the JetStream install directory. You can copy the edited file to the stylesheets subdirectory of any of the JetStream search directories. See for more information.
From the File menu, choose Export, Viewpoints Report HTML...
Enter a new filename and location, if you wish to change from those suggested.
Click Save to export the report, or Cancel to return to JetStream.
Autodesk DWF files can be exported from JetStream if a valid Publisher license is available. The exporter creates a .dwf file containing:
All geometry
All materials
Per-vertex colors
Properties (where available)
To export a DWF file:
From the File menu, choose Export, Autodesk DWF...
Enter a new filename and location, if you wish to change from those suggested.
Click Save to export the file, or Cancel to return to JetStream.
Google Earth KML files can be exported from JetStream. The exporter creates a compressed KML file with the extension .KMZ and supports the export of:
Triangles
Lines
Materials (colour and flat transparency only)
Viewpoints (adjustments may occur due to Google Earth limitations)
Model Hierarchy
Hyperlinks (currently only URLs work correctly in Google Earth)
From the File menu, choose Export, Google Earth KML... . This brings up the following dialog.

Select Export model relative to terrain height to put Google Earth in a mode where all heights are measured from the surface of the ground. When this is off all heights are measured from sea-level.
When positioning a model relative to sea level, the height of the Google Earth reference points must also be measured relative to sea level. When positioning a model relative to the ground, the Google Earth reference points must be measured relative to the ground.
Google Earth always places new placemarks at an altitude of zero, irrespective of whether that is relative or absolute.
Collapse on export allows different levels of collapsing parts of the model hierarchy in the exported file.
None ensures the whole heirarchy is exported
All objects collapses everything into one node
Files collapses each file into one node
Layers collapses each layer into one node
Limit number of Polygons should be enabled to restrict the amount of geometry exported into the output file. Geometry is selected on the basis of taking the most obvious objects in preference to the fine detail. If the exported file is too large for Google Earth to display, try enabling this and reducing the number of polygons. View, Scene Statistics in JetStream shows the number of triangles and/or lines in the current project. By setting a polygon limit you are choosing to export only some of these items.
Google Earth's ability to handle large numbers of polygons is far more limited than JetStream. Hence it is worth noting that currently Google Earth will consider 1,000,000 polygons as being a big model.
The Origin position values are the first pair of reference points on the Google Earth surface, and must always be defined. The JetStream reference point will always be positioned to exactly overlay the Google Earth reference point.
Second and Third reference points can be used, and if enabled then the position and orientation of the model can be more accurately defined.
Use the Import buttons to read-in saved placemark locations from KML files exported from Google Earth.
The Origin Import button differs slightly from the other two; if the KML file contains multiple placemarks, this button will offer the user the choice of importing second and third reference points if available. The other two buttons will only import a single reference point.
The Pick buttons allow the reference point locations to be selected in the main 3D view.
These points must be visible in the main 3D view prior to exporting, as once the KML Options dialog is open you will not be able to navigate before picking.
You may wish to use View, Split to split the main 3D view enabling you to have separate views of each reference point.
Go to File, Exit
If the model has been changed since opening it, JetStream will ask you whether you want to save any changes. Respond appropriately and JetStream will then close.