- XLSX files created from Spreadsheets or Event Resources tab will not open in OpenOffice.
Files with the extension .xlsx that are created in the Spreadsheets or Event Resources tabs of Vivien will not open in OpenOffice. However, these files will open with Microsoft Excel 2007.
- Transparent surfaces that touch non-transparent objects are not transparent in the rendered image.
To ensure that transparent surfaces touching non-transparent objects are completely invisible in renderings requires a slight workaround. When placing the transparent surface or object in your drawing, ensure that a minuscule space exists between it and any non-transparent objects in your drawing (this space can be as small as you like). For example, if you are placing a transparent surface on a floor, nudge the surface just above the floor. When you render the image, the surface will be invisible.
- In Vivien files which contain more than one Seating Area, increasing any of the Seating Areas may result in non-sequential numbering of the new items added.
The new table/chairs added will be assigned unique numbers, but in some cases the numbers will not be sequential.
Workaround: If this occurs, use the Quick Numbering Tool in the Guest Management tab to renumber the tables/chairs as you wish.
- Bring to Front and Send to Back commands in Drawing Wireframe/Quad tabs and in Layouts tab cannot be undone.
The Undo command will undo the action previous to any Bring to Front/Send to Back commands. Reversing the operation must be done manually and it may take several steps to return objects to their original draw order.
- ‘Windows’ created with the Boolean > Subtract tool may disappear when the file is re-opened.
Sometimes, if ‘windows’ are cut out from a ‘wall’ surface when both the wall surface and the surfaces that will be used for the cutouts, After saving and closing the file, re-opening it causes the windows to be filled in again in the Virtual View. In Drawing Wireframe views, the cutouts are still there.
- Performing 15-20 Boolean operations in a File may lead to a crash on the next Boolean operation.
There is a limit for how many Boolean operations may be performed in a file, but this limit depends on the geometric complexity of the objects within the file, and is therefore unpredictable. If performing repeated Boolean operations on the same objects, it is recommended that you save and back up your work often or even after every successfully completed operation.
- Linear Scale objects do not export in 3D DWG/DXF exported files.
Although Linear Scale objects will export to a 2D DWG/DXF exported file, they currently do not export to a 3D DWG/DXF exported file.
- You cannot perform a second Merge operation on a merged item that has been mirrored.
After mirroring an object that was originally created through a merge operation, you cannot reliably perform another merge procedure on this object.
Workaround: It is recommended that you perform all Merge operations on these objects before you mirror them.
- After saving your Vivien file directly to a Network Attached Storage (NAS) device or any other remote drive/location, including (potentially) USB drives, you may have trouble opening the file.
Workaround: Work on files that are kept on your local hard drive. Before you begin working on the Vivien file, copy it to your local drive and open it from there; once you are finished working on it, save the file (on your local hard drive) and then move it back to your NAS device.
- Undo/Redo is not supported for Camera Path nodes set to User Defined.
- Users running Vivien on computers with integrated video cards have reported quality- and performance-related issues in the Vivien Virtual View
This problem is related to very limited hardware support for features required by Vivien’s Virtual View. Please ensure that you have the latest graphics drivers for your computer. If issues are still experienced in Virtual View, please turn off any unnecessary visualization features. For advice on this, please refer to the following wysiwyg article, which offers valuable insights to the Virtual View settings: http://cast-soft.com/wysiwyg/improving-performance-in-shaded-view/ . Please note that although Vivien will run on a computer with an integrated graphics card, this is not recommended for larger files, and especially not for complex visualization projects — please use a computer with dedicated/discreet video card instead. For more information about updating your video card drivers, we recommend that you refer to the following thread on our Forum: http://forums.cast-soft.com/index.php?threads/general-information-on-fixing-shaded-view-problems-crashes.302/.
- Vivien cannot print to a PDF file if the file’s name or path contains Unicode characters that do not exist in the current system language code page. For example, if your system is using English (United States), you cannot specify a path with Chinese characters.
Workaround: One workaround is to name the file using only characters in your system language from Vivien, and then rename the file afterwards from Windows. Alternatively, if you set the Windows OS language settings to a language which uses the same characters used in the file name or path, then the image can be exported successfully.
- Vivien cannot export the Virtual View to a JPEG image if the file’s name or path contains Unicode characters that do not exist in the current system language code page.
Workaround: One workaround is to save the JPEG in a different image format, (e.g. BMP, PNG, etc.), and it will save successfully. Alternatively, save the JPEG image file with a name and path only containing viable Unicode characters from Vivien, and then rename the file afterwards from Windows.
- The glow feature for Screens may display a white glow when running on some systems using integrated graphics.
Integrated graphics cards do not always support all Enhanced Visualization or Deferred Shading features. As a result, although the glow is visible, the color of the glow may be displayed as white, rather than the color of the content on the Screen.
- When exporting the Virtual View using “Export to Image”, video card settings are not ignored in the exported image.
Workaround: This does not happen if the Virtual View is saved to the Image tab first, and then exported from the Images tab. Another option is to use the PrintScreen feature to capture a screenshot and then paste the image into an Image Editing application.
- For imported hatch patterns with dots, printing may not provide the expected results.
When printing a hatched object that uses a hatch pattern with dots, the dots may appear very small and faint or may not appear at all. Vivien has several hatch patterns with simulated dots that use short line segments instead. This is only a problem if a pattern file is imported.
- Occasionally when opening a dialog in Vivien 2019, the window’s border is displayed but the contents of the window are not shown.
This issue happens randomly. If you experience this problem, you can use the ESC key to close the dialog or click in the top right corner of the dialog where the X button would be. Usually if you try to reopen the same dialog again, all the contents will be displayed the next time it is opened.
- When switching between tabs or between Visual Themes, Vivien mouse clicks may affect the window shown in Vivien.
During these slower operations, Vivien may become temporarily inactive. Avoid clicking the mouse until the switch is complete and Vivien will stay in the foreground.
- Due to differences in how applications work with text, some issues exist with exporting text labels to DWG.
Exporting text labels with multi-line text will result in a text object with one line of text in the DWG/DXF file. Text label borders and background fill are not exported. The Align to View property is ignored. Text will appear slightly larger and may be in a slightly different position from how it appears in Vivien, but it is much more accurate than in previous releases.
- Depending on DPI settings, Layouts may not display or print Worksheet and Report objects at the specified scale.
Sometimes when you render a file which has objects imported from SketchUp, the textures do not appear in the rendering. This is a random bug which happens from time to time. It is possible to determine if the textures will be rendered from the small preview before you start the render job. If you do not see any textures appearing in the small preview, close the Render Wizard window, and reposition your camera and start the Render Wizard again. In most cases, the next time the textures will appear in the rendering (just verify first in the last step of the Render Wizard before starting the render job).
- Pure black-colored objects (i.e. R/G/B = 0/0/0) and up to a color Luminosity value of 16 (in the Color Picker) do not show the footprint of light beams that touch them.
This is part of Vivien’s Black Body Optimization feature. In order for the beam footprints to appear, set the Luminosity to 17 or higher.
- When the model (objects) contained in files being imported are far from the origin, they will not appear in wysiwyg (even though the file imports successfully).
Unlike many (but not all) other CAD/3D modelling applications’ workspace, Vivien’s workspace is not unlimited, so anything drawn more than ~5Km away from the origin in any direction will likely not appear once the import is complete.
Workaround: open the file being imported in the application where it was created, move the model close to the origin (perhaps even surrounding it), save and import that version of the file.