Force feedback Joystick from Moza

[Mr_sukebe]

I use a Virpil Alpha on my AB9.

The analogue axes don’t currently work via the AB9.  The wheel brake axis currently operates as a button.

Moza have stated that the capability to use the axes will be added, but there’s been no timelines stated as yet.

[Koziolek]

28 minutes ago, Mr_sukebe said:

I use a Virpil Alpha on my AB9.

The analogue axes don’t currently work via the AB9.  The wheel brake axis currently operates as a button.

 

Does that mean that the analogue hat is not showing at all or is it working like buttons ( the same as brake axis)?

[MAXsenna]

Does that mean that the analogue hat is not showing at all or is it working like buttons ( the same as brake axis)?

Which Virpil grip do you have. You don't specify, and they all are not the same.

Sent from my SM-A536B using Tapatalk

[Mr_sukebe]

3 hours ago, Koziolek said:

Does that mean that the analogue hat is not showing at all or is it working like buttons ( the same as brake axis)?

Doesn't seem currently possible to map even buttons to the analogue hat.

I knew that before ordering, and have another analogue hat on my throttle, so doesn't really bother me if Moza take a while

[Wostg]

Could you firmware-set the axes to button in the VPC software first?

(no I don't understand how any of that works, thank you for asking)

[Mr_sukebe]

I believe that the Virpil firmware is applied to the controller board.

In the Virpil world, that exists within the base, not the grip.

[Scott-S6]

9 hours ago, Koziolek said:

Does that mean that the analogue hat is not showing at all or is it working like buttons ( the same as brake axis)?

The brake lever, mechanically, has both an analogue axis and a button. The base isn't doing any kind of conversion or mapping.

The analogue stick is analogue only. 

4 hours ago, Mr_sukebe said:

I believe that the Virpil firmware is applied to the controller board.

In the Virpil world, that exists within the base, not the grip.

Correct, there's nothing you can configure that will be transferred with the grip to another base.

Edited November 12, 2024 by Scott-S6

[zcaa0g]

A Discord poster from 22 days ago said the axis in the Alpha Prime was working, so not sure what the story is:

https://discord.com/channels/976306826947743766/1256056097924714672/1297867445935145031

 

[Hadeda]

I just got the Moza base and am using it with a TM warthog stick as well as a 10cm stick extension. FFB seems to be working ok but I'm not getting any haptic feedback when I fire guns, drop gear, flaps etc., even though I have them switched on in the options. Any idea what could be the problem? Thanks  

[VR Flight Guy in PJ Pants]

May I ask which plane were you flying and what profile was in use?

[Hadeda]

Flying the F18 and using the associated profile in the software. Have tried all three different modes - direct, telemetry and integrated...

[VR Flight Guy in PJ Pants]

Strange. I don't have this issue...have you tried any helicopter?

[Hadeda]

Yep, tried helos, warbirds but nothing. The shaking does occur when you reach a stall but there aren't any haptic responses to button presses. 

[VR Flight Guy in PJ Pants]

It is very strange. I suggest you need to bring your case up on the Discord and seek support. Sorry.

[MAXsenna]

I just got the Moza base and am using it with a TM warthog stick as well as a 10cm stick extension. FFB seems to be working ok but I'm not getting any haptic feedback when I fire guns, drop gear, flaps etc., even though I have them switched on in the options. Any idea what could be the problem? Thanks  

Have you checked the entry in the export.lua?

Sent from my SM-A536B using Tapatalk

[Hadeda]

Thanks for your response. Here's my export.lua (from the scripts folder which I assume is the correct one). I don't see any entries for the Moza base so perhaps this is the issue? 

 

local SimShakerlfs=require('lfs'); dofile(SimShakerlfs.writedir()..'Scripts/SimShaker.lua')
dofile(SimShakerlfs.writedir()..[[Scripts\SimShaker-export-core\ExportCore.lua]])
local vaicomlfs = require('lfs'); dofile(vaicomlfs.writedir()..[[Scripts\VAICOMPRO\VAICOMPRO.export.lua]])
dofile(lfs.writedir()..[[Scripts\SimShaker-export-core\ExportCore.lua]])
local SimShakerlfs=require('lfs'); dofile(SimShakerlfs.writedir()..'Scripts/SimShaker.lua')
local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua')

pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Services\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil)
 

 

[Hadeda]

Seems to be working now. I had to redirect the Moza Cockpit software to the correct DCS install path. Then the Moza entry was added to the Export.lua. I also placed this entry at the top of the lua for good measure. 

[Hadeda]

I'm faced with new challenges now  

1) When using the trim button in helos (Apache and Huey), I can hold the trim button and then move the stick to a desired location but as soon as I let go it jumps to a random location rather than staying in the new position. It makes it impossible to trim. The annoying thing is it was working earlier! I have attached a video showing the problem.

2) For a number of planes including the F4 and Sptifire, there is a constant pull upwards. No matter how much downward trim I apply (even to the max possible value) the plane will continue to rise. If I let go of the stick it shoots violently upwards. I have done several recalibrations, tried different profiles, settings, base restarts etc., but nothing seems to help.

