For information on Component Catalog Editor issues, click here.
VRML |
Textures cannot be imported in VRML 1.0 files. |
Graphics Performance Enhancement for V5 Products |
V5R18SP2 is taking more benefit from the graphics hardware (GPU).
Graphics performance of V5 is enhanced thanks to the support of the OpenGL
feature, Vertex Buffer Object (VBO). This performance gain matches perfectly the requirements of V5 Products like:
This graphics optimization is only available on Windows XP 32-bit &
64-bit and by exporting the following
environment variable in your V5 install: It is strongly recommended to switch on this optimization on the latest hw graphics having at least 512 MB of video memory like:
It is recommended to install the NVIDIA 182.08 driver series or later.
It is recommended to install the ATI FireGL 8.543 driver series or later. Refer to the DS certified configuration website to check your configuration. |
View Mode Customization |
We do not guarantee an identical triangulation of meshes between releases and from one Service Pack to another. |
Printing using the Microsoft Office Document Image Writer printer |
When printing documents using the Microsoft
Office Document Image Writer virtual printer, it is recommended to select
the Monochrome mode in Version 5 (click the Options...
button in the Print dialog box):
Otherwise, selecting the
TIFF-Monochrome Fax option in the printer's Advanced Parameters may lead to a crash. |
Language-Specific Fonts |
Korean and Chinese characters may not be well rendered if you are working on UNIX. |
Memory leaks for GDI objects |
Memory leaks may occur for Graphics Device Interface (GDI) objects when you
create and destroy child windows. For more information, browse the following Internet site:
|
Digital Rights Management |
For security reasons, there is no downward compatibility between DRM-protected
data created from V5R19 SP6 and DRM-protected data created in previous
releases. Therefore:
To make DRM-protected data compatible again, security HotFixes are available on all previous levels. To do so, follow the instructions below:
Note that on all levels lower than V5R19 SP6, native DRM-protected data will no longer be compatible with the corresponding fixed level. Therefore, it is very important to keep a clear version of this data to be able to protect them again through the DRM capability. |
VBA |
When using VBA in a 64-bit environment, you may encounter an error message from
VBA indicating memory allocation problems or may not even succeed in loading
your VBA project. These problems can be removed by upgrading to the most
recent version, VBA 6.5.
The
|
Print Settings |
The settings displayed in the Print dialog box can be modified through the Print dialog box only. The Windows Printer Properties dialog box does not reflect the settings used for printing (e.g. number of copies, page setup, etc.). |
Screen dimensions on Vista |
When using some Vista configurations, the size of the screen is not correctly
computed, which may lead to a bad visualization: for instance,
points may disappear. Workaround: Store your screen dimensions in the following two variables:
You have to do these measurements by yourself using a tape measure. The
screen dimensions correspond to the horizontal measurement followed by the
vertical measurement. |
DLNames |
The following commands do not support the DLName environment: File > Print..., Tools > Image > Capture..., Tools > Image > Album... and Tools > Image > Video.... |
Anti-Aliasing Full Scene |
The Anti-Aliasing Full Scene option available in Tools... > Options > General > Display > Visualization is not compliant with Object-to-Object shadows in the Real Time Rendering Product. |
Viewing objects |
When you set a white background color in Tools... > Options > General > Display > Visualization, annotations, texts and lines with a white color cannot be seen. |
Using Russian fonts on SUN |
|
Recording videos on Windows 64-bit |
In the Video Properties dialog box you open through Tools >
Image > Video, there is no access to DirectShow codecs on Windows
64-bit. The only accessible codecs are VFW (Video for Windows) codecs. Off the shelf VFW 64 bit codecs are very rare and most often not compatible with Version 5. Consequently, a Version 5-compatible MJPEG VFW codec for 64-bit is provided. The DirectShow MJPEG codec is not provided on Windows 64-bit. Refer to the official documentation for more information about how to install this codec. |
Large memory allocation |
When printing large documents, the printing process tries to use the dpi
value defined in the raster driver's settings and checks if memory
allocation is possible before printing. However, note that the detection of large memory allocation is available on Windows 32-bit only. |
Capturing images in Screen Mode on UNIX |
On UNIX, the Screen Mode available via Tools > Image >
Capture supports only 24-bit visuals (TrueColor or DirectColor):
it does not support 8-bit visuals (PseudoColor or StaticColor). Workaround: use the xdpyinfo UNIX command to check the current visual characteristics. If this visual is 8 bits, then change the settings of the Windows Manager to a 24-bit visual. |
Printing/Capturing using the Print white vectors in black/Capture white in black option |
If you print documents with the Print white vectors in black option activated or if you capture images with the Capture white in black option activated, white specular spots displayed on parts in Shading rendering mode appear in black. |
Printing 2D drawings |
When the text has
overlapping contours, some of the contours are not correctly
tessellated. Below are two examples: Example 1
Example 2
|
Printing using the Rasterization rendering mode |
|
Print Batch utility |
|
Printing clipped entities |
The clipping of entities is not correctly
supported by the vector rendering mode named Dynamic Hidden Line
Removal.
Workaround: use the Hidden Line Removal rendering mode instead. |
Print variable |
The PRINT_CAPTURE_DPI variable is ignored when saving a CATDrawing to a Tiff file. The DPI stored in the settings is used instead. |
Saving a document with multiple sheets in single vectorial file |
When using the Save multisheet document in a single vectorial file option available in Tools > Options... > General > Compatiblity > Graphic Formats, note that the only Version 5 viewer supporting multisheet information is the TIFF viewer. Other Version 5 viewers for GL2, GL, CGM, SVG and PS do not support this feature. |
Copying/Pasting .CATDrawing documents on UNIX |
On UNIX, note that when pasting an existing
drawing to a new one, the viewer of the new drawing may not be correctly
dimensioned. Workaround: resize manually the viewer, or use the Maximize capability to resize the viewer. |
3D XML |
Saving in 3D XML format - General information
DMU NavigatorFor open issues specific to the DMU Navigator product, see the DMU Navigator Program Directory. MaterialsFor open issues specific to materials, see the Real Time Rendering Program Directory. CATDrawingsFor open issues specific to CATDrawings, see the Interactive Drafting and Generative Drafting Program Directories. Scenes and Presentations
Measures (Item and Between)
Sections
|
Double-clicking a document on Windows |
When double-clicking a document icon using the
Windows Explorer or My Computer, the following error message may appear,
even though the double-clicked document is correctly loaded in session:
Ignore the message. |
Interrupting batches on UNIX |
Using the Interrupt
contextual command in the Processes tab of the batch monitor lets you
interrupt batch execution. When you interrupt a batch on UNIX, an abnormal
end is generated.
Ignore the abnormal end. |
Rendering styles |
When using View >
Render Style, the Customize View mode appears
twice:
This mode should be named Customize View Parameters as
explained in the documentation and should appear only once in the list. |
Knowledgeware |
xlsx files (Excel 2007) used by Design Tables cannot be saved in ENOVIA. Only Design Tables that use .xls files can be saved. |
DLName support in Macros |
The section "Automating Repetitive Tasks Using Macros" in the
Infrastructure Users Guide now includes the following remark about
DLName support: "Furthermore, DLNames are now supported. If you set the DLName option to Current via the Tools>Options>General>Document tab, and access Directories as Library Type using the Macros... command and click the "Add existing libraries" button, the DLName window is displayed. For more information about setting DLNames, refer to the DLName documentation section in this guide." |
||||||||||||||
Macros |
The External References screenshot has been replaced with the correct
icon:
|
||||||||||||||
Viewing Tools |
The SpacePilot PRO is supported from R19 SP4.
Just like the SpacePilot, the SpacePilot PRO can be used, in addition to the mouse, to perform graphic viewing manipulations (zoom, pan, rotate, etc.) in one single motion. To download the latest 3Dconnexion software, browse the following Internet site:
SpacePilot PRO is supported on Windows XP SP2/SP3 and Vista (all editions) x86 and x64. It requires a 3DConnexion 3DxSoftware 3.7.6 (minimum level). SpacePilot PRO developed by 3Dconnexion is an advanced 3D Mouse equipped with a color LCD panel which, among other features, labels the functions of the device buttons. This new device offers more capabilities such as: advanced MCAD navigation (standard views and 3D Mouse settings keys), LCD Workflow Assistant (e-mail, calendar, function key feedback, and more) ; dual-function keys for frequently used commands ; superior comfort for long work sessions.
Device buttons are mapped using the dedicated Button Customize
dialog box. Whenever you change a button function in the 3DxWare driver,
this change appears on the color LCD panel and in the Button Customize
dialog box. For detailed information on this device, browse the following Internet site:
|
||||||||||||||
Increased Similarity between HLR and HRD when Printing Documents |
Customizing Print Settings
About HLR Algorithms
|
||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
Automatic disconnection after ... minutes |
Restriction: on Windows operating systems, if a message popup box is displayed, then automatic disconnection does not occur. |
||||||||||||||
Lighting with a low-angle camera |
When visualizing a surface with a low-angle camera, visual artefacts
might appear. This is due to the lighting computation which is done per
vertex. In that case, the standard OpenGL lighting mode is used. The OpenGL lighting model is hard-coded in the graphics card and works as follows: given the color of the three vertices, the color of pixels within a triangle is computed as a linear combination of the color at the three vertices of the triangle. Of course, it is an approximation of the real computation. Below is an example showing how white stripes are triangle-dependent:
The pictures below show how the visual artefact disappears when applying advanced materials:
However, if you keep on zooming in, this visual artefact will reappear when the camera is getting closer to the mesh. The only way to reduce this visual artefact is to modify the tessellation settings (i.e. the 3D accuracy and the curves' accuracy ratio) and to reduce the material reflectivity. |