drallabco

Just hit the SEQUFC button in the bottom left of the DATA page on the HSI. Then Hit "INS" for Insert. Make sure the bottom right has SEQ 2 (Or whatever sequence you want it in) Selected, Then type the waypoint you want in the sequence in the UFC, then hit enter and Bob's your uncle

Indicated: what the indicator shows Ground: how fast you are moving over the ground True: how fast you are moving past the air molecules True airspeed differs from indicated because as the air gets thinner, the ram air pressure on the pitot tube goes down, thus indicating lower, but we are still moving past those air molecules very quickly. They're just not producing the same pressure as they would at low altitude where the air is thicker. So, true airspeed is corrected for air temperature and pressure at a given altitude.

When you box the climb option on the FPAS, you get an airspeed for best climb on the HUD. A couple of questions regarding this: 1. What is this climb speed giving? Vy? A cruise climb for Max Range? A fuel conserving climb for Max E? Because these speeds will all be different. 2. What is the power setting for this climb speed? There can be any number of combinations of pitch and power to get that speed, but obviously, you'll be burning more if you're full burner and 30º pitch up. Best guess is that it's a mil power climb and you're pitching for the airspeed on the HUD. 3. Is there a way to set ATC to hold FPAS Climb Airspeed?

+1 can confirm, wrong computer right now, but have a track as well that I can upload if I remember

Are you pressing TDC while trying to slew? And you can't have a WP designated and slew. Have to choose one or the other. Have to undesignate to slew.

>Remarks

Not always. PIREP just stands for Pilot Report. Could be about the state/condition of a runway surface. It can really be for anything, but yes, it is typically a weather report.

Same problem here. Spread out on the EW page, but clumped on HUD.

In my experience it's still pretty tough to see unless I get pretty zoomed in even at .7 tacan distance. Doesn't get clear enough to see at regular zoom until about .4-.3

Now we just need an IFLOS that's actually visible at 3/4 mile. Glad ED is making fixes though, the community greatly appreciates it!

As they should be. MSL is useless in this case and since we have a radar altimeter, AGL is far more precise in terms of hitting the same numbers every time.

Exactly. Anything that runs off the bleeds reduces engine power available because this pulls compressor air. This compressed air can then no longer be used in the combustor cans to combine with fuel and create power. Whether DCS models bleed air losses is something I'm not sure of, but until then, I'm gonna leave my engine heat off unless I'm actually flying in icing conditions.

Hadn't seen that before. Still no response from ED on the issue though. The natops even states conditions for when you get an inlet ice warning- .025 inches of ice on the left engine probe. This ice cannot form in these conditions, therefore, no warning should appear. You can see this info on the NATOPS page referenced in page two of that post you linked. Thanks for the info.

Anyone who knows anything about aviation weather knows that for structural ice to form, the temp can be anywhere from 2°C to -20°C and that there must be visible moisture- clouds, rain, mist. I get that friggin inlet ice warning on every flight when it's clear and a million. Maybe DCS doesn't have a way to know if you're in visible moisture, but I'm pretty tired of hearing that advisory pop up when it's physically impossible that ice is forming.

This has GOT to be it. Thank you so much for the update. This was really frustrating me. Thank you so much. So does the Maverick work if you just turn the DDIs off on VCS?

Happened to me too when I choose to selective jettison an empty fuel tank. I will try to get a track file together and add shortly.

Having DUD displayed on the HUD with all LGBs. Followed the steps in the Wags training video and have included a track file and a mission file of the flight I had the problem with. Please let me know if there is anything else I should include. FA-18C LGB DUD Issue.trk JTACTest-Day.miz

Didn't have this issue in other versions. Anyhow, if anyone is having this issue, I just reinstalled the Hornet. Also, not sure who changed my post title...mods? My post was originally titled "AGM-65F Display Issues"

Any time I try to use the AGM-65F at night, I have nothing displayed on my DDIs. I make sure to slew to the ground and the seeker will even lock...I shot down a light pole last night... The DDI, however, displays absolutely nothing, not even the DDI button options like "SHIP" "FOV" or Fusing...For some reason, I can only replicate this at night. During the day I have no issues. Is this simply because it's night or? I can attach the mission file I use as well if that is helpful, not sure how to do that, but can put it into a dropbox. This is on both the PG and NTTR maps, have not tried on Caucasus. The same mission set to a time when it is light out does not reproduce the issue I have.

I believe this means that if your target is cold, it should, in theory display as black; if your target is hot, it should display as white. The TRACK WHT/BLK should change whether your seeker will lock a cold target or hot target. At least that's how I understand it. Someone else can probably tell you more with better accuracy.

Any time I try to use the AGM-65F at night, I have nothing displayed on my DDIs. I make sure to slew to the ground and the seeker will even lock...I shot down a light pole last night... The DDI, however, displays absolutely nothing, not even the DDI button options like "SHIP" "FOV" or Fusing...For some reason, I can only replicate this at night. During the day I have no issues. Is this simply because it's night or? Thanks

Do you have it set up on a single monitor? If so, how do you have the MFDs set up? This is where I'm having my trouble. Also, I believe the best way to contact OP is through the SIMVC website. I emailed them last night and got a response this morning. Haven't heard back regarding the single monitor/MFD issue I've been running into.

Okay, so I've sorted some of my problems. All of the buttons work as advertised, but having a really hard time getting the displays to show up on the ipad. When I go to configure the displays, none of the overlays show up unless I restart my computer. I can set them up, and then they end up disappearing when I go to adjust them again.

I had a hard time getting it set up. Do you know if there is a tutorial anywhere? The manual had me confused. Maybe just need to give it a second look

I'll do it. Here's the link.https://forums.mudspike.com/t/dcs-vr-iflols/6293