Jump to content

Gizzy

Members
  • Posts

    654
  • Joined

  • Last visited

Everything posted by Gizzy

  1. On 'shutdown trainer' no previously saved 'user snapviews' are available - is there any simple remedy for this and will this state continue within any other campaign missions? 'Startup tester' is fine and so far the BFT seem ok but it is early days... Cheers...
  2. Gizzy

    ATC comms

    Thanks for your time BN... :thumbup: Found the issue, AriesWings was connected to DCS although using DCS in SP mode getting to grips with the Huey.. result on partial response from ATC if at all! Once I disconnected it, perfect - working as expected. Thanks Again
  3. Gizzy

    ATC comms

    Yes, I can duplicate that fine, from a clean start from runway. However from a ramp start I experience no response to [1] startup request, or if started, [2] taxi to runway, nor a [3] hover check and once taxied to start, no response to [4] Take off request - likewise if in the air no response to [5]inbound, [6]azimuth or [7]landing requests... Maybe I'm missing something (probably) but can anyone get ATC responses on the above - if so I will just have to work on it...
  4. Gizzy

    ATC comms

    Thanks for your very fast response BN, it is very much appreciated... :) Now back to the task....
  5. Gizzy

    ATC comms

    Can someone please confirm that Huey <> ATC comms are working fine? Certainly I'm not winning here at all... a search of the forums returns some saying all good and others saying that they are broken... If they are working fine with you please give a location and freq.. Cheers...
  6. This will do it for you, add on line after ....keyCommands = {....... --Alternate flaps {down = device_commands.Button_1, up = device_commands.Button_2, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 1.0, value_up = 1.0, name = _('Alternate Flaps Up middle'), category = _('Flight Control')}, {down = device_commands.Button_3, up = device_commands.Button_2, cockpit_device_id = devices.CONTROL_SYSTEM, value_down = 1.0, value_up = 1.0, name = _('Alternate Flaps Landing middle'), category = _('Flight Control')}, Set bindings for Flap UP and Flap DWN and the MID (T/O) will look after itself....
  7. Got it sorted TXMTB, your last post confirming that the throttle works made me persist. With me the initial test screen is 'dumb' if the throttle is at all selected as Joystick 1 or 2 until the circular arrow to the right is pressed then voila all works.... Strange as if the Joystick is selected on its own without the throttle it works as expected straight away.... Rep your way, thanks
  8. Sometimes a pic better than words - no matter what button you press on the throttle nothing will indicate in the test mode.... Tried all normal actions, removed from hub, only one uhb device plugged in, reinstalled software, checked device firmware update and even tried VoiceAttacks latest beta to no avail...... Other than this, the device works faultlessly...
  9. Thanks for the reply but I cannot be clearer, if you select the throttle device under Joystick Options singularly or with the joystick device, i.e. you assign the voiceattack joystick to the TMWH throttle device then if you use the test button nothing is recognised - therefore you cannot proceed to the joystick button recognition stage as displayed in your pic.... Deleting and reinstalling TMWG drivers made no difference. Could you let me know your VoiceAttack version... please
  10. Thanks the response but why? This setting is disabled. You cannot initiate it until you have a functioning device, sure I can use the joystick device but that's not what I am after.. Under Joystick Options, if you select the Joystick device the test generates a correct response. If you select the throttle device there is no response under test... If you select Joystick in one option and Throttle as another option, you get no response in test from any device. Have you a response under test from a TMWH throttle device button?
  11. Using TMWH & Voice Attack.... I use these as 2 separate devices - they work just fine in all games and Windows Game Properties. Trying to set up a button [DX5] to initiate ‘Joystick Button Recognition’ in VoiceAttack. Under ‘Joystick Options’ :- if the ‘Thottle HOTAS Warthog’ device is selected there is NO response under test. If the ‘Joystick HOTAS Warthog’ device is selected THERE I A response under test. If ‘Joystick HOTAS Warthog’ is selected as joystick 1 and ‘Throttle HOTAS Warthog’ is selected as joystick 2 there is NO response from anything... Looks like it will not interact with the throttle device... anyone had success in this area?
×
×
  • Create New...