moody

I haven't seen one of these in a few days, so I thought I'd toss in one of my own.

It's meant for via ferrata to reduce the impact of falling on static gear. You loop a short rope through the holes and it absorbs the forces of the fall by friction of the rope slipping through. This is the Kong Kisa.

Recently my micro SD card failed and I had to to a full reinstall of klipper.

When I first set it up, I found a guide with pictures and all the software setup specifically for the ADXL345 and Pi Zero 2, but I can't find the guide anymore.

Everything's already wired, but I definitely don't remember how to set everything up.

Currently running Nobara, and having audio annoyances.

Any time any app loads anything new, it will switch my audio device back to default. For example, if I open a playlist in VLC and choose my speakers as the output device, when it's done playing one file, it will open the next one and start playing audio through the headphones.

If I'm watching a video on Youtube and choose speakers, as soon as I leave the page it goes back to headphones.

Is there a way to prevent the device in use from switching back? If I switch device, I just want it to stay on that device until I choose to switch back. I literally never want it to switch on its own. ATM, the only way is to manually go it and change the default every time instead of just clicking the checkbox in the volume popup.

This is a recent issue, and I don't know what has changed to cause it. There seems to be no rhyme or reason as to which games work and which ones don't. My monitor's resolution is set to 2560 x 1440 in the display settings, but some games don't recognize it.

Of the games I have installed, Subnautica, Dark Souls III, Sekiro, Control, Hades, and Hi-Fi Rush think my native resolution is 1896 x 1067 and they won't let me change it to anything higher than that.

Elden Ring, Ark Survival Ascended, and Returnal detect my resolution correctly and work fine.

This is all from Steam without any custom launch settings, and with and without gamescope. I've tried custom resolution command line options for Subnautica and that hasn't helped either.

I'm running an RX 6700 XT on Nobara with everything currently up to date. I'm not sure when this issue started, but it's recent, probably within the last week or so. I've definitely run Control and Sekiro at the correct resolution before, but in my recent testing they no longer work right.

Does anyone know what could be causing this? Why some games work fine and others don't?

I haven't bought from Amazon in several years, but I made an exception for this deal. I've never seen this go below $80 before.

Are there any software issues I may/should deal with when doing a full system upgrade? I'm going from AM4 to AM5, so new CPU, motherboard and RAM.

It should be pretty straightforward under Linux, right? Just swap my drives over and boot up? I've only ever done single upgrades at a time, never a full generation.

I've had the game running fine for months, but experience constant crashes if I have foliage and fluid interaction enabled. Has anyone been able to run the game with this on?

Currently on Pop!OS running a 6700XT, and having the issue under both X and Wayland.

A friend of mine was a gamer many years ago but hasn't been gaming in a while. They run a Mac and I run a PC. What are some good patient games we can play together?

Every time I use calibrate_probe, I get the message "The SAVE_CONFIG command will update the printer config file with the above and restart the printer."

When I click Save Config, it restarts the firmware, and then I get the warning "Option 'z_offset' in section 'bltouch' must be specified."

If I go check my printer.cfg, the [bltouch] section now has z_offset commented out with the old value and I have to remove the comment and copy in the new value.

Am I missing something? What am I doing wrong?

I'm getting increasingly frustrated trying to get my printer calibrated. I've done a bed calibration using screws_tilt_calculate, and that's all nice and good. Got a bed mesh variance of 0.19mm which seems great.

Now for the z-offset, it won't let me get the nozzle low enough. No matter how low I set the Z minimum, it won't let me get closer than about 0.5mm to the bed. I've tried setting the position_min in [stepper_z] anywhere from 0 to -9 and I get the same result every time.

If I raise the bed, the probe adjust its height accordingly, so the result is the same.

What can I do to fix this?

I picked it up and have been playing it. The first day, it seemed to run fine, but today I've been having a ton of trouble with it. I'm struggling to go 15 minutes without crashing, and when it does crash, Steam stops responding entirely until I reboot.

Edit: I can't explain why, but after checking my logs, whenever my computer full-crashes, it's apparently caused by bluetooth, despite not having any connected bluetooth devices. I've disabled the bluetooth service, and now the game only crashes to desktop. Small wins, I guess.

Another edit: I appear to have fixed my problem. I installed gamemode via apt, and added 'gamemoderun %command%' to the launch options in Steam. Haven't crashed since.