Darkdiz

Yup, that was it. Re-linked all my Steam-bought stuff, no auth fails. PHEW!

Hmmmm, do Steam-bought modules need to be re-linked from time to time? Each of the above are Steam-bought

Using standard windows time (time.windows.com). DCS worked fine last evening, now I get this. WIndows defender indicated nothing out of the ordinary, already have exception for DCS. Full repair did NOT fix it

Anyone else getting this? Worked fine last evening. Tried a repair... trying it again...

Funny thing is though, it USED to work fine up until the last patch, saved a ton of disk space. Oh well

Indeed...

Exactly the same issue I'm having, so now I know its not just me. @BIGNEWY can you get your guys to take another look at this issue? Thanks

No I didn't. I have both the dedicated server terrains AND core game terrains fully installed. It works (as one would expect), but it is a heck of a waste of drive space. Prior to the last patch, the symlinks worked fine, but now all I get with the symlinks installed is Error Starting Server

What @draconus said. I don't believe there is a HOTAS command that will change the PRF though (PB6 excepted), not sure if it automatically changes with distance (I don't think so?). I'll have to have a look and see what happens

I haven't seen ANY reference to a MPRF TWS mode. Only thing I have seen anywhere is MPRF is used in the Auto Acq modes since they are generally short-range acquisition modes, with the exception of LR BST, which uses HPRF.

I tried the command prompt method, same issue. I'm really at a loss here, clearly there is some setting somewhere that is preventing the proper redirection of windows to the linked folder. As soon as I remove the link (symbolic, hard, whatever), the server works as advertized.

Its clearly an issue with the link creation, but it worked fine before. @Rudel_chwWorked fine before with symbolic links, but I tried hard links (called hardlink clone in the link shell extension), no success. Scratching me head here...

Thing is, I tried both repairs (default and full) on both installations. Nothing worked for the server install, it refused to start, or even let me add missions. After the re-install, it worked, I could add missions, and the server would start. As soon as I pointed the server mods folder symbolic link to the newly full-repaired core install Mods folder (this was the link source), the server refused to start. I remove the link, rename the server install mods folder back to mods, server works (I had renamed the server mods folder to modsold prior to dropping the symbolic link). Up until yesterday when I updated, the links worked fine. Now??? I just re-repaired BOTH installs, no change. As soon as I put a symbolic link in pointing to the core mods folder, the server refuses to start. I remove the link, works fine

Yes, did several yesterday, I actually had to completely re-install the modular server, and did several repairs (both quick and full) to the the client. This patch for me has been a nightmare

Anyone having issues since the last patch (8394) with their symbolic links? I tried rebuilding mine for terrains using the core game as the source and the modular server as the symbolic link. Causes the server to give the unable to start server error. If I remove the link and use the server-installed terrains the server works normally. Prior to the patch, everything worked fine.

I did several full repairs, but the issue was after the repair was done. I run a dedicated server, but the issue was with the core game I have on the server rig. I use the core for simple mission edits, so I don't have to transfer missions from my main game rig to the server rig. The TF51 reappeared after I checked it in the Available list, and I had to reinstall it and Supercarrier, seems to be working now

It does. Although the core terrains have many more files and are significantly larger than the server versions, I had a symbolic link setup with the core terrains as the source. When I ran the server after the patch, I got server error. If I went to the server terrain install (removed the symbolic link), it worked fine. Something in the patch changed the terrains, because it was working fine with the symbolic link prior to the update. I'm still going to see if I can get it to work, but not sure right now.

Ended up re-installing through the launcher, seems fine now

@BIGNEWYthanks for the prompt help Also for whatever reason now, my symbolic links don't work (I had put a link from the core install for the terrains to the server terrains, saves the disk space for 2 installs to one) Had to revert to 2 complete terrain folders, one for the core game and 1 for the server

Yeah, did that, I only get it on my server rig when I need to run the mission editor, main rig seems fine

Yes, at least I THINK so? Didn't see anything that looked like a refresh though, maybe I missed it

A full uninstall, then a full re-install of the DCS Modular server. At least it runs now as it should

Thats what I thought too. Tried the Steam Account on the DCS website, said Supercarrier was already licenced. This patch has been pretty bad for breaking things, had my server completely die afterward

I'm getting the same thing since the patch this morning for the TF-51D and Supercarrier. How do I re-athorize in Steam?

Sorry to keep posting, but more troubleshooting info: It seems that the dedicated server keeps overwriting the mission list line in serversettings.lua. I managed to populate the list so it shows in the GUI, but I have been unable to get the server to actually start (server offline, hit start WITH a mission showing in the list) I get "error starting server". Run next to the given mission does nothing, all are greyed out. I even tried starting a new server from the core game, still no joy. Copied the server setting lua from that to the serverrelease folder/config version og the serversettings.lua, still unable to start the server. I get the "loading" message in the gui, then the error.