You are not using the TB stopwatch or clock are you??
I got my V1F on the pre-order so have had mine a while. I just pull the yoke out and clean the shaft with a lint free cloth now and then.
I don’t use it everyday as I also run a HOTAS setup.
But I can report that the sticky pitch has completely gone for me now, one handed ![]()
And you are not using TB training mode?
Advice is to come out of the menus altogether.
I often had this issue but stopped it by no longer using the chronometer. Haven’t experienced it since at all.
Yep the timer or clock causes this behaviour, TB are working on a fix.
I think I was using the stopwatch for that flight. Well no more of that for now! thanks all!
Great to hear that! It’s my only concern with the product currently.
Hey at all,
i have troubles to activate the SIP feature…
MSFS, Win10, Firmware 1.1.0, InputMode PC, StatusPanelMode SIP FP001 active (LEDs turned from blue to green - everything fine up to this point).
Now i am staring the SIPConnect-1.0.0 (yes, of course with the dll´s in that folder),
right click on the icon, check MSFS, right click again, click connect.
In some videos i saw, that this should be the time, where the LEDs turn off / going on one by one.
But in my case nothing happens. The “connect” turns greyed out, i can click on disconnect (seems fine).
I still can continue by clicking start and when MSFS is active i even see that the “start” turns greyed out, stop is available - but as i said all LEDs stay green, nothing happens.
Any ideas??
Thanks a lot!
Hi
I have recreate all profil for yoke en propeller and I no longer have a problem
I problem came from the B4 is on the propeller not on the yoke
on default profils (default, single prop and quad enginer) the buttons are used for several actions and this creates conflicts
Best regards
Hey at all,
sorry for posting here again, but there is another VelocityOne-Channel here…
I have troubles to activate the SIP feature…
MSFS, Win10, Firmware 1.1.0, InputMode PC, StatusPanelMode SIP FP001 active (LEDs turned from blue to green - everything fine up to this point).
Now i am staring the SIPConnect-1.0.0 (yes, of course with the dll´s in that folder),
right click on the icon, check MSFS, right click again, click connect.
In some videos i saw, that this should be the time, where the LEDs turn off / going on one by one.
But in my case nothing happens. The “connect” turns greyed out, i can click on disconnect (seems fine).
I still can continue by clicking start and when MSFS is active i even see that the “start” turns greyed out, stop is available - but as i said all LEDs stay green, nothing happens.
Any ideas??
Thanks a lot!
Same here,
James TB informed me that they are working to solve this issue.
Wired thing, the first version of SIP connect works FB.
So I’m hoping the TB finds a solution, patience may the key word… ![]()
Yours,
Frans.
PC - Steam -
Holy effin cow. 5 month break from flying (Fibromyalgia makes a lot of things impossible in the winter), 1 update later and still my VelocityOne Flight is a steaming pile of ---- that nosedives during every flight.
I have fiddled around with the settings, followed much of the advice on here (the stuff that I can understand anyway) and it’s still messing up.
Seriously getting close to refund time and going with one of the more established firms. Packing it away after an utter frustrating afternoon which I had hoped would relax me ahead of stressful week at work.
Hi @Wivenswold, definitely worth trying these steps, as nosedives are not part of normal behaviour!
- Have you checked the game controller settings? (you can do this by typing ‘joy.cpl’ into the search bar, and selecting each of the devices (top one is yoke and bottom one is throttle quadrant) and clicking ‘Properties’, then moving the controls. This will check the control inputs, to make sure the VelocityOne Flight is not giving nose down inputs on its own).
- Also worth checking your assistance settings, from the main MSFS dashboard, go to Options, Assistance Options and make sure that in all of the drop down menus, all of the AI options are turned off, including AI trim, takeoff assistance, and anything that could interfere with your control inputs.
- When you fly next, move the trim wheel a bit to make MSFS sense the position of your VelocityOne Flight’s trim wheel, and make sure that it’s set to the ‘takeoff’ position in the cockpit before applying full power.
Those steps should check for any VelocityOne Flight issues related to the symptoms, and some basics involving MSFS. However, it sounds to me like these symptoms are down to MSFS, as some other users have experienced similar issues without the VelocityOne Flight.
I have also seen many more reports of users having problems with the Steam version than the downloaded one from the Microsoft Store, irrespective of which yoke / HOTAS they use.
Please let me know (via DM if you like) how you get on with these steps and we can take things further to organise a replacement if that appears necessary to fix the issues.
Don’t use both programs together, use only Sipconnect and it should be Allright. They both conflict with each other.
Wow, thanks a lot!
After making sure, that the TB Control Center (i really hope you ment that program
)
is not running, it is working!
And as seen in the video: Click MSFS, then click “connect” and the LEDs turns OFF, so you dont have to try and try and try with open MSFS ever and ever…
THANKS a LOT!!
Now the other way ![]()
This really worked for me:
You’re welcome, many happy landings
really looking forward to getting my VelocityOne for X Box, in a couple of weeks, seen many good reviews of it ![]()
Hi although I have had my velocity one yoke for a while I have just recently started using it on the Xbox,I have noticed the throttle works ok but prop and mixture controls don’t work at all, any help please