Biggus

@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.

What control reference is that? If it's BIOSBuddy, it's pretty out of date.

Ah, good stuff. I'm happy to talk with him, it's great for immersion. Just the issues with the interaction interface that I find a bit frustrating in this case.

Wonder if this is why the Voice Attack commands haven't worked for me. Hey Zabuzard, related question - can I preempt Jester's questions by telling him that we're going below 50ft before we hit the point where he normally asks how low we're going? Or will Jester ask the question even if I've told him before we taxi?

3070 pleb here. The combination of the two new presets and dlls with the optimised textures powershell script has been remarkable. I've been able to crank my view distance out to the highest settings with water, cloud and shadow settings that I wouldn't even consider previously just using DLAA. Unfortunately it breaks IC, so I've only been using it on my private server.

Haven't really paid attention to roll angles, but no issues with alt hold at any wing sweep up to high subsonic speeds. Once you get to about .9 the AFCS has a hard time maintaining stability. Push past 1.2 and reengaging the alt hold is fine though. The rocking backwards and forwards is the AFCS maintaining your altitude. The stick should move a heck of a lot more during ACLS recoveries, but that doesn't seem to work very well unfortunately.

Anyone had issues with the Mirage F1 using this? I've had a lot of missing textures.

Yeah, R7 is the one to remove. You'll want to keep that resistor on the ends of the bus. So one at the last device and one at the master. These breakout boards are one of those rare cases where I'd prefer to just use the bare chip and add my own biasing and termination resistors, not to mention being able to place the caps closer to the IC power pins. This post is a wealth of information.

If you're using the breakout boards, have you removed the bus termination resistors on the boards that aren't at the ends of the bus?

I've gone from a WarBRD with a TM Warthog on top of it with a 200mm extension to the AB9 with a TM offset adapter that adds about 75mm with a Hornet stick and I feel like I'm not missing much.

Try to plan some missions without uncontrolled AI and see how you go. I've gone from all users having crashes within an hour every night on my dedicated server to maybe an unrelated crash every two or three weeks.

GX12 extensions have arrived. They work. Unfortunately I ordered the 100cm ones and not the 100mm ones. But that's not the end of the world and it probably gives me a little more flexibility with my console layout. The next question is going to be about how to tension the arms. I don't think it would be wise to rely on the tensioners within the base, so I'll need to do it externally.

Yes.

It's not even just VR users. I'm flatscreen and it renders the map largely unusable to me.

See this post.

That's really valuable input. Thanks, @Cgjunk2!

Dropping settings probably helps mitigate the issue enough to mask it. But people with 4090s on flat screens still suffer it.

I'm open to different materials. My plan at the moment is to mock up the arms and then have them made in alloy once I'm happy with the geometry. I did find the files for the 3d printed replacement arms and had a good look at them in Fusion, but STL files aren't particularly easy to work with when it comes to making changes. But I've been using them as a reference for the designs I'm working on. I was planning on doing very much like you're suggesting, sandwiching the base arms with the extension. I'll report back when I've got something useful to show.

I've worked out that they're GX12 connectors. I've found some on Aliexpress in a few lengths already assembled, so I ordered a pair of 100 mm extensions. Left throttle is six pin and right throttle is three pin. I'm working with an original Orion 1 without fingerlifts, so it's going to be less complicated for me on that front. Next step will be to design the plates. I'll start with PETG prints with six walls and a fair bit of infill. I've got a small CNC that might just be able to do some alloys, but it looks like it's 5.5mm thick which is probably outside the capability of my machine. MDF might be worth a try.

I'm slowly building a left console and I'm hoping that I'll be able to make the throttle grips a bit taller. Has anyone else done this before? Are the connectors mini-DIN like the joystick? Any potential traps that might need to be considered?

@Hagenthat's beautiful! I'm really interested in how you designed your solenoid switches. Could you share how you did it? I've been tinkering with electromagnets but I'm not completely happy with them, I'd love to see your solution.

The very talented guys behind Retribution have narrowed it down to an issue with uncontrolled aircraft. When they become active, they sometimes start flickering and moving oddly and stop rendering, and when another unit interacts with them (shoots them down, for example), clients will freeze. By setting all AI aircraft to warm starts or air starts, the bug doesn't seem to occur. @BIGNEWY this is might be worth mentioning to your team.

As the old thread was closed, I'm adding a log for both client and server. I sat in the F10 screen and ended up getting a better handled crash with logs this time. dcs client.log dcs server.log Edit: Here's a clip from another mission where you can see when the freeze happens. This is two F-14s shooting at a Flogger that stopped rendering about 10 or 15 minutes after the mission started. You can hear audio freeze prior to video and I can still move the map for a moment or two. I've added the client log for this mission too. dcs client log for video freeze event.log

Okay, that's genuinely the funniest comment I've ever seen on these forums.