Fmm let me check
Fyes
F1, 2 and 20
Fits alpha gen 1
S@walmis, @skypickle I also just encountered the same error regarding the config.ini, it was because in the config.ini, there is a duplicate section: the [UH-1H] section is in there twice. I removed the first one (which only had type=Helicopter in it) and now it seems to be working.
SI pulled the latest revision from the github.
SThe config.ini file is present
SI add this to the cinfig.ini file:
S[FW-190D9]
type=PropellerAircraft
buffeting_intensity = 0.0 # implemented by DCS
runway_rumble_intensity = 1.0
engine_rumble = True # rumble based on RPM
type=PropellerAircraft
buffeting_intensity = 0.0 # implemented by DCS
runway_rumble_intensity = 1.0
engine_rumble = True # rumble based on RPM
Sstill seeing this:
DThanks for using comments
STraceback (most recent call last):
File "C:\Python311\Lib\threading.py", line 1038, in _bootstrap_inner
self.run()
File "F:\Dropbox[DCS\Joysticks\VPforce-TelemFFB\main.py", line 163, in run
config.reload()
^^^^^^
NameError: name 'config' is not defined
File "C:\Python311\Lib\threading.py", line 1038, in _bootstrap_inner
self.run()
File "F:\Dropbox[DCS\Joysticks\VPforce-TelemFFB\main.py", line 163, in run
config.reload()
^^^^^^
NameError: name 'config' is not defined
DIs that missing “]” after DCS?
Sno, the directory is named [DCS to put it at the top of the list
Sfor some reason sliphavoc's comment just showed up. I'll try his edit
SWorks fine now
S@sliphavoc thank you
RIs there anyway to disable the "Rhino FFB Joystick detected" message from Microsot Edge? Every time I power the Rhino up, the message comes on, and sometimes, the close button doesn't even work.
DI reported a similar thing 🧰support
MAre the motors made in China or do you manufacture them yourself (in EU)?
WYes we import them and process them inhouse
SFYI, maybe we should add this to the troubleshooting section of the manual in some fashion? I just built a new pc but the stick is not recognized. I tried to connect through the web config tool and it didnt work. I did however get a message that there not enough usb endpoints. I moved the usb plug of the hub to which the rhino is connected to another usb port and now it worked. I was using a port in a startech 7 usb port card but apparently that pci usb card shares its chip among all the 7 plugs. A motherboard usb socket worked fine.
JI come again with a question I asked earlier but I either did not understood the answer right or it just don't work that well So again.... I fly the F-14 almost exclusively and think the FFB is very well implemented. I just wish that the Rhino would be a little harder/stiffer around the center.
Now, the last time the answer was, to work the saturation, BUT, as I understand it, the center of the stick is constantly moving due to different trim for all possible flight regimes. If I set the saturation, that should only work in the physical center of the rhino.
So, is there a way to stiff up the center of the stick not regarding the physical center? Is there a way to implement something that will be working (extra stiffening of the first, lets say 1-2% of movement) around the current stick position? Like a bubble following the current setting? That might be necessary to grab the current trim position from the game as well as it is projected for the Harrier? I'm a little bit on the lost here...so any help...
Now, the last time the answer was, to work the saturation, BUT, as I understand it, the center of the stick is constantly moving due to different trim for all possible flight regimes. If I set the saturation, that should only work in the physical center of the rhino.
So, is there a way to stiff up the center of the stick not regarding the physical center? Is there a way to implement something that will be working (extra stiffening of the first, lets say 1-2% of movement) around the current stick position? Like a bubble following the current setting? That might be necessary to grab the current trim position from the game as well as it is projected for the Harrier? I'm a little bit on the lost here...so any help...
WIf you adjust the spring mapping (like in the pic) it will stiffen up around the virtual center:
JOh, OK, I will try it, thank you. Might have misunderstood the last time.
ILet me know if that works for you
JIt does, but it gets kind of edgie, means if I give it a nudge the stick gets himself in a shake of death. Have to figure out what to do against it. Keeping it firm in my hand it works well.
IGotcha. Yeah I was playing the speed and angles campaigns and it was really hard to keep perfect position next to them without getting into an oscillation because its too sensitive for soft movements
WWhat spring Filter value do you have set?
JSame. Working on adapting that stuff for our group. To fly the Tomcat precise, I would like it stiffer.
J6.2Hz, I guess that is what you are talking about?
WYeah, you can increase it to 8-10Hz - will give more stability for spring
T
TCan anyone tell me why button 1 is permanently red (pushed) on my system just like in this picture from the manual?
P@.durham so that number 1 button is it linked to any of the buttons on the grip?
TMeans that I cannot set any buttons in dcs as this is always pushed.
Also is there a way I can get my brake axis on the stick to act as axis rather than button?
Also is there a way I can get my brake axis on the stick to act as axis rather than button?
TIt is the new Virpil CM2, and no I am not using the loopback app. The picture was from the manual - Loaded software is V 1.0.14 and firmware is V1.0.14-2, both of which I believe are the latest
TYes the first detente of the trigger
TAre you available for a call on Discord?
TOr telephone?
Pahh ok, can you plug the grip into the virpil base & make that a pulse not a constant button press?
Pnot right now, I could soon like 30min
TThe Virpil software is no longer working as the base is gone, so it cannot read anything.
TThat sounds great, although you are able to use all your vkb software as you have a pass through from the grip
Pyeah I really like the idea of the passthrough for that reason, maybe as Walmis does more work if it's possible he could add config software for the different grips that plug direct in
PSo it looks like the trouble is that trigger being constant, when you're in the DCS keybind settings can you press the wanted button & get it to come up at all?
Pyou could also take note of the button # for each physical button & when binding in DCS manually add the button for each, I'll have to check that
P
P