ZeroReady

I may be wrong here and I welcome any correction, but isn't force correlate exclusive to the mav seeker itself and independent of the TGP? What I mean is, if you're relying on force correlate, shouldn't you be using the Mav as SOI and not using the TGP to target? I know that DCS uses LOS from various cameras and seekers, so if you're aiming right at a tank or a window in a building or whatever your laser or point track whichever you're using is actually going through the object to the ground behind. But just as general practice, to eliminate any erroneous variables, have you tried aiming with the Maverick as SOI opposed to the TGP? I never use force correlate so I can't offer any real advice sorry. I've done it in Flacon BMS but it's been a while.

You are an absolute legend. Just got my Gunfighter today, first thing I wanted to do was make the flip trigger work as it does in the bird, was a bit disappointed to see that it didn't. But your fix just made my day. Thank you!

You can change it to a finer setting in the lua if you didn't know. It's the only way to make it flyable in my opinion. You can dial back the speed at which the trim wheel rotates as low as you want. Unfortunately NineLine seems to not have the trim issue the rest of us have so it will probably never get changed and we'll have to update lua ourselves every time there's a patch.

Sir, all due respect, are you really saying that when you use a hat to trim the Mossie, you don't feel like the trim wheel in the plane moves way too much and too fast for every little tap on the hat? Everyone I fly warbirds with on a regular basis, a solid group of 7 or 8 people, as well as everyone in this thread, thinks that the trim wheel in the plane moves way too much given small inputs on a trim hat. As it is by default it is impossible for us to put the trim where we want it. Making the suggested adjustment to the lua is the only way any of us can trim the plane successfully, literally all of us agree on it. The group I fly with figured this out and made this change on day one of release.

I know for sure the A10C2 probe will not function correctly with pitot heat off. I have definitely seen airspeed errors when I forget to turn it on. So it is modeled in DCS itself, weather or not it's on every aircraft is anyone's guess.

If you have the TM TFRP pedals, the ones where the pedals ride along the metal rails on the sides, then you would really notice a big improvement if you took them apart and applied just a little bit of Nyogel 767a on the contact points that touch the rails. It doesn't take a lot, less is more with that stuff. It complete eliminates the sticktion and makes them really smooth.

I have a TM Warthog. In the twin engine aircraft I fly in XPlane, the B58, King Air 350, I use each throttle for an engine throttle, and control Mixture and RPM with hat switches. Works well enough there, I don't see why it wouldn't work in the Mossie. Hopefully we get to find out today!

It'll be better once we can set the burst height lower. I always set it to 700 feet in the Warthog, almost negates any effect the wind has on the parachutes.

If something isn't working in the Viper, TMS down is usually the answer.

After years of using both 97 and 105 I still don't really understand the advantage of the WCMD. I understand it uses a spi to CCRP drop to precise location via INS magic. Or something. But doesn't the CCIP sight use LASTE info to predict where a bomb would impact, also taking wind into account? If CCIP drops didn't take wind into account, wouldn't it be kind of useless? I can CCIP a Mk82 into the window of a truck from 15,000 feet. Does the 105 dispenser actually have guidance like a JDAM? Is it supposed to account for the parachutes blowing in the wind and burst at the right spot to negate the wind?

Not to mention when the crew is penetrated in vital compartments.

Got it thank you!

Last night I tried to put a GBU54 on a building, I wasn't going to lase for it just using GPS. My SPI was right where it should have been. The bomb fell short by about 100 feet. I adjusted the SPI forward next to try to Kentucky windage the bomb forward. Came on the same heading and altitude as the first drop, the bomb hit right on the SPI which was now forward of the building.

The yaw channel is holding the heading until you apply pedal pressure. Then it will try to hold whatever new heading you end up at when you get off the pedals.

Question is does the WCMD use the DCS way of reporting wind direction ie where the wind is blowing to, or does it use the way the rest of the world reports wind direction ie where the wind is blowing from?

If you are in CCIP, place the pipper on the thing you want to bomb when it's still a few miles out, press and HOLD weapon release. You will now be in CCRP with whatever you selected with the pipper as the target. Keep the VV lined up with the steering cue line. Keep holding pickle and the bomb will drop when the release cue passes through the velocity vector as in CCRP.

OK got it thanks for the explanation!

This is my question. IRL the pilots feet are strapped to the pedals. It doesn't seem like it would be easy to remove one's feet from them in flight, then get strapped back in when it's time for pedal work. So I'm just curious how the switches are actuated.

This makes it sound like the pilot takes their feet off the pedals.

How does a Hip pilot remove their feet from the pedals to actuate switches? Aren't they strapped into them? Serious question.

First mission, ATC gives the pressure as 2833. Setting that on the altimeter puts me at 0ft baro elevation even though Vaziani is at 1519 feet. 2992 would be correct with the altimeter reading 1519 on the ground. I feel like if I set 2833 I will be failed for being 1500 feet too high if there are altitude restrictions. Am I wrong in thinking that the barometric altimeter should always read elevation above MSL not ground? We have a radar alt for elevation above ground.

I'm doing the a10 tactical qual campaign again after a few years. First mission, ATC gives the pressure as 2833. Setting that on the altimeter puts me at 0ft baro elevation even though vaziani is at 1519 feet. 2992 would be correct. I feel like if I set 2833 I will be failed for being 1500 feet too low if there are altitude blocks.

Well it seems I figured out the problem but I don't know which it was. I ran a repair (stand alone version) then I got the bright idea to TMS down with Mav as SOI before trying to change modes. I'm inclined to believe the problem was that I wasn't hitting TMS down first but who knows.

I just experienced this today, first time back in the Viper in a bit. I am completely unable to change the Mav mode. Clicking the OSB does nothing. Is this common or only happening to a lucky few of us?

It used to be that with flight director off, and the 3 main channels on, you would hold the trimmer, get the bird set how you want it, then release the trim and it would hold everything. It feels like it's still doing that I guess, but on the heading tape at the top of the hud, there used to be a carat that would illuminate over the heading you had when you release the trim and that's what it would hold. That carat isn't there anymore.