Some video card drivers might have issues with OpenGL rendering: fonts do not appear correctly, or the Safeguard Desktop Player application crashes when started with warnings about the graphics card. If this happens, Safeguard Desktop Player tries to fall back to software rendering, but it might fail to do so.
To force software rendering, start the Safeguard Desktop Player using the Safeguard Desktop Player - software rendering item in your application menu, or with the --software command-line option:
Windows: player.exe --software
Linux: ./player --software
Note that on Microsoft Windows, you cannot import CA certificates from a shared drive. In this case, copy the certificate to a local folder and import it from there. Also, the Safeguard Desktop Player application must be installed locally, you cannot start the player.exe file from a shared drive.
The Safeguard Desktop Player application displays important log messages on the Warnings tab. If you increase the log level of the application above the default, additional log messages are also displayed.
Figure 5: Warnings and logs
You can use the following command-line parameters to specify the log level of the Safeguard Desktop Player application.
Set the log level of Safeguard Desktop Player. The default is 3, 0 completely disables logging, 7 is the most verbose, used for debugging. For example:
Windows: player.exe --log-level 5
Linux: ./player --log-level 5
Specify the path and filename of the log file. For example:
Windows: player.exe --log-output desktop-player.log
Linux: ./player --log-output /tmp/desktop-player.log
Specify different log levels for certain components of Safeguard Desktop Player. For example:
Windows: player.exe --log-level 3 --log-spec "bdp.core:5"
Linux: ./player --log-level 3 --log-spec "bdp.core:5"
To install the Safeguard Desktop Player application, read the following sections.