Any ideas for how to resolve this would be much appreciated! 

[MAXsenna]

@Hadeda
1. What's your settings in FFB tune settings? Seems like x/y are incorrectly swapped/inverted. These settings (if needed) must be changed in every module. Unfortunately.
2. I have gotten this a couple of times lately in the F-4. Had to restart the module. Mind you, the points from 1. can be the reason. Have you watched the trim indicator in the Controls Indicator?

Sent from my SM-A536B using Tapatalk

[Hadeda]

18 minutes ago, MAXsenna said:

@Hadeda
1. What's your settings in FFB tune settings? Seems like x/y are incorrectly swapped/inverted. These settings (if needed) must be changed in every module. Unfortunately.
2. I have gotten this a couple of times lately in the F-4. Had to restart the module. Mind you, the points from 1. can be the reason. Have you watched the trim indicator in the Controls Indicator?

Sent from my SM-A536B using Tapatalk
 

Thanks for your response. I've tried different FFB Tune settings for Pitch and Roll, swapping Axis, inverting X and Y, but every time I press trim the stick jolts violently in a seemingly random direction. My force setting is 100 and Shake is 50 (both default). What should the correct settings be? It's not clear to me.

Edited November 19, 2024 by Hadeda

[MAXsenna]

Thanks for your response. I've tried different FFB Tune settings for Pitch and Roll, swapping Axis, inverting X and Y, but every time I press trim the stick jolts violently in a seemingly random direction. My force setting is 100 and Shake is 50 (both default). What should the correct settings be? It's not clear to me.

It's not random, and it's very easy to find the correct settings.
Swap - does exactly that. It swaps X for Y. Now, this is for the FFB only. Not the X/Y position when you move the stick.
Invert - is exactly that. It will make X/Y move the other way.
So, how to check. Hop in a hot jet. NOT the F-4. Remove the FFB tuning, and make sure the trim hat is correctly set. Now. Trim up or down, and if the stick moves sideways you need to swap the axis because X is now Y. If you trim up and the stick goes forward, you need to invert Y. If you trim right and stick goes left. You need to invert X. That's how easy it is to test. And like I wrote above, you need to apply those settings for each and every module.
For my MS FFB2 I need to swap axis in all modules. Do not need to invert in any.
Cheers!

Sent from my SM-A536B using Tapatalk

[Mr_sukebe]

Latest software update to the Moza cockpit has just arrived.

In addition to support for that well known Civ Sim, that's currently impossible to load, it also appears to have added:

 - Support for a well known WW2 combat sim that is currently being expanded to include early jets

 - An "expert" setting tab, allowing dead zones to be added

 - A "special" tab, that appears to allow "trim support for games that don't support FFB"

[Hadeda]

56 minutes ago, MAXsenna said:

It's not random, and it's very easy to find the correct settings.
Swap - does exactly that. It swaps X for Y. Now, this is for the FFB only. Not the X/Y position when you move the stick.
Invert - is exactly that. It will make X/Y move the other way.
So, how to check. Hop in a hot jet. NOT the F-4. Remove the FFB tuning, and make sure the trim hat is correctly set. Now. Trim up or down, and if the stick moves sideways you need to swap the axis because X is now Y. If you trim up and the stick goes forward, you need to invert Y. If you trim right and stick goes left. You need to invert X. That's how easy it is to test. And like I wrote above, you need to apply those settings for each and every module.
For my MS FFB2 I need to swap axis in all modules. Do not need to invert in any.
Cheers!

Sent from my SM-A536B using Tapatalk
 

Thank you! Inverting both X and Y axis did the trick and solved my trim issues. If I could buy you a beer I would :-). Thanks again

[Mr_sukebe]

1 hour ago, MAXsenna said:

It's not random, and it's very easy to find the correct settings.
Swap - does exactly that. It swaps X for Y. Now, this is for the FFB only. Not the X/Y position when you move the stick.
Invert - is exactly that. It will make X/Y move the other way.
So, how to check. Hop in a hot jet. NOT the F-4. Remove the FFB tuning, and make sure the trim hat is correctly set. Now. Trim up or down, and if the stick moves sideways you need to swap the axis because X is now Y. If you trim up and the stick goes forward, you need to invert Y. If you trim right and stick goes left. You need to invert X. That's how easy it is to test. And like I wrote above, you need to apply those settings for each and every module.
For my MS FFB2 I need to swap axis in all modules. Do not need to invert in any.
Cheers!

Sent from my SM-A536B using Tapatalk
 

 

Try going into DCS and unticking FFB.

When I did that, seemed to resolve it.  Option B, switch to telemetry in the Moza cockpit software.

My guess is that we're in early days and there's a few "areas of opportunity".  Feels good in telemetry mode.  The Spit is light and a bit mushy in normal flight, but then tightens up when performing Gs.

 

[MAXsenna]

@Mr_sukebe I guess that was for @Hadeda as I'm still on my MS FFB2 sans telemetry.

Sent from my SM-A536B using Tapatalk