Page 2 of 3
Re: Struggling with keys to access all the stuff I need to use
Posted: Sun Nov 26, 2023 11:03 am
by another_commander
HDR output mode is enabled only when explicitly requested at launch via the command line. Launching the game normally creates standard 8 bpc backbuffer as it always has been the case.
IMO the issue is that the gfx card is just too old to support the requirements of the new renderer. My initial suggestion would be to drop detail level to Shaders Enabled.
PS: phkb's .GNUstepdefaults edit is not wrong, but the absence of the "hdr" key defaults to NO, so if it is missing HDR is not activated anyway.
Re: Struggling with keys to access all the stuff I need to use
Posted: Sun Nov 26, 2023 3:55 pm
by Switeck
phkb wrote: ↑Sun Nov 26, 2023 10:53 amSomething to try: can you put
into your .GNUstepDefaults file, to see if that clears up the performance issues
Should I use the stylized quotation marks or the simpler " quotation marks?
another_commander wrote: ↑Sun Nov 26, 2023 11:03 amIMO the issue is that the gfx card is just too old to support the requirements of the new renderer. My initial suggestion would be to drop detail level to Shaders Enabled.
That is what I shall do then.
...Seems to work, and it's not rock-bottom frame rate anymore.
Re: Struggling with keys to access all the stuff I need to use
Posted: Sun Nov 26, 2023 8:02 pm
by hiran
another_commander wrote: ↑Sun Nov 26, 2023 11:03 am
HDR output mode is enabled only when explicitly requested at launch via the command line. Launching the game normally creates standard 8 bpc backbuffer as it always has been the case.
IMO the issue is that the gfx card is just too old to support the requirements of the new renderer. My initial suggestion would be to drop detail level to Shaders Enabled.
PS: phkb's .GNUstepdefaults edit is not wrong, but the absence of the "hdr" key defaults to NO, so if it is missing HDR is not activated anyway.
For quite some time I thought having Oolite log it's command line on startup might be a good idea for troubleshooting based on the logfile.
Would that be a big change in the code?
Re: Struggling with keys to access all the stuff I need to use
Posted: Mon Nov 27, 2023 7:12 am
by another_commander
hiran wrote: ↑Sun Nov 26, 2023 8:02 pm
For quite some time I thought having Oolite log it's command line on startup might be a good idea for troubleshooting based on the logfile.
Would that be a big change in the code?
Seems quite straightforward. The build containing this is currently cooking.
Re: Struggling with keys to access all the stuff I need to use
Posted: Mon Nov 27, 2023 7:39 pm
by hiran
another_commander wrote: ↑Mon Nov 27, 2023 7:12 am
hiran wrote: ↑Sun Nov 26, 2023 8:02 pm
For quite some time I thought having Oolite log it's command line on startup might be a good idea for troubleshooting based on the logfile.
Would that be a big change in the code?
Seems quite straightforward. The build containing this is currently cooking.
Oh that was quick. Thanks a lot!
Re: Struggling with keys to access all the stuff I need to use
Posted: Mon Nov 27, 2023 7:41 pm
by arquebus
Ok I am losing my mind here, where do I go to set the extra keys?
Re: Struggling with keys to access all the stuff I need to use
Posted: Mon Nov 27, 2023 7:47 pm
by phkb
In the keyboard config screen, where all keys are set.
Re: Struggling with keys to access all the stuff I need to use
Posted: Tue Nov 28, 2023 8:30 pm
by arquebus
phkb wrote: ↑Mon Nov 27, 2023 7:47 pm
In the keyboard config screen, where all keys are set.
My main screen and in-game game options has autosave, docking clearance protocol, sound volume, spoken messages, music, wireframe graphics, graphics detail, field of view, joystick config, view keyboard config, back. The view keyboard config doesn't allow modification. (I'm only able to check this right now on my Mac, which doesn't appear to have a 1.91 build, so maybe there's something else in the 1.91 build? But I don't recall seeing it.)
Re: Struggling with keys to access all the stuff I need to use
Posted: Tue Nov 28, 2023 8:51 pm
by hiran
arquebus wrote: ↑Tue Nov 28, 2023 8:30 pm
phkb wrote: ↑Mon Nov 27, 2023 7:47 pm
In the keyboard config screen, where all keys are set.
My main screen and in-game game options has autosave, docking clearance protocol, sound volume, spoken messages, music, wireframe graphics, graphics detail, field of view, joystick config, view keyboard config, back. The view keyboard config doesn't allow modification. (I'm only able to check this right now on my Mac, which doesn't appear to have a 1.91 build, so maybe there's something else in the 1.91 build? But I don't recall seeing it.)
phkb has re-worked keyboard handling into 1.91, and we have not had any release since (note that all the builds on Github are tagged Pre-Release). Today's builds do not cover the Mac, that makes two reasons to not expect it there.
Here is how you can find it:
Re: Struggling with keys to access all the stuff I need to use
Posted: Tue Nov 28, 2023 8:54 pm
by phkb
arquebus wrote: ↑Tue Nov 28, 2023 8:30 pm
My main screen and in-game game options has autosave, docking clearance protocol, sound volume, spoken messages, music, wireframe graphics, graphics detail, field of view, joystick config, view keyboard config, back. The view keyboard config doesn't allow modification. (I'm only able to check this right now on my Mac, which doesn't appear to have a 1.91 build, so maybe there's something else in the 1.91 build? But I don't recall seeing it.)
Ah, you're on a Mac, I didn't realise. Unfortunately, we don't currently have a 1.91 build that includes the in game keyboard config. The most recent build we have for 1.91 predates the introduction of it, and we don't have any active Mac maintainers who can produce the package for you. Our Mac build environment is languishing at the moment.
hiran wrote: ↑Tue Nov 28, 2023 8:51 pm
we have not had any release since
Major release, that is. ie 1.92.
Re: Struggling with keys to access all the stuff I need to use
Posted: Tue Nov 28, 2023 8:58 pm
by hiran
phkb wrote: ↑Tue Nov 28, 2023 8:54 pm
hiran wrote: ↑Tue Nov 28, 2023 8:51 pm
we have not had any release since
Major release, that is. ie 1.92.
Interesting. I am open to adjust my wording but would like to have some consistency.
If you call 1.92 a major release, what would you name 2.0? And what do we call the artifacts that get built currently?
Re: Struggling with keys to access all the stuff I need to use
Posted: Tue Nov 28, 2023 9:20 pm
by phkb
hiran wrote: ↑Tue Nov 28, 2023 8:58 pm
If you call 1.92 a major release, what would you name 2.0? And what do we call the artifacts that get built currently?
In this environment, ie Oolite, my opinion is that 1.92 will be a "major" release, in that it will be the one published to the website, the version which will receive dev support, and the one we recommend to new players. And given how long it will have taken us to get there, it will definitely be a major release. My use of "major" reflects the content, rather than the number.
The artifacts being released against "Trunk", which currently all have a version of 1.91, are pre-release versions.
Re: Struggling with keys to access all the stuff I need to use
Posted: Tue Nov 28, 2023 9:47 pm
by hiran
phkb wrote: ↑Tue Nov 28, 2023 9:20 pm
hiran wrote: ↑Tue Nov 28, 2023 8:58 pm
If you call 1.92 a major release, what would you name 2.0? And what do we call the artifacts that get built currently?
In this environment, ie Oolite, my opinion is that 1.92 will be a "major" release, in that it will be the one published to the website, the version which will receive dev support, and the one we recommend to new players. And given how long it will have taken us to get there, it will definitely be a major release. My use of "major" reflects the content, rather than the number.
The artifacts being released against "Trunk", which currently all have a version of 1.91, are pre-release versions.
Aye, then a major release it shall be.
Re: Struggling with keys to access all the stuff I need to use
Posted: Wed Nov 29, 2023 6:42 pm
by arquebus
phkb wrote: ↑Tue Nov 28, 2023 8:54 pm
Ah, you're on a Mac, I didn't realise. Unfortunately, we don't currently have a 1.91 build that includes the in game keyboard config. The most recent build we have for 1.91 predates the introduction of it, and we don't have any active Mac maintainers who can produce the package for you. Our Mac build environment is languishing at the moment.
I'm not on a Mac, only on a Mac when I'm away from home - my gaming rig is a Windows PC.
I think the problem is that I had a really old build of 1.91. (I hate Github, it's so counterintuitive.)
Re: Struggling with keys to access all the stuff I need to use
Posted: Wed Nov 29, 2023 8:18 pm
by hiran
arquebus wrote: ↑Wed Nov 29, 2023 6:42 pm
I think the problem is that I had a really old build of 1.91. (I hate Github, it's so counterintuitive.)
I understand that a 1.91 is not comparable to a newer 1.91 or the latest 1.91 or even the older 1.91.
That's why I placed full version numbers on all artifacts that you can download. With that you can download them all, drop them in the same directory and still can tell one from the other.
If we had semantic versioning it would be even easier for humans to compare older and newer version. But well, we have what we have.
This (conter) intuitive stuff is not Github but the way we use it.