• Posts

  • Joined

  • Last visited


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Skrumpy's Achievements


Apprentice (3/14)



  1. I updated to Q35-6.1 and latest VirtIO when I upgraded to Win11.
  2. I did have a measurable performance (FPS) hit in 2 games that I play (Hunt Showdown & League of Legends), but more in Hunt (consistently ~20ish FPS less) due to how processor heavy of a game it is. These weren't "scientific" tests, just anecdotal pre-upgrade (Win 10) and post-upgrade (Win 11 full update) game launching and playing for several hours each (no other changes done). I was able to mitigate most of the performance drop in Hunt by doing some other tweaks in/out of game. It is still not in a pre-upgrade state and I occasionally experience random, quick, infrequent, and severe slowdowns/lag when experiencing visually demanding areas. These did not occur pre-upgrade. I do slightly regret updating my VM to Win 11 as I have not noticed any significant benefits to updating that make it worth the hassle of trying to mitigate the performance drops and of dealing with it in game. I do not know how other systems and/or other games may be impacted and can only speak to my own experiences and the 2 games I have tested. I would suggest other people give it a go and see if we can have QEMU take a look at virtualization changes. Q35-6.1 (latest ver in RC2) already had some AMD "fixes" and perhaps they'll be able to tweak things specifically for Win 11 at some point.
  3. There's an unraid thread here where someone was wondering about the same and someone had mentioned using SEABIOS. "Right now i have 2 vms running SEABIOS with Q35-4.2 and AMD drivers are installing like a charm and not causing me any headaches." Do you think the emulation will avoid the performance degradation with AMD processors and Win 11? Otherwise, this may be something to bring to the attention of AMD users prior to upgrading via VM.
  4. Thanks, got RC2 & Win 11 installed. However, I'm unable to update to the latest ver ( of AMD chipset drivers which is required to resolve the Win 11 performance issues. The installer does not recognize my system as AMD and exits. Running the new OVMF TPM, Q35-6.1, and virtio-win-0.1.208-1 and still no luck. Have also tried the chipset version directly from mb website and still no luck. Device manager lists Computer as 'ACPI x64-based PC' and Processors 'AMD Ryzen Threadripper 3960X 24-core Processor' Anyone have a suggestion?
  5. Yes, the RC, I thought it was discussed in this thread that the release would be available soon.
  6. Any update on how "soon" the next release will be out? Alturismo posted on Sept 30th; AMD has patched their Win11 bugs so looking to get it going on my rig. Thanks gents.
  7. Was going to use the Zoltan option, but if @ich777 says that may mess things up once it's integrated, I will wait a few more days. Is this unRAID update allowing pass-through or is everything going to be emulated? I am currently running a Win 10 VM and would like to just update to Win 11 VM.
  8. During gaming my parity (usually) and sometimes another drive will get above normal operating temps. This otherwise only happens during a parity check. My VM OS and all games are installed to a passthrough NVME dedicated to the VM. Using unRaid as a daily driver, TR 3960x v6.9.2 with my Win 10 VM xml below. Anyone have any thoughts on why these non-VM drives are getting hot while not utilizing them directly? Also if you're parsing through it, any additional optimization tips would be greatly appreciated. Thanks!
  9. I deleted docker & folder, then reinstalled. Running multiple versions so no need to update SteamCMD files and delete the entire image right? 0.9.4 (the basic pull from the docker for V+ = true) worked fine without issue. When I copy & paste the 0.9.5 unix server files into the docker and overwrite I still get the error.
  10. Good news.. I knew I wasn't going insane! Thanks for verifying with me so I could go back to them and tell them it wasn't the docker they wanted to blame it on!
  11. Yes, it is on cache only. It must be something with their 0.9.5 files as I have tried the above process (and other variants for the past 8 hours without any luck. It's odd, because the same error happened to someone who was using the 0.9.4 files and in a different docker environment. Which is what made me think there may have been another change. The V+ dev said the only change they did was put some " into the start server/, however, I tried just copy & paste the 0.9.4 sh files and same issue. Must be something else they'll have to sort out. Thanks for looking into it at least and I'll report back if I find out anything else.
  12. Having the same issue.. anything to do with the recent update to 6.9.1? Docker get updated? I was trying to install the 0.9.5 alpha to do some testing.. but getting the issue below. I have tried deleting, reinstalling, default settings, etc. Here is the pastebin of my log and just sent you the alpha 0.9.5 files of V+ for unix server/windows client in the event you want them. RecordSteamInterfaceCreation (PID 75): SteamNetworkingSockets008 / /opt/scripts/ line 140: 75 Aborted ${SERVER_DIR}/valheim_server.x86_64 -name "${SRV_NAME}" -port ${GAME_PORT} -world "${WORLD_NAME}" -password "${SRV_PWD}" -public ${PUBLIC} ${GAME_PARAMS} > /dev/null Another user trying to install from Debian having issues as well...
  13. @ich777 I came across this compression mod, but something is going on and it is not working. Speaking to the mod dev, I have installed BepInEx (FULL) over the client/server to update that. I also have V+ installed. I can connect fine with these 2 changes. Then I install his mod (server + client) but not getting to connect. Anything you see right off the bat that may be a cause? He's not seeing where things would be stopped on the mod DLL end. The mod config log shows it is enabled. Unfortunately I can't see the console as web console doesn't show anything. This mod could be pretty big for reducing server lag and wanted to test it out. Not sure what could be the issue here.
  14. Thanks guys, just used the openssh docker and added the other docker container path as access to that path. Seems to work. Just need to figure out how to add multiple users in openssh docker as it only has variables for a single user.
  15. I think we got it setup, appreciate the help!