Wizard1393

Wow, I think you're all talking about the exact same thing but seeing it differently. Yes, the throttle is used to manage sink rate, not speed, in landing configuration. Yes, throttle adjustment will also cause the FCS to change pitch of the aircraft to try to maintain set AOA. @NeilWillis I was unaware the the TVV is a sinkrate indicator in landing configuration... I doubt it, but even if it is, the plane DOES in fact change pitch slightly with throttle adjustments, anyone can see that.

Not intirely true but sure... The true size will also be correct if your in game FOV setting (zoom) corresponds to the true FOV that is made up of view cone angle made up between your eyes and the sides of your display. But that means playing at a FOV of ~25 degrees for all the time, for most "regular" screen setups, and that offcourse would not work as it would look way too zoomed in. You would come close® to "correct" FOV with a VR set or a triple monitor setup.

Good find! Hope this gets fixed!

I have a feeling you are correct. I've noticed this too. I'm not sure though.

Or, your could just navigate with command prompt to "C:\Program Files\Eagle Dynamics\DCS World\Mods\Aircraft" and there type: del *.diff.lua /S That deletes all of those files recursively.

This.

Have you guys tried the well known trick to delete the folders "fxo"and "metashaders2" directories within your "saved games\DCS" folder? That have been known to fix some shader problems, like this might be.

@falk85 what would you like? More base defenses? Less available Blue AI help? 1.3 is coming soon. Expanded Mission Area Red EWR coverage Better GCI handling

Yes. Second mission was indeed stuttery / jumpy / small continuous hickups Also, BRC on the boat in the first mission is wrong.

:thumbup:

Another usage question. I have a mission with a RED EWR network, detection and AI_A2A_Dispatcher setup with only GCI. Squadrons set at three airbases with unlimited resources. Blue task is to capture the airfields RED is using for GCI. What is the correct way to have the Dispatcher stop spawning GCI fighters at an airfield once it goes blue? I've tried setting the squadrons resources to 0 like below example, but that does not work. I have not found a way to "delete/remove" a squadron, as in "A2ADispatcher:RemoveSquadron("LAR") A2ADispatcher:SetSquadron( "LAR", 'Lar Airbase', { "LAR MIG-23" }, 0) EDIT: Would a re-init of an existing squadron at a different base overwrite previous squadron settings and hence stop GCI from, in the example, Lar Airbase? A2ADispatcher:SetSquadron( "LAR", 'Kerman Airport', { "LAR MIG-23" })

Ok, thanks! Ill check that out! EDIT: I don't fully understand github I guess. Which is the "latest" development branch? There are several branches with the word "development" or "develop" in them... EDIT2: I downloaded the branch "develop" that seem to be it. But there's just an almost empty moose.lua in there. Apparently you have to "build" the moose.lua file for use with DCS yourself from an LDT environment. Could anyone provide me with a pre-built moose.lua from the lastest dev-branch? EDIT3: Nevermind. Found it. :doh:

So, a question regarding the Detection class. As per my testing, it seems like the detected status of an aircraft "sticks" even though it goes out of an EWR's scope of detection. In my test I set up a RED EWR network, and AI A2A Dispatcher GCI response range at ~60nm. I set up a Blue AI Hornet at 20 000ft start alt at ~80nm from target base, and succeeding waypoints from 75nm out, at 100ft AGL towards the target base. I carefully checked that it is terrain masked all the way up to the target. So the EWR detects the Hornet on its way down from 20 000 ft, prior to reaching it's first 100ft AGL waypoint. No GCI response, as it's still out of the GCI range. The Hornet is terrain masked from ~75nm and all the way to the target. However, when passing the GCI range at 60nm, the AI A2A Dispatcher still spawns a GCI fighter when the hornet passes the GCI range at 60nm. IMHO, shouldnt the detection object purge detected aircraft outside of it's scope? To verify that this is in fact the issue, I set the Hornet up at 100ft AGL starting alt and let it fly all the way to target base and it works. No GCI is scrambled since it's never detected by EWR.

Yeah, to be honest, can't wait for either one of yous twos story driven campaigns for the Hornet, once that is feature complete.

I got a little bored with DCS yesterday and went ahead and bought this campaign. I've only played the first two missions, but HELL YES! Loving it! Well done Ranger79! Hoping to see more campaigns from you! You and Baltic Dragon should merge into one great DCS campaign superhero! :thumbup::pilotfly:

Its here. Hopefully it's like the last patch where most (all?) updates to the Hornet were omitted.

This. Just, please. Make it like this. Wasn't there an official statement that there would be a significant FLIR overhaul years ago?

Sadly, nothing at all for the Hornet in the update today :( Except for another fix for sliding on the deck... EDIT: Apparently quite a few changes has been made with no mention in the update release notes. :)

Yes you can do this. Create the first trigger and add action "flag on" on flag 1. Create the second trigger with condition "time since flag" and specify flag 1 and the time you want in seconds. Then add your do script or group activate action to it.

+1

Most often the AI will not descend to less than 300ft AGL.

So, Hamburgler, you said the Save Game Scripting would be released as a standalone package? Where can I find it? I'm very interested in taking a look at this. :)

