Hawkeye91

+1 Would be nice. Looks like they were used by Hornets in ODS. I don’t think it will be as simple as just adding them to Hornet though as I would think they would have to program the CCIP and CCRP low and high drag ballistics https://www.dstorm.eu/pages/loadout/f-18.html

Huh, surprised the function isn’t just bound to the selected display so it would still work with Targeting pod and HARMs/Mave, but I guess it doesn’t have to make sense if it’s accurate

@Tholozor Should the behavior still change when using LMAVs since raid/FLIR/FOV has no function for them?

The RAID/FLIR/FOV button doesn’t change the FOV with short press nor does the long press switch between IR/TV. Chuck’s guide says it should. I sensor select the ATFLIR first. The button does nothing. It works on the radar in TWS.

So you can lock a moving target in GMT with sensor control switch right and drop a bomb on it using CCRP, but the mode currently doesn't compensate for target motion velocity and the unguided bombs always land some distance behind the target. Now I know that I could just use LGBs and Mavericks, but I want to simulate some ODS (operation desert storm) combat where they might actually use things like the GMT IRL and a typical loadout might be Mk20s or some other GP bomb so I want to know if GMT should be compensating for target motion when predicting the bomb fall line for release. Anyone know?

Glad to here it thanks! My Super Libra + Super Taurus is on its way as I type this!

I thought the Viggen has anti skid, no?

Ordered off amazon. Thanks man

Where I circled is where the play is. Is there anyway to tighten that up?

I want to get the Taurus base, but will it be compatible with the Winwings new F16 grip? I only ask because it appears the F16 grip has the side wall modification for the idle cutoff and after burner detents. Would they even be able to make something like that work with the Taurus throttle base?

No, crosswinds are pretty much a death sentence in this plane. Even just normal landing roll out with no thrust reverse I start oscillating with just the tiniest amount of rudder input. I’ve tried the rudder aileron interconnect on landing and it seems pretty impotent at really helping with directional control on roll out. if you watch the landings in F2 view you can see the rudder slam side to side at full deflection. Yaw dampers shouldn’t be that aggressive from my experience.

The Viggen has a yaw damper that I believe is way over correcting yaw inputs making it extremely difficult to maintain directional control while landing. When I land I get horrible yaw oscillations that often result in me going off the side of the runway, even with a high curve on my rudder axis. I can fly and land warbirds, helicopters and the only plane that gives me yaw problems is the Viggen. I don’t remember it always being this bad.

eh, I'm just trying to play Liberation generated missions. Messing with start times and stuff is too much fiddle farting around for my patience.

Will the Viper throttle grip be compatible with the Taurus base?

yeah I did try this, though I was also trying to trap, not launch, so I don't know if it works for any planes on the deck or only the player.

Realistically carriers would have launch configurations and recovery configurations. I don't know what plans are for the future of the SC module, but a simple toggle ingame to swap the carrier between launch and recovery, would help prevent AI from trying to simultaneous launches and traps and prevent the feedback loops. I guess this could almost be a wishlist item to make large operations with AI more manageable. Thanks BN

I'm trying to play Liberation missions and when ever I return after I finished my sortie, the Deck is 100% of the time always jamming up because AI aircraft trying to trap prevent the deck crew from launching a plane waiting to take off on that catapults while simultaneously forcing the AI to do constant go arounds/wave offs so its stuck in a feeback loop and makes it pretty much impossible to get back on the deck nearly 100% of the time.

@LJQCN101 Hey, hate to dredge this up again, but it seems like the JF-17 is falling on its tail while trying to aerobrake when landing. After touchdown, if you leave the control neutral, it will continue to pitch on its own until the tail hits unless you push the stick very far forward to counter act it. It seemed like this was fixed before but now its happening again. Anything changed recently? Edit: a quick test with a light loadout and a heavy loadout, the light loadout didn't pitch up and scrape the tail, but the heavy full loaded one did. Maybe its a weight and balance issue? Edit 2: I've attached a second trackfile where I landed with a full heavy loadout and fuel and I made a very soft landing with a modest pitch up attitude between 8--10 degrees. I then let go of the stick while it was stable there and as the plane decelerated it pitched and back on its tail from about the most textbook landing I could make. JF17 Landing.trk JF17 Perfect Touchdown.trk

yeah I really hope we get a hotfix before ED is out for the Holidays otherwise I feel like we're going to be sitting on this until late January I'm afraid.

Just noticed I had this problem as well. Hopefully we get a hotfix or the Viggen is going to sit for a loooonnng time before the next patch.

Yeah this is exactly my question. The A10 works off the principle of a "SOI" or sensor of interest, ie the sensor that all other equipment will be slaved to, and for the main target point it as a SPI or sensor point of interest that the SOI will be initially slaved to. The SOI doesn't really exist in the F18, instead everything is just slaved to the SPI and when the targeting pod is moved around, it simply just moves the SPI the other weapons like Maverick will be slaved to. Problem being that the Mavericks will still be slaved to the original SPI location before you moved the pod instead of slaving to the current SPI when you sensor select the Maverick which makes you have to undesigate the original SPI, sensor select back to the pod, and back to the Maverick, to get the Maverick to go to the current TGP set SPI. From a human factors standpoint, this feels like terrible design. Did they really engineer it this way? It just doesn't seem right.

I thought about this and TWS auto does not let you slew radar elevation in Auto mode. Also I don't have an axis bound, Its bound to buttons on my throttle. I even tried taking control of the track to see if I could manually set the elevation in auto, and it doesn't move.

So currently, when I want to use IR mavs on a moving target, I start by designating a target waypoint with the WPDSG to get the pod looking in the right direction. Then, I move the pod over to the moving target and “auto track” it. Sensor control switch to the Maverick, but wait! It goes to the waypoint instead of the TGP! So I have to press undesignate, sensor control to the TGP, then back to the Maverick, only then will it slave to the TGP, but if it doesn’t track I have to repeat the undesignate, sensor control off and back on the Maverick to get it to reslew itself to the targeting pod because it doesn't follow the TGP. Also I'm unable to manually slew the Maverick seeker to the target while the pod is in Auto Track because undesignate doesn't work to actually allow for manual slewing. This workflow seems incredibly janky and it feels like I'm doing something wrong. Also while the TGP is in Auto Track, you can't manually slew the Maverick to adjust it. The whole system seems rather cumbersome. Am I doing something wrong or is there a better way?

Attached Trackfile. Using TWS auto the radar sets itself to max up radar elevation. Radar bug.trk

Any updates on this? Still seems to be a thing. It doesn’t happen at all in the Mi8.