Please check your NX log file for the information which files are used. If you have a customized installation for NX in your work environment then NX might use other files than the default ones. The installer for our driver creates an entry in this file that sets the path to the files for the UI: $UGII_3DCONNEXION_DIR/$UGII_VERSION (Example: C:\Program Files\Siemens\NX 8.5\UGII\menus\customs_dir.dat). The file customs_dir.dat is in the installation folder of NX in the subfolder “UGII\menus”. UGII_3DCONNEXION_LIBRARY=$\startup\3DxNX.dllĢ. The installer for our driver creates an entry in this file that starts the plugin:> (Example: C:\Program Files\Siemens\NX 8.5\UGII\ugii_env.dat). The file ugii_env.dat is in the installation folder of NX in the subfolder “UGII”.There are two files in NX that are responsible that the plugin is loaded correctly, resp. However, if NX is installed on a server rather than your local machine it might be necessary to make a few changes. To manually change output settings (rotation, enabling/disabling outputs etc) use the KScreen KCM.The 3Dconnexion devices have a plug-in for NX called “3Dconnexion Plug-In for NX” or “3DxNX” for short. System Settings -> Startup and Shutdown -> Service Manager, uncheck "KScreen 2"
Hence, if your X2Go Server machine is also used as a physical desktop machine, consider well, if it is OK to remove that package or not.įor X2Go we suggest disabling the KScreen KDED module in the user's profile, since X2Go handles resolution switches for you: The kscreen package handles hotplugging of display hardware. This, however, may have a negative effect on your X2Go server's plug'n'play capabilities.
On machines that act as an X2Go Server only, it may make sense to remove the kscreen package completely. Using two applications - kscreen and X2Go client applications' resizing features - that handle display resolution is not supported, as it can lead to many unexpected situations and race conditions. You might encounter an X2Go session trying to launch KDE and this KDE session not resizing properly to your client-side screen or session window size. This happens because of a package called kscreen.
0 kommentar(er)
