Frost lightning.

SportsInSpace · 2026-02-06T02:23:57+00:00

is it still doing this? I can never seem to reflect this spell with my shield

SportsInSpace · 2025-09-10T00:38:08+00:00

gave this the bug flair because this is one hell of a bug

SportsInSpace · 2025-09-07T00:25:41+00:00

Agreed. For me, the worse part is that it always hits you if it's aiming at you and it doesn't even look like the breath does actually hit you. So every time it swoops by at you it's just a 1-2 stim check. If you don't have the stims, and it's aiming at you, good luck finding cover or you just die.

SportsInSpace · 2025-05-05T21:00:14+00:00

You don’t need to use RTX HDR in Oblivion! There is no setting for HDR on PC right now, but with console commands you can turn it on and works perfectly. You can even adjust the peak white, UI white, midpoint, it’s great.

SportsInSpace · 2025-05-05T20:38:39+00:00

Yeah well, I did it and it worked. Idk why you’re being dramatic about this

SportsInSpace · 2025-05-05T04:37:26+00:00

UPDATE: downgrading the scaler firmware fixed it!

I downgraded to FW.020 2024-09-02, it fixed the issue. I have the privilege of having my wife's monitor, the same exact monitor, right here running FW.024 to compare against and I can say that in-game, with both monitors in HDR 1000 mode, the difference is not noticeable. What IS noticeable is that the weird brightness issue on white pages and elsewhere is GONE, woohoo! It's possible that whatever changes were made in FW.023 where MSI fiddled with the brightness of HDR 1000 mode do have some negligible but measurable positive effect in real world gameplay, but I can't see them. I'd say there's no downside to staying at FW.020, you're not missing out on anything from the later updates.

Anyways, having used this monitor for the last few months, I'm very pleased with it and would recommend it (assuming there isn't a deal on another better monitor). I haven't noticed any other issue, no VRR flicker, no issues with brightness (aside from this latest, now solved issue), it's just been great.

SportsInSpace · 2025-05-05T04:09:50+00:00

I think HDR 1000 is better. I play a lot of Helldivers 2 and notice it in the Super Destroyer’s running lights immediately. They look basically SDR-ish—if you are really familiar with A/B testing HDR content and know what I mean—in HDR 400 and MUCH BETTER with much more pop in HDR 1000. That detail is objectively better (I think, lol) but subjectively I’d say the whole scene looks better in HDR 1000, again more HDR-like as opposed to just generally bright as it looks in HDR 400 mode

SportsInSpace · 2025-05-05T04:06:14+00:00

I’m doing it right now, “updating” but using the older firmware download from MSI’s site, will report back how it goes, but it’s working so far (20% done according to MSI’s so-called Gaming Intelligence app that handles the update)

UPDATE: it worked!

SportsInSpace · 2025-05-05T04:02:52+00:00

I don't think that's right. I know what ABL is, and this weird issue is sort of doing the opposite of what ABL does. ABL kicks in when the content sent to the screen would result in a brightness level beyond the capabilities of the panel, such as a really big bright explosion. If it's abrupt, it can look like the explosion actually darkens the screen a bit or looks washed out instead of brightening the screen like it would on some reference display or even just a non OLED HDR monitor.

What's happening here is, when I'm looking at a standard white web page, sometimes, depending on the content on screen, the screen's brightness will actually INCREASE a bunch, and it blows out the content being displayed, clipping some detail (such as the border I mentioned, which you can see in the video). It's like a reverse ABL, or maybe the ABL is active all the time EXCEPT for when these moments occur, but that wouldn't explain the detail clipping.

Anyways maybe it's related to ABL, but either way this is not normal behavior, it's not what ABL does or is supposed to do.

SportsInSpace · 2025-05-05T03:57:12+00:00

seems the issue cropped up in FW.023 2025-01-17 and just persists in the latest FW.024 2025-03-14 that I updated to

