Currently trying to get PA:Titans to work reasonably well under linux with the following config: Fedora 24 (kernel 4.7.4-200) Mesa drivers (can provide version if need be) R9-280X GPU AMD FX4170 CPU 8GiB DDR3 The hardware is more than enough to run the game effectively as I have been using the game in Windows 7 since the *nix version is giving me trouble. Having issues with the following: On larger maps it seems PA or server suffers from a memory leak; will eventually suck up memory until I hit my swap space which kills the framerate. Saving, closing and re-opening the save results in regular gameplay for a while before it happens again. PiP is hit and miss, sometimes I'll get the proper rendered view others I'll just get black After playing a match pretty much any menu is black, occasionally with the social bar at the bottom. Usually have kill PA at that point. Makes playing the galactic mode nigh impossible. Anyone have some solutions to try? I do have some log files available if it'll help; seems they don't always get written as the last match I tested it with didn't seem to output anything.
Yeah, log files could help. So please do upload them here. You may also want to try the --software-ui flag, which seems helpful for AMD users on Linux. I don't know if that will fix the memory leak though.
Just had a look and seems I had that flag on already (IIRC PA didn't do much of anything outside of crashing at the start of a match without the flag). I've attached the log file I found (I think the files I was looking before may have been something else); here I had PiP issues and the empty menu screens but the memory usage didn't end up as a problem; possibly because I chose a smaller map than previous to end the match faster.
Wow, so many GLTexture errors in there. Could you try running PA outside of Steam to see if maybe the outdated libraries that come with Steam itself are to blame? To do so, go to "/fedoraBlack/fedora22_SteamLibrary/steamapps/common/Planetary Annihilation Titans". You'll need to make a symlink there that points to libudev.so.0. I think on Fedora you have a libudev.so.1 in /lib64 or /usr/lib64? So type Code: ln -s /lib64/libudev.so.1 libudev.so.0 Then you'll also need the libsdl2-2.0. I'm not sure what that package is called in Fedora. As you can see I don't run Fedora. Anyway, then you can run PA from the terminal with Code: ./PA --software-ui You won't be able to play on-line without Steam auto-logging in of course, but local games should work to test if you still have the memory leak. (Unless you have an UberID linked to Steam, then you can still log in manually of course.)
No worries; I can see about overriding those libraries easily enough and see what all happens. Was rather surprised to see so many errors myself, though I'm always surprised how many games just constantly yell various angry things at you while running perfectly fine haha
Hmmm, are you sure about libudev? ldd doesn't show that PA is linked to udev; I get the following libraries linked to PA (see attached; pretty long lines and a LOT of linked libraries). Though swapping out the SDL2 libraries for the ones Fedora ships did not go over well; entered a match and pretty much no rendering and I went from a few gigs of free memory to killing my swap space in about 10 seconds.
I'm afraid "--software-ui" results in black screens as well. All it does, is preventing texture corruption inside any of the Coherent panels, but instead the entire panels turn black instead. Same issues now also with the recent Intel Linux drivers, ever since the OpenGL core profile got updated from 4.3 to 4.5.
Yeah, it's a bit of a hit and miss. For some people it works perfectly, for others not so much. Especially AMD users seem to benefit from it. It stopped working for me (on NVIDIA) after upgrading to Kubuntu 16.04 for instance. I get some black panels, but also invisible panels. I also can't press the "start annihilation" button to make my comm land. Also metal spots and unit icons have a black square behind them now. Without --software-ui I just have to settle for menus only appearing after I mouse over them, otherwise they sort of half appear, which isn't too bad, but not ideal. Never got around fixing that myself. And then there is of course the black screen after every match that goes with --software-ui that needs a window resize to fix.
Things I tried, which didn't help: Enforcing a lower OpenGL / GLSL version (tried 3.2, 4.0, 4.2, 4.4, 4.5), same bugs with all of them Using as much of the (outdated) steam run time as possible, rather than native, still same bugs. (Used everything apart from libgpg-error.so.0 and libstdc++.so.6) Well, what helps **hiding** the corruption is not using an OpenGL accelerated window compositor. But that's really just hiding the problem, not solving it. PA, respectively Coherent, will still eventually mess up the textures. Launch another OpenGL using application concurrently, and you will see the buffers getting mixed up sooner or later. What's odd, is that there is also a potential crash occurring on Windows, at the very same time as when the texture corruption occurs on the Linux build. Only except that the crash on Windows is a lot rarer and doesn't occur on every single launch, but only every few dozen attempts or so. As for the resize "fixing" it: It doesn't. That's merely resulting in a re-allocation of the buffer for the corresponding panels. Eventually they get corrupted again.
I'd actually be ok with the resizing workaround if it worked on my box. Outside of the issues with the memory leak ,which I'm sure I could delay being a game-stopping problem by allocating some swap on my SSD rather than my HDD; or getting more memory; or just winning a match faster, I can live with hit-and-miss PiP but not being able to do anything after a match except force quitting and reloading kinda kills any sort of momentum to keep playing. I do wonder though what would happen if I switched to Wayland rather than using X11 and mutter. I suspect terrible things will occur but I'll give it a shot tonight.
Yeah, I'm sure. It's not PA that links to it, but rather host/CoherentUI_Host that does. So PA will start fine, but with a black screen because the UI crashes. You'll see an error in your log saying it's missing libudev.so.0. It's not actually being used as far as I know. Though since you were able to start the game without making the symlink, it may already be present on your system. What exactly do you mean with swapping out the SDL2 libraries by the way?
Aah, ok that makes sense; will give that a go as well then. As for the swapping I just made a symlink to the SDL2 on my system in the PA directory and exported LD_LIBRARY_PATH for that session to point to where the link is. I usually make a proper place for libraries to live when I need to provide replacements for a game but this works well enough for quick testing and doesn't leave a messy footprint outside the symlink.
Interesting. Thanks for that. I always run outside of Steam. The no-Steam version of PA still comes with the steam-runtime, but it doesn't make a difference for me either with or without that. I'll have to look into setting the GL version and see if that does anything. As soon as I find the environment variable that control that for NVIDIA cards...
Ok so I think I made some progress, following DeathByDenim's library advice seemed to have reduced the impact of the memory leak (I think) as I played the map that caused me grief before and no issues this time, further matches will tell. PiP was still hit and miss but that's fine; it was always more of a 'neat idea' than a proper utility for me. Still got the black screen at the menu but apparently restarting gnome-session did the trick this time (it hasn't in the past). Overall it seemed to work finally more or less.
Yeah, I'm not sure if it's the drivers or PA at this point. In any case, both still get updates, so maybe it'll be fixed at some point...
Yup; maybe a Mesa or PA update will fix it, or break it even worse haha. I'll be able to deal with this until I get a mobo with proper IOMMU support. At the least hopefully this thread will be of some use to anyone running into similar issues.
I had not, looking through the detailed patch notes it doesn't look like there may be much that'll help. Maybe some of the changes to better handle multithreading will help with the memory leak. Will give it a shot anyway.
Seems to work a bit better. PiP is consistently working (but kills the frame-rate, didn't have a counter but I'd say steady 60 to <20), memory issues seem better but would need to do a longer/larger match to test, still have to reset gnome-session when the match is over to get around the black-screen issue. I get the feeling further updates may put some more polish on all this.
