DI think so. With the TM F-18 grip, I do not seem to be able to get the stick to recognize the hat switch, it recognizes it as button pushes. If I change the grip in the setup menu to a Virpil grip, it sees the hat switch as a hat switch, but then inverts the effect of pushing the switch, even though in the VP program I see the 'arrows' correctly displaced.
Wroger that, can you list the hat buttons that light up in the VPforce configurator, I'll add those to the next firmware as hat switches.
something like - "up:11, down:12" etc
something like - "up:11, down:12" etc
DI have them memorized, LOL... Buttons 13, 14, 15, 16 starting at the left 9 o'clock position and cycling counter clockwise.
DI plan on working more on it today.
DYep, very weird. I cannot seem to get the hat to register as a hat, it only registers as a button push.
PThat's not an unusual setup. Wouldn't it be better to be able to define the center with the offset in the calibration?
WYou still need to balance it in software for good force trim performance
DEureka moment! Okay, by selecting Virpil CM50 grip, it activated the hat switch, shows as Hat 1, then by reassigning the trim functions to Hat Viewpoint 4 in the controls page, it is working! It is making some of my other switches, notably the small Up-Down-Press switch that is not found on the real F-18 grip, but is added on the TM grip, appear to DCS as a hat switch. A little weird there, but definitely workable.
DThe only other thing I changed was inverting the Y axis in the DCS control software, and then checking the Inverted box in the Y axis for the VP Force config software.
PTrue
WDoes the axis movement indicator correspond to actual axis movement in the VPforce config tool? If the axis is inverted, then there might be issues with wrong force direction.
SIf you have inverted the axis in VPForce config and it moves in correct direction in the indicator then you shouldn’t need to invert it in DCS also. Try to uncheck the invert FFB Y-axis in DCS if you have that on.
DI will check again.
DI am getting a lot of Motor X FAULT_ENCODER_MAGNET, I am getting a lot of Motor Y FAULT_ENCODER_MAGNET, messages... is this because I have the Gain too high? Seems to happen when I make sudden moves with the stick.
DAlso occasionally get Motor X: FAULT_UNEXPECTED_D_CURRENT messages for Motor X and Motor Y.
WYeah, some gain is too high and it enters protection mode.
Can you show your settings?
Can you show your settings?
DI am using the default profile from the Import. I can post it later.
Afwiw, was doing some experiments a while back and loaded up the default profile, and noticed it had a tendency to spin out into faults quite easily, and so reverted back to my profile
Aso wondering if the default profile needs some tuning
WAsk? Can we get a DCS Section with Sub folders for each A/C so we can discuss specific tuning issues in those channels? Looking for assistance with DCS-F14-Auto Pilot - Alt Hold issue. I think it might be Sim-A/C specific.
Athat might be a bit overkill since there are many aircraft and modules, but what are your specific questions?
WDCS-F14-AP-Alt Hold - won't lock in / hold alt select alt with in game F14 specific FFB option on/or off when using TelemFFB. Getting ready to go down the rabbit hole of troubleshooting.... eg. with/without TelemFFB etc. Just wondering if anyone actually has it working with DCS 2.9 Beta.
WNote: There is an old DCS forum post about the F14 AP Alt Hold not working well, which was supposed to be patched, but need to verify current state with community to determine if it is a DCS / FFB / etc issue.
Ahmmm, AP hold has generally been working fine for me, although I did a mission the other day, and was potentially noticing that it wasn't totally holding properly, or rather, it kinda was, but was swinging a bunch back and forth (i figured it maybe was related to turbulence or whatever, so i didn't really investigate further)
Ait would be good to see if you can isolate more though -- e.g. is it an issue with telemffb not running?
Amaybe take it a step further and also try a session with FFB in general disabled just using the rhino as a default spring joystick, and see if it's still an issue
Ait also wouldn't surprise me if there's some DCS bug lol
WYup, ok down the troubleshooting rabbit hole I'll go. I'll report back with what I find. Can you PM me your TelemFFB config and VPForce Configs for comparison?
Amy vpforce config isn't really anything special, everything on 100%, except periodic effects at 50%, and friction at like 10%, all other default effects are essentially disabled (i have a balance spring I think though?), i can't get telemffb for you right now cause my stuff isn't connected so telem won't show me settings (currently workin rn too)
WNP, I'm also technically working...... we can touch base later when I have some notes to share.
DThe F-15E feels really loosely-goosey in the stick unless I crank everything up. A module specific set of settings would be great.
CIs this not already possible with VP configurator profiles that can be automatically applied by TelemFFB?
DI have not noticed it doing that... maybe I have not properly set it up.
CI haven’t done it myself but I have definitely read about that capability in the manual
CPage 55 of the manual: https://docs.google.com/document/d/1YL5DLkiTxlaNx_zKHEYSs25PjmGtQ6_WZDk58_SGt8Y
SIs this the right place to ask about shipping date on order #612?
Fdm Walmis
SI don't know how to DM in Discord
S@walmis do you have shipping date for order #612?
Fright click username and there is a "message" option
DHere are my settings now. I backed them off a bit from the default config.
D
DI keep getting Fault_encoder_magnet errors.
DI am not sure what is happening, although it is probably because of user error. The Rhino will work okay in the F-15E, then when I move to another plane, the F-5E for example, it seems to want a complete recalibration or reboot. I jumped into the F-5E, the stick works for a minute then I get the fault encoder magnet error. Reset, unplug, plug back in, it goes away, recalibrate then it seems to be fine, as long as I do not yank the stick around.
DLOL, in the end, it might actually make me a smoother pilot.
DThe F-14 has been a complete disaster so far, every time I try to fly it whether it is from the take off position on the ground or a free flight air start, the stick shakes uncontrollably, then finally gives up the fight, gives me the encoder errors for booth X and Y axis and goes limp. A reset then usually works for a bit, but then the cycle repeats.
Again, I am positive I do not have the settings correct or something is not installed right. I will disconnect everything, uninstall everything and try again.
Again, I am positive I do not have the settings correct or something is not installed right. I will disconnect everything, uninstall everything and try again.
DTry segmenting the issue for each problem, one effect at a time slowly ramp up until you get what you want and it feels right. Remember, a true experiment is where you change one value and leave the others fixed and adjust that one change how you want it. From a cursory view of your settings, you have friction, inertia higher than mine possible damper as well. Turn down periodic effects much lower and finetune the F-14 specifically. HEATBLUR did extensive work on ffb effects so you really have to segment that one to get it right. I kinda wish people would post their per plane profiles more. There's a few but not many. I havent gotten to the F-14 much yet, if I do ill post my settings. Also the ffb settings to adjust are two-fold; one VPForce FFB Configurator and one VPForce Telemffb software.
WYes, agree, working through that now. When I get something that works and I think is repeatable, I'll post my settings for the F-14.
DCS system base - Use FFB - Checked
DCS F14 special use FFB Trim - Checked
DCS F14 Controls - VPForce stick - FFB Tune settings: Trimmer - TBD and Shake - TBD
VPForce Config: Settings TBD [Master TBD, Spring TBD, Damper TBD, Inertia TBD, Friction TBD, Constant TBD]
VPForce Config: Effects TBD [Spring OFF, Damper OFF, Inertial Off, Friction Off, End Stops As Needed, Hardware Force Trim Off, etc... as needed]
VPForce TelemFFB Config: TBD
Oh the joys of troubleshooting
DCS system base - Use FFB - Checked
DCS F14 special use FFB Trim - Checked
DCS F14 Controls - VPForce stick - FFB Tune settings: Trimmer - TBD and Shake - TBD
VPForce Config: Settings TBD [Master TBD, Spring TBD, Damper TBD, Inertia TBD, Friction TBD, Constant TBD]
VPForce Config: Effects TBD [Spring OFF, Damper OFF, Inertial Off, Friction Off, End Stops As Needed, Hardware Force Trim Off, etc... as needed]
VPForce TelemFFB Config: TBD
Oh the joys of troubleshooting
DAwesome stuff. So full disclosure, I rarely, rarely, rarely ever fly the F-14. Did I say rarely? I mainly fly the F-15E, sometimes A-10 and F-5. Of course with the F-4E coming out, I will add that to my stable. I also fly the Apache and the F-16. I have the F-16 covered, and will work on the Apache after I get the fixed wing done. The effects are not the issue for me UNLESS having them turned up is turning the rhino base off, which is what is happening.
Si've found that the spring and damper LPF frequencies should not be evenly dividable. otherwise they tend to 'line up' and makes it worse. i see in your case the spring is 4hz and damper 8hz.. try spring 3hz and damper 10hz