Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Great, have fun and happy hunting!
After changing the CPU type to "Host" (that is, do not simulate a CPU), it worked like a charm. The drawback is that this VM cannot be migrated to another Proxmox guest... it must have the exact same CPU. In that Proxmox I have a Intel(R) Core(TM) i5-2300 CPU @ 2.80GHz (1 Socket, 4 Cores), witch supports the AVX flag.
Reinstalled the Win10 instance, installed the Microsoft VC Redist (x64), configured the .bat script and .json parameters files, and played for about 2 hours without any problem.
Thanks again for your time and this excelent document.
Take care, friend. :)
Nice, thx for the feedback, glad you got it working!
Yeah, I'd be curious too if you could set the correct flags and make it work without deleting the file. Feels like it'd be a better solution.
After deleting the file lib_burst_generated.dll the server started flawlessly. It is, as you said, a CPU flag indeed (damn boy, you know what you are talking about... respect). As far as I could see, did not find any clue of that problem by just looking at the log file, but the scenario got the smell of a "VM not compatible" thing.
Tried to switch the AVX CPU flag, but Proxmox don't have that option, not at least for a KVM64 CPU type. I have to switch to "host CPU", but that requires to reinstall Win10. I will do that, just for the curiosity of it. I will return with an answer as soon as I can dedicate a moment to this.
By the way, there was no need to reinstall VC Redist, as I already installed from the same source that you mentioned.
Again, thank you very much for your time and effort.
I know you mentioned 3 times that you installed VC Redist, but just make sure you have the latest version installed, here is the link [learn.microsoft.com].
I see now, thx for the details. Try deleting lib_burst_generated.dll from ..VRising\VRising_Data\Plugins\x86_64 . If that helped, the problem was probably your server's CPU instruction set.
OR you gotta tweak your VM, in particular set the CPU to host and make sure that avx flags are enabled.
in your proxmox shell try grep -o 'avx[^ ]*' /proc/cpuinfo , it should return avx / avx2 or sth
let me know if that helped
I've successfully installed the VRinsing server using a clean steamcmd install over a clean Win10 install.
On my first try, configured the server editing the example .bat file and tweaking the 2 .json files, with no luck.
After that, reinstalled everything (steamcmd + vr server) and without touching any config, tried a 'dry' run of the example .bat file, again with no luck.
Took a look into the log files, and saw a complain with some .dll files and then installed Microsoft VC Redistributables. Tried again (vanilla untouched config), that error dissapeared from the logs, but again, after a few seconds, the server console closes.
This is the VRisingServer.log file:
https://pastebin.com/UNcUJ9Ce
The public IP & steam ID has been removed on purpouse.
Thank you in advance for your time and patience :)