Ok, running on Xubuntu 14.04. Runs well right to the point of selecting where to put the commander just before the game start. Graphics are fine, can spin the planet all over the place, but I don't get the prompt to place the commander, and though I get the red circle if I click on the planet, I don't get the button to start the game. If I wait long enough, I get a commander that I can walk around but no menus to build anything. I can get it to run on the default X.Org AMD display driver wrapper (and onboard R880 graphics), but it does so extremely slow. Any ideas? System particulars: AMD Phenom(tm) II X4 965 Processor 2.2ghz 8gb ram Running on most recent AMD Linux driver. OpenGL vendor string: Advanced Micro Devices, Inc. OpenGL renderer string: AMD Radeon HD 5800 Series OpenGL core profile version string: 4.3.12874 Core Profile Context 14.10.1006.1001 OpenGL core profile shading language version string: 4.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.4.12874 Compatibility Profile Context 14.10.1006.1001 OpenGL shading language version string: 4.30 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions:
I not sure what exactly blob version distributed though Ubuntu repos, but most likely its first revision Catalyst 14.4. In this case you might try to install 2nd revision or 14.6 beta: http://support.amd.com/en-us/download/desktop?os=Linux x86_64 You can also try to run PA with "--software-ui".
thanks... the "--software-ui" switch allowed me to run it successfully... I'll give the beta catalyst a try when I get a bit of spare time and let you know how that works out. Regards Gully
Make sure to use the --build-pkg method instead of installing it directly with the installer. Makes it easier to uninstall and update and is generally less of a headache. I sometimes also run into this issue on my laptop, closing and reconnecting to the game usually helps.
I have exactly the same problem as gullyf, altough on a completely different machine: Ubuntu Gnome 14.04 i7 2600k + 16 GB RAM GeForce GTX 670 with FW 343.13 PA build 70289 running via Steam I haven't tried the software-ui switch yet, will report when done so.
Exactly the same issue here sad to see Linux isn't getting much love. The UI problems have been around on Linux since day 1 with things like black screen. Is this uber's code or a 3rd party lib causing it? What does using that software UI switch do exactly? If it's happening a lot shouldn't it be in a sticky? FYI using that switch made my mouse cursor vanish, so that didn't help at all. Nvidia 560ti, Intel 4670K 3.4ghz, 8GB DDR3 RAM, Linux Mint 17.
I don't think so. Although it is correct that fix is meant to stop the cursor from vanishing, it should only be necessary when you are using open source drivers. It's easily installed through PAMM, so no harm in trying though. Are you using the proprietary drivers for your NVidia card? If so, which version?
PA have game breaking bug on Linux at moment, but you can't say it like that because: Uber go with OpenGL-only to keep feature-parity between platforms. They promote OpenGL, make Nvidia/Intel/AMD fix their drivers, this is great benefit for Linux. Likely devs released Linux client earlier than any other developer in many years. Obviously I not talking about casual games on Unity. Though till April/May devs actually can't spend enough time on Mac and Linux problems because as far as I know there was no dedicated programmer who can handle platform specific issues. @UberWilliam was able to handle those, but he's really busy guy with tons of other work to do. Now @jorgenpt support both versions and as far as I can tell he fixed mostly all platform-specific problems that I know and also make some changes to better support Mesa on some hardware. "Black screen" was caused by AMD Catalyst bug and disappear when it's fixed in Catalyst. I have no idea if it's me or not, but I passed it to fglrx developer 8 months before it's was fixed. "Causing?" It's triggered by Uber code for sure, but it's make Coherent crash so most likely it's middleware problem. I personally suppose it's related to full UI crashes bug. Most likely same thing what "--disable-gpu" do for Chrome/Chromium. No it's not happening to everyone. Full UI crash with "BadAccess" far more bigger problem.
