All Activity

Man I don't know why nobody listened to you here but these same points are driving me insane. Why am I constantly being asked to go 2v4 against fighters that spawn 15 miles away hot, and then I only have Fox-2s? Their AI seems to know exactly where I am even when we're in clouds, but then I don't even have an AWACS to help me keep an eye on them. The first half of Mission 8 is awesome but I don't really feel like going through another 40 minutes of it just to attempt this bull<profanity> dogfight again.

HI Morse homing works perfect with preset frequencies and C38 but i can't succeed to use homing with C26 manual frequency ..... tried everything and always AGA morse code i undersand that the essex carrier frequency is always 190 Mhz that is minimum position of the C26 dial frequency but .... Readed on the F4U manual NOTE 1: As there is no correlation between the frequency range on the C-26 remote, the manual frequencies are set automatically at mission launch. Each airfield on the map will have a specific frequency. The frequencies are distributed in equal increments over the frequency range of the C-26 remote. The lowest frequency is always allocated to the aircraft carrier, if available. This is a convention specific to the simulator. NOTE 2: Both Preset Channel and Manual frequency can be ON at the same time if both CW-VOICE switches on the C-38 Control Unit and C-26 Remote are set to CW. If this happens, the navigation 42 MORSE signals will overlap, making the signals not intelligible. The pilot must make sure that both modes are not turned on simultaneously. What should i do ?

I don't use the Nvidia App, so there another way or command for insertion in the autoexec.cfg file for turning this on?

There's no active SAM scheme currently in the game, so every mod/asset pack adding ARH SAM have to use SARH or TVM.

Flying the MiG-29A, I encountered a situation where my R-27ER continued homing and destroyed an F-14 after I had been shot down by said F-14. At first, I suspected a lucky balistic flight, but the missile is actively pulling Gs and correcting even if target illumination stopped because I was hit by the Phoenix. R27_autotracking.trk R27_autotrack.acmi

Facing the same issue. I've actually faced similar issues with this campaign on at least 6 of the missions.

Mission 05 features AWACS but I can't create/set an existing waypoint as bullseye for better situational awareness as it's not mentioned in the briefing or the keel board.

hello. not sure if it helps. although i have no need to boot into safe mode for windows, i am running the latest geforce driver 581.15 for my 3090. no issues with DCS. note that some game titles are checking the system before installing their application. most recently for me was BF6 beta. i have always kept on the latest nvidia all along, and never had DCS problems. but again, i have not needed to boot to safe mode.

And another loadout that blocks all A2A like guns, AIM-9 and AIM-7 ...

I have 3 Standard Edition Monster Rhino kitbases in Stock. I am about to move in the next weeks so These will BE the Last ones for a while. I am offering These AS a discounted END OF SUMMER SALE rate of 540,- 3d printed PSU Cover IS included. Beltcovers are optional also at a reduced Sale rate of 20,- Shipping needs to BE added on top

hello this is likely a problem with your ISP or your own network equipment. it is not a system wide issue with DCS updates. the VPN cleans up DNS issues. it probably means your locally provided DNS is not the best. no offense. it happens to many users from all over. too many to count. i suggest you post your latest autoupdate_log.txt found in the DCS install folder. also test using ping and nslookup of cdn.digitalcombatsimulator.com try disabling your antivirus and firewall, checking your Windows hosts file for any incorrect entries, ensuring your computer's date, time, and time zone are correct.

hello both files you mentioned are core windows files ntoskrnl.exe or ntoskrnl.sys Hardware Abstraction: How the operating system interacts with the computer's hardware. Process Management: Handling the creation and management of running programs. Memory Management: Allocating and managing system memory for all processes. Security: Containing the security reference monitor for system security functions. Wdf01000.sys is a Windows driver file that belongs to the Windows Driver Framework (WDF), which hosts other device drivers like USB devices, Bluetooth, or graphics. loads on those two files is not surprising. but problems can also introduce BSODs. my suggestion is to run SFC /scannow https://support.microsoft.com/en-us/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e also check to see if there are any updates to the WINWING and associated drivers.

I have the same issue, haven't found a solution yet

FYI - I finally got around to the Win11 upgrade, and no need for any kind of process manager as far as I can tell. No sign of the demon lags like I was seeing before... So as much as we might love to hate on Win11 it at least does this better

Here is the mission. It seems i can not fix it.Maybe you can give it a look. Syria Operation Lizard Phase #1 .miz

^ I can only assume temp changes were slower / easier to manage (?) in RL, because when you think about it, P-51 was the only US WWII fighter with full auto cooling flaps. All the others, whether army or naval ones, were full manual or auto/manual hybrids.

Just a heads up...Don't forget to go into the LUA to allow use of the ED Sniper pod. I forgot to do that and now I don't have it...Might have to do a rebuild of DCS and double check all that when I reinstall the mods...

We don't know either how to fix it if you don't upload it, as a reference for future issues like this.

Just a heads up!! Don't forget to go into the LUA and changed the code to allow for the new Sniper pod to be used. I forgot about that and now I don't have it...

Here is the LUA. i fix it i run mission lua and it crashes again almanac[32] = {} almanac[32]["System"] = SAT_SYS_GLONASS almanac[32]["Number"] = 4 almanac[32]["Orbital"] = 1 almanac[32]["GLONASS_Data"] = {} almanac[32]["GLONASS_Data"]["NKU_Number"] = 795 almanac[29]["GLONASS_Data"]["Cosmos_Number"] = 2403 -- WRONG almanac[32]["Eccentricity"] = 4.054000e-003 AND HERE almanac[36] = {} almanac[36]["System"] = SAT_SYS_GLONASS almanac[36]["GLONASS_Data"] = {} almanac[36]["Number"] = 8 almanac[36]["Orbital"] = 1 almanac[36]["GLONASS_Data"] = {} -- WRONG almanac[36]["GLONASS_Data"]["NKU_Number"] = 797 almanac[36]["GLONASS_Data"]["Cosmos_Number"] = 2412 GPS_GNSS.lua

Open the script and fix it. Something in there is triggering that error.

Is it blue? Lol

Got it!! Changed a few lines but got to work, at least in the M.E. anyway. Full-fledged MH-47G with M-134's and all. Well, mostly...Still needs the waist gunner on the M-240's. Maybe ED will get into that at some point, who knows.

No, but I've heard they make a pill for that.

Hello mates. i am getting this error when i try to open my mission. Any idea how can i fix it?