Hello,
I am running a dual screen setup and for some reason the Linux build of my Urho3D fullscreen application always starts on the secondary screen. This happens since Ubuntu 18.04 (currently 19.10) with the native Nvidia drivers. Everything is fine on Windows.
I have found this topic but unfortunately none of the suggestions worked for me: Fullscreen Monitor Select
Are there any updates on that?
It is a long shot but did you install “libxinerama-dev” package as one of the SDL2 (and hence also Urho3D) prerequisite? Our Linux prebuilt binary from CI is built with “libxinerama-dev”, so you can give the sample demo a quick try too to rule out whether missing “libxinerama-dev” is the root cause of your issue.
Thanks for the suggestion and sorry for the late reply but I somehow forgot about this thread over Christmas and winter holidays…
I’ve built Urho3D from source and the libxinerama-dev package was installed and enabled in cmake at build time.
The “Urho3DPlayer” indeed starts fullscreen on the primary screen. But I still couldn’t find the runtime option to enable that on my program…
I am using only C++ and no scripting.
I don’t have multiple monitor setup so take what I said with a grain of salt. I can see two things that could potentially be the cause. One, your build tree need to be regen after the new dep is installed on your host, or clear CMake cache and rerun CMake to reconfigure. Second, your program has requested a resolution that is better matched by your secondary monitor.
Thanks again for the suggestions. Both screens have the same native resolution and the cmake cache doesn’t need to be cleared because nothing was changed. libxinerama-dev was already installed and enabled on my very first build of Urho3D.
@Pencheff: Thank you, too. My problem is not running the program in fullscreen which works fine already. It just starts on the wrong (secondary) screen which (as mentioned above) has the same resolution as the primary screen (1080p). I will look through your code to see if I can find something useful.
Hi, just wanted to mention here that I could solve this with a fresh (K)Ubuntu install.
Since then my application starts at the correct primary screen. This even works fine after swapping the monitors.
Not sure what was wrong with my previous >4 years old installation, but obviously there was a mix-up of the primary screen somewhere in the depths of the window manager/compositor.