Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About janinko

  • Rank
    (1) Prestidigitator


  • Pillars of Eternity Backer Badge
  • Pillars of Eternity Kickstarter Badge
  • Deadfire Backer Badge
  • Deadfire Fig Backer
  1. Well, not destroy, but I'm talking from experience that while trying to make drivers work, my system ended up in a state that I wasn't able to repair it and needed to make reinstall.
  2. I tried glmark2, glmark2-es2 and glxgears. Everything was ok, glmark score around 2825, nothing suspicious in journalctl. If it would be faulting graphic card it wouldn't IMHO be so deterministic. I don't know if I have any other Unity3D game, I only know about several 2D games and they worked fine. I'm not sure if I'll be able to test proprietary drivers as I read there were several issues with Fedora 21 and Gnome (and I would rather not destroy my OS while trying to make it work ).
  3. The same for me, I can't run PoE from steam - I get PlayerInitEngineGraphics: GPU not supported; OpenGL GLSL support is required. Your GPU (Gallium 0.4 on AMD JUNIPER) does not support it in Player.log, although glxinfo says OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.0 and the game runs when started from Steam/steamapps/common/Pillars of Eternity/PillarsOfEternity.
  4. Does your log say anything? I have them in "/home/janinko/.config/unity3d/Player.log" and "/home/janinko/.config/unity3d/Obsidian Entertainment/Pillars of Eternity/Player.log". I had sometime problems with running PoE while Chrome was also running.
  5. I run into problem when I tried to run PoE while my Chrome was running. I have linux and using strace I was able to pinpoint that it was Chrome GPU process causing the problem. In /home/janinko/.config/unity3d/Player.log was: Player is already running (Filename: Line: 438) Using strace, I found out that when starting PoE, it scans /proc folder (and IMHO tries to figure out if the app is already running). Strace output: munmap(0x7f517d1fd000, 4096) = 0 lstat("/opt", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 lstat("/opt/google", {st_mode=S_IFDIR|0755, st_size=4096, .
  6. I managed to start the game again with the graphic card plugged in. The issue is back. My graphic card is Radeon HD 5770. Output from Player.log when going to the Copperlane map: (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) ------- BEGIN LEVEL LOAD INITIATED -------- Pending level = AR_0101_Copperlane_Exterior. (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) Checking to instantiate global... (Filename: /BuildAgent/work/d63dfc6385190b60/artifa
  7. I tried to unplug my graphic card and run just on integrated card. The map loaded ok. However after I plugged the card back, the game won't start at all now (but this is another issue).
  8. Yes, I have it on steam and I have tired verify my game files. I tried quit and load the game, load different save and go there again, nothing helps. It looks to me that the texture wasn't loaded properly and instead there is just some memory junk. Every time I start the game and load the artifacts are different, but consists of squares some of which are parts of previous map texture (bridge) and some just random junk.
  9. I'm having issues with map textures when entering Copperlane in Defiance Bay. The minimap is also bugged the same way. I'm playing on Linux (Fedora 21, kernel 3.19.1-201.fc21.x86_64, radeon opensource drivers).
  • Create New...