Vik

OLED is practically contingent on HDR colour space for optimal experience. You wouldn’t want to limit yourself to SDR on that type of display.

Madison I think

QuickSync also makes it a great encoder asic, though it may be worth holding out for an even smaller GPU.

I seem to remember there was some antialiasing setting

Can you show us which in-game settings you have available? Has been a very long time since I last played FC5

I’m sorry to hear that. Does this system only have access to this single display? Did you use a kernel command to modify your EDID? If so, are you able to temporarily modify your grub before booting into the OS?

Archwiki references a [@<refresh>] (presumably denoted as [@144] for something like 144Hz) property, hopefully that’s all you should need to define, though I’m not sure if you’ll need to manually recalculate vertical and horz timings or something.

Maybe this can help fill in any gaps

https://tomverbeure.github.io/video_timings_calculator

You want to look into modifying your display EDID.

I don’t believe there’s a GUI for this on Linux but this post referencing the Archwiki might come in handy

https://foosel.net/til/how-to-override-the-edid-data-of-a-monitor-under-linux/

naw unfortunately not. It’s kind of crazy that they nestle each individual engine within a wrapper. I’m not sure of this brings the api level to d3d11, or if they had to work to bring each engine up for that. Somewhat explains why MCC as a whole was so difficult to back port improvements to, like configurable FOV and weapon model placements, frame rate unlocking and interpolation, custom keybinds, missing assets and such.

it’s kind of interesting seeing the player models rendered in UE when you use the customisation menus; everything looks so glossy and odd.

no you’re cool

The ‘wrapper’ around each of the individual halo engines is in unreal and is arguably the wost thing about the collection from a reliability standpoint.

That said, they’d definitely be able to find people suited for the work, provided said people agent already scared away by stories of the work culture at 343i / MS

okay cool but it works with a usermode module in Linux for now, and will probably continue to do so.

slipspace was just an iteration of blam with a marketing name slapped on top, and cost them dearly in any case :/

O’Connor, Ross, Wolfkill, and several others.

yeah chances are they’ll stick with EAC and continue to be friendly towards the steam deck (and indirectly towards desktop Linux as a whole)

It means a couple things I guess.

It’ll probably still run bad thanks to associated technologies like nanite (see relevant threat interactive video).

They’re not longer constrained by the technical debt of blam engine.

they’re trying to ensure an acceptable UX with their browser.

I suppose the root of the issue is developers specifically targeting and testing on chrome.

I don’t understand how this would make Firefox look bad unless you’re pointing at the dire browser share situation.

it do be that way :(

Their latest microcode update from 7 days ago was declared as final. Time will tell about the efficacy of the most recent fixes.

Unfortunately it may only be available via board partners as beta BIOS updates at present.

Isn’t this the kernel driver included by default?