Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Needicla]

And?

[cameni]

Why not the latest?

[Needicla]

It is the latest.

[zuluknob]

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

[KelvinNZ]

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.

[Needicla]

Months later, I'm still having the same problem and nothing was fixed.

[Jagerbomber]

You realize it's not ready yet, right?

Did you even try going to the AMD website and getting the latest drivers?

[cameni]

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.

[KelvinNZ]

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.

[cameni]

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.

[KelvinNZ]

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.

[Jagerbomber]

& entitlement

from someone who hasn't even bought the thing...