Matt Glover

this seems fixed after last upate

same

Running Foothold Syria cold war

still an issue but can confirm people still see me in the F5

Quick update: If I disable the Remastered module it doesn't tag it. I save the mission then re enable the remastered and reopen the saved mission. the f5e is no longer in the units list. iIf I then open the original with the F5E remastered enables its tags it again. its like it thinks the Remastered is a Mod or "required module" and not just a default part of DCS

after yesterday's update it seems the F5 remastered is giving all missions saved with it present/installed with the: ["requiredModules"] = { ["F-5E 2024"] = "F-5E 2024", } This only started happening after the update and I do know that I can manually remove this by editing the mission file in the .miz but why has this started happening to a DCCS core module? Also if I do edit it out manually I run the risk of other who only have the base DCS not seeing the F5 AI/external module I'm in an instead it getting subbed in for the usual SU33. Example attached but its all missions edited after the update MA_Foothold_IR CAVOK DAY.miz

any chance of sharing how to make it standalone?

We are still gong strong always looking for fresh meat. currently we are rotating through Foothold, pretence and Training missions. https://discord.gg/VxqhuJYtq4

Sorry to Hijack this post but for anyone interested we have a UK armed forces DCS community which is supported and founded from the RAF Navy and Army gaming networks. https://discord.gg/VxqhuJYtq4

#BAFG server has this issue for quite a few users we run foothold on different maps

5950X and 4090 here CH47F unflyable in Syria. Track too long to upload. was fine in Gazelle and apache right before jumping in CH47F. dcs.logDxDiag.txt

inbound rules for DCS.EXE its not that hard to find.

it was a DCS entry in the firewall is all

yes

32GB On the server of which 15-20GB in use so I don't think that's the issue. I just don't know how to decipher the Log to see what went wrong if I'm honest so hoping someone might know wat to look for.

My server seems to keep crashing but only when players are on it. running a modified version of pretense and cannot figure out what's causing the crash. any help would be great. dcs.log-20240813-211703.zip server-20240813-165708.trk

Ill get back too you but its a CDU page somewhere. Think the same page you tupe in the tacan freq on the left starts TR then click the LSK to change

wrong there is distance readout if tuned right and on T/R

Update. The latest version added a new line to windows firewall and blocked it by default. Fixed by unblocking it.

It did for us but had radio issues.

to add contrast we don't have the issue with the UH-60L but haven't tried a load in other mods yet. sure your dynamic spawn are set up right?

already do this but after the last update DCS.exe as a program had been added and blocked. thanks im good now no need for further advice here

Hi I just had same issue with last update something made DCS get blocked by the firewall again but fixed by enabling and allowing connection through windows firewall. I think the new version added a new rule to the firewall that was blocked by default.

So I have run into a slight issue where dynamically spawning the UH-60L causes the radios not to work. May be the same with other mods I haven't tested. Its fine if I use a traditional spawn.

Using a weapons mod already in the user files I modded further: Made sure the A10A.lua is the current version. Added more options to carry. Extra Mavs. Extra rockets and different types of launcher. GBU10. GBU12 1/2/3. The LGB's automatically set themselves to code 1113 you need a JTAC or buddy lasing 1113 your Pave penny pod will pick the and lock the lased target in the HUD you just got to switch to CCRP and fly the line. Process to use LGB: Select A2G Select weapon CCIP or CCRP doesn't matter at this point Make sure buddy/JTAC is lasing target on code 1113 Fly so the Pave penny pod is pointing roughly at the lased target and wait. The Pave Penny will lock onto the target and display the lock in the HUD. Switch to CCRP and fly the line to release as normal. Buddy/JTAC will guide the bomb in so you can disengage and prepare for the next run. WARNING: install using OVGME and will break IC