dingoniner

So yeah, INS definitely plays a role. In free flight, starting straight and level, autopilot works fine. Turn the INS off, and autopilot doesn't work at all. Turn it back on, it still doesn't work (not calibrated?). Master Caution said "AUTOPILOT" and "INS DEGRD" So the issue is..what am I doing wrong on startup with the INS? I'm pretty sure it's calibrated properly, and I have no INS DEGRD when I'm flying. More research is in order...

Barometric altitude is determined by the static port, and is calibrated with an altimeter setting.

I would think that the autopilot altitude lock doesn't need to know your altitude. It's not going to maintain any particular altitude, it's just going to prevent it from changing. It's not hard to measure a change in altitude (a change in pressure). When the pressure drops, your altitude has gone up. But I'll try a full startup again and make sure I have no INS degradation, and see if this makes a difference. Thanks. Update: Even with no INS degradation, I still get a Master Caution and neither barometric nor radar altitude hold will engage. But it does work if I start a flight in the air. I must be doing (or not doing) something during the startup that is causing this. Any insights? What am I missing in the startup?

I have my joystick deadzones at 100%. I'm at 10,000 feet, vertical velocity is zero. And my BALT won't function, gives me a master caution. HOWEVER....if I go directly into free flight, the autopilot functions wonderfully. The times that it doesn't work are when I go through the engine start process. Anyone know what I might be missing during the startup? I see INS degradation as a caution, but would that cause a simple BALT to not function?

So here's one for you: My default FOV for the FA-18 is 20.1 degrees higher than the value I set for "default view" in <User>/Saved Games/DCS/Config/View/SnapViews.lua. This happens regardless of what I set in DCS World/Mods/aircraft/FA-18C/views.lua, and regardless of what I set it to in-game with RT-ALT Num0. No clue why.

I realize this is an old thread, but FYI, having anti-skid does not decrease stopping distance. The purpose of anti-skid is to maintain control of the craft while it stops, not actually "brake better." Just Google "does anti-lock decrease braking distance" and you'll find plenty of reading material.

I wonder why this is so complicated. When I open the mission editor and look at the livery skins for the F-18, I see that they are being pulled from C:\Program Files\Eagle Dynamics\DCS World\CoreMods\aircraft\FA-18C\Liveries\FA-18C_hornet When I look at the livery skins for the P-51D, I see that the skins are being pulled from C:\Program Files\Eagle Dynamics\DCS World\Bazar\Liveries\P-51D And I see that although all the tutorials say to put them here, no livery skins are being pulled from C:\Users\Me\Saved Games\DCS\Liveries\ (Even though kneeboards are being pulled from C:\Users\Me\Saved Games\DCS\Kneeboard\) So....where exactly do I put custom and downloaded liveries for my aircraft?

Same Issue Same issue here in the F5, easy to reproduce (happens every time). I have a workaround involving a repeating mission trigger.

Okay, found it. I put the enemy aircraft right on top of mine in the editor, and when I fly the mission, he's right in front of me. The aircraft IS there, it's just not visible on the map. If I go to mission editor, I can force "all icons" to appear on the map. Problem solved. Thanks again David for taking a stab at it. :-)

Still Having Issues I've posted a very short clip of me creating a mission here: https://youtu.be/lHVkLs_FeM0 Would anyone care to take a look and see what I'm doing wrong? Thanks!

Thanks David. It looks like my mission is set up the same way as yours. Tomorrow I'll follow your entire video and see what happens, then I'll change one thing at a time until I have the mission I'm looking for. Thanks again.

I want to create a very simple mission to practice air-to-air combat. I create a mission, start time is 8:00am. I add an F5, set it to "client", 16000 feet, with one waypoint to the northwest. Northwest of this, I add a Mig, set the skill to average, altitude to 16000 feet, headed northwest. He starts at 8:00am as well. I add a few waypoints for him to fly, all to the northwest. I start the mission. In the mission briefing map, I can see the Mig. In the mission briefing text, one possible threat is the Mig. When I start the mission, the Mig is not there. Not in sight, not on the map, not on radar, and not in any view. Can anyone tell me what I'm doing wrong? Thanks in advance.

I've been trying to do the F5E TACAN navigation lesson most of the evening. Speaking as a pilot, I have to say that the lesson is just completely inaccurate and counter-intuitive. I hope that someone reviews that one day and changes it so that it makes sense. I could go into details if someone is interested, but I suspect that's not the case lol. But seriously, it's completely borked. Just an FYI. :-)

Thanks for the replies. I created a brand new mission and it seemed to work fine. The new one that I created was identical to the original mission that didn't work. One P51 plane, take off, fly to three waypoints, land. The original mission kept circling out over the water, but this new one worked. Not sure what the issue was, but starting from scratch fixed it. Thanks again!

I cannot get any aircraft to land on any airfield as part of a mission. Like, ever. They will take off, fly to any point I specify (although not always a direct route), but when I add a waypoint to land at an airfield, any airfield, they fly to the approach end of the runway, then circle indefinitely. Am I missing something?