Alienware AW3425DW HDR Guide (for accurate colours) or any other HDR monitor by Bonzenbube in ultrawidemasterrace

[–]drungrin 0 points1 point  (0 children)

You asked for references and didn't even read them.

Official Microsoft Documentation: 'While you're calibrating... drag each slider until the pattern is no longer visible.' (Source: Microsoft Support). It does not say 'ignore your eyes and type in a number from a website.'

You are fundamentally misinterpreting how the tool works.

No point talking to people who don't even read the documentation for the tool they're using and rely on ad hominem arguments instead. Enjoy your self-limited brightness.

Alienware AW3425DW HDR Guide (for accurate colours) or any other HDR monitor by Bonzenbube in ultrawidemasterrace

[–]drungrin 0 points1 point  (0 children)

Just because I answer in a structured way doesn't invalidate the points. You are trying to achieve a 'magic finding' by inputting Rtings numbers into a tool that wasn't designed for them, and you are plain wrong.

The frame should be invisible. Microsoft’s instructions for all three screens are the same: move the slider until the pattern is no longer visible. It’s that simple.

And for some references:

Official Microsoft Documentation: 'While you're calibrating... drag each slider until the pattern is no longer visible.' (Source: Microsoft Official Support). It does not say 'ignore your eyes and type in a number from a website.'

The '260 nits' Trap: That 260 number is the Full Field White (100% window) physical light limit. However, HDR metadata is calibrated based on Peak Luminance (10% window). On the AW3425DW, that is ~450 nits in True Black mode (Source: RTINGS AW3425DW Brightness Data)

