SylenThunder

Sounds like it might be a thermal or PSU issue. Make sure that Windows is not set to auto-restart on the BSOD, and you might catch it better. Or check the event log as it may be noted there.

Any semi-major Windows update may re-install the idiot GPU drivers that Microshaft pushes. First thing I do after these updates complete is do an extra restart, and then perform a clean install of GPU drivers.

Not to mention that thanks to limitations imposed by Sony and Microsoft regarding save file integrity, The console version could never get to A16 because it would break existing saves. Literally the only thing that could be added to the console at this point is some a16 content and engine optimization. Even if TFP managed to get the source code for the consoles, they still would not be able to update the game there. They aren't the publisher for the existing client.

There is another Asus tool that causes issues as well. RamCache. Most of the software is just bloatware anyway. I have a number of Asus systems. They run just fine without any of the crap installed. Get your GPU driver from the actual manufacturer. That would be Nvidia, AMD, or Intel. Not Asus. Motherboard and CPU chipset drivers come from Asus and Intel. You only need the driver. Not any software.

Well in your case EVGA specialized in GPU's. Asus specializes in laptops and motherboards. As a result, most of their driver packages are bare minimum. Because laptops. Also, IIRC that B550 LAN chipset is Intel.

GPU driver needs to come from Nvidia/AMD Not Asus. That's nearly as bad as getting them from Microsoft.

Migrating saves is covered in the Support FAQ thread. It's pinned to the top of this forum section.

Technically this is a result of modders making the region selection obsolete. You can install a dll mod that bypasses the region selection and makes the server show up in every region.

^^ This right here. I know what this is. Over a year ago there was a Windows update that had a CPU chipset driver in it. This driver targeted overclocked CPU's and severely underclocked them. (May have been intentional, but I don't recall the truth ever being found.) Even if you don't intentionly OC your CPU, your motherboard has a "Gaming mode" built into it, and in the bloatware that gets installed with it that will auto-OC your CPU a small amount. The fix is pretty easy. Just pull the latest chipset drivers from MSI and Intel. Install them and reboot. Ensure your RAM is set to the XMP profile as well.

Try running the client in exclusive mode. What you describe is common when you aren't running fullscreen exclusive. What you describe is an issue especially if you're running windowed or borderless windowed.

You don't. Cross-Platform play was never supported on the console version.

OMG, did you read the instructions? One minute while I fix your post for you. 1. Backup your save and profile data. 2. Wipe everything. All save data and downloaded worlds. There is a tool in the launcher for this. 3. Exclude your client from security software. (Covered in detail in the Pinned threads you're not reading.) 4. Validate the client files. It is recommended to do this at least twice because Steam's CRC check sucks. 5. Start a fresh game and try again.

Also note that that laptop isn't going to do well at 4k. You will want to drop your resolution to 1440p or 1080p. Doesn't matter that it's a 12th-gen with a 3080. You might as well have a desktop 8th gen with a 1070. Your video driver is also from June. Install this one. Don't forget to opt out of the GeForce Experience bloatware, and you should choose Advanced to perform a clean install. This is a driver issue. It's not a bug with the client. You're probably just using the crap "Microsoft Certified" driver that Windows installs with major updates. It doesn't include full Direct3D support, and causes this issue.

Also note that that laptop isn't going to do well at 4k. You will want to drop your resolution to 1440p or 1080p. Doesn't matter that it's a 12th-gen with a 3080. You might as well have a desktop 8th gen with a 1070. Your video driver is also from June. Install this one. Don't forget to opt out of the GeForce Experience bloatware, and you should choose Advanced to perform a clean install. This is a driver issue. It's not a bug with the client. You're probably just using the crap "Microsoft Certified" driver that Windows installs with major updates. It doesn't include full Direct3D support, and causes this issue.

Also note that that laptop isn't going to do well at 4k. You will want to drop your resolution to 1440p or 1080p. Doesn't matter that it's a 12th-gen with a 3080. You might as well have a desktop 8th gen with a 1070. Your video driver is also from June. Install this one. Don't forget to opt out of the GeForce Experience bloatware, and you should choose Advanced to perform a clean install. And as Star69 stated, that is a driver issue. It's not a bug with the client. You're probably just using the crap "Microsoft Certified" driver that Windows installs with major updates. It doesn't include full Direct3D support, and causes this issue.

Moved to the correct forum section. Read the Pinned threads.

Yep, return is going to be managed entirely by the store you purchased the client from. Typical rules are less than 14 days from point of sale, and less than two hours of gameplay. Also note that neither the PS4 or the Xbox versions are advertised as supporting cross-platform play.

I responded to you with this in Discord, but pasting it here for others that may happen across this thread... If you use SteamNetworking, it basically uses Steam servers like a VPN. All traffic goes through Steam before it gets to your server, and makes the same path in the opposite direction. This increases latency incredibly. SteamNetworking should only be used if you are unable to properly forward the ports, or for troubleshooting. In absolutely every other situation it should be disabled. Disabling LiteNetLib will have a severe impact on network performance of the server.

Probably not. Just because they didn't cause a problem before, doesn't mean they weren't an issue. It just means that you didn't run into the part of the mod with a compatibility problem yet. Always validate that the mods you are using are compatible before loading.

You have mods that are not compatible with a20. One was never even updated for a19.

Need the whole log. Please read the Pinned thread.

If your mods are only xml edits, then the server pushes the changes to the clients when they connect. If you have any mods with extra assets or dll changes, then every player must have that mod installed. Most overhaul mods like Darkness Falls fit this category. Usually the mod author will note if they are server-side only or not.

You can either just type it out normally, or use \n for a new line.