- Like V8i? You’ll Love CONNECT!
- What is the activation period for MicroStation CONNECT Edition?
- Basic FAQs
- Opening multipage files in Raster Manager
- Raster reprojection
- Image Server attachments
- Display plane and display priorities of rasters
- Graphics Card Support
- Advancing your V8i WorkSpace to CONNECT Edition Configuration
- API: What is a font number? (and why you’d rather not use them)
- Common Font Number Questions
- See Also
- Before You Start
- How do I migrate MicroStation BASIC macros to the new version?
- Georeferencing and location
- Batch convert vs Save As output raster location
- Why aren’t my fonts available in the font picker?
- Hiding of Duplicate Font Names
- Font Definitions Are Not Found
- Which Bentley products does Bentley V8i (SELECTseries 4) — Autodesk RealDWG 2016 work with?
- Installation Requirements
- How do I migrate my V8i user interface customizations to this version?
- Do object enablers work with Bentley V8i (SELECTseries 4) — Autodesk RealDWG 2016?
- What are the minimum hardware requirements?
- Raster Format specific information
- What is a XWMS file ?
- What is an ECWP attachment ?
- Geo PDFs
- DEM and DTM Raster formats
- Supported raster file formats in MicroStation V8i:
- Customizing your CONNECT Edition Applications for Maximum Productivity
- Minimum Profile
- Stay Current with MicroStation CONNECT
Like V8i? You’ll Love CONNECT!
Configuration Variables Dialog Improvements
Coordinates and Scaling
- Stay current with the latest geographic coordinate systems in MicroStation CONNECT Edition
- Recommended Scales
Stay Current with DWG Files
- Locate Anything in Your Designs
- Simplify Viewing of Object Properties
Stay Current with Online Help
Installs and Updates
- Automatic Updates
- How to create a deployment image
- ItemTypes and PickLists
- Replacing Tag sets with Item Types
- Annotations for Item Types
- Excel and Item Type Integration
- Item Types — Populating Items using Lookup Tables
Models and Sheets
- Make Using Bing Maps a Snap by Using MicroStation CONNECT Edition
- Sheet Tracking and Ordering
- Performance Enhancement — File Opening Time for MicroStation CONNECT Edition Update 13 Vs V8i SS4
- Performance Enhancement — DWG File Opening Time
- Performance Enhancements — Properties Dialog Loading Time
Replacing Feature Solids with Parametric Solids
Tables in MicroStation CONNECT Edition
- New in MicroStation CONNECT Edition Update 13 – Physically Based Rendering
- Getting Started with PBR Materials
- Physically Based Rendering (PBR) Settings in MicroStation CONNECT Edition
Side by Side: The MicroStation CONNECT Edition and MicroStation V8i
What is the activation period for MicroStation CONNECT Edition?
MicroStation will run without a license for 7 days as an evaluation period. After being licensed, it must communicate with a license server at least every seven days to continue operation. In fact, all Bentley desktop products are now standardized on a seven day activation period. This ensures better, more accurate reporting and helps to make sure a company does not inadvertently exceed their license count.
For those customers running disconnected or mobile solutions the best option for uninterrupted operation is to check out a license. A checked out license can run up to a year without connecting to a license server.
Opening multipage files in Raster Manager
Starting with MicroStation V8i, there are two ways to visualize the content of your multipage raster files in MicroStation:
- You can open them directly from the MicroStation Manager or within the MicroStation Open File menu by using the Common Raster Formats, Common Geo Raster Formats, or All Files of type filters. This will open all the pages of your raster document as read-only into a MicroStation view.
- You can open a DGN, go to the Raster Manager dialog box, do File — Attach Raster ensuring the Open Settings Dialog toggle is set on, then select your multipage raster and click Open so it gets listed in the Raster Attachment Options menu. Once in that menu, right-click over the raster attachment and select the page you want to display, then click the Attach button. This allows you to pick the exact page you want displayed from your raster attachment.
Starting with MicroStation V8i, you can reproject rasters just like any other referenced DGN onto a master DGN with a Geo Coordinate System definition. Please consult the MicroStation Help for more information under the Managing References and Raster Images > Modifying Raster File Attachments > Reprojecting Images topic.
Image Server attachments
It is possible to use Raster Manager to open up images stored on the ProjectWise Publishing Server. Information about the Raster Manager Image Server menu can be found under the MicroStation Help > Menus > Raster Manager > Image Server Settings dialog topic. You will find more information on the ProjectWise Publishing Server at the following link: http://www.bentley.com/en-US/Products/ProjectWise+Integration+Server/Services-Modules.htm
Display plane and display priorities of rasters
When handling display priority of rasters in a model, we first have to determine whether we are in a 2D DGN, a 3D DGN or a DWG file. Although they have a few things in common, raster display priorities are handled differently in 2D and 3D space.
In a 2D DGN/model:
In a 3D DGN/model:
Bring Element to Front
Graphics Card Support
Below is list of current generation Graphic Cards that have been tested to work with MicroStation CONNECT Edition in addition to these cards the previous generation cards that work with MicroStation V8i SS4 will also work fine. That list can be found here MicroStation V8i Requirements note that for best performance we recommend the newer cards listed below for CONNECT Edition, LumenRT and ContextCapture Products.
MicroStation CONNECT Edition
P3200 and above when working with LumenRT and ContextCapture
MicroStation CONNECT Edition
For High end visualization, Path Trace* rendering, ContextCapture, and LumenRT VR
AMD Radeon Pro
MicroStation CONNECT Edition
WX7100,W5700 and higher for LumenRT and ContextCapture
MicroStation CONNECT Edition
For High end visualization, Path Trace* rendering, ContextCapture, and LumenRT VR
*Note: e-on VUE Path Tracer will be included in a future release of MicroStation CONNECT Edition.
Advancing your V8i WorkSpace to CONNECT Edition Configuration
- Terminology Changes
- Folder Structure Changes
- Changes to Configuration Levels
- Configuration Files in CONNECT
- The CONNECT Configuration
- Some changes to MicroStation and it’s configurations
- Enable V8i Task Theme in MicroStation CONNECT Edition
- Search in the Configuration Dialog
- Variables you should know
- Use Variables in Key-ins to Quickly Open Files or Folders
- Reference file variables
- What does _USTN_USER_CONFIGURATION do?
- Managing WorkSpace and WorkSet creation tools
- Configuration Assistant (Technology Preview)
- Understanding Configuration Assistant
- Add the Configuration dialog to the Quick Access Toolbar
- Custom Configuration — Initial Creation Step
- Custom Configuration — Standards Folders
- Custom Configuration — Standards CFG File Contents
- Custom Configuration — Separating Project Data from Standards
- Should I edit ConfigurationSetup.cfg?
- Deploying ConfigurationSetup.cfg
- Working with Standards Across Bentley Applications
- Migrating to MicroStation CONNECT Edition
- Migrating V8i Projects to MicroStation CONNECT WorkSets
- With CONNECT there is no need to migrate all of your V8i projects in one go
Silently Uninstalling MicroStation and Allied Features
- 5 Easy Steps to Create a Hybrid WorkSet in the MicroStation CONNECT Edition
- DGNWS File and WorkSet Template
- Adapting an Application in a Project
- Edit WorkSet CFG in the Configuration Variables dialog
- Where should I keep my DGNWS files?
Since the introduction of the new level system in MicroStation, levels can be deleted. Given the situation, it may be difficult to understand why a given level can not be deleted.
The general rule is that a level that is used by graphical data will appear as «bold» in the level list. When a level is not bold, the level should be able to be deleted by simply deleting it in Level Manager, however, there are times when a level will not delete even when it seems apparent that it is not used.
General Note for specifying level names in key ins:In case the level name that you want to specify contains spaces, always use double quotes when entering the name.Example:Level name in the Level Manager is shown as: Roof of house, make sure to enter:»Roof of house»
API: What is a font number? (and why you’d rather not use them)
Most of the following information comes from the FontManager.h header file in the Public API, which also contains additional information.
Fonts are identified by their name and type. However, it would be inefficient to store a copy of the font name every time it is referenced inside a design file. For this reason MicroStation stores a «Font Table» in the non-model storage area of design files. The font table stores a mapping between a «Font Number» and a font name. So, for a given design file, all elements that refer to a given font number refer to the same font. However, it should be obvious that elements from a different design file may refer to same font through a different font number. Also, note that there is only one font table for the entire design file, so that all elements from all models use the same font table. To find a Font object from the font number in an element, the procedure is:
- Get the DgnFile that contains (or will contain) the element
- Get the FontNumMap from that DgnFile via one of the methods of FontManager
- Call either GetFont or ResolveFont on the FontNumMap to get a pointer to the Font
There is a convenience method on FontManager to return a FontNumMap from a DgnModelRef, since that is frequently the most convenient value from which to find a DgnFile. Note that this is merely a convenience method and it does not imply that there is a FontNumMap associated with DgnModelRef’s. DgnModelRef’s are associated with DgnFiles and DgnFiles have FontNumMaps. Therefore, all calls to GetFontMap through DgnModelRefs from the same DgnFile will return the same value.
There can be some confusion about font numbers related to legacy APIs. For example:
- Font number ranges: Much of the existing MicroStation API encodes meaning to the values of font numbers. It implicitly defines that font numbers from 0-255 are RSC fonts, font numbers from 256-1023 are SHX fonts, and font numbers 1024 and above are TrueType fonts. One reason that these ranges are implied is that the Font Table only stores a mapping between font number and font name. It does not store the font type. Therefore, the font number implicitly specifies the font type. In retrospect, this association between font number and font type is a mistake and causes limitations and errors. In a future version of MicroStation, this limitation will be corrected and font numbers will NOT imply font type. Programmers should never, henceforth with the FontManager API, presume an association between font number and font name. The proper way to tell the font type for a font number is to get a Font object for the font, and query it directly.
- RSC font numbers: RSC fonts existed before Font Tables were invented. So a given RSC font has the same font number across all files. Therefore, lazy or uninformed programmers can pass «any» file to lookup an RSC and it will succeed. It is best to forget this fact and write code that works for all font types.
Common Font Number Questions
Q: Given a Font, how do I get its font number?A: The question makes no sense. The same font may be referenced by many different font numbers from different design file. Now, if the question is «How can I determine if a Font exists in the Font Table for a design file, and if so, by what number?», then the answer is to get the FontNumMap for that file and call GetFontNumber.
Q: Given a font number, how do I get a Font?A: The question makes no sense unless you qualify the font number with a DgnFile. In that case, get the FontNumMap for the file and call either GetFont or ResolveFont.
|Original Author:||Dan Koval|
Before You Start
- When installing or uninstalling this product, you must be logged on with Administrator rights.
- It is highly recommended that you close any programs and disable any antivirus software that is running prior to the installation of this software. Be sure to turn on your antivirus software when you are finished.
- MicroStation CONNECT Edition is designed so it can be installed and safely coexist on the same workstation as an existing MicroStation V8i or MicroStation V8 XM Edition commercial release. It will not attempt to upgrade or uninstall the existing commercial release, and by default it installs its program and configuration files to different locations than the other commercial release. When you install MicroStation CONNECT Edition it creates the registry entries responsible for file associations. If you do not want this to happen, during installation, in the Select Features to install list, turn off the File Association check box. MicroStation CONNECT Edition also creates the registry keys for VBA-initiated launching. Windows architecture allows for only one program to own these registry keys and the existing MicroStation V8i or MicroStation V8 XM Edition Commercial Release should continue to function normally by default.
- If you installed MicroStation V8i and MicroStation CONNECT Edition on the same workstation and then uninstalled MicroStation V8i, you must run the Repair tool to make sure the registry and file associations are correct. Note: If you used Microsoft’s program to uninstall, the Repair tool will work correctly. However, if you used a third-party’s product to uninstall, it may have removed files needed by MicroStation. For the procedure to repair MicroStation, refer to the topic To Repair MicroStation.
- MicroStation CONNECT Edition will not install if any technology preview (Â“betaÂ”) release of MicroStation CONNECT Edition already exists on the machine. You will have to uninstall the technology preview (Â“betaÂ”) release before installing MicroStation. You should always back up your data prior to installation.
- When you install MicroStation CONNECT Edition , the following applications are installed with it: — Product Documentation- Example WorkSpace- Visualization Content- CONNECTION client- Bentley DGN IFilter- Bentley DGN Index Service- Bentley DGN Preview Handler- Bentley DGN Thumbnail Provider- HDR Preview Handler- Bentley i-model ODBC Driver- Bentley DgnDb i-model Importer 1.5 (64 bit)
- Examples WorkSpace contains optional downloadable examples, selected to install by default. Unselecting will avoid download of these examples.
- Visualization content in the form of ready-to-render cell libraries is selected to install by default.
- The Bentley DGN Reader for Windows 7 is an application that can be downloaded from Bentley iWare section on http://www.bentley.com/en-us/free+software/. When you install this application on your system, the following applications are installed along with it: — Bentley DGN IFilter- Bentley DGN Preview Handler- Bentley DGN Thumbnail Provider
- Bentley DGN Thumbnail Provider is required to correctly view DGN thumbnails on the Windows 7, Windows 8, and Windows 10 operating systems. Immediately after installing Bentley DGN Thumbnail Provider, you still may not see the correct thumbnails for DGN files. This will be corrected by rebooting or re-logging onto the system.
- The Bentley i-model ODBC Driver is used to expose properties in i-models as an ODBC data source. It offers direct access of i-models from ODBC-compatible third-party applications such as Microsoft Office, reporting systems, and Business Intelligence applications. It allows application developers to use familiar tools to access and present i-model data from databases. When the driver is installed, the Bentley i-model ODBC Driver User Manual (Bentley_i-model_ODBC_Driver_User_Manual.pdf) is also installed.
- Bentley DGN IFilter, Bentley DGN Thumbnail Provider, Bentley DGN Indexer, HDR Preview Handler, Bentley i-model ODBC Driver, and Bentley DgnDb i-model Importer are installed as separate applications. When you uninstall MicroStation CONNECT Edition (v13.0.0), these applications are not removed. If you do not need them, you will have to uninstall them separately.
How do I migrate MicroStation BASIC macros to the new version?
MicroStation BASIC macros can be migrated to the new version with one of the following methods:
- Simple macros that only set parameters (color, style, weight, etc.) can be converted to Element Templates. The Element Templates will be immediately usable in the new version. If your macro also needs to execute a command you can create a custom tool which utilizes the Element template, this processes allows the Element template to be reused by several different tools.
- Rewrite your MicroStation BASIC macro in VBA using the information provided in the MicroStation VBA Help documentation and the Bentley Institute course “MicroStation VBA Programming”.
Georeferencing and location
When using raster’s default positioning in a DGN, there are three possibilities:
- The raster contains no georeference information in its header. In that case the only geopriority available is «Attachment» and by default it gets attached at origin 0,0 and at pixel size = 1, unless a DPI tag scales the pixel size to a value that will honor the DPI value (common DPI values range from 0 to 300, but 600 or 1200 DPIs are also possible, mostly for printing purposes). Example raster formats of this sort are: JPG, GIF, PNG, etc.
- The raster contains georeference information in its header. In that case it can be assigned the «Raster Header» geopriority and the raster will be attached at the origin and pixel size indicated in its header information. Example raster formats : Geotiff, JPG2000, ITIFF…
- The raster contains no georeference information in its header, but it comes with a worldfile or an HGR file, which are text files containing the raster’s origin and basic positioning factors. The geopriority of these files can be set to «Sister files» and the raster will be attached as though it was georeferenced. Example raster formats : TIF raster with TFW worldfile, JPG raster with JGW worldfile, BMP raster with HGR worldfile, etc.
Batch convert vs Save As output raster location
It is important to note that when rasters do not contain georeference info in their headers (e.g. JPG, BMP, etc.) and are not assigned a worldfile or HGR file for positioning, batch converting them to a georeferenced format like Geotiff will not allow assigning them a georeferenced location, even though the JPG or BMP could be attached at a precise location in your DGN.
For a raster’s georeference to follow through, it either needs to be accompanied by a worldfile or HGR file when you batch convert it, or you can save it using the Raster Manager Save As command. You can either save it to an output georeferenced file (like Geotiff) or to a non-georeferenced file with worldfile (like BMP + BPW).
Why aren’t my fonts available in the font picker?
Below are some common reasons why you may not see your fonts in the font pickers and/or see font substitution warning messages in the message center.
Hiding of Duplicate Font Names
Summary: RSC fonts hide SHX fonts, and both RSC and SHX fonts hide TrueType fonts (by-name).
What to do: Disable font hiding completely, or manually hide the undesired fonts so that the desired fonts are visible. See the ‘Font Configuration File’ section in the MicroStation help topic: ‘Composing Drawings’ > ‘Annotations’ > ‘Using Fonts’.
MicroStation V8i introduces the ability to hide fonts with duplicate names; this is the default behavior. This can occur if you have fonts of different types (RSC — MicroStation resource fonts, SHX — AutoCAD fonts, and TrueType fonts), but with the same name (e.g. «Arial»).RSC hides SHX because MicroStation can generate SHX fonts for the shear purpose of exporting to DWG; this means you will still generally want to use the appropriate RSC font, and ignore the SHX variants unless you need to work directly with the DWG file. SHX (and RSC) hide TrueType because over the years, many RSC and SHX fonts may have been converted to TrueType equivalents for various reasons. Preferring TrueType fonts could potentially prevent the use of many SHX and/or RSC fonts.
Font hiding can be disabled completely (find the HideDuplicateNames element in your configuration file, and change its value from ‘true’ to ‘false’), or for specific fonts. See the MicroStation Font Configuration File Wiki page. Hiding specific fonts may be the best option as it preserves the intended behavior above, but allows the picking of the intended font in specific scenarios
As a side note, it may also be preferable to remove the offending lower level font(s). Fonts like «Arial» (normally TrueType) are sometimes hidden due to legacy RSC equivalents; TrueType fonts have many advantages, and the TrueType versions, when they exist, are recommended for use instead of RSC (or SHX) versions.
Font Definitions Are Not Found
Summary: MicroStation’s message center says it is substituting fonts because they can’t be found, or you believe that the font should be available but is not hidden as per above.
What to do: Ensure that the fonts are in places that MicroStation can find them; these locations can vary based on font type (see below). MS_FONTPATH can be used as a search path for all font types.
TrueType fonts: These are normally installed at the system level, and are found in your Windows fonts directory (%SYSTEMROOT%\Fonts, e.g. C:\Windows\Fonts). You must be an administrator on your computer to install TrueType fonts at this level. V8i also allows you to append search paths via the MS_FONTPATH configuration variable. V8i will also search the same directory as the design file if the font is not otherwise found (TrueType and SHX only).
RSC fonts: These fonts cannot be installed at the system level, and must be in a location found by configuration variables. RSC fonts are collected into RSC font libraries (*.RSC files), and are typically deployed with a workspace, or in the ‘system’ directory of your local workspace. MicroStation will search all resource files in locations found via the following configuration variables: MS_SYMBRSRC and MS_FONTPATH. It builds a file list of first MS_SYMBRSRC, then of MS_FONTPATH. As it reads the RSC fonts, if there are font number conflicts, then the one added to the file list last wins. If there are multiple font libraries in the same directory, the order is alphabetical.
SHX fonts: These fonts cannot be installed at the system level, and must be in a location found by configuration variables or AutoCAD registry entries, or in the same directory as the DGN or DWG file in which it is referenced. MicroStation will search the AutoCAD font directory (as dictated by AutoCAD registry entries describing the most recently run version of AutoCAD), as well as all locations identified by the MS_FONTPATH and MS_DWGFONTPATH configuration variables.
Which Bentley products does Bentley V8i (SELECTseries 4) — Autodesk RealDWG 2016 work with?
- Bentley V8i (SELECTseries 4) — Autodesk RealDWG 2016 works with following Bentley products:
- MicroStation V8i (SELECTseries 4) or MicroStation V8i (SELECTseries 3)
- MicroStation PowerDraft V8i (SELECTseries 4) or MicroStation PowerDraft V8i (SELECTseries 3)
- Bentley Navigator V8i (SELECTseries 5)
- Bentley View V8i (SELECTseries 4) or Bentley View V8i (SELECTseries 3)
- Bentley PowerCivil for Country V8i (SELECTseries 3)
- Bentley PowerCivil for North America V8i (SELECTseries 3)
- Power GEOPAK V8i (SELECTseries 3)
- Power Survey V8i (SELECTseries 3)
- Power InRoads V8i (SELECTseries 3)
- Bentley MX V8i (SELECTseries 3)
- Bentley MXROAD V8i (SELECTseries 3)
- Bentley Map V8i (SELECTseries 4)
- Bentley Map Enterprise V8i (SELECTseries 4)
- Bentley Map PowerView V8i (SELECTseries 4)
- Bentley OpenPlant PowerPID V8i (SELECTseries 5)
- Bentley OpenPlant Modeler V8i (SELECTseries 5)
- AECOsim Building Designer V8i (SELECTseries 4)
- Bentley PowerRebar V8i (SELECTseries 3)
A CD drive or access to the Internet is required for product installation. The minimum system configuration for installation is:
|Supported Operating Systems||
Bentley does not support its software running on Microsoft operating systems versions that Microsoft has «retired». For more information see and the Bentley Application Support Lifecycle.
|Internet||Internet connectivity is required to use some of the features of the product and installation of software pre-requisites, if not already installed on the machine.|
|Software Prerequisites||The Prerequisites for Bentley Desktop Applications are automatically downloaded and installed to your workstation while you install MicroStation. The contents of the Prerequisites for Bentley Desktop Applicationsinclude:
Microsoft Internet Explorer, minimum v11.0, with 128-bit cipher strength is also required. It is not installed as part of the product pre-requisites. Microsoft no longer supports any versions prior to v11.0. Internet Explorer is not installed as part of the product pre-requisites.
Copyrights in all components are owned by Microsoft Corporation or one of its affiliates, subsidiaries, or licensors.
|Supported Databases||The database versions supported by MicroStation are subject to updating after the product release. You can search for MicroStation CONNECT Supported Databases for the latest information.|
How do I migrate my V8i user interface customizations to this version?
All of your exiting toolboxes, tasks, cursor menus and custom application user interfaces from MicroStation V8i are supported in this version. We have also provided easy migration tools to upgrade your existing V8i customizations to the new ribbon and ribbon panel popups when you chose to do so. We estimate that 80-90% of your user interface customizations are immediately useful in this version.
Here is a complete list of what V8i user interface concepts are supported in this release with no additional effort
- Tasks and Task Workflows
- Icons and Toolboxes
- Cursor menus
- Custom application interfaces using MDL, MFC, and Winforms
Do object enablers work with Bentley V8i (SELECTseries 4) — Autodesk RealDWG 2016?
Yes, this update leverages Autodesk and other third-party object enablers to display the content stored in a DWG file that is created by an application that requires an object enabler. There are two types of object enablers. The first one is ObjectARX which runs only on AutoCAD. It produces graphics that represents its objects. The second type is enhanced ObjectARX. In it you can add properties to these objects. This type of Object enabler runs on any RealDWG based program, including Bentley products listed above.
When using an Autodesk object enabler this update provides graphical display of AEC Objects in MicroStation, AutoCAD, and other RealDWG-based applications that support object enablers.
Object enablers may be downloaded from Autodesk and other interested vendor’s web site.
Note: In tests on Bentley V8i (SELECTseries 4) — Autodesk RealDWG 2016, it was found that some MEP files failed to open on some old x32 computers. The work around to this is saving the old file to a new file in MEP or AutoCAD.
What are the minimum hardware requirements?
- Processor: Intel or AMD 64-bit processor.
Memory: 4 GB minimum, 16 GB recommended. More memory almost always improves performance, particularly when working with larger models.
Hard Disk: 9 GB free disk space (which includes the 5.6 GB install footprint for a complete installation)
Video: See the graphics card manufacturer for latest information on DirectX drivers. 256 MB of video RAM or higher is recommended. If insufficient video RAM or no graphics card supported by DirectX can be found, MicroStation attempts to use software emulation. For optimal performance, graphics display color depth should be set to 24-bit or higher. When using a color depth setting of 16-bit, some inconsistencies will be noted. For more information on recommended workstation profiles for MicroStation, see MicroStation System Requirements and Hardware Recommendations.
Screen Resolution 1024 x 768 or higher.
Raster Format specific information
What is a XWMS file ?
XWMS files are special XML — like structured text files which send queries to WMS servers. These are internal to Bentley and allow attaching the map layer query results as Raster Manager attachments. There are restrictions on these attachments : they are read-only and cannot be moved, scaled, rotated… like other raster formats. But they will maintain their location info and map layer data integrity. For more info please see the MicroStation Help document under Menus > File Menu > Raster Manager > WMS Map Editor dialog topic.
What is an ECWP attachment ?
ECWP attachments are the result of URL queries sent to servers containing ECW rasters, known as ECWP Image Servers. For additional info please see the MicroStation Help document under Menus > File Menu > Raster Manager dialog > File > Attach > ECWP Image Server.
Raster Manager can now georeference PDF files containing location header information. For more info on how to create GeoPDFs in MicroStation, see the MicroStation Help document under the Working with Complete Designs > Printer Driver Configuration Files > PDF Printer Driver > Enable Georeferencing topic.
DEM and DTM Raster formats
Some DEM and DTM raster formats can now be attached by Raster Manager, but they will only be properly displayed once Bentley Descartes is loaded. The formats that fall into this category are USGS DEM ASCII and USGS SDTS DEM .
Supported raster file formats in MicroStation V8i:
Adobe PDF Apple PICT Esri BIL Type 29 Type 30 Type 31 CALS Type 1 CCITT4 CIT Type 24 Type 2 COT Type 10 Compuserve GIF Digital Terrain Elevation Data USGS Digital Ortho Quad ERMapper Compressed WaveletsErdas IMG FLI Animation format GEOTIFF Bentley HMR Img (24bit) Img Ingr. TIFF Internet TIFF Internet TIFF64 File Format JPEG (JFIF) JPEG 2000 Anatech LRD Ingr. MPF MrSID National Imagery Transmission Format PCX Portable Network Graphics Ingr. Type 27 Ingr. Type 28 RLC Ingr. Type 9 SPOT CAP Image Sun Raster TG4 TIFF Targa Landsat TM FastL7A USGS NDF Wireless BitMap Web Map Server File Format Windows BMP
|Original Author:||Bentley Technical Support|
Customizing your CONNECT Edition Applications for Maximum Productivity
- Customizing the ribbon
- Introduction to the Ribbon Interface
- Creating a ribbon group pop-up
- Adding tools to ribbon groups
- Managing visibility of tools
- Designing a ribbon group pop-up
- Introduction to ribbon group pop-ups and Keytips
- Customizing and creating ribbon group pop-ups
- Keyboards Shortcuts
- Screen Menus
- About screen menus
- Creating a Screen Menu
- Using screen menus
- What happened to the spacebar?
- Where did that tool go?
- MicroStation CONNECT Edition’s Integrated Ribbon Search
- Tips for Ribbon UI
- User-Interface Enhancements: Dialog Flyouts and expanded Dialog Docking
- Batch Process Series Part 1: Updating Your DGN File
- Batch Process Series Part 2: It’s All About the Key-in(s)
The minimum recommended workstation profile for running MicroStation CONNECT Edition is:
|Processor||Intel or AMD processor 1.0 GHz or greater. MicroStation is not supported on a CPU that does not support SSE2.|
|Memory||4 GB minimum, 16 GB recommended. More memory almost always improves performance, particularly when working with larger models.|
|Hard Disk||25 GB minimum, 40 GB depending on additional installations such as Companion Features and Companion Products.|
|Video||See the graphics card manufacturer for latest information on DirectX drivers. 512 MB of video RAM or higher is recommended. If insufficient video RAM or no graphics card supported by DirectX can be found, MicroStation attempts to use software emulation. For optimal performance, graphics display color depth should be set to 24-bit or higher. When using a color depth setting of 16-bit, some inconsistencies will be noted. For more information on recommended workstation profiles for MicroStation, see MicroStation System Requirements and Hardware Recommendations.|
|Screen Resolution||1024 x 768 or higher.|
Stay Current with MicroStation CONNECT
Tip: CAD Administrators may also find Upgrading to MicroStation CONNECT Edition article useful.