Virtual Crew Chief for BMS
-
@Tomcattwo I have pretty much the same setup as @Wingedsky with
Joy 1 - vkb gladiator nxt (rudder on twist)
Joy 2 - X56 ThrottleFor VA I have AVCS, my set up looks different to your screen shot: I have CORE as global and BMS loaded automatically with VCC as an included profile.
And as previously mentioned, I use Ice’s Helios profile that has no key bindings for Stick or Rudder axes (just a thought)
-
Hi all, sorry I’ve been offline here for a while.
@Tomcattwo and I have very nearly finished a version 1.1 of the Virtual Crew Chief for BMS. One of the improvements is more reliable storing and retrieving of settings, including the joystick axes. If any of you are still having trouble with 1.0 in this area, maybe wait a few more days for 1.1 and then try again fresh. If the problem still exists, I’ll send you a diagnostic version of the profile that outputs more information, so that we can see what the cause is.
-
@Wingedsky @CriticalMass , (@Ricky for info)
Hmm…OK, so it appears to me that the configuration routine is functioning, but my bet is that the routine is unable to save the axis assignment values to the profile, and I think I might know why.
The Configure Joysticks routine is designed to save each axis assignment value to the “Active Profile” - in your case, to VCC4BMS profile. However, the way Voice Attack works is by keeping ALL imported profile information in a single file, called VoiceAttack.dat, and then associating the saved information with the VCC4BMS profile within VoiceAttack.dat
So, something is causing VCC4BMS Configure Joysticks routine from saving the axis data properly to the VoiceAttack.dat file. Let’s try two things:
-
VoiceAttack default installation folder is C;\Program Files (x86)\VoiceAttack If you installed it there, then you may need to run VoiceAttack as a Program Administrator, or Windows may not allow VoiceAttack to do the saving it needs to do. So, try this:
a) Locate the shortcut you use to start VoiceAttack
b) RIGHT Click on the shortcut, and in the dropdown list, select Properties
c) In the Properties Window, click on the Compatibility Tab
d) In the Compatibility Tab, check the box that says “Run this program as an Administrator”
e) Click the Apply button, then the OK button.
f) Open VoiceAttack using the shortcut.
g) Make Virtual Crew Chief for BMS the active Profile
h) Say the voice command “Configure Joysticks” and follow all the prompts in the events window
i) Make AVCS CORE v1.11 the active profile (it will eventually make AVCS4 Falcon BMS Radios (v1.42) active profile as part of AVCS initialization)
j) Try a Ramp Start in BMS and see if this did the trick. -
Another thing to check:
a) Navigate to the folder where VoiceAttack.dat is saved: C:\Users<Your Username>\AppData\Roaming\VoiceAttack
b) RIGHT Click on the VoiceAttack.dat file and from the dropdown, select Properties
c) In the Properties window, General Tab, make sure that the block for “Attributes: Read Only” is UNCHECKED. If it is Checked, UNCHECK it, click on Apply and OK buttons.
d) Open VoiceAttack using shortcut, and follow the above steps to Configure Joysticks and test in BMS.
Note that AppData folder may be hidden. If so, in your C:\Users<Your Username> folder, in the Windows Explorer window, click on View Tab (at the top), and ensure the checkbox for “Hidden items” is checked.
Give these things a try and please let me know how it went. Thanks. We’ll get this fixed!!
@Ricky This check to make sure VoiceAttack is run as Administrator should be included in the installation notes for V1.1 The new version would run into exactly the same problem if VA is located in Program Files (x86) and is not run as Administrator.
Regards,
Tomcattwo
(VoiceClone) -
-
@Tomcattwo
Great job on your viseo TC2 -
@Tomcattwo
One has to really appreciate the job of the crew chief! -
@Tomcattwo
Thanks for your effort.
Your analyse appears to be correct, but the issue is not the one you think.- To run AVCS profile , it is already request to use Voice attack as an administrator.
- Read only is not checked
One more test now , and still same result. Sorry
-
@Wingedsky
Hmmm…OK. We are very close to releasing V1.1 of VCC4BMS. Perhaps we will have a positive response using that new version, as @Ricky said. If we still have the same issues, he will work with you using a special diagnostic version to see what is going on.
Regards,
Tomcattwo
(VoiceClone) -
@Tomcattwo I also have VA already set to run as administrator (a requirement of AVCS).
I don’t have a standalone VA, but via Steam.
Thanks for taking the time to support us.
-
-
@Wingedsky ,
Where is VoiceAttack installed in your setup (I.e., is it in c:\Program Files (x86) or in c:\Program Files (x86)\Steam\StamApps\common or some other location)?@CriticalMass ,
Thank you for that info. When you give the voice command “Configure Joysticks” do you get all the proper prompts and expected axis assignment responses in the VoiceAttack event window?
Can you please try changing the “Start this profile when VoiceAttack starts” to AVCS CORE v1.11 instead of AVCS4 Falcon BMS Radios (v1.42) and try a Ramp Start.For both of you, this sounds like a dumb question but I don’t want to overlook anything, but in BMS, do your control surfaces actually work properly in BMS using your stick/rudder assignments? Are they properly assigned in Settings/Controllers in BMS and respond properly there?
As I understand it, VCC4BMS commands work for both of you in BMS except “Big Movements” “DBU” and brakes. Is that correct?
Can you try the following test for me and let me know the results:
a) Start VoiceAttack normally using your shortcut and set up your systems as usual
b) Do a Ramp Start using VCC. When you get to Big Movements and DBU, try to use key commands and see if the control surfaces and VCC respond (if they don’t, break out using voice command “Disregard”). When you get to Check Brakes, try to do the brake check except use the “k” key for movement and see if VCC responds. Again, if the command hangs, break out using voice command “Disregard”Thanks again for your patience and your replies/information.
Regards,
Tomcattwo
(VoiceClone) -
@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)