Visualization Guide
Visualization Guide
Visualization Guide
|
You can save your rendered images to disk using the Save Image dialog box.
In addition, you can use the Save Multiple Images dialog box to render multiple images and save them to disk. This can be done from within the MicroStation environment or from the system command line.
You can save rendered images as follows:
Recommended: Saving an image, which is done by choosing Image > Save… from the Utilities menu. You can save true-color images (also referred to as 24-bit or 16.7 million color images) that display or print in full color on a system with that capability, even if you do not have a true-color display. Images also can be rendered and saved at resolutions higher than the resolution of the screen. There is a banded rendering option that is useful for overcoming memory limitations when saving large images. Banded rendering can be performed by multiple systems over a network.
Screen Capture is performed by choosing Image > Capture from the Utilities menu. Images saved in this way are limited to screen resolution and the number of displayable colors.
Save Image dialog box | |
If your system cannot simultaneously display all the required colors, rendered images are dithered to simulate the extra colors. Dithering is the creation of a pattern of pixels, using available colors, to approximate any unavailable color(s).
With screen capture you are limited to the number of colors and resolution your monitor can display. You should save images rather than use screen capture if a high-quality image is required.
Because of memory limitations it can be difficult to render high resolution images in order to save them to disk. Consider that during the rendering process, an extremely large image with antialiasing can exceed tens of megabytes in working size prior to its completion. For example, a 2000×2000-pixel antialiased image requires 48 MB of RAM to process.
You can overcome such memory limitations by using the Render Image in Bands option in the Save Image dialog box. The banded rendering process breaks up the image into a series of bands. Each band is then, in turn, processed as individual images within RAM and written to disk as a rendered band file. Upon completion of the last band, all of the rendered band files are combined into a single, finished image file, and the rendered band files are then deleted.
Banded rendering only works with true color (24-bit) or RGB Alpha rendering and does not support the JPEG format. |
The following settings in the Save Image dialog box affect banded rendering:
Memory — the amount of RAM, in KB, allocated to the rendering process. The more RAM allocated the fewer bands required to process a given image at the current resolution and the faster the processing.
Number of Bands — the complement to the Memory setting, this setting is automatically calculated based on the rendering parameters and the amount of memory made available. You can directly enter the number of bands which will result in a recalculation of the amount of memory required for the rendering of each band.
During a banded rendering process, the file extension is used to identify individual rendered band files during the rendering process. The file naming syntax is “<image_file_name>.b##,” where ## is a sequential hexadecimal number (0-F) starting with .b00 and running through .bff (a maximum of 256 possible bands per rendering). Because of the potential of overwriting existing files with similar extensions, it is recommended that these band files be stored in a separate directory. This directory is identified with the configuration variable MS_IMAGEOUT (Image Output in the Rendering/Images category of the Configuration dialog box).
For example, when banded rendering is being used to render and save a 2000×2000-pixel image with the banded memory set to 8 MB, 22 band files are created.
In addition to the rendered band files, the banded rendering process creates a temporary control file named “<image_file_name>.bnd.” This file contains the rendering settings, the total number of bands to render, and the number of bands thus far rendered.
Rendering an image in bands and writing each band to disk makes it is possible to recover from an interruption in the process.
The Render Image in Bands option lets you use multiple systems to render and save a single image. All of the systems must be connected to a common networked file system.
The system on which the banded rendering process is initiated creates the control file on the shared network drive. The Continue button in the Save Image dialog box (see To restart a banded rendering after an interruption) is used on subsequent systems to continue the processing with the first unrendered band. After the last rendered band file in the series is created, the system by which this file was generated combines all of the previous bands together and creates the final image file. This system also deletes the individual rendered band files.
As well as saving single image files, you can set up your system to save a list of images. This is useful for creating and saving rendered images, automatically, when the system normally is not being used, such as overnight. For this procedure, you create a script that contains the names of the files to be rendered along with the view number, or the saved view to be used.
Output File Name macros provide a convenient way to format the output file name based on information about the script entry. When the script entry is executed, the macro definitions are replaced with corresponding properties of the script entry. The following table shows the macros that are available. These macros may be keyed-in manually, or selected from a right-click menu in for the Output File name field.
Macro |
Expanded value |
---|---|
%d |
DGN file name |
%m |
Model name |
%v |
Named view, or view group name |
%n |
View number |
%r |
Render mode |
%s |
Render setup name |
%e |
Script entry number |
%a |
Auto-increment number |
A length modifier can be specified by inserting a number after the percent sign in the macro, with the following results:
If the macro evaluates to a string, the length modifier specifies the maximum length of the string inserted into the output file name. For example, %6d would be replaced by the first 6 characters from the DGN file name.
If the macro evaluates to a number, the length modifier specifies the minimum length of the resultant string. If the number of digits in the number is less than the length modifier, the string is padded with zeros. For example, %3e in the first script entry would be replaced by 001. Using numeric length modifiers allows the resulting file names to be sorted in numeric order.
Typical examples illustrating the use of output file name macros are shown in the following table. All examples below refer to the third entry of a script, using DGN file kitchen.dgn, view number 4, with a render mode of Ray Trace.
Output File String |
Output File Name |
---|---|
%d-%n.jpg |
kitchen-4.jpg |
My %d [%r].jpg |
My kitchen [Ray Trace].jpg |
%5d [%3r].jpg |
kitch [Ray].jpg |
%d (%e).jpg |
kitchen (3).jpg |
%d (%3e).jpg |
kitchen (003).jpg |
Menu items and icons in the Save Multiple Images dialog box let you build image scripts automatically.
Typical entry in an image script file. Information from each entry is used by the rendering process to select the design file and view, and to set the rendering mode, output file name, type, and resolution. | |
You can create one or more scripts and save them to disk. As well, you can recall an existing script, or include an existing one with the currently displayed script.
Options for creating scripts are contained in the Save Multiple Images dialog box's File menu and options for editing the open script in its Edit menu. Several of the most commonly used selections are accessible also via icons in the dialog box, plus you can the right-click menu for any script entry.
Once a script has been created, and the entries displayed in the list box, you can selectively enable or disable entries for processing. Only those entries with checkmarks, in the Enabled column, are active and will be processed. Clicking in the Enabled column toggles the checkmarks on or off.
Only those entries with checkmarks in the Enabled column will be processed. Clicking in the Enabled column, next to an entry, toggles the checkmarks on or off. | |
The following procedures are used to work with script files.
The following procedures are used to work with script entries.
When creating entries for a script file, make sure that each output file has a unique name, so that they do not overwrite previous images having the same name. |
The script entry is pasted below the highlighted entry in the currently displayed script file.
The script entry is pasted below the highlighted entry in the currently displayed script file.
You can also execute image script files from the system command line.
Be sure to unset the MS_INITAPPS system environment variable after the rendering has completed. |