NZ is usually the twist axis. If you don't have the version of the grip with the twist axis, you don't need to worry about it
Vis there a way to disable this cause it always saying im using the Z axis
FHave you tried doing a calibration in windows? Since there will be no input in the z axis maybe it will center it for you.
Press Windows Key + R, type joy.cpl and press enter.
Select the controller on the list > Properties > Settings tab > Calibrate
Press Windows Key + R, type joy.cpl and press enter.
Select the controller on the list > Properties > Settings tab > Calibrate
Vi mean i have the twist axis but i dont want to use it sorry i should have said that
FCalibrate the twist axis in windows. That should center it.
Vthank u will try
SWorked for me every time
My current raw values are 1870 and 2390
My current raw values are 1870 and 2390
DThat's strange.
My process was:
joystick not calibrated, since I never moved the stick to max positions.
If I follow the instructions on the app:
(without centering tool)
but at least my stick is calibrated
My process was:
- Centering tool
- Motors on
- click on Auto calibrate
- Set X,Ymin=0 X,Ymax=4096
- click on Auto calibrate, then Apply Settings, then Store Settings
- Remove centering tool
joystick not calibrated, since I never moved the stick to max positions.
If I follow the instructions on the app:
(without centering tool)
- click on Auto calibrate
- move stick to max positions
- click on Auto calibrate
- Store settings
but at least my stick is calibrated
Dthat's my guess, too, since after connecting the boot, protomaker's manual says to repeat the calibration process, as in the vpforce manual this time
Dbut protomaker's steps never worked for me. raw_x ranges from aprox -1100 to +1100 and raw_y ranges from aprox -175 to +2400
H@Dimitris @Subsonic (Protomaker) That can only work, when the Belt is put on with the motor axis in the right position. The Motoraxis has a marking that needs to be to point north before the belt is put on. Another method, that I find easier, is to first set the calibration manually to 0-4096, save and apply, activate the spring and THEN put on the belts.
HThat way, the axis will orient itself properly and you can put on the belt at the right position. With or without the centering tool (which I found to be obsolete)
DHuge thanks! I did what you said and everything is perfect now. It also makes perfect sense.
DAlso, very happy I didn't need to unscrew the boot cover to use again the centering tool 
Vsadly it didnt work it still is like always activation z axis
Ndoes your grip have the twist axis or not?
FIf your grip has the twist axis locked it may be locked while twisted to one side. I would unlock it and see if the readings in the configurator change as you twist it and lock it when it's in the center. If you twist it and there is no change in the reading then there may be an issue with your twist axis sensor in the grip itself.
FVIRPIL Controls Support Center
Attaching Your VPC Grip IMPORTANT for the latest revision of the VPC Grips with twist axis! Before attaching your grip, ensure that the locking screws are flush with the screw collar. 1. Visually inspect both the grip plug and b...
VI have the old version i cannot lock it
CHey guys, finally got my rhino mounted and configured and the base stuff is incredible. Having some issues getting telemFFB to even recognize that im playing DCS and give me the option to play with affects there at all, would anyone know how to resolve this? got a screenshot of the live log for reference
LSo no telemetry from DCS. My first thought is there is something wrong with export.lua.
- Have you checked for clues in the DCS log file? It can look like this for example:
Lua::Config (Main): Call error LuaExportStartand so on - If you are using other programs which depend on Lua export, you can try moving TelemFFB line up/down in case the other program has installed itself incorrectly
- A relatively easy thing you can try is this: Rename your saved games/DCS folder to something like DCS.saveme. Then start DCS and let it create a new file structure. Then load TelemFFB and let it install the export script and modify the export lua. Restart DCS and load into an aircraft and see if the telemetry starts flowing or if you get the same error in the log. All your bindings will be gone since they are stored in DCS folder you renamed, but this is just a test and you can delete the new DCS folder and rename your old one back
Cdidnt think of moving the telemFFB line in the export.lua to the top, that seems to have fixed it. appreciate the suggestion!
RReplacement arrived and unit is working again. Thank you for the link. Wanted to provide an update that this has been resolved.
Swhere is that marking? can you make a video how to perform proper centering and calibration?
HAll three motors I got from Walmis had a marking on the face of the motor axis that showed the middle (~2048) position. Assumingly he put in on when calibrating the motors and putting on the firmware. But of course I don't know for sure if he does that every time.
HBut it isn't that important anyway. I can't make a video because I don't want to take apart my rhino (again) but it is really pretty simple. Leave the belt off, manually set the calibration values to 0-4096 for each axis apply and save. Then turn all effects except spring off. The motor will turn to the correct position on its own and due to the spring it will hold it with some force. THEN put on the belt (of course hold the stick upright for that). That will give you a center position in the proximity of 2048 (doesn't matter when it is 1999 or 2078). Then do a proper calibration. Et Voila.....
HThe axis might jitter a bit without the belt due to the lack of damping mass, if it is too much reduce the spring gain.
S^this is great process explanaton, thanks man! appreciate
TAny basic docs/videos on changing out the 3D printed Thrustmaster adapter that comes with the pre-assembled Rhino joystick for the metal version? It looks like it should be straight forward, but I couldn't find any docs and always like to verify before I start taking stuff apart!
*YouTubegodfreynet
Performed by my 11 years old wingman, under my supervision...
Music used in video:
Pat and Mat Soundtrack (A JE TO! 1979-1985)
Music used in video:
Pat and Mat Soundtrack (A JE TO! 1979-1985)
*Here is my MSFS pitch oscillation and settings... please help if you notice anything wrong in my settings...
*
*
*
*
*
TI am pretty sure since you don’t have damper, inertia, or friction checked in the effects tab, that the sliders on the settings tab do nothing. My understanding is that you take effects% * settings% to get total allowable %.
Try ticking damper box first, store settings, and see if that helps. High values for inertia and friction can cause instability (motor shutdowns) so best to feed those in slowly.
Try ticking damper box first, store settings, and see if that helps. High values for inertia and friction can cause instability (motor shutdowns) so best to feed those in slowly.
*I think TelemFFB overrides the configurator settings by using recognized or generated profiles, right?
TOnly if you set them to do so. It doesn’t look like you have, so TelemFFB uses the device settings.
TUnless you’ve changed your “startup” vpconfig or set a custom aircraft specific vpconfig in TelemFFB
TSection 4.12 of the manual: https://discord.com/channels/965234441511383080/1091401951951982602/1091401951951982602
CHey guys I'm having some issues with the config for the F4. The stick's neutral postion requires a ton of nose down to maintain level flight in cruise. The trim seems to do nothing. Any ideas?
HWhat do you mean? The trimmed stick position in level flight is forward from center - that is correct. The faster the more it needs to be trimmed forward (down).
CNo the trim does nothing
Cdoesn't move the stick at all
HAre you talking about the VP hardware trim or the in game trim?
Ctrim in game
CI suppose, honestly I'm not sure which
CJust got this thing. I'm pretty new to all of this
HNo problem.