FlyDigi Vader 4 Pro now working for me. A few things that are needed:

• Controller must be in PC/Dinput mode, blue led (hold O + A to switch)
• Don’t enable the built in gyro mode in the Windows app as it might cause problems
• Udev rule:

KERNEL=="hidraw*", ATTRS{idVendor}=="04b4", ATTRS{idProduct}=="2412", MODE="0666"

(get the idVendor and idProduct from lsusb if you have a different controller)

• Some (patched) versions of xpad/xpadneo might conflict with it. If you’re using the stock versions it should be okay.
• Your user might need to be in the input group.

One last thing that may or may not be needed is that I installed the SpaceStation app on Windows to test some things. It started working after that but I can’t recall if I force reloaded the udev rule so it might have just been the reboot that fixed it.

Anyway, now I have gyro + all extra buttons working with Steam Input.

See here for further discussion: https://github.com/paroj/xpad/pull/268

They are violating the GPL by not including source code for their modifications. I’m not sure about using the word “stolen” in this context though, but I suppose language evolves.

A dick move in any case.

Just having VSync on can introduce frame pacing issues. It’s just not an issue if you can maintain the monitor refresh rate consistently, of course. And you can turn it off altogether if you can tolerate tearing.

But that’s the main benefit of VRR for me which is frame pacing at sub monitor refresh rate, rather than latency reduction compared to the various types of VSync.

Triple buffering. Needs to be implemented by the game, not by the OS. Provides maximum frame rate and no tearing with minimal latency.

Vulkan mailbox mode is pretty much this and doesn’t require game support (can be forced on with environment variables if it’s not already being used). And since almost everything is Vulkan on Linux these days, one way or another, that covers most games (might be compatibility issues in rare cases).

Plasma wayland has an automatic mode which should at least turn off VRR during desktop usage, as long as the application window isn’t fullscreen. A hacky way that can help when VRR is active is to increase the minimum frequency and kick into LFC more readily, by creating a custom EDID (you can also do a sysfs edit historically but I think that’s AMD only).

That’s only really viable if you have a high refresh rate monitor with a large range. I’ve found that 120hz may not be enough (since you may end up with gaps where VRR doesn’t work if the range is too narrow), which is of course the most common OLED TV refresh rate. In my experience a minimum of >=54hz minimises the flicker, but that may vary with the display.

There’s also an issue with cursors where moving the mouse can make the refresh jump to the maximum. It only affects desktop usage and some games (RTS and the like, not usually FPS camera usage). There are fixes coming for this with Plasma I believe, but I’m not sure about Gnome. Forcing a software cursor may help, as others have indicated.

Some users are reporting gyro working for some of the controllers. It’s early days anyway (I tested it and it’s all broken for me on the Vader 4 Pro).

I have the Vader 4 and there are some reports of gyro working too. It’s no replacement for my steam controller(s) due to the lack of touchpads, but it’s probably the highest quality conventional controller I’ve owned in terms of build quality, so good to see support.

Are you using the handheld/deck image? If so, see if you can replicate the issue in desktop mode as it might be a game mode specific issue. I’d also test a different keyboard and gamepad, if you have easy access to those.

It’s just saying it’s not supported, not that it doesn’t work. Depending on your country, I doubt that warranty voiding claim is enforceable either.

Also, if you get one of their units that has an ARM chip inside instead of an intel one, there is basically no chance you’re ever going to be able to use anything other than the software that they have by default.

Their x86 models are fine as you imply, just avoid ARM and you can install any OS you want.

You could recommend droidify which is a bit more straightforward as a client.

A basic FIFO scheduler from what I understand, which isn’t ideal.

It’s mainly Linux Unplugged where that stuff leaks into it. I haven’t heard it on “self hosted” very much.

• Removed sparse buffer usage that was introduced in DXVK 2.6. This caused all sorts of driver issues that would cause hangs and instability on AMD Vega GPUs and others. (PR #4763) Note: This may increase peak memory usage in some games again.

On this change, it seems it only affects pre-RDNA1 AMD GPUs and so the feature should continue to work on other GPUs. See: https://github.com/doitsujin/dxvk/pull/4763/

The proton logs are fairly inscrutable, and probably aren’t helpful if it’s a driver issue.

There’s a big discussion on the Proton issue tracker that may include your problem.

Looking at the specs:

Positives:

• Higher refresh rate (with VRR) and slightly larger screen (so smaller bezel), higher resolution.
• Hall effect joysticks
• Possibly better speakers

Negatives:

• IPS instead of OLED display (but a good quality one at least)
• Only one touchpad, and its tiny
• Seems to be only 2 back buttons instead of 4 on the deck

Neutral / unknown:

• Long term support compared to official Valve devices (hopefully Valve is handling this for third party devices similar to Bazzite).
• Price seems to be the similar to the Deck OLED model (depending on region)

Going by the Verge review of the Windows version of the hardware, it seems the SOC of this isn’t that powerful (and may even be outperformed by the Deck when rendering at 720p on both systems with some games): https://www.theverge.com/reviews/617613/lenovo-legion-go-s-review-feels-good-plays-bad

They did see framerates improve with Bazzite, so presumably the Steam OS release will have similar improvements.

Calibre is used as a server all the time, see calibre-web.

calibre-web is technically not Calibre and is written and maintained by different people, although it does use the Calibre database (and I believe it must be created with desktop Calibre initially). But it’s a good option and I highly recommend it.

you just load your books from Calibre (or right through USB if you’re hardcore for some reason) and you’re basically off to the races.

There’s also an OPDS server option with calibre-web that you can use to load books from if you’re using koreader.

You can also use the Kobo server replacement option with calibre-web although I personally couldn’t get it to work at the time I tried it. But this will give you a sync option that works like the official Kobo server which is quite nice.

You can also set --accept-dns to false with the commandline client although magic DNS etc won’t work.

Essentially, although it depends on the specific issue. I don’t think hardware decoding with Wine is well supported either, so this should help with performance in the case of slow CPUs (or very high resolution / frame rate video).

If nothing else, the wrapper can just focus on translating to Vulkan Video, which should simplify things significantly.