Biggus

My feelings about my AB9 are a bit complicated and probably sound more negative than I intend. I love the hardware. The software situation lets it down in terms of both minor bugs and the failure to comply with the terms of the license for what they've taken from Walmis. The activity of the software devs on the Moza discord went from constant discussion before the discovery of the appropriated code to zero immediately after. If I had the time available to wait or to build, sure, I'd have grabbed one of those other options. The Moza was available immediately, didn't require me to put it together and was a reasonable price. If the Winwing FFB had been available when I ordered, I probably would have had a harder time deciding. With all that said though, I have a pretty big smile on my face every time I fly now. It's been quite transformative.

I'm more than a little bit impressed by this idea. Well done!

Has anyone with a Moza AB9 put together a decent profile? I've been toying around and taking inspiration from some of the Rhino suggestions and the pdf linked in one of the threads on the first page of this topic. I'm mostly interested in how people are modelling things like the buffet sliders. Right now, I'm at spring 0, damper and inertia 50, friction 40, game feedback gain 100 and using the DCS F-4 gain of 200 for pitch and 150 for roll. I've got a 200mm extension holding a Warthog grip, so that's a factor in how I'm setting things up.

This bug has apparently been reported by others on the DCS Discord. Hopefully it'll be squashed soon.

@tikijoetots37 There's definitely something about the Fishbeds causing the flickering effect. I'm not sure if it's something that Retribution is doing with the mission or whether it's a DCS bug. Right now, all I know is that there's no flickering at all if I don't have MiG-21s in the mission. I tested to see whether installing the liveries on the server would help, but it did not. I might try and copy the entire module to the server to test next.

A-4E mod was in the game folder, not the save games folder. Something I've noticed - Missions without Fishbeds seem to not have flicker.

Update - Although I've fixed the A-4 missing weapons issue, the flicker remains and I've just had a mission spoiled by a Fishbed that did not render and was therefore impervious to heat seekers. I've had Fishbeds fail to render a few times since this bug has been in effect. Haven't noticed any other planes doing it.

If green is one where you can place it at the middle of the seat, then I'd do that. I'd consider blue if running a pair of transducers.

That's pretty much exactly my setup, Retribution and that trio of mods. Repair has not worked, however I think I might have isolated the cause. Will report back in a day or so with a possible fix.

Well that's nightmare material! The A-4E weapons issue I've isolated to the server box. I created a mission as you described a couple of days ago. Weapons appear fine on my gaming rig. I have asked for assistance in the A-4 discord but I haven't had much luck there. I will retest that issue tonight as I begin to add the small number of mods I have again. However after a repair on the server, weapons are still showing a flicker every now and then.

Will it actually work properly with the Tomcat within a reasonable timeframe? I get that sometimes it takes a patch cycle for third parties to accommodate ED-driven changes, but at this point I've waited years to have it all working as well as it does for the Hornet.

I regret that I did not see this message roughly an hour earlier! @MAXsenna, you're absolutely correct. In hindsight though, I don't consider it entirely a wasted effort as just wiping the entire thing, downloading and then importing my binds helped clear out all the superfluous scripts I've accumulated over the last few years. The game is running a bit smoother as a result. Alas, the flickering remains. I'm considering the possibility that it's not my gaming rig at fault but rather my dedicated server that is causing the issue, as my wingmen have now reported that they are seeing the same flickering. That same server seems to have issues rendering weapons on the A-4E for some unknown reason, so I'm going to run a repair on that and see if I can work out the root cause.

I have seen this from the cockpit occasionally, but it is probably easier to notice from an external view just because of the amount of time I have eyes on those objects that tend to disappear. There is one other place where I see anomalies, and that's the F10 map. A grid will sometimes render and disappear with roughly the same timing. I'm going to do a full reinstall today, because I'm inclined to think it's just an issue on my end.

Not sure if this one has been reported or not as yet. Sometimes aircraft and/or their weapons flicker in and out of a rendered state. I've had an AI aircraft that I was fighting entirely derender during BFM. See video below for example.

I really hope the upcoming update can address this. There's a small subset of us that really struggle with the framerate being mauled under 900ft.

Not so much a complaint, more of an observation with my particular hardware configuration. People put travel limiters on Rhinos regularly, particularly with extensions like mine. The centre position of the stick in those particular modules is roughly 3/4 arm extension with my setup. I'm just looking for a way to limit the total throw to something a little more comfortable. I'm not touching curves in DCS at all though, just experimenting with the Moza software to find a compromise. I'm not convinced that all of the settings within the axis travel page work entirely as intended right now, though. The software limiter appears to function slightly differently at the ends of the pitch axis travel.

I'm really enjoying mine. My main gripes with my setup were that the neutral position of the Phantom and Tomcat seem quite far forward while my chair is in a position where it is as close to the stick as it can be without limiting pitch nose-up too much. Altering the offset for the pitch axis is one fix, but it reduces the output range pretty significantly with a workable value. Limiting forward travel feels a bit like it's creating a curve on the positive side of the stick, the raw numbers from the ADC stay within the 0-65535 range but passing through the middle there is a bigger voltage step per unit of distance travelled. Setting curves to compensate is a bit annoying right now because you can't decouple the forward of centre section from the rear of centre section. I've just hacked a joystick cutout out of my horrific ancient office chair and I think this might be most of the problem solved. Now I'm just interested in developing profiles, and I'm not sure where to start.

Mine arrived today after ordering on October 10. I thought I was prepared for the size of the thing, I knew the dimensions and I'd thought I'd made appropriate accommodations for it. I was still stunned when I sat it beside my beloved WarBRD, though. First impressions are really positive. Had to reorder my export.lua to put the Moza line at the top in order for SRS to work, and updating the firmware wasn't particularly intuitive, but I'm happy with my purchase.

+1 on this, it's quite frustrating. The helipads is definitely Syria only right now, a recent update introduced a fairly large number of them. Steps to reproduce: 1. Spawn into Phantom in Syria 2. Ask Jester to add an airfield to the flight plan, or to divert to an airfield. Depending on where you are on the map, there will be at least some helipads. In some places, they are the majority of options.

DHL have picked my AB9 up from Moza in Hong Kong and I've got an expected delivery date of November 1. Getting quite excited reading about everyone else's experiences. I've spent the morning re-rigging my floor mounted extrusion setup to accomodate the extra height, both with a 200mm extension and without. Note to self - 200mm extension on WarBRD with the TM stick is not something I want to try again. I've asked Moza about the possibility of a Winwing adapter. The software is apparently usable right now and we're just waiting on a hardware solution.

Probably best to ask in the Moza Discord. I'm sure someone there will have experience with a similar setup. The big question is, has it left Hong Kong yet? Interestingly despite being given tracking by their support on Tuesday, I didn't receive an actual 'it's shipped' email until late last night. It's still sitting in Hong Kong though.

I wholeheartedly agree with that.

Yeah, their customer service is leaps and bounds ahead of TM so far in my experience. After @Mr_sukebe's last post, I opened a ticket. A day later, I've got an apology and a tracking number. My account still says that it's processing, and the location of base is Hong Kong still, but it feels like progress.

Has yours shipped yet, @Mr_sukebe? I ordered on the 10th of October. Still processing.

DTC did it too. Was quite good. If it returns to active development, it'd be great to use the tool to build flight plans in the Phantom rather than the Jester menu.