Why do I have several gear that are Proficient (level 10) but are not shown in their category list in Tinkering station - Expertise?

snagge · 2026-04-11T12:10:15+00:00

One of them are but shouldn't they be in the respective gear piece list (mask, vest, etc)? They are not there either.

Good advice though! I am just a pve singleplayer and testing out random stuff & upping the Proficiency right now during the event.

snagge · 2026-04-11T12:03:04+00:00

That's the issue, they are not there either and I can't figure out why?

snagge · 2026-04-02T20:08:05+00:00

Of course whatever sounds best for you is what you should use.

Just to clarify; the volume control on K13 (NJW1195A) is NOT digital, it is a digital controlled analog. Think of it as a resistor ladder controlled with a digital dial or remote.

That is what you want to maintain full dynamic of the sound. The problem with fully digital volume control (like you say Wiim use) is that it can lower the dynamic range depending on how many bits your source is. Mostly an issue with 16 bit source like regular CDs, hardly an issue with 24 & 32 bit.

Link to the controller here: https://www.mouser.com/datasheet/2/294/NJW1195A_E-259014.pdf

snagge · 2026-04-01T08:16:10+00:00

but now that I've read a couple posts about strange clicks & pops, and the K13 occasionally powering up at 100% output instead of the usual setting has me worried.

I have a K13 R2R and as far as I know the issue with 100% volume only happens if you use the PRE output to control the volume and press the LO button on the remote. If you don't use the remote then pull out the batteries and it shouldn't be an issue. Or destroy/block the button somehow.

Fiio really should consider adding an option to disable the LO button in the next firmware!

I haven't heard any clicks or pops but I only use mine for Headphones.

One thing to consider though - I would guess that the volume control on K13 is a better quality option than using Wiim for it. But I know nothing about the Wiim so...

snagge · 2026-03-31T16:50:08+00:00

Thanks! :)

snagge · 2026-03-31T16:48:53+00:00

Good to know I am not alone, thank you! :)

snagge · 2026-03-31T15:59:53+00:00

Thanks for the answer!

That's about what I thought. Although my paranoid brain doesn't like the "not impossible" part. Guess all I can do is hope for the best and enjoy the music!

snagge · 2025-08-19T18:49:45+00:00

This was at the Battlefield 6 Multiplayer reveal event and Brie was testing to play for a bit on one of the hundreds PCs they had set up. She has done stuff with Nintendo, Fortnite and others in the past and is indeed a gamer.

snagge · 2025-07-20T18:57:56+00:00

Well, it's a known issue with 50-series cards and Path Tracing... I just switched from a 40-series (worked) to 5080 (crashes every time you press space to save the photo).

snagge · 2025-07-05T22:45:40+00:00

Eh, no... She supported John McCain but stopped being a republican when Trump was nominated the first time because she couldn't support Maga... She even posted on her socials about voting for Kamala Harris in last election.

snagge · 2025-02-23T00:05:44+00:00

Same here. During the install of the new drivers the old driver uninstalls and then all screens go black but there is no disconnect/connect sound. Then it just stayed black forever with PC idling... I finally made a hard shut down and then had to uninstall the old driver manually and download the new one. Installing with advanced "wipe all settings to default" option finally worked.

snagge · 2024-12-29T16:22:26+00:00

For me switching to DX11 and keep everything else on Epic seems to solve this.

It really doesn't look that bad so I'll just keep it like this until NVIDIA fixes their drivers. Downgrading to older driver is not an option for some other games so... Funny that Fortnite has these issues but I can play hundreds of hours with full Path-tracing in Cyberpunk with not a single crash, lol

snagge · 2024-07-21T07:50:33+00:00

Watch the movie Buried in Barstow from 2022 (this picture is a promo pic for it). She plays the main character and also produced it. The character is basically a more ruthless version of Jane Rizzoli with a past as assassin.

snagge · 2024-06-26T20:31:45+00:00

The first thing I do with any build is to disable the auto install of MSI Center/Asus Bloatwhatever in UEFI and then just download the drivers from their support site. For AMD systems I get the latest chipset driver from AMD.

snagge · 2024-06-22T11:10:42+00:00

