VEGA ZZ and VEGA are pieces of software with many functions, therefore it might be possible to discover minor bugs.
22.1 Bug report
VEGA ZZ 3.0 contains a built-in bug report utility called madExcept that help you to send the data needed by us to identify and fix the problem. If a serious error occurs, this dialog window is shown:
in which it's possible to choose different actions:
changing the tabs, its possible to show the data that will be sent to us;
Complete the form typing your name and your e-mail address, check remember me if you want save your contact information and click Continue.
Explain the situation in which the error occurs and click Continue or Skip if you have nothing to explain.
Clicking Continue, the report will be sent to us. Please note that no sensitive personal information will be sent to us and all data will be used for debug purpose only.
If you find a non-critical bug not showing the report utility you can contact
us by this e-mail address:
For other questions please refer to the Authors address in copyright section.
22.2 Known bugs
22.2.1 Amiga version
The powerpacker.library accepts only standard Amiga DOS paths and not Unix-like syntax of ixemul.library. The Data Decompressor Engine shows an error (file not found) if a file is powerpacked and the path has the Unix-like syntax.
The HyperDrive library is statically linked and it doesn't support symmetrical multiprocessing and OpenCL.
22.2.2 VEGA ZZ
Using multi-monitor systems (e.g. dual head graphic cards or two graphic cards) under Windows 9x/ME, the 3D hardware acceleration is not available. This is not a VEGA bug, but a limit of the Microsoft operating system. Windows 2000/XP don't have this problem.
When the monitor in suspend mode is waked up, the double buffer of the main window could be corrupted. You must force the refresh, minimizing and restoring the main window.
When you save an image using the hardware rendering and you installed a Matrox P-Series graphic card, the labels aren't rendered. This is a bug in the Matrox OpenGL driver: the switching of the device context is not detected. The rendering with the software driver (provided by Microsoft) works fine.
The PDF, PostScript, EPS and LaTex drivers don't support transparencies and smoothed vectors.
See the compatibility list for the graphic accelerators.