In this time i think DriverClassNameFallback which is set to OnlineSubsystemUtils.IpNetDriver should work, am i right? But it seems that something wrong there. If i am closing steam client and runing game, event with -nosteam parameter i see many errors in logs that steam init failed. I sent you new logs some time ago, also this issue not happens in 4.14 but there as you can see when you pass -nosteam parameter, then steam sysbsystem is still used instead of subsystemNULL which was in 4.12 and elder (before 4.13) I have a server requires that the client uses the -nosteam parameter so I cannot use the normal version. It only crashes when I am using the -nosteam parameter. I updated the game to 34.27 and it stated crashing. I've been playing the game for a while now and without a problem. Run the server using the normal command line or alternatively from the SteamCMD GUI Run Server tab. Go back one one level up to LumaEmu main folder and copy LumaEmu.ini to C:\srcds\. So I've been playing the game for a long time but on a different account, running the -nosteam command (don't ask why) and now it just doesn't work and I don't trust hirez customer service with unlinking my old account so that I can play on the one with all my progress. Open the extracted LumaEmu, go to x86 folder and copy the steamclient.dll file to C:\srcds\bin\ directory. I was looking at the megathread and noticed nosteam bein listed us unsafe with no explenation while every other one had an explenation? i have been using nosteam for years and all the games worked great and i had no issues at all.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |