OpenMW 0.48.0

Anything related to PR, release planning and any other non-technical idea how to move the project forward should be discussed here.
User avatar
AnyOldName3
Posts: 2678
Joined: 26 Nov 2015, 03:25

Re: OpenMW 0.48.0

Post by AnyOldName3 »

FXN55 wrote: 01 Jul 2023, 20:51
AnyOldName3 wrote: 01 Jul 2023, 16:07 As I said, the location dumps are saved to changed with RC11
A little clarification please, in case I need it in the future. Where were the dumps stored and where are they now, with RC11?
They used to go in the same directory as your settings.cfg and openmw.log, but now they go into your temp directory. This wasn't my idea.
User avatar
FXN55
Posts: 38
Joined: 01 Dec 2022, 02:44

Re: OpenMW 0.48.0

Post by FXN55 »

AnyOldName3 wrote: 02 Jul 2023, 02:53
FXN55 wrote: 01 Jul 2023, 20:51
AnyOldName3 wrote: 01 Jul 2023, 16:07 As I said, the location dumps are saved to changed with RC11
A little clarification please, in case I need it in the future. Where were the dumps stored and where are they now, with RC11?
They used to go in the same directory as your settings.cfg and openmw.log, but now they go into your temp directory. This wasn't my idea.
As in the ./tmp directory? I'm still utilizing RC9, but unless the temp directory is a new one created with RC11, I assume you're referring to the one I mentioned.
User avatar
AnyOldName3
Posts: 2678
Joined: 26 Nov 2015, 03:25

Re: OpenMW 0.48.0

Post by AnyOldName3 »

Dumps go wherever the Win32 GetTempPath function says to put them. That could be one of several places according to https://learn.microsoft.com/en-us/windo ... ha#remarks (I did mention that this wasn't my idea). When a dump is created, the popup tells you where it's been saved to, otherwise you're going to have to go hunting.

If you're not on Windows, then you don't have crash dumps in the first place, but crash logs also now go to the temp directory. This is
The path supplied by the first environment variable found in the list TMPDIR, TMP, TEMP, TEMPDIR. If none of these are found, "/tmp", or, if macro __ANDROID__ is defined, "/data/local/tmp".
Did I mention that this wasn't my idea?
User avatar
FXN55
Posts: 38
Joined: 01 Dec 2022, 02:44

Re: OpenMW 0.48.0

Post by FXN55 »

AnyOldName3 wrote: 02 Jul 2023, 16:13Did I mention that this wasn't my idea?
Haha! Yeah, you kinda did. I take it you're none to pleased about it either.

Anyways, I'm on Linux, so no dumps for me. But, in my /tmp folder there are two OpenMW-CS related files: a text document, 'openmw-cs.pid', and a socket? file, 'org.openmw.OpenCS'. If you feel inclined, could you please enlighten me as to what I'm looking at? I'm assuming they're related to my 0.47 install.
User avatar
AnyOldName3
Posts: 2678
Joined: 26 Nov 2015, 03:25

Re: OpenMW 0.48.0

Post by AnyOldName3 »

The CS uses a socket for inter-process communication. I can't remember what that actually achieves, but it's normal and you can ignore it.
User avatar
FXN55
Posts: 38
Joined: 01 Dec 2022, 02:44

Re: OpenMW 0.48.0

Post by FXN55 »

As it turns out, I didn't ignore it and left that directory open in my file manager and noticed that those two files disappear/reappear when I close/open the CS, respectively. My assumption made me an ass! Hah! They weren't relevant to my 0.47 install.

That actually some interesting background process information, so, thanks, AnyOldName3.
User avatar
fraang
Posts: 23
Joined: 26 Apr 2013, 13:48

Re: OpenMW 0.48.0

Post by fraang »

Is Atahualpa still around to make a release video? I would like to help out by proof-reading. :D
User avatar
akortunov
Posts: 900
Joined: 13 Mar 2017, 13:49
Location: Samara, Russian Federation

Re: OpenMW 0.48.0

Post by akortunov »

Is there an update about what should be done for 0.48.0 release?
Dadinjo
Posts: 6
Joined: 03 Dec 2022, 21:11

Re: OpenMW 0.48.0

Post by Dadinjo »

When I turn Auto HDR option in Windows 11, the brightness settings doesn't do nothing.

Is that a bug or is there some other reason behind it?
User avatar
AnyOldName3
Posts: 2678
Joined: 26 Nov 2015, 03:25

Re: OpenMW 0.48.0

Post by AnyOldName3 »

You mean the gamma correction slider in the in-game options? It's not really a bug. Basically, that just asks the OS to set the gamma value for the current monitor, but the OS is free to ignore that, and it's not a particularly good way of controlling brightness in the first place. I'd guess that the Auto HDR option makes Windows start ignoring it. Instead, you should enable post-processing, and at least one of the built-in post-process shaders lets you adjust the brightness properly.
Post Reply