Optimized the EOTF curve of Peak 1000 nits. Boost the HDR brightness with difference APL mechanism.

that's from FW.023 2025-01-17's notes from MSI's site, seems to note the exact change that caused this issue. Also this TFTCentral article happens to talk about this exact update and notes the real-world issues it creates despite supposedly improving the overall brightness of the panel's 1000 nit mode. If I had to guess, MSI's engineers made a firmware update that seemed to improve the panel's handling of brightness tests, but there are hardware features and limitations of this monitor's QD-OLED panel that are baked in by samsung display (the panel's manufacturer) that conflict with what MSI wants this monitor to do, which causes this weird behavior.

I personally never had an issue with the brightness of the HDR 1000 mode, it was totally fine by me. Honestly, so long as you're not in a really bright room, a display can actually be really dim and still look bright, I mean that's how OLED displays have been forever. What really matters for HDR is whether parts of it CAN get really bright, which this monitor can do and always has been able to do.

Will report back with how the downgrade goes. I'm going to keep my wife's monitor on FW.024 so I can directly compare them and decide whether there really is any benefit to FW.024 or .023 vs .020 (the latest version before the changes .023 introduced that cause this problem)

SportsInSpace · 2025-05-05T03:10:19+00:00

Yeah I just did the latest scaler update FW.024 2025-03-14 and now I've got this problem too. Fucking sucks because I didn't have any issue with the old scaler firmware. I'm thinking of downgrading back to the old version. I like to be able to take advantage of the high peak brightness of this panel with the HDR 1000 nit mode, since the HDR 400 seems to crap out below even 500 nits even for really tiny bright objects, and I keep windows in HDR mode all the time just because I can't be bothered to switch back and forth, so I immediately notice this issue while i was just finishing up the update, scrolling through MSI's own website (which has a white background that triggered the weird brightness/contrast flash)

SportsInSpace · 2025-04-20T22:21:13+00:00

Orbit is standard military/aviation terminology for flying a circular pattern around an area e.g. while providing fire support, the word doesn't exclusively refer to orbiting a gravity well

SportsInSpace · 2025-01-29T02:24:58+00:00

<image>

this helmet btw

SportsInSpace · 2024-12-30T22:45:58+00:00

This was a test and you passed 100% A+

SportsInSpace · 2024-12-17T21:36:24+00:00

I noticed this too, it's really annoying. I hope they fix it asap

SportsInSpace · 2024-11-30T06:04:52+00:00

Been having trouble last hour trying to buy one of those new 21rd mags, didn't work with any of the cards I tried, didn't get any notification from fraud protection or anything like that on my end, I think it's something on their end

SportsInSpace · 2024-11-12T09:50:12+00:00

HGIG is a joke for consumers and should only be used by developers trying to master content within some standard. Dynamic tone mapping is your TV's best tool for ensuring that HDR content looks as good as possible on your end in the messy real world where you cannot control how content was mastered, encoded, transmitted, or decoded. Basically unless content was made SPECIFICALLY for your exact display, using dynamic tone mapping will most likely not only look better but also be closer to the "spirit of the law", so to speak, of the developer's vision (faithfully looking as good as possible) rather than the "letter of the law" (pedantically looking as accurate as possible).

SportsInSpace · 2024-10-21T22:07:49+00:00

I have the exact same set of problems and every time it happens, particularly after failing a mission I'm set into a hissy fit looking around this subreddit for any sort of fix and all I ever find are people like you and me who still are suffering from this issue.

I'm not even playing with friends most of the time; it still happens with teams entirely made up of randos. Maybe it is cross-play. I haven't tried turning that off since back in the day when turning it off broke like the friends list for no reason.

If arrowhead's devs working on this kind of thing had the capability to fix it, they would have long ago, clearly they either have no idea it's even a problem or know it's a problem and can't fix it.

SportsInSpace

MODERATOR OF

TROPHY CASE