Jump to content

Razor18

Members
  • Posts

    1951
  • Joined

  • Last visited

Everything posted by Razor18

  1. Well, it does not work. Even if I turn selector knob to MULTI, the moment I enter even just a single player F/A-18C instant mission (Ready at the Ramp), VAICOM disables TX3 and TX4. This is the apparent reason from the VAICOM manual, page 14: "TX1-TX3: For DCS aircraft with multiple MIC hotkeys, the plugin maps the available aircraft radios to TX1-TX3. If less than three radios are available for the current aircraft, one or more of these TX nodes will be disabled." Even if I have 4 radio PTT buttons set in SRS, and if I check SRS mapping and SRS Integration on the MP tab in VAICOM config window just to try it, VAICOM still does not let me use more than 2 radios. Thank for trying to help though.
  2. Just to clarify, I think they are two different things. I think MULTI position does not say it is supporting MULTIplayer (vs you said it doesnt support MP at all), it rahter says you have MULTIple radios instead of nomal (type specific numbers of) radios available. And if it will work in single player, then probably it will work also in multi, as multiplayer. Hope I wasn't confusing, just stating (and clarifying) the obvious rather... Again, thanks for both of ya ! Of course I will test it before saying anything more...
  3. Thank you very much !
  4. But then how can I use the two MIDS in the F-18?
  5. Hi Gents, some weird phenomenon happens with VAICOM all the time. I start up Voice Attack and VAICOM before starting up DCS. Testing TX1, 2, 3 and 4, both Voice Attack and VAICOM recognizes them all. See screenshot. Everything stays fine until I press "Fly" button, then on VAICOM config window, TX3 and TX4 disappears from possible TX buttons. Voice Attack still sees them in the listening window, but VAICOM only sees and transmits on TX 1 and 2. See picture. Then when I exit the mission, TX3 comes back. No screenshot from that though... I don't know what can cause this...
  6. Yeah, but that one is refers to speed, not G. And deceleration is displayed on most of the modern airliners on the electronic ADI, just beside the speed scale. How was your time in the Spanish Air Force?
  7. Hmmm... Just wondering, why would the speed brake opening ever induce any negative G value on the HUD?...
  8. Same thing just happened to me. After VID, Poodle turns away from SAMs, but slows down in the process, and with nose high, he deep stalls all the way down to around 4k, and slows down to 0.2. Then it somehow recovers, but... Oh, by the way when Poodle snarks at me for not replying timely, both enemy aircrafts are just a dot at the front of a huge smoke/heat contrail head on to us, so no way anyone could identify aircraft type even on full zoom and narrow FLIR FOV.
  9. Hi Gents, I have a TM WH, that's why asked here, but question refers to any controller. Which files or folders should I save if I want to have back the same input settings after a Win/DCS reinstall? Anything else worth saving a backup of before a DCS reinstall? Thanks for feedback !
  10. Thats why I wrote the alternative.
  11. Do you know about the Ctrl-F search function in Adobe Reader? Or alternatively, https://www.google.com/search?client=firefox-b-d&q=DCS+FA%2F18+std+hdg
  12. And if you put your cursor on the D/L contact on the SA page and press STEP (bottom second button from left), it remains displayed, don't even need the AZ/EL page to see the altitude...
  13. I think this phenomenon is very subjective. Can you maybe show a picture, so everybody talks about the same visual "picture"?
  14. Which means only to replace VAICOMPRO.dll with that 2.5.24 version, right? (And do the usual "FINISH" dance)... And should I maybe downgrade VA from v.1.10.3? EDIT: downgraded VAICOM to 2.5.24, and VA to 1.8.9. Now recognizes both command, but only if I prest TX, even with REL/HOT on HOT. I just clicked DIAL from MAN to OPER and back, now VA recognizes both without a TX press too... Restarted VA, now it does not again... Weird... OK, restarted VA, this happened: Said "Salute" without TX, but with REL on - nothing. Pressed and released TX button on my joy once, but said nothing. Then said Salute WITHOUT pressing transmission, and voilá, recognizes everything, incl. Request launch.
  15. Yes, Hornet on SC.
  16. I think the problem is rather while listening, VA is too sensitiv and making up words based on environment noise like typing on my keyboard. I click my mouse, and VA thinks he heard "is". And yes, that is the commands that are not working even if REL/HOT is enabled.
  17. Yeah, REL/HOT is enabled, but Request relaunch what you give for the carrier crew to put me on the catapult to launch. YOu do it with canopy closed, and it used to work before. And my "original" "DCS" profil commands, that do not need transmission to be pressed, they get executed no problem.
  18. Couldn't find out why this message comes up when trying to say "Salute!" 10:51:01.643 Command 'salute' is currently disabled for this session and was not executed. While for instance: 10:51:41.833 Recognized : 'request launch' And in general, not saying anything, Voice Attack recognizes commands with me saying nothing just typing this message right now. 10:59:19.332 Recognized : 'perth' 10:59:13.148 Command 'perth' is currently disabled for this session and was not executed. poppes up every time I'm typing... and if I click my mouse: 11:03:42.476 Unrecognized : 'it's' Oh, btw when trying now, DCS doesn't run yet. But VAICOM/VA does the same when DCS runs. Sorry if too obvious, I couldn't find it in manual...
  19. Did you also check if your keypress (not axis!) command for rudder (yes, there is such thing too, making full deflection when the key pressed) is not assigned to something accidentally, or by one of the updates, that regularly do mess up your key assignements without you realizing it.
  20. You have exactly those two buttons in Skatezilla's application: VR on, or VR off (for launch)
  21. It's on HSI, for navigation. SA page is for combat, where you mostly dont care, where home is yet, so...
  22. Because previously you pressed Alt-Home using the Home key on the numeric keypad?...
  23. Btw, did you try looking up in the manual, maybe with the search function?...
×
×
  • Create New...