Troubleshooting

RuntimeError: Could not create main OpenGL context

The imfusion module currently requires an OpenGL context and therefore a GPU. First thing to check is therefore that you have a GPU and a working driver. While a discrete GPU is recommended, any integrated GPU works.

If you are using Windows Remote Desktop (RDP) and a Nvidia GPU, you need to run nvidiaopenglrdp.exe which you can download from Nvidia. Otherwise, Windows Remote Desktop won’t support OpenGL. We are currently not aware of a similar solution for AMD or Intel GPUs, other than switching to a different remote desktop tool like Teamviewer or NoMachine.

This issue was also encountered on Linux when there was no X Server running, e.g. on headless server machines. As a workaround , you can start you python interpreter with``xvfb-run``. It is part of the xvfb debian package and provides a software implementation of OpenGL but will be slower in most situations.

Floating point parameters are loaded as integers in Properties

Some Python modules change the locale of the program to e.g. German which uses , instead of . as decimal separator. You can change the locale with:

>>> import locale  
>>> locale.setlocale(locale.LC_NUMERIC, 'C')  

See https://docs.python.org/3.7/library/locale.html for details.

Extra whitespace in Windows console

On certain setups, all log messages produced by the ImFusionLib contain a extra space after every character, l i k e t h i s. This seems to be an issue with Python changing the console mode from O_TEXT to O_BINARY and log4cxx messing up the encoding. As a workaround you can redirect the logging messages to the Python logging module (see Logging).