Topic on User talk:Aemony
I'm new to this but I will have it down soon enough. Having some health issues that are slowing me down. Anyways... I confirmed the memory leak on 3 different systems (all with different hardware and tested with multiple driver revisions on a fresh install of win10) using tools designed specifically to look for them. Also the fact that every system showed over 70% memory use after 5 hours on a system with 64 gigs of memory and no other major tasks running is good reason to investigate hence the use of tools and why I'm so adamant about it. I was a programmer and behavior is consistent with unreleased memory. I agree it's inconsistent but likely not as inconsistent as you seem to believe. It's the leak that causes attempts to read or write to non existent address space causing a crash. It also causes performance issues because despite already loading data it needs into memory the leak makes it invisible to the game (at times) so it has to load the same data twice in a row.
The point of bringing it up is to draw attention so hopefully the developer fixes it. Otherwise crashes will continue. Also if users know about it then they can restart the game every hour or so to help avoid crashes and/or performance issues.
True HDR... It's determined by the measurements of contrast, nits and color. This game doesn't meet the criteria for HDR because it's color space is 8 bit and their are some major inaccuracies with said color (at times) which isn't the main reason. The main and defining reason is nits. It doesn't meet the criteria for the HDR spec.