AutoVue

Following are known problems with the AutoVue viewers in some Meridian Enterprise versions. These problems are actively being resolved wherever possible. Some of these issues are limited to the BlueCielo implementation of the viewers and are the responsibility of BlueCielo. Other issues are native to the viewers themselves and are the responsibility of Oracle, Inc. Solutions will be provided as hotfixes or in future Meridian releases.

  • When draft printing with an AutoVue server set as the default viewer and the BlueCielo viewer is installed on the PC, the Number of copies option has no effect.
  • AutoCAD P&ID 2015 drawings opened and saved by AutoCAD P&ID 2017 may not display correctly.
  • Generating thumbnail images of 3D models is not supported by AutoVue 21.
  • AutoVue 20.2.3 can stop working when viewing some Microsoft Excel (.xls, .xlsx) files.
  • The Adobe PDF printer driver might not print right-aligned watermark text completely.
  • Print previews may not show the correct color and position of watermarks.
  • The error Failed to Initialize JVue applet can occur if all of the following are true in the same Internet Explorer session:
    • AutoVue is installed on the local PC as a desktop deployment
    • A document is viewed in the Meridian Web Client with AutoVue installed as a client/server deployment and the Use Oracle AutoVue for viewing documents option is enabled
    • The option is then disabled
    • Viewing a document with the desktop deployment is attempted

    The problem is that the Java virtual machine cannot be reloaded. Restarting the browser reloads the virtual machine and the other viewer deployment can be used.

  • The AutoVue Desktop versions are not supported by the 64-bit Meridian clients. Consider installing AutoVue in a either a client/server or desktop deployment in such cases. For more information, see the BlueCielo Meridian Enterprise Administrator's Guide.
  • No support for object enablers in .dwg files created by the AutoCAD vertical applications and Autodesk Inventor. The objects are not shown in the viewer.
  • Right-clicking to display the shortcut menu may execute the Zoom All command.
  • License file information may be requested when switching between the AutoVue Desktop and AutoVue Client/Server viewers. Restarting the client application resolves the error.
  • If AutoVue 3D is installed on a computer where AutoVue 2D was originally installed by a BlueCielo setup program and the BlueCielo setup program’s Repair option is executed, the original BlueCielo installation will be restored and the computer will revert to the AutoVue 2D viewer. To restore AutoVue 3D, uninstall AutoVue 3D before executing the BlueCielo setup program's repair option and reinstall AutoVue 3D afterward.
  • The AutoVue Document Converter will fail to install if User Account Control (UAC) is enabled on 64-bit computers.
  • The borders drawn around hotspots can appear inaccurate depending on the computer's operating system. The region that the borders surround can be several pixels too large or too small in height or width. The location of the borders has no effect on the functionality of the hotspots.The borders are drawn using the Autodesk RealDWG library that does so with a virtual graphic device so that the borders can be shown on any hardware graphics device. The screen coordinates of the virtual device are slightly different on different operating systems and in different versions of RealDWG.The borders drawn by AutoCAD are accurate because AutoCAD does so with the hardware graphics device.
  • When used with Java 6, the viewer may retain focus after showing a document when browsing a navigation view. This can make it difficult to browse the view with the keyboard arrow keys. This can be resolved by installing a newer version of Java. For information about issues with other versions of Java, see the BlueCielo Meridian Enterprise Supported Software document.
  • When used with Java 8, the Print and Print Preview commands might not work. The solution is to either downgrade to Java 7 or perform the following workaround:

    1. Stop AutoVue Server

    2. Open the file AVS\binallusers.ini in any text editor.

    3. Add the setting NATIVEJAVAPRINTING=1 to the [PRINTOPTIONS] section like this:

      [PRINTOPTIONS]
      NATIVEJAVAPRINTING=1
    4. Save the change.

    5. Restart Autoue Server

    6. Test the Print and Print Preview commands.