Biggus

After having used the original script for awhile, I've been really happy with it. I was hoping to exclude the terrains and cockpits using this set of parameters but I've been getting an error when I attempt to use what's in the quote above. Any idea of how to fix it? dcs-texture-optimizer.ps1

Just adding because I'm seeing some odd behavior when enabling AFMF and Super Resolution in the AMD software. It takes a big hit in frames from 900ft down, just like the 3070 did. Running vanilla MSAAx4, there's a tiny drop but it's barely noticeable. I'll experiment with Optiscaler too over the next few days just for the hell of it.

The work looks absolutely stunning. That said, long nose liveries on short nose Phantoms are an affront to all that is holy. I'm not going to look in this thread again until we get a proper Naval Phantom, but I do want to encourage you to keep making excellent skins.

Just in the SA map? I tended to get that on every map with the old GPU. I haven't tested it yet with the new one. My coping strategy was to make sure I did a proper case 1 so I'd be close enough to the boat to load the textures so I wouldn't get the stutter during the actual recovery. I also found a script that changed all the ridiculously large textures to smaller ones so I wasn't getting a big VRAM overflow in situations like that. I've had a few more flights on the SA map now and I've turned a few things up like forest and scenery details, clutter, some of the shadow options. I probably see the same number of fps cut off on average, but it's not anywhere near as noticeable at 120fps as it is at 60fps. I still don't think it's necessarily a hardware issue given there are 4090 users that have reported suffering from it, but I think there might be combinations of hardware, drivers, background processes and the like that might be the killer here. I might have just been very lucky.

So I've just installed a 9070XT after having a 3070 since release. I'll need to test more, but just in the first Phantom free flight mission, I took her down to below the stutter threshold. I immediately saw the frames take a nose dive. 50fps, which is probably about 5fps more than the old GPU at that point. Just as I was beginning to curse my luck, the framerate increased. I assume that it had a few moments where it needed to build some shaders and then I was back to ~120fps. Will see how it plays out over the next few days. I've had posts in this thread before when I thought I'd found a fix and it turned out to be a false hope.

Earlier Fishbeds and Floggers, more Fitters, some Flagons and Fiddlers, some Badgers and a Blinder or two would be great additions. Some support assets would be nice too. A-3s in tanker and jammer variants, some EC-121s and Grumman's Tracer and Tracker would be lovely. And in between adding aircraft, it'd be nice to see an SA-7 and a Redeye too.

Yup, for the DMAS Phantom.

LORAN would also be good if it's possible to implement.

Anyone else having issues getting the Tu-16 to launch missiles? Bombs are fine, but I can't see to get them to launch any of their missiles at all.

You might or might not be aware of some of the shenanigans that Thrustmaster have played with their connector design. That might be a factor in your confusion too. Things like adding shapes to the casting to prevent them being used with other brands.

I don't entirely understand this thread. I don't have any problems at all using the TM Hornet and Warthog on my AB9.

Thank you @Hagen! What model toggle switch did you use? My E-ten 1322 looks ever so slightly different in the middle part of the switch.

Great work @Jar72. Hopefully it'll get added to DCS BIOS soon!

I hope for a J or an S. If it's going to be a single flight model module, I'd expect that it would be a J as it covers a really wide timeframe with several distinct variants from the first lead-nose birds through to the Super J and the pre-slat J/S. Not to mention the J (UK) variant.

Thats more than fair, just a thought bubble.

Search for F-14. I'd have assumed Virpil would have had a fairly standardised protocol given the usage of the 5 pin mini DIN and their range of other sticks. I don't think that's a completely unreasonable assumption to make, even if it's obvious to you. I didn't post to complain about the apparent lack of effort to implement support but rather to express disappointment about the situation in general.

Was wondering if it was possible to do waypoint entry on the Phantom using Scratchpad?

I believe it's the actual Moza branded Winwing adapter, so I'd be surprised if it didn't work. I was about to post a question about whether anyone has tested the Virpil VFX as I'm keen to buy one if Virpil ever produces another run of them, but a few hours ago someone posted on the Moza discord talking about their issues with the AB9 and the VFX. The Moza response has been that they can't do much without obtaining a stick to test. Not very reassuring for current VFX owners, and disappointing considering how phenomenal the Tomcat is with FFB.

Would you mind sharing your revised files? I've attempted to duplicate the original design a couple of times without success.

I made this a few months ago using an ESP32, a couple of GC9A01 displays and DCS BIOS.

The voice change caught me by surprise! This is a genuinely useful bit of software and I'm surprised it isn't used on more public servers.

I did end up buying Kola and it's brilliant. No issues. SA is far prettier though IMO. Hopefully one day the sub 900ft performance issue will be fixed.

I'd expect most modern FFB bases to have some gain adjustment. From what I remember of the VPForce rhino, you can alter it in software and possibly also on a potentiometer. The Phantom has some gain adjustment in it's DCS settings which aren't available in the Tomcat as of today, so I generally alter that via DCS and the Tomcat I just adjust via sliders in the Moza software.

@JupiterJoeMy AP is fine, with some tweaking. Moza with a Hornet stick with a 75mm extension, previously a Warthog stick on a 200mm extension. I think we talked a bit about my experience in the Moza thread, but I'll add a bit more after some more stick time. I do occasionally see some pitch-up with alt-hold engaged if I bank aggressively. If I disengage alt-hold and then bank, I don't get nearly as much of a pitch-up and I am normally turning with roughly zero vertical speed so re-engaging the alt-hold is easy. The caveat is that I haven't tried this with normal gain on the gimbal, because I found many of the AP functions somewhat unreliable until I turned the gain up to roughly 160%. But for 98% of my AP usage, it's rock solid and I have zero complaints. ACLS is quite broken though. Things seem to work well up until roughly a mile out, and then it goes from being steady as a rock to unpredictable and somewhat suicidal. There are some other oddities like the behavior when you spawn into a Tomcat after being in some other modules, where the stick is limp. The way that hopping from the back seat into the front results in an immediate violent pitch up is quite inconvenient. There are probably other issues I haven't touched on. I know HB are aware of most or all of the problems and I'm confident that they'll eventually fix them. There are several long threads on the HB discord. But in normal usage it's a fantastic implementation. I know you're after more feedback from others, so maybe ask the same question on the VPForce or Moza discords, because you'll probably get a much better response there.

Hub's not actively developed and is increasingly out of date. Save yourself the pain now and just switch to the FP fork.