October 21, 2016 at 3:43 pm #61579pirogronianParticipant
Hey, it’s again me, unhappy with outdated but still working GeForce 8600M GT. I just installed last pioneer version (20161015-1). My software: Arch Linux, with legacy nVidia driver 340.98-2.
Game seemed to work fine, until sudden freeze (at spaceport, external view), then unfreeze, then freeze again, then unfreeze but being extremely slow (while leaving orbital spaceport), then became nornal again, and after some time became slow permanently (but only in 3d view screen, in other menus/views performance is normal). Twice I got widnow with warning about gl out of memory, the same was still in console:In function DrawBufferIndexedOn line 769OpenGL error(s) during frame:GL_OUT_OF_MEMORYI have no mods. Setting cleared and set from defaults. Added only “DisableEclipse=1”, becasue it helped with previous issue.Forget to add: all graphics setting set to minimum. Vsync both on and off.I know my hardware is old, but I’m not so rich to buy something betetr and other programs (as FlightGear) worked fine, and I’m sad that the only usable space simulator is unplayable 🙁
October 22, 2016 at 9:22 am #109971
I am genuinely amazed that it runs on an 8600M!
Ok, lets try some other hidden settings that are there for coaxing it along on older machines.
So open up the `config.ini` then find these entries in it and change them to the following:
Ignore the fact that it’s called AMD_MESA_HACKS, that’s just what it started out in life as and I don’t want to break peoples settings by renaming it now 🙂Try those first and let us know how it goes please.Andy
October 22, 2016 at 9:23 am #109972
Oh and as usual if you can post the contents of the “opengl.txt” and “output.txt” files somewhere then that would be very useful thanks.
October 22, 2016 at 10:03 am #109973impaktorParticipant
Another report on this through IRC, regarding the latest build, lastnight.
October 22, 2016 at 4:20 pm #109974pirogronianParticipant
Well, after apply suggested changes in config.ini, problem seems to disappear, so probably I can mark it as “Solved”. However, I’m linking opengl.txt and logs from working configuration, just in case:
BTW: Is output.txt a conventional name for console output? I have no such file in pioneer directory, so I pasted just console output.
I also noticed, that sometimes spaceport bulletin list is dramatically short (2 – 3 items), but is populated after fully game restart. If problem will continue, maybe I started new topic…
November 27, 2016 at 1:11 pm #109979
There has recently been some progress on this with JohnJ finding a number of rendering issues which can cause performance problems, especially on AMD cards. When a new build is ready in the coming few days (_currently 27th, Nov,2016_) it might be worth trying that new build.
May 22, 2017 at 10:18 pm #110458ShodanParticipant
So i get this GL_OUT_OF_MEMORY error when visiting gas giants (Windows 7, Geforce 250GTS 1GB), on my usual detail settings (planet textures already disabled). Setting planet detail distance and fractal detail to very low allows me to orbit gas giants without error, but looking at the gas giant makes framerate very low and it looks all “grey” (jupiter), not sure if that’s the normal appearance from orbital distances, with low detail.
I can’t find a config.ini file, but there is a GasGiant.ini file in the data/config/ directory
Edit: actually it seems I get the GL_OUT_OF_MEMORY error even with the lowest detail settings, I think I didn’t fully re-start pioneer the first time so the error was already present, giving the planet the “grey” appearance
May 23, 2017 at 8:23 am #110460
Shodan the config.ini / output.txt and opengl.txt files are to be found in your “/My Documents/Pioneer/” folder that we create when you run the game.
It the Gas Giant is grey then it sounds like a bug I’ve seen recently on my laptop where the GPU texture generation fails for an unknown reason – although I don’t have the accompanying GL_OUT_OF_MEMORY error.
Find the config.ini and find the line saying “EnableGPUJobs=1”, change that to “EnableGPUJobs=0” and try it again please.
May 26, 2017 at 10:37 am #110463
Shodan did you have any luck with this?
May 26, 2017 at 10:46 pm #110466ShodanParticipant
yep that worked, thanks
- You must be logged in to reply to this topic.