A101Wayz

The in game airspeed is showing indicated airspeed. But in the editor, you have to enter TRUE airspeed. To get a little closer to your desired airspeed, you can use this calculator: http://www.csgnetwork.com/tasinfocalc.html For the OAT correction factor, I've found that .015 is pretty accurate at 1000 ft MSL, and .019 is pretty accurate at 20,000 ft MSL. So a factor of .017 will put you in the ballpark (within 5-10 knots) at whatever altitude your tanker is at. These numbers are based on an altimeter setting of 29.97 and a temp of 68 degrees F... What doesn't make sense about this setting is that telling a pilot to fly at 300 knots, he should fly at 300 KIAS... what his airspeed indicator says. And NOT TAS.

Did you place statics? Statics don't have labels...

I've never downloaded or installed the non steam version. But I would assume that you would install it like the Release version. One point to note: the Beta version and the Release version are incompatible with each other in Multiplayer... So if you have friends in multiplayer that you fly with, you won't be able to enter the same servers together unless they switch to the beta version as well.

The F-14 is still in Early Access. You have to be running the Open Beta version of DCS. V2.5.4.28461 If you're using the Steam version of DCS, just select the game in your library, right click on it, select properties and on the Betas tab, select "Open Beta - public beta versions". It will then install the Beta version and you should have access to your F-14

Best advice I can give is: Moderation.... Baby steps... Crawl first, then walk, then run, then FLY! Don't try to master a perfect pattern landing all at once. Start out by launching, coming around and lining up for a landing by the seat of your pants... Leave the arresting hook up, and do a touch and go. Second pass, concentrate on maintaining a constant airspeed. Third pass, concentrate on airspeed and altitude. When you get comfortable with your pattern and approach, drop the hook and catch the 3 wire. But the important thing is to have fun. Just fly the Cat for the fun of it. After a while, the precision will just creep into your flying completely unnoticed.

Today, I was out for a joyride in my new F-14. It was a warm, clear and windless day. Perfect for just tooling around and getting acquainted with the Tomcat... After about 30 mins, I decided it was time to head back to the carrier. So, I instructed Jester to tune the TACAN to the carrier freq, switched the steer point to TACAN and started into a steep left back towards the HSI carrot. Sun streaming through the canopy, watching the HSI to roll out on the correct heading... and suddenly, the sun illuminates a big smudge on the HSI glass. I reached out to try to clean the smudge a little and *BANG* my knuckles hit the edge of my desk! :idiot::doh: Kudos to the Heatblur team for a job so well done, that I tried to clean up after them.

After a LOT of playing around with the radios, I found that VA needs to be updated to work with the F-14. Actually, I don't remember if it was VA or ViaCOM Pro that needed to be updated, but if you're checking for updates for one, you might as well do both. :thumbup: Once the update was finished, the single button coms set up works on the F-14... Hope this helps

Ahhh, so I can't open the coms menu with the ICS button... I've only used the one button so far. Guess I'll have to map the other buttons now. Thanks!

Ok, so I've been flying the A-10C, F/A-18 and the UH-1H and using Voice Attack and ViaCom Pro for all my radio communications. And to date, it's been working flawlessly. However, to install the F-14, I had to switch to the OB install. So I really don't know if this is an OB issue, an F14 issue, or that I'm just missing something. For the life of me, I cannot contact ANYONE on the radios in the F14. Whether using VA, or using the menu to make contact. I.E. I want to contact the tanker to refuel... I tell Jester to tune to the proper channel. I verify on the radio panel that he has selected the proper channel. I can hear the tanker broadcast that he is on station. I request rejoin either by VA or radio menu. I sometimes hear my pilot make the request ("Texaco... Ford 1-1... request rejoin") and .... NOTHING. the tanker never responds. Same is true for all communications, Towers, Carrier, AWACS... What am I missing??? :helpsmilie:

Another way that should work... When the command to Embark or disembark is given, set a user flag to true. Then make a new Once trigger with the condition "Time since flag" with a time of 20 seconds or so... Then play the voiceover... Just a thought

If all you are looking to do is simply display the fuel stats, you can use the following code: for i, unitObject in pairs(Group.getByName('flight'):getUnits()) do local fuelstring = string.format("Unit %i fuel : %f",i,Unit.getFuel(unitObject) ) trigger.action.outText(fuelstring, 30) end Bear in mind, this does away with the storage of the fuel status in the table "flightFuel" because it's unnecessary, unless you plan on using that data later. As for triggering when to call this code, I'll leave that up to you....

No. The example script merely stores the fuel status of each unit in the group into the table "flightFuel", and only the amount of fuel at the time that section of script was executed. You would have to add an output method to the script to print the fuel status to the screen.

Correct me if I'm wrong, but with the ONCE/NOEVENT type of trigger, wouldn't it keep testing for that condition until it's TRUE? Therefore, it keeps testing until your 25% random chance is achieved... (yielding 100% chance) So, you could set two triggers like so: Trigger #1 TRIGGERS: ONCE/NO EVENT CONDITIONS: ALL OF GROUP IN ZONE (SINGLE A10, New Trigger Zone) ACTIONS: FLAG SET RANDOM VALUE (1,0,100) Trigger #2 TRIGGERS: ONCE/NO EVENT CONDITIONS: FLAG IS MORE (1,75) ACTIONS: GROUP ACTIVATE (MIG-23)