SITUATION: Two months ago a successful US covert intel operation has revealed and delivered proof to the US administration that Iran have been producing nuclear weapons for quite some time. Since then, the US and NATO with support of most of the western countries has publicly condemned the operation and demanded Iran to cease and desist immediately and allow UN personnel access to the locations and oversee the dismantling and/or destruction of the production sites and already produced weapons. Iran has not responded to any of the US/NATO demands but instead been making aggressive threats of retalliation for the unapproved US military operations in the country. US/NATO has been conducting intel/recon flights close to the Iranian border for the past 3 days, and is now prepared for a full scale invasion of Iran with a first goal to gain a foothold of southern Iran. BLUE TASK: Mission goals: (In any order) Seize Qeshm Island Airbase Seize Havadarya Airbase Seize Lar Airbase INTEL: There are several low to medium range SAM systems (SA-6) on and in the vicinity of the target airbases. There are several EWR's in the general theatre area which looks to be defended by SA-6 systems. Destruction of EWR's should be a priority to lower the enemy ability to detect and intercept our flights. Intel suggests there are an SA-11 Buk system close to Lar Airbase. AWACS DARKSTAR is enroute and will be on station orbit at BULLS 207 for 80, watching the airspace. TANKERS 'Texaco' (KC-135), 'Shell' (KC-130) and 'Arco' (S-3B) is enroute and will be on station orbit at BULLS 208 for 70. Arco should only be used for refuelling in case of emergencies. AI SUPPORT: Called in through F10 menu options under Mission Command. AI CAP flights will have callsign Springfield. AI CAS flights will have callsign Colt. AI SEAD flights will have callsign Uzi. Map Marker AI targets: Create a map marker, type SEAD or CAP in the textbox. Use mission command menu to launch a flight and choose Map Marker option. CVN-74 John C. Stennis is currently located about mile outside Umm Al Quwain in UAE waters, grid CP53. The Stennis is on a 15kt BRC310 cruise, and plans to get to grid BQ43, which is roughly 70nm 180 from Lar Airbase. All flights have preconfigured flightplan: WPT1: Qeshm Island AB WPT2: Havadarya AB WPT3: Lar AB (Some flights have WPT4 which is homebase) Radio/TACAN Frequencies: Mission: 254Mhz AM AWACS: 243Mhz AM Shell: 251Mhz AM, TCN 45X Texaco: 251Mhz AM, TCN 46X Arco: 251Mhz AM, TCN 13X John C. Stennis: 127.5Mhz AM, TCN 12X DOWNLOAD

Invasion Iran SITUATION: Two months ago a successful US covert intel operation has revealed and delivered proof to the US administration that Iran have been producing nuclear weapons for quite some time. Since then, the US and NATO with support of most of the western countries has publicly condemned the operation and demanded Iran to cease and desist immediately and allow UN personnel access to the locations and oversee the dismantling and/or destruction of the production sites and already produced weapons. Iran has not responded to any of the US/NATO demands but instead been making aggressive threats of retalliation for the unapproved US military operations in the country. US/NATO has been conducting intel/recon flights close to the Iranian border for the past 3 days, and is now prepared for a full scale invasion of Iran with a first goal to gain a foothold of southern Iran. BLUE TASK: Mission goals: (In any order) Seize Qeshm Island Airbase Seize Havadarya Airbase Seize Lar Airbase INTEL: There are several low to medium range SAM systems (SA-6) on and in the vicinity of the target airbases. There are several EWR's in the general theatre area which looks to be defended by SA-6 systems. Destruction of EWR's should be a priority to lower the enemy ability to detect and intercept our flights. Intel suggests there are an SA-11 Buk system close to Lar Airbase. AWACS DARKSTAR is enroute and will be on station orbit at BULLS 207 for 80, watching the airspace. TANKERS 'Texaco' (KC-135), 'Shell' (KC-130) and 'Arco' (S-3B) is enroute and will be on station orbit at BULLS 208 for 70. Arco should only be used for refuelling in case of emergencies. AI SUPPORT: Called in through F10 menu options under Mission Command. AI CAP flights will have callsign Springfield. AI CAS flights will have callsign Colt. AI SEAD flights will have callsign Uzi. Map Marker AI targets: Create a map marker, type SEAD or CAP in the textbox. Use mission command menu to launch a flight and choose Map Marker option. CVN-74 John C. Stennis is currently located about mile outside Umm Al Quwain in UAE waters, grid CP53. The Stennis is on a 15kt BRC310 cruise, and plans to get to grid BQ43, which is roughly 70nm 180 from Lar Airbase. All flights have preconfigured flightplan: WPT1: Qeshm Island AB WPT2: Havadarya AB WPT3: Lar AB (Some flights have WPT4 which is homebase) Radio/TACAN Frequencies: Mission: 254Mhz AM AWACS: 243Mhz AM Shell: 251Mhz AM, TCN 45X Texaco: 251Mhz AM, TCN 46X Arco: 251Mhz AM, TCN 13X John C. Stennis: 127.5Mhz AM, TCN 12X Download

Hey all, Don't know if this is known or not, but trying to spawn aircraft "From Runway" works only in SP, not if hosting the same mission in MP. At least this is the case with the PG theatre.