Virtual Crew Chief for BMS
-
@Tomcattwo
Voice Attack is at the default place :C:\Program Files (x86)\VoiceAttackeverything is set correctly and is working fine with control surfaces in the sim. And yes, it is with “Big Movements” “DBU” and brakes only.
I did the test you asked for :
a) ok
b)With the key commands, the VCC is responding but surfaces are not movingHope it will help
-
@Wingedsky ,
Thanks for the quick reply. What you saw in the test was what I expected, and confirms the axis values are not being stored in VoiceAttack.dat properly. We are very close to releasing 1.1 Hopefully today. Hang in there…when V1.1 is released, delete the V1 profile from VoiceAttack. Follow the installation instructions and give it a go. The new version saves axis info and Pilot Gender in text files within …VoiceAttack\Apps\Virtual Crew Chief for BMS folder and calls them when needed from there - it doesn’t save that info to profile any longer. We’ll see if that change solves the issue for you.
@CriticalMass for info.
R/
TC2 -
1.1 is out! I’ve updated the first post.
@Tomcattwo’s contribution has grown into much more than just helping with testing and support. So we are now co-authoring VCC4BMS.
@Wingedsky and @CriticalMass, I hope this update solves your problem with the joystick axes. Let us know how it goes.
-
-
@Ricky said in Virtual Crew Chief for BMS:
1.1 is out! I’ve updated the first post.
@Tomcattwo’s contribution has grown into much more than just helping with testing and support. So we are now co-authoring VCC4BMS.
@Wingedsky and @CriticalMass, I hope this update solves your problem with the joystick axes. Let us know how it goes.
Thanks, @Ricky and @Tomcattwo I’ll take a look tomorrow and report back.
-
Same here, Thanks,both of you. I’ll take a look tomorrow and report back.
-
@Ricky and @Tomcattwo :
thanks so much
Yes, v1.1 installed and everything is ok now -
I’ve tested v1.1 and the stick movements are now being responded to, thank you, though…
…they are reversed, both X and Y axes. I have a VKB Gladiator which needs to be inverted in AL to give the correct movements in-game, but changing this made no difference.
I use the Z axis (rotate) for the rudder, this is not “inverted” and works (VCC responds) as expected.
MPO also doesn’t respond when pressed - I have this on hold. Again changing this to toggle made no difference in-game?
-
And, as always, you send a reply then your brain kicks in. I went into the VKB config software and set the “invert” there, VCC responds to stick movements as expected!
MPO is still an issue.
-
@CriticalMass , with the MPO, you have to be very short (0.5s as written in the check list) with your press key.
First try, I was more than 1s and the CC didn’t answer
MPO on hold doesn’t workHope you will solve your isue
-
@CriticalMass said in Virtual Crew Chief for BMS:
And, as always, you send a reply then your brain kicks in. I went into the VKB config software and set the “invert” there, VCC responds to stick movements as expected!
Woo hoo! Glad you got that sorted!
MPO is still an issue.
The VCC response for “Kick” (MPO engaged) works like this:
The “Kick” response will only occur when the pitch is full down.
So try this: when going through Big Movements and DBU movements:
a) Do pitch UP, get VCC Response “Nose Up”,
b) then do pitch down and hold it there (full down), get VCC response “Nose Down”,
c) wait for VCC response to stop completely, then
d) press and hold O key (or your assigned button for O keypress) for about .5 to 1 sec, get VCC response “Kick”.
e) Let go of O key and then press O key again (this disengages MPO - verify when you get back in the cockpit)
f) then continue on with roll and yaw testing.Please give this a try and please let me know how it goes.
Regards,
Tomcattwo
(VoiceClone) -
@Tomcattwo Are you detecting MPO switch position from shared memory or is it tied to the keypress? I was trying to find it in shared memory variables but I’m not seeing it…so I’m guessing it’s the latter but wanted to see if I was just missing it.
-
@foxster
We could not find MPO switch position in shared memory, therefore we had to sense the keypress for the default bound key (o). The keypress test is nested inside the loop for “Nose Down” and keypress search occurs once nose down is properly sensed and VCC has completed reply (“Nose Down”). See explanation above on proper way for users to go through this part of the procedure (for both Big Movements and DBU) .
R/,
Tomcattwo
(VoiceClone) -
@Tomcattwo Ok thanks for confirming that. I also didn’t find indicators for the AAR door. I’m going off joystick/keypresses as well.
Same for brakes…
-
@foxster
We could not find the AAR Door position nor the cockpit switch position in Shared Memory. So we used the RDY and DISC light bits, which are in Shared Memory. If you look within the profile, you’ll be able to see the inline C# code which looks for the RDY light on (bit set) or off (bit cleared). We also had to design in code to ensure that VCC did not respond when the pilot pushes the disconnect button (RDY goes out, DISC comes on for 3 seconds then DISC out, RDY on), and after the pilot places the switch in shut (which causes RDY and DISC to go out), a slight (~3 second) delay between when RDY and DISC lights are both out and when VCC responds (to give time for the “door” to close completely).Shared Memory does not contain brakes applied or not (at least we could not find it). For Brakes, we used the toe brakes (which are mapped along with the pitch, roll and yaw joystick/rudder axes at initialization or by a voice command. If the user doesn’t have toe brakes, we look for keypress “k” (the default keypress for wheelbrakes).
Regards,
Tomcattwo
(VoiceClone) -
@Tomcattwo Ahhh…Ok, that helps with the AAR Door. I don’t have voiceattack and can’t see the inline c# you’re using, but I see the bits in the FlighData.h header and can work it out from there. Your description of the logic is helpful.
-
@Tomcattwo
Hi, With v1.1 profile, I have an issue with Brakes Checks.
Once Channel 1 is announced, CC immediatly replies “Movement” without any action on the brake. And I have to Disregard waiting no movement never coming.
Same once announced Channel 2 .
Same on left or right brake.Controls configuration is ok
Any idea ?
-
@Wingedsky Are you using pedals? It sounds like you may need a little bit of a deadzone in the vcc profile to accommodate for axis sensitivity/noise.
-
@Wingedsky
I see from post above you have toebrakes mapped. I agree with @foxster - check the deadzone around your toebrakes. Based on your description, sounds like BMS thinks your toebrakes (both of them) are always being applied.
Regards,
Tomcattwo
(VoiceClone) -
@Tomcattwo @foxster
thanks for your answer.
Yes i have a thrustmaster T-Pendular- Rudder.
Are you talking about Saturation ? Dead zone is not associate with Brakes
I Have tried Small and medium Saturation without any changes
Large saturation : once “Channel one” recognize, immediately I still ear movement without any action on the toe Brake. The change is, after pumping brakes, I have no movement…Now no need to Disregard, that is the only progress…
the calibration is correct
-
@Wingedsky
This is from the Thrustmaster TPR Owner’s manual. This page tells you how to set the deadzones for your left and right differential brakes. I think you would need to widen the deadzones for both left and right brakes a bit.@Ricky for info.
Regards,
Tomcattwo
(VoiceClone)