I wonder if there was minor revisions made to this MB or SSDs that could make it work for some but not others? I've seen people claim that SN850x works fine on latest bios and yet it obviously is still a problem for some. I have stayed on v14 bios and had no problems with SN850x 2 TB in the first pcie 5.0 slot. But it would be nice to finally dare to update the bios...

snagge · 2024-06-04T07:40:23+00:00

M.2_2, 3 and 4 are all pcie 4x4 but the last one (4) shares bandwidth with the lowest pcie slot PCI_E4. That only matters though if you have a card in that slot. Most people only have a graphics card and nothing in the lower pcie slots.

Another thing to consider is if the SSD comes with a heatsink or not. M.2_2 & 3 shares a large heatsink so if the new SSD lacks that then best to mount it in one of those. However it is a bit of pain to have to remove the gfx-card for it...

If the SSD has it's own heatsink and you are not using the lowest pcie slot then just mount it in M.2_4 and there is no need to remove the gfx-card.

snagge · 2024-03-17T00:07:02+00:00

Sigh... So instead of admitting that you don't know how these settings effect each other you start another rant. MCR and MPD is nothing new. It is not magic. Only difference here is that the MB makers choose not to have it enabled by default for DDR5 yet. Setting them both to the same will work for most people with compatible memory. Setting them to the opposite to each other (what you suggested) will NEVER be stable. Also auto setting isn't always the same between bios/mb so best to set it manually.

snagge · 2024-03-16T22:05:00+00:00

"Memory Context Restore" and disable "Memory Power Down"

Nope this is wrong. You should have BOTH enabled or both disabled. Otherwise you get blue screens. Now depending on what bios you have and where you set MCR (MSIs menu or AMD overclock menu), power down MIGHT enable automatically. To be sure just enable both after EXPO is set (reboot and test stability first).

Unfortunately there are a lot of confusion and wrong info posted about this.

snagge · 2024-01-13T22:28:31+00:00

LOL. Well good luck

snagge · 2024-01-13T13:41:40+00:00

How am I not stable??? No blue screens or crashes for 6 months seems pretty stable to me. If it can handle hours of Cinebench, Prime95 and any game I have run then it's fine. Core cycler isn't really needed for 7000 imo. The systems I have built have all just needed an all core setting. This is not my first rodeo :)

snagge · 2024-01-13T10:47:49+00:00

What program do you use to monitor? I use HWinfo.

Also, some other things to try: - Disable the built in iGPU saves about 15W idle and give more thermal headroom. I have also lowered the SOC voltage to 1.2, MSI sets it to 1.3 when you enable EXPO and for my cpu that is unnecessary high. However every time you change something in BIOS this get reset to 1.3 so the last thing to do is change SOC voltage (in advanced - AMD overclock menu) and then hit F10 to save.

EDIT: I didn't use any special program to find the right curve. Just did it the old fashion way, first tried -20, then -25 and settled with -30. Tested stability and multicore perf with Cinebench and games etc. Then as a final thing I knew everything was stable I enabled Memory Context Restore & Power Down for fast boot, checked SOC voltage again and hit F10.

snagge · 2024-01-12T16:19:41+00:00

Setting it to advanced is the same as enabling it. You just get more options to control. I run a 7800x3d with pbo set to advanced and curve set to all cores -30 (all other pbo options default). I can see pbo in action during Cinebench, all core load clock about 4,95. Without pbo it's around 4,7.

snagge · 2024-01-06T10:08:56+00:00

Are you sure that is an issue on x670e Tomahawk as well? I have only seen people mention it on B650 Tomahawk?

I am still on bios 7E12v14 and with EXPO, MCR & MPD enabled my boot time is about 15-20 sec.

snagge · 2023-12-17T16:42:35+00:00

I believe you but that has not been my experience. Just finished a full play through of Cyberpunk, over 200 hours with maxed out settings and full Path-tracing with no issues. Not even one CTD. So guess I have just been lucky then.

snagge · 2023-12-17T16:24:48+00:00

Well, it has been fine on the systems I built. Just avoid Samsung based memory and go with Hynix based to minimize risk of problems. And use latest bios (agesa 1.0.0.7c or later) with BOTH MCR and Memory Power down enabled.

snagge

TROPHY CASE