Originally posted by bridgman
View Post
Announcement
Collapse
No announcement yet.
Nouveau Maxwell: Mesa 17.0 + Linux 4.10 vs. NVIDIA's Linux Driver
Collapse
X
-
Originally posted by duby229 View Post
What? So let me get this right.... You -didn't- update because it -doesn't- work? Isn't that the reason why you should've updated? Usually it's when things are working properly when updates can be let slide, but when things aren't working checking for updates is usually the -first- thing to try. Maybe you should try the latest version of the game right quick because it is entirely possible the issues you are experiencing don'e even exist anymore and all this time you were just screwing with your own self.
Leave a comment:
-
Originally posted by Hi-Angel View PostSorry for meddling, but as someone in the same situations: yes, I need higher OpenGL on mine HD5730. More over: I need specifically that 64 bit support for Space Engine. Because simply overriding OpenGL version leads to SpaceEngine crash, which most probably because it's using those extensions. Which not at all surprising, given how much work SpaceEngine does.
Going to install it and play a bit with it.
Looks good.
Leave a comment:
-
Originally posted by Hi-Angel View PostWell, with "3.3FC" it still crashes. And IgnoreCriticalCheck didn't help — though it might be because I have a 1.5 year old version of SpaceEngine (didn't update because it doesn't work). But thank you anyway — at least now I have something to look into. E.g. I could ask a question on their forum. I thought it's purely my fault, but now I could annoy them a bit — AFAIK using compatibility profiles is a moveton, aren't it.
Leave a comment:
-
So, if i understand this right, i can safely run nouveau on 750ti, because it downclocks the card when feasible?
If so, this is great news for me.
Leave a comment:
-
Originally posted by Hi-Angel View PostWell, with "3.3FC" it still crashes. And IgnoreCriticalCheck didn't help — though it might be because I have a 1.5 year old version of SpaceEngine (didn't update because it doesn't work). But thank you anyway — at least now I have something to look into. E.g. I could ask a question on their forum. I thought it's purely my fault, but now I could annoy them a bit — AFAIK using compatibility profiles is a moveton, aren't it.
I'm not a big fan of compatibility profiles... they were supposed to be a transitional aid so that CAD SW vendors with a big investment in OpenGL could take advantage of new GL features in the short term while they worked on moving to the new core profiles. I understand why they were added but I don't understand why they didn't also come with a roadmap for deprecating them.
Leave a comment:
-
Originally posted by bridgman View PostSounds like you found the issue - Space Engine might be looking for a compatibility profile rather than the usual core profile. Compatibility profiles allow an application to mix deprecated API calls with newly added functions, albeit with unspecified behaviour.
I have not found anything saying that Space Engine *does* require a compatibility profile; it just seems likely if it is reporting the 3.0 version.
BTW if this is the case then your GL override would have to be something like "3.3FC" rather than just "3.3".
There is also a check in Space Engine which might be worth disabling for a test:
http://en.spaceengine.org/forum/4-3483-1
Leave a comment:
-
Sounds like you found the issue - Space Engine might be looking for a compatibility profile rather than the usual core profile. Compatibility profiles allow an application to mix deprecated API calls with newly added functions, albeit with unspecified behaviour.
I have not found anything saying that Space Engine *does* require a compatibility profile; it just seems likely if it is reporting the 3.0 version.
BTW if this is the case then your GL override would have to be something like "3.3FC" rather than just "3.3".
There is also a check in Space Engine which might be worth disabling for a test:
But you still can try and run SpaceEngine by disabling checking of critical errors at startup. Open main-user.cfg and change value of this parameter to 'true':
IgnoreCriticalCheck true // ignore checking of OpenGL version and critical extensions supporting
NOTE: I can give no guaranties that SpaceEngine will be stable and work correctly if you do make this change.Last edited by bridgman; 24 January 2017, 01:23 AM.
- Likes 1
Leave a comment:
-
Originally posted by bridgman View PostSomething doesn't sound right - doesn't Space Engine only require GL 3.3 in the first place ?
What happens if you don't override ?
BTW I suspect nomadewolf was talking about processing power, not age of the card, specifically whether a 6470 would have enough processing power to run the most demanding games even if it had the GL support.
Your 5730 has ~4x the processing power and memory bandwidth of a 6470.
Now that I looked at it again, it's more interesting: the OpenGL SpaceEngine has in logs is just 3.0. It takes it probably from "OpenGL version string", not from "OpenGL core profile version" — well, I'm not versed in the terminology, I thought the latest is the version, in part because it's higher.
Probably, I need to ask on ML another question, for why I'm seeing 3.0 instead of even 3.3. But whatever, even if I override it to 3.3 "MESA_GL_VERSION_OVERRIDE=3.3 wine SpaceEngine.exe" — SpaceEngine just crashes. It might of course be not the problem with OpenGL, but from my research in the past, the app works fine for other peoples through Wine, so I have little to blame.
Leave a comment:
-
Something doesn't sound right - doesn't Space Engine only require GL 3.3 in the first place ?
What happens if you don't override ?
BTW I suspect nomadewolf was talking about processing power, not age of the card, specifically whether a 6470 would have enough processing power to run the most demanding games even if it had the GL support.
Your 5730 has ~4x the processing power and memory bandwidth of a 6470.
Leave a comment:
Leave a comment: