Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.

Topic on User talk:Rose

D0x360 (talkcontribs)

I made a couple edits in Horizon ZD and they were removed. First and most importantly is the games massive memory leak. On 3 systems (2 intel, one Ryzen 3900) that all had 32 gigs of DDR4 the game went from 10% system memory use to 20, 30 and so on over 2 hours until it hit 68% of system memory usage. All memory was free'd upon exiting the game. There is also evidence that it's causing a memory leak on the GPU end. The game uses 98% of the vram on a 2080ti after 2 hours and 8 99% on a 5700xt.

Next is HDR... the image displayed is NOT HDR. It doesn't reach the proper levels to meet the criteria for HDR but even forgetting that fact the game is running with 8 bit color when HDR is enabled and it should be 10bit. I can directly compare HDR with the ps4 version and the colors of completely wrong when HDR is enabled in the PC version. It's like a different game.

Rose (talkcontribs)

Hi. It was not me that undid the edits but I had supported the decision on the wiki Discord.

The statements looked like a forum post - the style was very informal ("mess up", "apparently", etc) and they addressed the reader directly, which is against the guidelines. Moreover, there was a lot of uncertainty from the use of expressions like "more testing is needed", "seems" and "appears". Coupled with the complete lack of references and explanations for what a memory leak is or how one can benefit from the knowledge, it definitely had no place on the wiki in that form.

Shadowstealer7 improved on it by describing the issue as high memory usage, which is easier to understand and harder to contest, especially when backed with references.

As for HDR, there is nothing in the guidelines that suggests it should be compared to that of consoles before setting it either way. It is simply defined as "Support for expanded color space", which was further supported by my screenshots within the reference comment following your questioning of it.

Aemony (talkcontribs)

> Next is HDR... the image displayed is NOT HDR. It doesn't reach the proper levels to meet the criteria for HDR

What criteria are those? I took a couple of screenshots previously today and used HDR + WCG Image Viewer to visualize a heatmap and, uh... I don't see whatever you're seeing.

  • Original image (some details are lost in the HDR-to-SDR conversion -- as seen when compared to the heatmap)
  • Heatmap (blue-green-orange is basically lower than 300 nits)
  • SDR as grayscale

Beyond that, yeah, it sucks that the game doesn't make use of 10-bit at least. Preferably all HDR games should render in 16-bit and then just tonemap it down, but woe betide us. :|

D0x360 (talkcontribs)

First high memory use is different from a memory leak. I don't know how you would like me to create a reference for it since you need tools to test for said leak. I tested on multiple machines multiple times and every single time a memory leak was verified.

As for HDR I'm not comparing it to the console version whatsoever. It doesn't meet the HDR spec in terms of nits. Again tools are needed for testing. I'm using professional calibration tool, a device that sits in front of the display. The display used first was a 65 inch LG CX OLED and the second was a pc monitor, also an LG OLED (IPS). As a side note LG makes OLED panels for essentially all manufacturers except samsung. The only difference is software that runs the panel and LG is considered the best.

Regardless, it's obvious that there is no way I can "win" here so I will stop trying. That doesn't change the fact that I'm right and even the patch today did not fix either issue.

I understand people might not understand what a memory leak means, and this is not the place to explain but acknowledging it's existence would likely drive the user to search memory leak and they would find a layman's explanation on the first page of Google, bing and duckduckgo.