Outerra forum
Anteworld - Outerra Game => Tech demo, support, updates => Topic started by: Needicla on July 19, 2013, 02:18:54 pm
-
Before people say the same thing in every thing I've posted:
1. I've downloaded everything stated in all the previous threads with this problem.
2. I've updated my drivers.
3. There is no option to change in the BIOs
4. You can't update the BIOs.
5. This model is different, you can't fucking change it to fixed in the "configure switchable graphics" setting.
It won't detect my AMD Radeon graphics card, so fix your game please.
-
Unfortunately it's not in our powers to fix AMD OpenGL driver issues and Windows/BIOS issues. This is a problem with the AMD switchable graphics: if you don't see an option in Catalyst to assign the discrete GPU to outerra.exe for OpenGL, then the only way is to force it in BIOS. If there's no such option in BIOS, there's nothing we can do, unfortunately.
See this: http://abesto.net/the-sad-case-of-the-hp-pavilion-g6-opengl-and-amd-switchable-graphics/ (http://abesto.net/the-sad-case-of-the-hp-pavilion-g6-opengl-and-amd-switchable-graphics/)
or this http://h30434.www3.hp.com/t5/Notebook-Display-and-Video-e-g-Windows-8/HP-What-is-wrong-with-your-support-g-series-switchable/td-p/964099 (http://h30434.www3.hp.com/t5/Notebook-Display-and-Video-e-g-Windows-8/HP-What-is-wrong-with-your-support-g-series-switchable/td-p/964099)
... and many other posts about the problem on other models, like this (http://h20435.www2.hp.com/t5/The-Next-Bench-Blog/On-OpenGL-and-Switchable-Graphics/ba-p/67193), and this (http://www.notebookcheck.net/AMD-Dynamic-Switchable-Graphics-vs-Nvidia-Optimus.64378.0.html). Just google "amd switchable graphics opengl problem" .. flood of posts.
Seems HP is totally ignoring it for G series :(
Not sure why AMD doesn't just handle it universally in Catalyst, too, it just causes a lot of bad blood.
-
Just found this: http://leshcatlabs.net/category/unifl/ (http://leshcatlabs.net/category/unifl/)
It should bring newer switchable graphics support in Catalyst for models that don't have suitable drivers, if the hardware can support it. Might be worth a try.
-
Wow, it really looks like you didn't read my post, even though the first thing I said in the post is to read it. I did assign outtera.exe, but it still recognizes it as the Intel graphics.
EDIT: Also, I've read everything in the "Sad case of the HP PAvilion G6" and everything was terribly wrong, I can run both games listed in the best quality, also, it says the only supported operating system is Windows 7, false, I'm on Windows 8 now. So it's a problem with your game, fix it.
-
There's nothing we can fix about it dude, it's a driver thing. Either you manage to set it in the Catalyst/BIOS, or you complain to AMD/HP/Microsoft.
I did assign outtera.exe, but it still recognizes it as the Intel graphics.
It's outerra.exe, not outtera.exe
-
I did a typo, also, this is horrible service.
-
How do you know it doesn't recognize AMD? It may give you a warning about Intel graphics, but what happens when you let it go further, does it really use Intel and not AMD with the correct assignment in the control panel?
The OpenGL context used is logged in eng.log
-
It does give a warning about Intel graphics, when I start it and it loads, an error report shows up, so I assumed it's because it said stuff about Intel graphics.
-
Can you upload the eng.log from the Outerra data directory? Or just send the error report. It should contain all the version information, we'll see what OpenGL context/version is given to outerra.exe by the system.
-
INFO: Outerra 0.7.16, build 3749 from Fri, 21 Jun 2013 09:40:06 GMT
DEBUG: Initializing engine...
DEBUG: data root directory: C:\Users\On\Outerra\
DEBUG: Windows version: 6.2.9200
DEBUG: CPU info:
CPU string: GenuineIntel
CPU brand string: Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz
Stepping ID: 9
Model: 10
Family: 6
Processor type: 0
Extended model: 3
Extended family: 0
Brand Index: 0
CLFLUSH cache line size: 64
APIC Physical ID: 4
DEBUG: GPU System info
Graphics card: Intel(R) HD Graphics 4000
GPU vendor ID: 8086 (Intel Corporation)
GPU device ID: 0166
OpenGL driver version: (igldev32.dll)
OpenGL driver build number: 0
DEBUG: stopping renderer processing
DEBUG: Stopping renderer thread...
This is what it says.
-
That's odd, is this after you press Yes when it asks if it should run anyway?
Because this looks it's exiting immediately after logging the system info, and doesn't try to initialize OpenGL at all.
-
.. When I tried to run it again, a new error occurs, error initializing OpenGL subsystem. This program requires OpenGL 3.3 capable graphics card with recent drivers.
No suitable pixel format found.
-
Normally Intel HD 4000 driver reports that it supports GL 4.2, so this looks as if this was going AMD route (or the Intel driver was old). This error often appears with a corrupted Catalyst install, but since you said you did everything mentioned in the previous threads, I guess you did a clean install of Catalyst as well, removing the old one with a driver sweeper.
If so, please check the physical version number (properties->details) of c:\windows\syswow64\atioglxx.dll, the latest drivers should have 6.14.10.12337 or higher.
-
Says it is 6.14.10.11774
-
That seems to be a 12.9 Catalyst version.
-
And?
-
Why not the latest?
-
It is the latest.
-
goto amd.com and fill out the driver form(top right of the page). the latest version is 13.4 and beta version is 13.6
-
Wow, it really looks like you didn't read my post, even though the first thing I said in the post is to read it. I did assign outtera.exe, but it still recognizes it as the Intel graphics.
EDIT: Also, I've read everything in the "Sad case of the HP PAvilion G6" and everything was terribly wrong, I can run both games listed in the best quality, also, it says the only supported operating system is Windows 7, false, I'm on Windows 8 now. So it's a problem with your game, fix it.
I think you need to get your manners sorted fella. This is a friendly and helpful forum and demanding like you are being doesn't bring you any respect.
Cameni is extremely helpful so I suggest you work with him rather than vent any frustration you might have.
Outerra is still in Alpha state and drivers are an external factor that can cause problems as Outerra does not make the drivers just the software that utilises them.
Cheers,
K.
-
Months later, I'm still having the same problem and nothing was fixed.
-
You realize it's not ready yet, right?
Did you even try going to the AMD website and getting the latest drivers?
-
We have no power over what OpenGL context we are given from the operating system or from the vendor. Just as we apparently have no power to convince someone who comes biased and angry and blames us for it.
12.9 was the first driver that brought a new capability to switch between the cards, supposedly working for OpenGL and some AMD chips. There were many new driver releases since that, so I'd try a newer one. And since the Catalyst is chronically messing up the install, I would do a clean reinstall. These are all listed in the driver help post.
But still, if it doesn't work, there's nothing we can do about it from the application side, because such functionality is not exposed in OpenGL, it's a functionality of the system that's deciding it in such a "smart" way.
-
Months later, I'm still having the same problem and nothing was fixed.
understood, but just keep feeding what you can, logging all errors providing as much detail as you can. you signed up to an Alpha program and that's the reality. however essentially you are a tester as with the rest of us. so treating it as that may just help a little.
even though it's months later it doesn't mean all issues will be fixed.
-
even though it's months later it doesn't mean all issues will be fixed.
If it was our bug it would have been fixed months ago. Unfortunately we have no control over it, and that's what he doesn't want to accept. Maybe the newer drivers fixed that issue, maybe the old drivers have to be cleaned for it to work - all of that happened/helped others before.
Waiting until outerra.exe magically fixes the OS state or the Catalyst install certainly won't help here.
-
there is some perceptions out there that it all rests with Outerra developers to resolve other third party problems. I really think it is a lack of understanding of the difference between the application layer and hardware layer and how they work. This lack of understanding causes unfounded statements from unmanaged anger which also seems to prevent one from actually being a part of the solution.
-
& entitlement
from someone who hasn't even bought the thing...