How do people get past FH101 and FH201/FH205 errors on Linux?

November 2, 2026 5 answers
Asked by LagLoft

Some players are seeing CPU core check errors or GPU not supported errors even on systems that should be able to run the game. There are reports that these checks can be bypassed with launch options on Linux by changing what the game thinks the hardware looks like.

What launch settings are people using, and what should someone expect in terms of performance or limitations after getting past the checks?

Answers

TurboGlyph

The basic idea is that these errors look like gatekeeping checks, not true capability checks. One workaround is to make Wine report more logical processors than the machine really has, which can satisfy the CPU-side check without actually creating fake cores.

For a 4-core system, the common trick is to repeat some core IDs in the topology mapping so the game sees 6 logical processors. For the GPU side, the launch options usually force a higher feature level and enable a few VKD3D and RADV flags that help the game get past the D3D12 feature test on older Radeon cards.

If you have a 6-core CPU, the CPU workaround may not be needed at all, and only the graphics-related launch flags are used. Just keep expectations realistic. Getting past the launcher check does not mean the game will run well everywhere. The open-world driving parts may work fine at low settings, while dense city areas can still hit performance hard.

CtrlMosaic:

That makes sense. So the system check is mostly separate from actual in-game performance, and once it boots the real bottleneck is still the hardware itself.

Reply to this answer
QuietSpawn

If someone is trying this, the cleanest way is to add the launch string in the game’s properties and test one change at a time if needed. The CPU workaround and GPU workaround are solving different problems, so it helps to know which error you are actually hitting.

A 4-core machine may need the processor remap, while a 6-core machine can often skip that part. The graphics flags are the more important piece for older AMD cards in this case, because the game is checking for features that Vulkan translation layers can sometimes expose even when the original hardware path would look unsupported.

One caution is that this is not a magic fix. People should expect to lower settings, possibly run at 720p or similar, and accept that frame times may still be rough in busy areas. It sounds like it can be playable, but not exactly smooth on every scene.

LagLoft:

Good point on testing one part at a time. It sounds like the CPU trick is just to satisfy the check, while the GPU flags are what actually matter for getting the game to start.

Reply to this answer
NimbleRaid

What stands out here is that the game seems to care more about reported hardware labels than raw ability. That is why these launch options work at all. They are not adding power, they are changing the answer the game gets when it asks questions it should probably not be asking.

For older Polaris cards, the D3D12 feature-level override plus the VKD3D and RADV settings seem to be the key part. On the CPU side, the remapping trick is basically a compatibility lie that keeps the game from rejecting a 4-core chip too early.

The downside is that this is very configuration-sensitive. Driver version, Proton or Wine version, and the exact CPU and GPU all matter. If someone copies the settings and still gets trouble, the next step is usually to check whether the graphics stack is current, because these workarounds depend on Mesa and VKD3D exposing the right features.

StackSprint:

That last part is worth saying. A lot of these fixes only work if the Vulkan stack is already in decent shape, so outdated drivers can make the whole thing look broken when it is really the translation layer that is falling short.

Reply to this answer
OrbitFumble

I would treat the 4-core CPU workaround as a last resort rather than the first thing to rely on. It can get the check to pass, but it does not change the fact that a low-core CPU can still struggle once the game is loaded, especially in heavier areas.

The more useful part for many people is the GPU compatibility override. If the card can actually handle the workload through VKD3D-Proton and the driver stack, the game may run better than the error message suggests. That said, there is a real difference between booting and being comfortable to play.

So the short version is, yes, the launch options can help. No, they do not guarantee a good experience. Think of them as a way to get the game to stop rejecting the machine, not a promise that performance will match newer hardware.

HexaJolt:

Pretty much. Bypassing the check gets you into the game, but the actual frame rate still depends on the old parts doing old-part things.

Reply to this answer
PixelMarrow

There are really two separate questions here. First, can the game be made to launch. Second, can the machine handle it once it launches. The launch options mainly answer the first one.

For a 4-core system, the processor mapping trick makes Wine report six logical processors by reusing existing core IDs. For an older Radeon card, the feature-level and driver flags make the graphics stack present a more capable D3D12 environment to the game. If both checks are the only thing blocking startup, that is enough to get past the errors.

After that, the usual tradeoff applies. Lower settings, lower resolution, and expect the city or dense traffic areas to be the worst case. If someone is on hardware like an older quad-core and RX 570 class card, it may be usable, but it is not going to feel like a modern high-end setup.

LagLoft:

That clears it up. The key takeaway seems to be that the fixes are for the launcher checks, not a performance boost, so expectations should stay pretty modest.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions