new-lg4ff VS windows-driver-docs

I found that the above comes in two variants, PS/PC and XBOX/PC. While the former is currently supported via an external driver (new-lg4ff), the latter has native kernel support. While I do expect to have a smoother experience with the native module, the custom driver claims to have a richer feature set than the native hid-logitech module (differences).

Go to the game settings and adjust the FF levels. (Except if you're on Linux, you'll also need the experimental kernel module, as the stock one has only rudimentary FF support).

The people Behind the logitech driver new-lg4ff most logitech wheels work fantastic now.

On Linux there's libratbag/Piper for keyboards and mice and new-lg4ff/Oversteer for steering wheels, if you want to take a look at how they do some things or straight up just fork them and port to Windows.

You want this for your G29 if you haven't already installed it. I will admit that sim racing is a blind spot in Proton's support, but this should at least fix some of the wheel-related problems.

In my opinion the best (community) support at the moment is from Logitech. I have one and it works very well with the new-lg4ff driver. I know the creator, u/berarma, and I know that the support is active. If you need an opinion on models, the G27 (second hand) or the G29 work great on Linux with new-lg4ff.

Assuming the dump file provided is representative, have you gone through the steps in the Resolution and Remarks sections on this page? The sub error from the bugcheck is:

Edit: Apparently there is a new API that simplifies this process (docs)

I opened on issue on https://github.com/MicrosoftDocs/windows-driver-docs/issues/3289

This is pretty technical, but it can help point you at what's causing this issue. https://github.com/MicrosoftDocs/windows-driver-docs/blob/staging/windows-driver-docs-pr/debugger/bug-check-0xa0--internal-power-error.md

I thought ChangeDisplaySettingsEx and EnumDisplaySettings was superseded by SetDisplayConfig and QueryDisplayConfig, respectively? https://github.com/MicrosoftDocs/windows-driver-docs/blob/st... calls ChangeDisplaySettingsEx "legacy API".

From my experience, changing topology using SetDisplayConfig() is straightforward.

The biggest thing with digital signatures is that getting one trusted by Windows means entertaining a racket enabled by Microsoft.

There are two types of code signing certificates: regular, and EV. With regular certificates, all you get is effectively a way to carry your antivirus-based reputation with you as you continue to sign new binaries with it. At first sight, Windows will still throw up smartscreen warnings about it being potentially dangerous, until it's seen the certificate enough to trust it for new binaries.

With EV certificates, everything is smooth sailing - only if actual malware is reported does your certificate get slammed by antivirus reputation, otherwise you can sign anything and it'll instantly bypass all AV software and Windows smartscreen prompts.

The issue with getting either of these is that absolute cheapest one you can get is $59 a year for 3 years via a reseller[0] of Sectigo certificates, and that is only for regular code signing. If you want an EV certificate, it's going to be $219 a year for 3 years at the minimum via the same reseller (do not try to go through the regular channels or you'll likely be paying 2x-3x more[1]).

Thankfully Microsoft is aware of these concerns[2,3] and there is a potential solution coming up called Azure Code Signing[4] however no new public information has been released since that video went up.

0: https://codesigncert.com/brand (this is just the cheapest site I've found - I am not affiliated with them beyond being a customer)

1: https://sectigo.com/ssl-certificates-tls/code-signing

2: https://github.com/MicrosoftDocs/windows-driver-docs/issues/...

3: https://github.com/MicrosoftDocs/windows-driver-docs/issues/...

4: https://youtu.be/Wi-4WdpKm5E?t=530

Okay, apparently this error is very new, here someone's asking about it. Unfortunately it doesn't give any additional information.