Jump to content

Darkdiz

Members
  • Posts

    222
  • Joined

  • Last visited

Everything posted by Darkdiz

  1. 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
  2. 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.
  3. 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.
  4. 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...
  5. 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
  6. 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
  7. 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.
  8. 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
  9. 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.
  10. Ended up re-installing through the launcher, seems fine now
  11. @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
  12. Yeah, did that, I only get it on my server rig when I need to run the mission editor, main rig seems fine
  13. Yes, at least I THINK so? Didn't see anything that looked like a refresh though, maybe I missed it
  14. A full uninstall, then a full re-install of the DCS Modular server. At least it runs now as it should
  15. 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
  16. I'm getting the same thing since the patch this morning for the TF-51D and Supercarrier. How do I re-athorize in Steam?
  17. 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.
  18. So when I looked for terrains folder, IT HAS DISAPPEARED! Perhaps when I did the full repair, it put it into the backup004 folder. Restored, so we'll see what happens Seems that even if I manually edit the serversettings.lua file, it gets overwritten so that whichever file I add gets deleted from the lua. Also, even if I manage to get a file into the list, it will not allow me to add a second file to the list
  19. Tried your suggestions, no joy. Attached my settings lua serverSettings.lua
  20. Did a FULL repair, tried renaming the serversettings.lua to .old so it would rebuild, still no joy. Tinkering, will post if I can get it running
  21. This miz file was the one that was running prior to the update. I can't add ANY miz files to the list, there were several in there prior to the update. Mission list after updated server start has nothing in it, but won't let me add anything, I get "error starting server" and the list remains empty.
  22. Had to get it off the server rig, here they are. Lots of errors, was working fine prior to the update autoupdate_log.txt dcs-20250326-151135.log
  23. Anyone else having issues with the hotfix from today? I updated my server, the GUI sees it, but won't connect, says server error. All my missions in the server list have disappeared, and it won't let me add anything. I have the core game installed on my server rig as well as the server, when I updated I did the core game first, then run the updater from the server folder. Usually when I update the server it looks first into the core game for the files, and downloads the delta. This time it did not appear to do that. I ran a server repair (had to copy the updater repair .bat into DCS World Server folder). Said it was repaired successfully after I ran it. When I run the server it gives the correct version on the splash screen (8394). When I run the GUI, it says server detected, it seems to connect, but I get the server error message in the bottom left, and it won't let me start the server at all. I completely rebooted my server rig, the problem persists. I'll try and find the server log on the server rig and post it
  24. The all function always seemed to work for me previously. I went in last night, discovered that individual stations are a workaround, but seeing the F1 All stations USED to work, for me anyway... Update: After much testing, turns out that if there is more than 1 GBU-10 on the LCFT, it sticks on 1511 laser code. If only 1 GBU-10 is loaded, the laser code works fine, and can be changed as necessary. GBU54s seem OK, I was able to change the code on the LCFT without issue. From this, it seems that if there is 2 GBU-10s loaded on the LCFT, it sticks. Obviously more testing needed.
  25. Just tried to change the LGB code via the radio groundcrew menu (/, F8, F8, F1). The window comes up, the mouse up/dn symbol appears, but clicking the L or R mouse button does nothing, the code in the window seems stuck on 1511. Tried on several different bombs, GBU 10, GBU 12, none seem to work. F-15E Used to work fine
×
×
  • Create New...