Windrose Dedicated Server/Steam issue

[violet plank]

When I run the dedicated server file on the same computer that I am playing the game on, Steam says the game is still running even after shutting both down. This forces me to restart Steam any time I turn off the game, which is preventing me from keeping the server up all the time (like a real dedicated server). This will actually happen whether or not the dedicated server is running but it forces me to shut down the server each time I close the game.

While that issue is annoying the real problem is that I am forced to do this as I cannot get the dedicated server running on a windows VM (server in basement), it crashes immediately with no errors, but event viewer claims ntdll.dll is to blame. I have tried two different versions of Windows VM, both using SteamCMD as well as copying the files directly from the computer where it works (Game + Server). I even went as far as downloading steam on a fresh installed VM and installing both Windrose and the dedicated server tool through Steam to get the same results.

I am fine with hosting the server on the desktop I play on as long as I can get it to function like an actual dedicated server (no restarting steam each time I close the game) but ideally I would love it if I could get the dedicated server running on a VM on my actual server. Any help or guidance is super appreciated.

[thorny plaza]

It should be OK if you run the server before you start Steam client, but if it crashes and restarts it hooks to SteamService again, I used to host SRCDS for various Source games that did this before we eventually bought a separate machine, so it's hardly unique to Windrose.

Also, the server launcher needs a CPU with AVX instructions, so if your Windows VM runs in ProxMox it needs to pass through the CPU HW to the VM instead of emulating some other system plus it apparently also needs Direct SOund, so it won't run on Windows Server Core (guiless

[hexed pollen]

Hmm let me check if we have anything on that

[violet plank]

If not having sound was the issue this whole time I might just cry lol. The VMs were both windows 11 since thats what the working desktop is using to run it

[thorny plaza]

It was a specific report about not being able to install DX runtimes (pre-requisite) because Windows Server Core has no DX nor desktop enviro.

If you use desktop OS in your VM that's not an issue.

The ProxMox example is now listed in the official server guide btw

[violet plank]

It was either the AVX or sound because the terminal has finally appeared

Cookies for you Arc, thanks for the assist

[thorny plaza]

It's really the users like you struggling with it that found the solution.

However I wanted to ask, the AVX requirement may or may not be just on the launcher exe, not on the actual Shipping exe. Might be worth exploring that so folks with old Xeon CPUs don't have to find weirder workarounds.

[violet plank]

I used the StartServerForeground.bat to launch the server, let me close out and launch the shipping exe quick

[violet plank]

I wouldn't have thought of the server requiring sound (it wasn't the fix for the record but it was more information than I found googling on and off all day)

Running the shipping exe allowed me to connect again, no problem all it apparently took was setting the cpu to host in proxmox

[thorny plaza]

Yes that's the fix, but my point about the Shpping exe is to test it with your initial ProxMox config, the one that didn't pass through AVX 👀

[violet plank]

Oh duh one sec

No bueno moving cpu option back to non-host

[thorny plaza]

Thankss !

Means no easy workaround to those that use old Xeons.