Amarok_73

I am not sure if You are aware, so I'll ask if after calibrating the axle, you center all of them before you save the settings? I know that thumb stick is centering itself by default, but this is the only reason of such strange behaviour that comes to my mind...

Sometimes - that was my scenario - the joystick grips comes from factory with wrong settings for analogue axles, and require correction/calibration in Virpil software so You should have also the Virpil base (or borrow one) to do it prior to connecting the grip to the Moza base.

...yeah, and there's still no option to enable the LST from the pilot's seat...

Just search the MIST or MOOSE for "net.dostring_in" and You'll know from where to expect unexpected.

Some time ago it was possible to "preselect" SKR in ACQ, and as soon, as the laser spot was caught by the seeker, the crosshair was placed over the lased target. Right now, the way to overcome the limtation that came with change of this behavior, is just to observe the rectangle that follows to some extent the pilot's head, and as soon as it became large and solid, we have the indication that the laser has been spot by the Hellfire's seeker. This moment we know, that it should be possible to switch ACQ on the SKR. I once saw a thread somewhere where @NeedzWD40 explained it quite comprehensively, but I still have hard moments with getting the point, why the dotted cross can't appear automatically, without having to "hunt" for the moment when it becomes possible to turn it on. If it would work as it was initialy implemented, it was pretty natural, that selecting the SKR prior to getting the spot, pilot (or CP/G) declares he has need to see the crosshair as soon as the laser is spotted by sensors. Such behavior rather contributes to improving situational awareness and shooting precision. Apparently something deeper must be escaping my overview of the subject.

Hello, I would like to kindly inquire whether the implementation of a north direction pointer in the TADS is currently under consideration. Such a feature would greatly enhance quality of life and improve spotting efficiency, especially during multi-aircraft operations.

Hi, You can define group entirely with Lua. This is what does Enchanced Gamemaster Script where You can find the Gamemaster_Templates.lua file, which contains plenty of templates definitions.

I've hardlocked the FPS slightly below the minimum shown without lock (about 10 percent) and my graphs are now flat as... Earth.

You brutal, you take pleasure in taking away hope, huh? They could include one in with collision model in the package with module...

Can I have keybind for Collision Steering in the RIO position, please?

That's the preferred setting exactly for the reasons You said. When I'll be back "in cockpit", I'll share my settings. There's chance You'll have some better ideas than I do.

With the FFB joystick in use, the optimal cornering isn't just matter of keeping the plane at the point (energy, speed and G wise), where the tension on joystick is highest, and when the one feels that it get's lower pulling it more, means he screwed the optimal parameters, and should unload adding the power just to regain that tension?

Exactly. They're not "combatible"...

In Moza software, there's indeed separate set of parameters for jet engine rumble, but they're active when Telemetry FFB is in use. But this vibration, that you described quite accurately is evidently related to the Direct Input mode, which gets the effects from the simulator. And to be honest, I wouldn't mind this effect if I'd have FFB hardware like Rhino, but Moza AB9 doesn't feel as robust as the Rhino, and it hasn’t been on the market long enough to truly gauge its durability. At the same time, it’s expensive enough that, for someone with limited means like myself, the abundance of unnecessary features raises concerns about how long I’ll actually get to enjoy the device. Yet.

I prefer to fly on very low settings when it comes to the basic ones like spring, intertia, friction, damping and such. There are a lot of parameters in the Moza Cockpit software, but they are all grouped functionally, very clearly and comprehensively described, so it is quite easy to analyze the origin of a given effect that interests us. We could get a grip on the Discord, so I could show You how does it look on my side, and perhaps that would be beneficial for this investigation. However, I still secretly dream that maybe one of the HB representatives who are knowledgeable about the subject will jump into this topic and simplify the whole process.

@Raven (Elysian Angel) Thanks for comment, but I've already checked all the other options and this one apparently comes from the direct input, meaning the game sends this to the joystick, not the software. I tested this by turning off each of the telemetry parameters in the Moza Cockpit software and checking whether it affects the strength of this particular effect. Only the Direct Input option with the aforementioned shocks in the in-game axis binds enabled causes this shaking and it is proportional to the value of the vibration parameter set there. Switching to FFB telemetry in the Moza Cockpit only also causes this effect to disappear (similarly to turning off vibrations when using Direct Input), but also others, the lack of which significantly worsens the quality of the interaction the plane has with me using FFB. Therefore, the only sensible option for flying the F-4 is "Integrated FFB". It is true that you can set the proportions of mixing the effects from Direct Input with FFB Telemetry so that this effect is minimal while maintaining the other effects to a relatively satisfactory level, but the one coming as I assume from the engine, will still not disappear and will be felt all the time.

Forgive me for asking, but for me this is a fundamental question - is there a planned function that would allow the deck crew to be sucked into the engine?

Hello, I’d like to ask if anyone knows whether it’s possible to disable the force feedback (FFB) engine-related shaking effect. I recently switched from the G940 to the Moza AB9, and I've noticed a constant vibration during straight and level flight. This seems to be caused by direct input rather than "Telemetry FFB" settings. Disabling the in-game shaking feature (found in the axis binding settings) does stop the vibration, but unfortunately, it also removes other effects that I’d like to keep. Is there a way to disable only the engine-related shaking while preserving the rest?

The benefit from using DLC goes far over the drag it create. And as the others above stated already, airplane reaction on throttle, flaps and stabilator is pretty latent not to say sluggish on low speeds and that's where the DLC comes with succor. Without changing the approach geometry and delay, the one can put corrections to the approach path.

Gentlemen, one little correction, name of this geographical region is "Strait of Hormuz", not "straight", like the narrow passage.

All right, so I am looking forward. Thank You for the information @Zabuzard.

Hi @IronMike, Now, when the Jester is open for our scripting ambitions, would it be possible to publish the sources of official scriptis as example and support for better understanding the possiblities? In the manual, there's link to the GitHub page mentioned as dedicated place for such examples and modders to share mods, but so far it's still "the page we're not looking for", and the current examples from manual to some (like me) may seem a bit too modest... Or perhaps there's another already active place for such purposes that I am not aware of, that some good soul could point me to?

If You did not noticed, this poll is not addressed to all, but strictly to the Apache pilots. I hope, that others respondents have noticed it and those not flying Apache did not took part in it.

I am not sure what You mean by "skewed", could You elaborate please?

Sadly it's not IC compatible...