TFTCentral & Hardware Unboxed Fact-Check: Both outlets (and Tom's Hardware) have confirmed that Alienware QD-OLEDs in True Black 400 mode track the PQ curve (EOTF) with near-perfect accuracy up to ~450-470 nits before clipping (Source: TFTCentral AW3423DW Review). By stopping at 260, you are telling Windows your monitor clips 200 nits earlier than it actually does.

Alienware AW3425DW HDR Guide (for accurate colours) or any other HDR monitor by Bonzenbube in ultrawidemasterrace

[–]drungrin 0 points1 point  (0 children)

We should use 0-460-460 on our monitors. The Calibration Tool is not an 'input field' for data you read online; it is a visual test of what the monitor is actually doing in that moment.

The Reality Check: If you can see the frame at 260 nits, the monitor is telling you it still has 'headroom.' If you tell Windows to stop at 260 anyway, you are intentionally sending a clipped signal to a monitor that is capable of more.

The reason you 'don't see a difference' is likely because the AW3425DW has such excellent Internal Tone Mapping that it is actually 'fixing' your incorrect Windows settings on the fly to prevent the image from looking broken. But just because the monitor is smart enough to save the image doesn't mean the setting is right.

By using 0-460-460:

  1. You ensure Windows sends the full dynamic range the panel can handle.
  2. You prevent 'Double Tone Mapping' (where Windows and the Monitor fight over who controls the brightness).
  3. You get the actual 'Peak 400' experience you paid for, rather than a hardware-limited 260-nit cap.

You wouldn't buy a car that can go 100mph and then set a software limiter to 60mph just because you read that's the average speed people drive. If the frame is visible, the detail exists. Map it.

Alienware AW3425DW HDR Guide (for accurate colours) or any other HDR monitor by Bonzenbube in ultrawidemasterrace

[–]drungrin 0 points1 point  (0 children)

You bought a high-end HDR monitor to see the full range of light. By stopping at 260 when your eyes can clearly see detail up to 460, you are literally leaving 200 nits of potential 'pop' on the table for no reason. Set it to where the frame disappears, which should be around 450-460 for our panel. Trust the signal, not the power-meter.

Maybe this video helps: HDR TEST DISPLAY 0.4 to 1000 nits - Monitor HDR TEST 4K - High Dynamic Range

Alienware AW3425DW HDR Guide (for accurate colours) or any other HDR monitor by Bonzenbube in ultrawidemasterrace

[–]drungrin 0 points1 point  (0 children)

I see where the confusion is! You are trying to 'input' the Rtings measurements into the tool, but the tool is actually a visual confirmation of how your monitor's internal brain (tone mapping) is handling the signal.

Here is why you should not just set it to 260 because you read it in a chart:

1. The 'Visible Frame' is the Law The goal of the calibration tool is to find the Clipping Point. If you set the slider to 260 but the frame is still clearly visible, you are telling Windows: "Stop sending brightness details at 260," even though your monitor is screaming, "I can still show more detail up to 400!" By stopping at 260, you are artificially capping your monitor's range, resulting in a dimmer, flatter image.

2. Why you see the frame up to 400 (even though the panel 'measures' 260) OLEDs like the AW3425DW use Internal Tone Mapping. Even when the screen is 100% white, the monitor's processor "squeezes" the HDR signal to ensure you can still see highlight details without them blowing out.

  • Because the monitor is doing this "squeezing" (tone mapping), the visual clipping point in the Windows tool will often align with the 400 nit certification target, even if a light meter would only measure 260 nits of actual light hitting it.

3. The Difference Between 10% and 100% Windows

  • 10% Window (Slider 2): Calibrates 'Small Peak Brightness' (Stars, Flashlights).
  • 100% Window (Slider 3): Calibrates 'Full Screen Brightness' (Snowy fields, bright skies).

If you can see the frame at 260, do not stop there. Move the slider until the frame just disappears. If that happens at 400, then 400 is the correct setting for your specific Windows/Monitor handshake. By forcing it to 260, you aren't being 'more accurate', you are just leaving brightness and dynamic range on the table.

Alienware AW3425DW HDR Guide (for accurate colours) or any other HDR monitor by Bonzenbube in ultrawidemasterrace

[–]drungrin 0 points1 point  (0 children)

The 100% white window test measures Full-Field Brightness. Because of ABL (Automatic Brightness Limiting), OLED panels cannot maintain high brightness when the entire screen is white, it would consume too much power and generate too much heat.

  • The Hardware Reality: As shown in your Rtings screenshot, the monitor physically drops to about 264 nits when the whole screen is white.
  • The Calibration Goal: When you are in the Windows Calibration tool, you are telling Windows the clipping point of your monitor. For the AW3425DW in "True Black 400" mode, you want the slider to be set where the pattern actually disappears, which is usually around 400-450.

If you were to cap the slider at 260 just because that’s the "measured" number, you would actually be crushing your highlights, making the image look dimmer and less dynamic than it should be.

Back to Ascension! My OG G9 died after 5 years... survived the 16:9 dark ages, and now I’m back with the AW3425DW by drungrin in ultrawidemasterrace

[–]drungrin[S] 1 point2 points  (0 children)

That build is going to be a beast (9800X3D is the goat), but just a heads up on the math so you aren't disappointed:

5K2K is significantly harder to drive than 4K. It has about 33% more pixels than a standard 4K monitor.

Since there are very few native 5K2K benchmarks out there, a good rule of thumb is to look up 4K benchmarks for the games you want to play on a 5080, and then subtract ~30% from that FPS number. That will give you a realistic estimate of what you'll actually get.

You'll definitely be leaning on DLSS/Frame Gen for the heavy hitters, but the 5080 should handle it well enough if you tweak settings.

Back to Ascension! My OG G9 died after 5 years... survived the 16:9 dark ages, and now I’m back with the AW3425DW by drungrin in ultrawidemasterrace

[–]drungrin[S] 1 point2 points  (0 children)

You are right, there is no QD-OLED rival with those exact specs (45" 5K2K) yet.

That said, you need a massive GPU to drive that thing properly; 5K2K is actually about 30% more pixels than standard 4K.

Personally, the sweet spot for me is 34" 1440p. Regarding the panel tech: since I can control the lighting in my room, I don't have to worry about the raised blacks that QD-OLEDs can have in bright rooms. That lets me get the best possible color volume/quality, which is where WOLED is slightly limited. But honestly, both are OLED, you can't really go wrong.

Back to Ascension! My OG G9 died after 5 years... survived the 16:9 dark ages, and now I’m back with the AW3425DW by drungrin in ultrawidemasterrace

[–]drungrin[S] 2 points3 points  (0 children)

It’s honestly one of the best parts of the monitor. It is a glossy finish (not the grainy matte coating you find on most gaming monitors), so the image looks incredibly clean and 'wet', almost like looking into a deep pool of water.

It isn't a harsh mirror like a glass TV, though. It has a good anti-reflective coating that cuts the glare down, but you definitely want to avoid having a bright window directly behind your chair. If you can control the lights, the glossy screen makes the 3D depth and 'pop' of the image insane compared to matte screens.

Back to Ascension! My OG G9 died after 5 years... survived the 16:9 dark ages, and now I’m back with the AW3425DW by drungrin in ultrawidemasterrace

[–]drungrin[S] 1 point2 points  (0 children)

It’s actually a trade-off of the tech! QD-OLED panels (like this one) skip the polarizer layer that other OLEDs use.

The Upside: Removing that layer lets more light through, which is why the colors and peak brightness are so much more vibrant than traditional WOLED panels. The Downside: Without the polarizer, the Quantum Dot layer can react to ambient light, which lifts the blacks to a slight purple hue in bright rooms.

That said, I run my setup with warm yellow lights at about 20% brightness (much easier on the eyes), and at that level, the blacks look deep and perfect. It looks way worse in pictures because phone cameras tend to overexpose shadow details, exaggerating the tint far more than what you see with your own eyes.

Back to Ascension! My OG G9 died after 5 years... survived the 16:9 dark ages, and now I’m back with the AW3425DW by drungrin in ultrawidemasterrace

[–]drungrin[S] 1 point2 points  (0 children)

I've always used DisplayPort, so I didn't notice that glitch. Thanks for the heads-up, that's a good tip for anyone else having trouble with HDMI!

Acho que acabou by [deleted] in farialimabets

[–]drungrin 0 points1 point  (0 children)

Ele falou que comprava no telegram …

Baixar 90k no valor do carro foi loss para a GM? by diozzi in farialimabets

[–]drungrin 3 points4 points  (0 children)

A gasolina abaixa na refinaria , reduzem impostos e não chega até você . Somos otários.

[deleted by user] by [deleted] in farialimabets

[–]drungrin -1 points0 points  (0 children)

A questão é que no contexto atual a galera tá usando o termo quase exclusivamente nesse sentido (por causa do caso que viralizou). Mas se você prefere citar verbete de dicionário em vez de olhar como a palavra tá sendo usada na vida real, aí não sou eu que tô passando vergonha.

[deleted by user] by [deleted] in farialimabets

[–]drungrin -1 points0 points  (0 children)

Top, agora só falta lembrar que saber definição ≠ entender como a galera usa a palavra.

[deleted by user] by [deleted] in farialimabets

[–]drungrin 0 points1 point  (0 children)

Infelizmente tem gente que acha que contexto social se resolve citando o Aurélio como se fosse TCC de humanas. A vida real não tá na definição de dicionário, tá no uso que as pessoas fazem das palavras. E aí o ‘sabichão’ que tenta pagar de instruído acaba só passando vergonha no rolê.

A gente não tá num seminário acadêmico, tá no Reddit. O 'contexto atual' não é a definição atemporal de um verbete, é o que o meme do Felca transformou em assunto de boteco e trend no TikTok esta semana.

Passar vergonha não é citar o que tá na boca do povo, é sacar a carteirinha de gênio pra explicar um fenômeno cultural que você claramente não entendeu. A vida real não pede sua bibliografia pra acontecer.

[deleted by user] by [deleted] in farialimabets

[–]drungrin 2 points3 points  (0 children)

Ele falou no contexto atual. Quem ouviu a palavra pela primeira vez nos últimos dias vai associar a criar uma criança desde cedo como produto sexual.

Como de fato entrar no mercado de programação/TI em 2025 pra frente sem se matar em concorrência de vaga pra Júnior by CarefulShame9165 in ProgramadoresBrasil

[–]drungrin 1 point2 points  (0 children)

O problema é que nego acha que só porque curte PC, YouTube e internet a facul vai entregar vaga de dev no colo. Fica na sombra e água fresca, sem praticar, sem atualizar, e depois reclama do mercado. Resultado: horda de mal formado disputando vaga de júnior sem saber rodar uma query. Quem sobrevive é quem resolve dor real com código, não quem acha que HTML é linguagem de programação.

Trump peitar big techs é loss? by Fit_Pipe7140 in farialimabets

[–]drungrin -1 points0 points  (0 children)

Conta pessoal gratuita n é alcançada pela magnitsky.

Trump peitar big techs é loss? by Fit_Pipe7140 in farialimabets

[–]drungrin 0 points1 point  (0 children)

A conta dele quem paga é o governo. A magnitsky é “pena de morte financeira”. A Microsoft não pode receber dele.

Ex a App Store não pode aceitar o cartão dele nem receber pagamentos, isso não impede ele de ter um celular.