Now Virpil sees sees no devices But windows does see them.
Edit-- VPC software now sees the joy stick
Such frustration. Tempted to go back to my wardhog.
Attachments
Last edited:
Virpil key bindings
- Thread starter Tonka
- Start date
Edit-- VPC software now sees the joy stick
Such frustration. Tempted to go back to my wardhog.
if I was You I would be patient and visit Virpil website for setup tutorials, once You nail it, You won't have to do it again probably until You reinstall windows or something daft like that.
Now, regarding Your screen shot it looks like You have not loaded the device/profile which You should do when You start the VPC software. Apart from that, it does not tell us much. Just another daft one but are You sure Your connection between the base and grip is sound? For me it was amusing to find out that the connector on the grip actually pulls out letting You insert it correctly. Before I figured that out, the connection was loose or non existant at all and like You I was pulling my hair out.
Edit: btw I am not 100% sure cos I don't have their throttle BUT I think when You create profile You should have all devices connected, otherwise I would assume they won't be detected/configured together? Might be wrong on that.
1 more tip, if You are not using an externally powered USB hub I would give that a go as well, I imagine that Virpil HOTAS will be a hungry power horse like X55/X56 and we all know how it works out when they don't get enough power.... BOOOOM into the station cause of ghost input...
Now, regarding Your screen shot it looks like You have not loaded the device/profile which You should do when You start the VPC software. Apart from that, it does not tell us much. Just another daft one but are You sure Your connection between the base and grip is sound? For me it was amusing to find out that the connector on the grip actually pulls out letting You insert it correctly. Before I figured that out, the connection was loose or non existant at all and like You I was pulling my hair out.
Edit: btw I am not 100% sure cos I don't have their throttle BUT I think when You create profile You should have all devices connected, otherwise I would assume they won't be detected/configured together? Might be wrong on that.
1 more tip, if You are not using an externally powered USB hub I would give that a go as well, I imagine that Virpil HOTAS will be a hungry power horse like X55/X56 and we all know how it works out when they don't get enough power.... BOOOOM into the station cause of ghost input...
Last edited:
Not sure, I saw yaw in the settings and just assigned it to the yaw on the joystick. Bad idea?
Last edited:
Yeah I have been hanging out on the Virpil forum but you guys seem to have more insight into problems. There I just get replies on how to map.if I was You I would be patient and visit Virpil website for setup tutorials, once You nail it, You won't have to do it again probably until You reinstall windows or something daft like that.
Now, regarding Your screen shot it looks like You have not loaded the device/profile which You should do when You start the VPC software. Apart from that, it does not tell us much. Just another daft one but are You sure Your connection between the base and grip is sound? For me it was amusing to find out that the connector on the grip actually pulls out letting You insert it correctly. Before I figured that out, the connection was loose or non existant at all and like You I was pulling my hair out.
Edit: btw I am not 100% sure cos I don't have their throttle BUT I think when You create profile You should have all devices connected, otherwise I would assume they won't be detected/configured together? Might be wrong on that.
1 more tip, if You are not using an externally powered USB hub I would give that a go as well, I imagine that Virpil HOTAS will be a hungry power horse like X55/X56 and we all know how it works out when they don't get enough power.... BOOOOM into the station cause of ghost input...
That screen shot show nothing other than the fact the software doesn't see the devices. I uninstalled VPC joystick software and reinstalled the latest version off the Virpil site, installed that and VPC sees the devices...so thats good I think. I have no idea why that worked because I thought I had the latest.
I agree 100 percent on the connect between the grip and the base. Took me forever to get that right. My fingers are too big I guess. There is a lot of discussion on the poorly designed connector between the grip and the base. Connection is really hit or miss. You may think its connected fully when only part of the pins are inserted properly.
They strongly recommend to connect one device at a time or you can brick the throttle,
On powered USB hub I got the most powerful one I could find.
AGEEN USB Hub 3.0 Powered 90W Data Hub, Multiport 16 Port Powered 12V/7.5A
Really appreciate all the help from you guys ...just sold my Warthog so I have no HOTAS until this is worked out
Last edited:
You have two (IIRC, maybe more) possibilities for yaw (and any of the other axes except throttle, where it becomes really complicated): you can assign it to an axis = analogue input, or you can assign it to a button = digital input. "Yaw left" and "Yaw right" are digital inputs, intended (but not limited to) if you fly via keyboard or e.g. a two-axis stick. What you probably intended to do was to assign the stick's twist axis to yaw, which means to assign it to the "Yaw axis".
When you assigned the stick's twist axis to "yaw left", any deviation from the neutral position will trigger yaw. What happens now is that, whenever you touch the stick to assign another button, you also move the axis from the neutral position (yes, the hall sensors are that sensitive), triggering the yaw command, which in turn prompts the game to ask whether you would want to reassign yaw....
I'll get you a screenshot when I go back into the game later on.
It's definitely possible to fly this way, i.e. use the digital inputs for thrust control. But you wouldn't need to spend a few hundred euros/dollars/... on a high end joystick for that. And it's definitely harder to land on a high g world if you have vertical thrust assigned to a digital control.
---
Edit: if you actually used the twist axis for yaw, I'm slightly surprised that it's that sensitive, on my stick, the twist has a small deadzone. If you used the y-axis for yaw, though, it would trigger if you even looked at the stick the wrong way.
The connection is dead solid actually when You pull out the cord from the grip, it extends about 2-3cm allowing for comfy grip and secure connection. Once You attached the grip to the base it folds snuggly back in.
On throttle I won't be much help because I don't have it. My only suspicion would be that one of the axis is not centering perfectly, which could be solved within vpc by recalibrating or setting a small dead zone. With the software you have VPC testers again can't remeber from top of my head but those can help you test weather you are getting any input and from what button/axis and take it from there.
On throttle I won't be much help because I don't have it. My only suspicion would be that one of the axis is not centering perfectly, which could be solved within vpc by recalibrating or setting a small dead zone. With the software you have VPC testers again can't remeber from top of my head but those can help you test weather you are getting any input and from what button/axis and take it from there.
Also this. Taking into consideration what Ashnak says as well as confirming that ALL axes and buttons are dead center (in vpc soft) and non of the buttons sends any signals, I'd say wipe Your binds clean and start from scratch. Pay attentiin when binding to assign buttons and toggles/switches to DIGITAL input designed commands and the analogue thumbsticks and axis to axis designed commands.
Just so I understand. the 2 assign boxes next to each other in ED in controls one is digital the the assign box on the left is analog?
No - that's so you can assign two different digital inputs (keys/buttons), e.g. a button on your gamepad and a button on your keyboard. Give me 10 minutes, I'll boot up my game machine and doctor a screenshot.
Ok, here we go:
Circled in red is what you (proabably) want to use. That's the Yaw axis, i.e. the analog input, which in my case is linked to the joystick's twist axis. Operation is "regular", i.e. the ship rotates in the direction I twist.
Next down there (you need to unfold the option, that's the "+" sign if it's folded in, "-" if it's folded out) is the Deadzone setting - unnecessary on a Virpil
.
Then you get "Yaw Left", with two options. That's so you can assign two physical keys to the digital yaw left. Both keys are equal, last one wins. Since I don't need them, they are empty (select the option, then hit ESC to clear any entry).
Yaw right, the same as yaw left.
Yaw into roll is an option for users with two-axis controls (e.g. mouse) , a sesitivity setting for that and what happens in the case of FA-off.
and so on.
Some way further down, there's another section with "landing override" (or something like that). In that section, you can select different inputs in the case the landing gear is down. Again useful for people who fly e.g. with a gamepad so they can reassign the buttons used for weapons to thruster functions (you can't shoot with the gear down in any case) so they can position their ship over the pad. If you have full 6-axis analog controls, you won't need that, either.
Circled in red is what you (proabably) want to use. That's the Yaw axis, i.e. the analog input, which in my case is linked to the joystick's twist axis. Operation is "regular", i.e. the ship rotates in the direction I twist.
Next down there (you need to unfold the option, that's the "+" sign if it's folded in, "-" if it's folded out) is the Deadzone setting - unnecessary on a Virpil
.Then you get "Yaw Left", with two options. That's so you can assign two physical keys to the digital yaw left. Both keys are equal, last one wins. Since I don't need them, they are empty (select the option, then hit ESC to clear any entry).
Yaw right, the same as yaw left.
Yaw into roll is an option for users with two-axis controls (e.g. mouse) , a sesitivity setting for that and what happens in the case of FA-off.
and so on.
Some way further down, there's another section with "landing override" (or something like that). In that section, you can select different inputs in the case the landing gear is down. Again useful for people who fly e.g. with a gamepad so they can reassign the buttons used for weapons to thruster functions (you can't shoot with the gear down in any case) so they can position their ship over the pad. If you have full 6-axis analog controls, you won't need that, either.
On the dead zone subject, I find a smudge of dead zone helpfull with boostin on silent mode when smuggling, and I can keep my hand on the stick rather than taking it off say for smuggling and silent boosting because its so sensitive and precise 
Edit: and I don't repeat myself repeat my self at all
Edit: and I don't repeat myself repeat my self at all
Last edited:
Finally I have VPC seeing the devices. Joystick and throttle.
Did a simple calibration and saved their profiles.
However when I go into ED/controllers and try to bind any command to a button I always see 'Joy RZ Axis" accept or cancel
It does not give me an option. I guess I need to create more headroom.
Somehow Controls sees only Joy RZ Axis as an input...I think..?
Did a simple calibration and saved their profiles.
However when I go into ED/controllers and try to bind any command to a button I always see 'Joy RZ Axis" accept or cancel
It does not give me an option. I guess I need to create more headroom.
Somehow Controls sees only Joy RZ Axis as an input...I think..?
Tentatively: sound like your RZ (twist) axis calibration is off - that would result in a lot of noise on the twist axis signal. What do the x, y and rz values in the windows game controller test dialog (or the virpil app) look like?
michaelfoc (IIRC) had the suspicion earlier that there was something wrong with the cable between base and grip - do all the buttons work when you test them in the Virpil app or Windows game controller test?
michaelfoc (IIRC) had the suspicion earlier that there was something wrong with the cable between base and grip - do all the buttons work when you test them in the Virpil app or Windows game controller test?