Quoting: scaine

Quoting: Cybolic

Quoting: scaine

Quoting: rustybroomhandleSeems to be here, but with Experimental bleeding-edge it does not seem to load Steam Input and the Overlay and my controller is not recognised.

I've heard as much for Experimental, but controller support seems pretty solid (for me) on GE. At least my dualsense (PS5) controller works perfectly.

Which GE version are you running? I have a PS5 DualSense as well and so far it has failed to work at all with Experimental beta, Experimental, 7.0-1, 7-5-GE and 7.3-GE-1.

It's been a few days, but it was GE-Proton-7.3 (NOT Proton-GE) at the time I think. 7.4 is out now. But you have activate the controller in Steam/Settings/Controllers/Profiles before it's recognised.

Hmm, I just tried with GE-Proton-7.3 and got the same result. I'm not sure what you mean by `Steam/Settings/Controllers/Profiles`? I don't have `Profiles` under the main Steam settings nor in BPM. I have tried selecting a custom mapping for the game, and togging forcing Steam Input on/off but neither did anything.
I should mention that the controller is working beautifully in BPM and Horizon Zero Dawn.

EDIT: Also, I'm trying it out on Pop!_OS, just like you. Very weird stuff.
EDIT 2: I just tried the Windows trick of disconnecting everything but the controller and launching from BPM, still no-go.

View this comment - View article - View full comments

Quoting: scaine

Quoting: rustybroomhandleSeems to be here, but with Experimental bleeding-edge it does not seem to load Steam Input and the Overlay and my controller is not recognised.

I've heard as much for Experimental, but controller support seems pretty solid (for me) on GE. At least my dualsense (PS5) controller works perfectly.

Which GE version are you running? I have a PS5 DualSense as well and so far it has failed to work at all with Experimental beta, Experimental, 7.0-1, 7-5-GE and 7.3-GE-1.

View this comment - View article - View full comments

Ah, that's good to see. I was getting a bit worried about the lack of updates!
Anecdotally, I got one of the biquintennial (is that a word?) hardware surveys recently, and it listed me as not having a VR headset, despite my Index being plugged in, on and registered in Steam, so hopefully, they aren't allocating development resources based on those stats.

View this comment - View article - View full comments

Quoting: Purple Library GuyThe trailer was eerie and cool, but I couldn't figure out what a player would be doing, exactly. I mean you're zooming down one track; you can't really dodge, most of the time it doesn't seem like you're shooting anything although now and then it seems like a shock wave comes out of you. I presume there's something, and it's related to the rhythm and all that--I'm just wondering what it is.

It's a bit like a rhythm game; you have to activate the right thing when the appropriate, usually glowing, other thing hits you (or right before). It's cool, I recommend it - gets you in a weird, dreadful, semi-hypnotic mood :D

View this comment - View article - View full comments

The wording is odd, but I can't fault their stance (for now). To me, it sounds a lot like when Ubuntu was the only officially supported distro for many games, only here they also protect themselves from NVIDIA driver bugs and any other hardware and software stack differences.

View this comment - View article - View full comments

Shout-out to Rune (also ported by Loki) from a few months later, that not only also let you sever the limbs off of your enemies, but also let you beat them with them.

View this comment - View article - View full comments

Quoting: Guest

Quoting: CybolicFor comparison, that's more than were ever released for the N64 (~300) and the Nintendo Wii U (~150) put together. Pretty nice launch already! :D

You've undershot a bit there, I could have sworn the Wii U had around 800 games

Anyways, I would expect this list to increase massively soon with WMA codec being worked on, exciting times ahead!

Yeah, it might be a bit undershot; I went by largest amount per region (JP/US/EU) to not count games released in all regions twice/thrice.

EDIT: Since we're all doing it:

VERIFIED:      94 games (4.97%)
PLAYABLE:      63 games (3.33%)
UNSUPPORTED:   14 games (0.74%)
UNKNOWN:     1719 games (90.95%)

Not a great ratio for me but I know most of the unknowns work on desktop so I'm not too concerned.

View this comment - View article - View full comments

For comparison, that's more than were ever released for the N64 (~300) and the Nintendo Wii U (~150) put together. Pretty nice launch already! :D

View this comment - View article - View full comments

Quoting: mmstickWhat ananicy does is only a fraction of what system76-scheduler is doing.

Quoting: Cybolic

Quoting: CybolicThis sounds like something that could also be implemented with bspwm, so I'll be sure to keep an eye on what tweaks they're doing.

Here's a quick version for anyone interested. Thanks to mmstick for correcting me on the logic.
bspwm-scheduler.sh

Doesn't appear to be applying the background process priority to all background processes, or matching all descendants of a PPID and their descendants, descendants. It'd be easier to simply do

 
dbus-send --system --dest=com.system76.Scheduler \
    /com/system76/Scheduler \
    com.system76.Scheduler.SetForegroundProcess \
    uint32:${PID}

I added support for using the System76 Scheduler in my little script now. Honestly, I don't see any difference in how it handles process groups in my limited testing, but it is a bit faster at changing the niceness levels.
Best of both worlds now :)

View this comment - View article - View full comments

Quoting: mmstickWhat ananicy does is only a fraction of what system76-scheduler is doing.

Quoting: Cybolic

Quoting: CybolicThis sounds like something that could also be implemented with bspwm, so I'll be sure to keep an eye on what tweaks they're doing.

Here's a quick version for anyone interested. Thanks to mmstick for correcting me on the logic.
bspwm-scheduler.sh

Doesn't appear to be applying the background process priority to all background processes, or matching all descendants of a PPID and their descendants, descendants. It'd be easier to simply do

 
dbus-send --system --dest=com.system76.Scheduler \
    /com/system76/Scheduler \
    com.system76.Scheduler.SetForegroundProcess \
    uint32:${PID}

I've updated it to better handle children of PPID and PID. I'm not aiming to handle the entire system with this, just the basic userspace processes to the extent that bash scripting allows without too much slow code. As for general background processes, that's what the limits.conf edit is for.

View this comment - View article - View full comments