Jump to content

t1mb0b

Members
  • Posts

    125
  • Joined

  • Last visited

Everything posted by t1mb0b

  1. bad first impressions Just bought one of these, I'd kind of expected the throttles themselves to work straight out of the box, but I am not impressed. When I try to add them to left and right thrust axes respectively in DCS World controls, I cannot get them to map in a logical way. The symptoms in game ( F18 ) are when I move the left throttle a tiny amount from 'zero' the throttle lever in game jumps to about 50%, then when advancing the throttle through its entire range, in game the lever travels to the fully forward position. With the right throttle, i have to advance the throttle all the way for it to go (in game) from zero to halfway. If i then just nudge it with very light pressure at the end of its physical travel, in game jumps to fully forward. I accept the fact that I may be being stupid(perhaps for buying a 3rd Logitech product ?) but i seem to be going round in circles(literally) with re-calibrating, inverting the axes, setting it as slider, most if not all combinationsi can think of but at the moment all i have on my desk is £200 worth of useless ornaments
  2. i attempted to PM you, let me know if you got it please
  3. Sure, my particular bindings; VA 'SRS PTT press' Button:Joystick 1 button 20(shortcut invoked when no other buttons are down checked) VA 'SRS PTT release' Button:Joystick1 button 20(shortcut is invoked only when all buttons are released AND shortcut invoked when no other buttons are down checked) In both cases the 'key to press' i chose (more or less at random i think) is 'RAlt O' So in SRS Controls i have 'Push To Talk - PTT' set to keyboard button 24(O) and 'Push To Talk - PTT Modifier' set to keyboard button 118(RAlt) The end result is that when i use the same joystick buttons with the addition of my 'pinkie finger' modifier for something not radio related, it doesn't clash and i don't issue an unintended PTT. No need for an additional utility to program your devices. sorry for the lag in replying - i have been on holiday !
  4. Do you use VoiceAttack or anything else that can re-map keys?, if you do that's one way around it - set up aliases and their conditions can be set to eg 'no other buttons are down', it's the way i acheive exactly that.
  5. [ATTACH]190895[/ATTACH] Yes i use(or have used) this. You're welcome to jump in a Gazelle with me to test. I just assign a spare button for 'Intercom Select' on the Controls tab, sit in the cockpit press that button and the asterisk should appear next to it in the overlay(Ctrl-Alt-Esc), then I use my common 'Push To Talk - PTT ' and the 'TR' appears on the overlay when depressed. Screenshot attached excuse the fuzziness. Tim
  6. Genius, thankyou. Faith restored :)
  7. assuming you are beta user? I have re-installed DCS today from scratch, and can confirm that as soon as I installed beta over the top of release, the comms menus in general don't work partially or at all in some cases(at least in the A10C), this is without any lua alterations for VAICOMPro. I just don't think it's stable enough to expect anything comms-wise to work reliably.
  8. If I toggle between 1.5.0.0 and 1.5.1.0 the latest just doesn't work. Uninstalling latest and re-installing 1.5.0.0 gets it back again.
  9. 2.5.2 doesn't work for me after re-installing and double checking the lua. Reverted to previous version and all is good again
  10. Did you get time to consider exposing the current callsign? If so, what's the var name? Cheers
  11. Do you mean when setting COM1/COM2 to 'M' on the UFC ? Just did this in Harrier MP - press the '-' key to clear the field, then enter frequency followed by 'ENT', worked for both radios. T
  12. ..and just another 'fyi' - when i try retrieving the module when using the J-11 (part of FC3 in 2.5.1) '----' is returned, understand this may well be wip and/or a 'openbeta' thing.
  13. You can add(or even import?) your own voice etc commands just like you would normally build a profile, create your own category so that you see them all in one place(2nd box below where you enter your key presses etc). I have a few dozen of my own working just fine. Just make sure you don't have any the same as any inbuilt keywords.
  14. A very fair question :) I wanted to be able to announce my callsign by command to voice attack, 'your callsign for the mission is ....' sort of thing. I know it kinda sends you off doing stuff you didn't really intend the package to be used for possibly, and there might be another way i can get hold of it but nothing i've tried has so far worked. edit: there is also a slight bug in that if you come out of a mission, then click 'Fly again', while you can choose a different airframe, the variable holding the aircraft type reports the original airframe.
  15. exposed variables First, thanks Hollywood for this app which adds to the immersion greatly for me. I have already used the aircraft type in some VoiceAttack commands of my own to great effect, but can I ask if 'player callsign' is available, or if it's not available can i request that it is added to the list? Thanks Tim
  16. AV8 TX1/TX2 Hi, am slightly confused. In the AV8 sat on the ramp at Nellis and it seems my 'TX1'(VHF AM?) has mapped to 'COM2' in aircraft. 'TX2'(UHF?) has mapped to 'COM1'. Upshot is I can only get a reply from TWR if I use TX2. Is this right, it doesn't behave like this in the A10C, I would just use TX1 Thanks
  17. thread is worth a 'bump'. I see the same symptoms, landing for 2nd time on a ship(CG-60) in the gazelle
  18. t1mb0b

    KC 130

    There is this in the meantime, which works well https://forums.eagle.ru/showthread.php?t=198983
  19. Many thanks, have a great 2018!
  20. Tx tones from VA scenario: sat in the A10C with VHF(AM), VHF(FM) and UHF radios on and selectable with mic switch mappings. All 3 are set as the relevant PTT in VAICOMPro and i can see in VA that when each is pushed i get the TX1/2/3 commands along with 'Listening resumed'/'Listening suspended' messages. I am however only getting the 'hash' tones at the press/release when using the TX1(VHFam) PTT. Any ideas why not the other 2 radios?
  21. non standard folder Thankyou for your reply, hopefully my 2nd question is not as dumb as my first. At startup of VAICOMPRO my DCS v1.5x installation is not being found, it doesn't matter what i put in the 'custom folders' section it doesn't pick it up. I have v1.5 in a non standard folder(not under c:\program files) Is there a manual workaround i can try for v1.5x? DCS v2.2 is fine Thanks in advance.
  22. no joy extensive user of 2.0 however when i try 2.5....on every interaction with PTT... 'UNABLE TO INVOKE PLUGIN, PLUGIN NOT VALID FOR THIS VERSION OF VOICEATTACK' version is 1.6.9
  23. voice attack 1.6.5 Hi, I was thinking of upgrading to VA 1.6.5, can i do this without fear? Thanks
×
×
  • Create New...