Anyone else having stuttering issues with RT enabled, and only with RT enabled?

I've been testing for a while now, and the more I play, the more clear the picture becomes. I performed a few CapFrameX captures, and:

RT on, 85 seconds: 6 stutters (55-85 ms frametimes)
RT on, 60 seconds: 1 stutter (60 ms)
RT on, 32 seconds: 1 stutter (180 ms)
RT on, 60 seconds: 1 stutter (185 ms)

RT off, 90 seconds: no frame above 14 ms
RT off, 160 seconds: no frame above 14 ms
RT off, 170 seconds: 1 frame at 23 ms, but I didn't notice it as a stutter

I haven't felt a single stutter with RT off, but in total hundreds with RT on.

Ryzen 5800X3D
Radeon 9070 XT, -75 mV undervolt
48 GB

One of my projects using Soundshed stopped working: the plugin doesn't really change the sound much, and the amp and IR nodes show errors.

Amp: Missing resource file: tone3000:418201
IR: Missing resource file: ir:tone3000:220917

I don't know if these have been deleted from TONE3000 or something, but I expected a local copy to handle that permanently if that is the case. I don't believe they've been deleted locally (unless by Soundshed). I last used them about two weeks earlier.

Other projects still work as expected; they almost certainly use different amps/IRs though.

What might have happened here, and how can I avoid it happening again? In this particular case, I don't need to recover

I'm assuming and hoping this is not intended?

Steps to reproduce (for me, at least):

1. Start a blank project, add track, add Soundshed
2. Change settings in the top bar (input, gate, transpose, EQ and so on)
3. Add or remove any component in the signal chain (FX/amp/IR/...), and all the top settings are reset to default.

I'm on Windows 11 (amd64), host is REAPER 7.74, Soundshed version 1.4.0.

Is there a stream/VOD somewhere?
I got the previous two concerts from Vimeo, links here, but the new one isn't there... and I just noticed the old ones are 404s, even.

Surely there has to be others that want to WATCH the concert without buying physical media?! I abandoned physical media before Blu-ray even entered the market in 2006.

Are you considering buying a monitor that uses DSC, but worry about the potential loss in image quality? You've come to the right place!
I couldn't find many comparisons online, so I made a few using the official DSC reference tool, used by e.g. monitor manufacturers.

Test settings

All test images are compressed using the DSC 1.2 reference tool using a 3:1 compression ratio, that is, 8 bits per pixel (instead of the usual 24 bits/pixel). I used the default settings for the program other than changing to 3:1 (from 2:1, i.e. the default gives higher image quality/less compression).
3:1 is enough compression

Are you considering buying a monitor that uses DSC, but worry about the potential loss in image quality? You've come to the right place!
I couldn't find many comparisons online, so I made a few using the official DSC reference tool, used by e.g. monitor manufacturers.

Test settings

All test images are compressed using the DSC 1.2 reference tool using a 3:1 compression ratio, that is, 8 bits per pixel (instead of the usual 24 bits/pixel). I used the default settings for the program other than changing to 3:1 (from 2:1, i.e. the default gives higher image quality/less compression).
3:1 is enough compression

Is anyone here aware of music in a similar vibe to e.g. "Libera (Part II) - Ascent of Burning Moths", "Painters Of The Tempest (Part III): Reveries From The Stained Glass Womb", "Devour Me, Colossus (Part II): Contortions" and similar NeO tracks?

Where do I even begin to look? (I'm familiar with the entire NeO discography, of course.)

Violin/viola/cello is the main requirement. Can be with or without vocals, and other instruments are fine, especially piano/acoustic guitar.
They don't need to be super calm, but nothing that's much heavier than the example tracks.

Also, for the record, Ascent of Burning Moths is one of the most beautiful pieces of music I've heard.

I just ran into a bizarre issue. I opened up the Adrenalin overlay to check my FPS in Baldur's Gate 3, and noticed that the GPU's coil whine increased by a lot, and that toggling the overlay toggled the coil whine.

I had a look at HWiNFO64 and Adrenalin, and they both show massive changes in power usage, clock frequency, core voltage and so on when the overlay is active, assuming the GPU is not near max load to begin with.

Overlay off: hotspot 62 C, 730 mV, 1940 MHz, 130 W, 700 rpm, GPU utilization 85%
Overlay on: hotspot 82 C, 1110 mV, 3167 MHz, 270 W, 1000 rpm, GPU utilization 92%

This is repeatable and I can toggle between these states by toggling the overlay.

Here are the images:

I have a red Spokey (3.25 mm) and a "universal" spoke key, one of those circular ones with cutouts labelled with various spoke gauges, 10-15.
13 and 14 are the same size though?! Both are 3.70 mm according to my digital caliper. 15 is 3.3 mm.

For my "new" wheels (Bontrager Connection DC-20 and DC-22), none of those keys fit. 13/14 are too big and feel like they almost work, but they always slip. 15 is too small and doesn't fit even with a bit of force.

I tried to measure the nipples but struggled as I was getting readings from 3.5 mm at the smallest to about 3.7-3.8 mm, all when trying to keep it square to the nipple.
I also photographed a few nipples and the shape wasn't what I expect

I'm running two computers with very similar software, but different hardware, and different ZFS configs (RAIDZ2 vs 2-disk mirror). Both run Debian 12 with the latest backported OpenZFS version, currently 2.2.4 (2.2.4-1~bpo12+1); both have 16 GB of RAM. One works fine, while the other has scrub issues, but is otherwise also fine.

The one running RAIDZ2 can rarely, or possibly never, finish a full scrub without issues. The scrub seems to slow down to basically 0 speed, but that's the only issue I have.
I can still use the pool, there are no data errors, no errors in dmesg, and no other issues with ZFS or even the computer in general. Just that I need to manually intervene to get the scrub

I'm in the first few chapters of Death's End Part II, and I'm really confused about what's going on between Earth and Trisolaris here. Did I miss something major in the prior chapters, or are these things explained later in the book? Or is neither guess correct?

In the third chapter of Part II, "Deterrence Era, Year 12 Bronze Age", this happens:

Just as Bronze Age was about to begin accelerating away from home again, the unimaginable happened: A sophon unfolded into low dimensions on the ship, establishing a quantum communication channel with Earth. Finally, the crew received confirmation of all that had occurred.

What happened here? How does Earth have access to sophons? Or rather, why

I'm setting up a second computer running Debian 12.5 with ZFS On Linux (2.2.3-1~bpo12+1 on both systems). After finishing the initial backup from system #1 (hyperion) to system #2 (exscape) I checked the data size (du -cks --apparent-size) and file/dir counts (find | wc -l) just as a sanity check, but noticed that the performance was vastly different on the two systems.

exscape has 2x 7200 rpm SATA disks in a mirror, while hyperion has 5x 5400 rpm SATA disks in a RAIDZ2 vdev.
The former finished find | wc -l in 5m 36s while the latter needed 16m 17s. Is such a large performance difference really to be expected? Both were soon after a reboot, so no cached data.
Other hardware specs are s

I have two ZFS pools; two 4 TB disks in a mirror, and a separate 8 TB disk with no redundancy. The system only stores backups, and the backups on the 8 TB disk are less important, so the lack of redundancy isn't much of a problem.

A scrub runs on these pools once a month. Both in November and now in January (but not in December), the scrub found checksum errors on one of the 4 TB disks. 6 of them each time, and "768K repaired" each time. Back in November I figured I'd let it slide and look it up if it happened again. Since it did, I replaced the SATA cable for that disk, and also swapped SATA ports between the two disks, figuring that if the port/controller is broken, the checksum errors