World V2.5.4 Yes.

Almost thru the campaign now. (Just got the Huey a month ago). Fantastic work, Wavehopper! I gotta say, I'm enjoying this campaign way more than the stock UN campaign. (I never wanted to wear a blue helmet!) A few things that must have been broken recently... In both mission 6 and 9, player helo spawns inside of an AI helo, to a catastrophic end. It seems that all helos have somehow been set to spawn on pad #1. For those trying to fly the campaign, it's an easy fix... Open the mission editor and load mission #6. (it's located in C:\Users\[uSERNAME]\Saved Games\DCS\Missions\Campaigns\en\Wavehopper Medevac\Medevac 6.miz) Don't zoom or pan the map around --- no mission spoilers! Click the "View Unit List" button on left toolbar. (near the bottom with a triangle, diamond and square in it) uncheck everything except "Helicopters" click on each helicopter listed, one at a time and IF Waypoint 0 is set to "Take off from parking" in the right hand Group Editor panel, then change the "PRK" parking spot, so that each helo is set to take off from it's own spot and no two helos take off from the same spot. From the menu, save the mission with it's original name and in it's original location. Do the same steps for Medevac 9.miz Exit the mission editor. Get back to flying!:pilotfly: Thanks again for all your hard work, Wavehopper!

"Clicky Cockpits" are a must have for VR... It's very difficult to use a keyboard to control the aircraft when you have to peek thru the gap between your nose and the headset. It may not seem like it right now, but it's actually quicker to use the mouse and click on the switch/dial/button you need. And it's not that much slower than it would be IRL... So, unless you have a fully functional cockpit (not very mobile) or a joystick with several dozen buttons, switches and dials, the clickable cockpit is the way to go. Especially, if you plan on using VR in the future.

Are you trying to randomly activate just one of those triggers? i.e. to randomly select a single CAP. Or, are the triggers all for different things?

The aesthetics of it all was what I was going for... Mainly on tankers. Now you have to be aware of those escort aircraft when you're refueling, and when you disconnect and peel off... (Plus it's kinda cool to be refueling and look over to see the pilot's helmet in the escort next to you. :D )

Actually, It's working quite well now that I've separated the tasks to Follow and Escort, rather than trying to accomplish it in one single task... Escorts don't leave the asset (until Bingo Fuel), they don't let the enemy slide right up into the formation and shoot down the asset, and they don't run away and leave the asset to fend for himself. (all of which I've seen while trying to use just TaskEscort() ) Just something I wanted to accomplish for a WIP mission I'm setting up for the anticipated F-14 release, next month (hopefully). EscortTest.lua Escort Test.miz

Not only could I not get any aircraft to spawn at Maykop, I couldn't get any to spawn from any other airport. Only aircraft I could see was the one that spawned in the air. I saw no errors in the log. However, I created a new mission and dropped some aircraft in the same parking spots and all was well. My suggestion, start from scratch...

OK, I think I just got it figured out... originally, I was issuing the TaskEscort to each UNIT in the group (to get a nice looking, tight formation)... I changed the TaskEscort to task follow for each unit. Then issued a TaskEscort to the GROUP of escorts... and viola! it worked.:doh: Like so: local units = escortgroup:GetUnits() for i, unit in ipairs(units) do local task = unit:TaskFollow(LeadGroup,formation[i]:GetVec3(),LastWP) unit:SetTask(task,1) end local task = escortgroup:TaskEscort(LeadGroup,formation[1]:GetVec3(),LastWP,EngageDistance, TargetList) escortgroup:SetTask(task,1)

Thanks for the response! IS there a certain combination of ROE and ROT that need to be set? I've tried not setting them, and several combinations (though not all). All resulted in various (and sometimes hilarious) results. But none resulted as expected... Guess I just need to keep experimenting...

Can I kill a thread, or what? OK, lets try this question... Why is it that no matter what distance I put as the EngagmentDistance parameter for this task, the escorts leave the escortee and fly directly at an enemy target the second it's detected, regardless of the distance to target? unit:TaskEscort(LeadGroup,formation:GetVec3(),LastWP,EngageDistance, TargetList) Shouldn't the escorts ignore any targets until the target approaches to within EngagementDistance?

Awesome news! Thanks for sharing it!

Did you get the chance to try out that solution? This should do the trick without the need to mess with user flags (provided you have a function "soundtoblue" that works. local function PlayMusic(params) soundtoblue(params.track) end local M1 = missionCommands.addSubMenu("Play Music", nil) missionCommands.addCommand("Play Track 1", M1,PlayMusic, {track = "music1.ogg"}) missionCommands.addCommand("Play Track 2", M1,PlayMusic, {track = "music2.ogg"}) missionCommands.addCommand("Play Track 3", M1,PlayMusic, {track = "music3.ogg"})