Hi,

i've recently got my new warthog and i was very happy to see you providing a decent profile. Unfortunatly i'm sometimes unable to use it because the joystick itself seems to kinda disconnects after i run the script. Any ideas regarding this issue?

Cheers,

Disi
 
Hi,

i've recently got my new warthog and i was very happy to see you providing a decent profile. Unfortunatly i'm sometimes unable to use it because the joystick itself seems to kinda disconnects after i run the script. Any ideas regarding this issue?

Cheers,

Disi

Hi Disi,

Congrats on your new toy :)

Disconnecting after running the script tends to indicate it is not creating the virtual device correctly and fails. Could be a number of things. Few suggestions below:

- Ensure the latest Software/Drivers/Firmware is installed to your PC and Devices.
- Unplug any other devices (outside of KB/Mouse) plugged into USB and retest. (May require a shutdown and restart)
- Check the order of the devices listed in Game Controllers view in Windows (type 'game' should bring it up from Start Menu). This should show the Joystick first, then Throttle, then other devices. If in wrong order it can cause issues from my experience. If so unplug everything and one by one add them again. Again may need shutdown and restart.
- Check any errors being returned in the printout of the script run, can give a clue to the issue.
- Test everything is ok in Device Analyzer before script run (ensure devices are recognised and functioning correctly).
- Try different USB ports or USB controllers (ie if plugged into USB3 ports, try USB2 ports etc)

Found quite a few users have some initial teething problems with Warthogs, but once good they are solid. Hopefully its something simple.

Regards, AD
 
Hi,

i've recently got my new warthog and i was very happy to see you providing a decent profile. Unfortunatly i'm sometimes unable to use it because the joystick itself seems to kinda disconnects after i run the script. Any ideas regarding this issue?

Cheers,

Disi

Hi,

If you had any other TM products installed before just unplug them, uninstall all software and drivers and restart.
Install latest drivers and TARGET GUI for Warthog, connect when prompted and restart after installation.

This combination resolved my problem with not creating virtual joystick in TARGET. I had T 16000M FCS before and lost almost 2 days to figure this out.
 
Hi Disi,

Congrats on your new toy :)

Disconnecting after running the script tends to indicate it is not creating the virtual device correctly and fails. Could be a number of things. Few suggestions below:

- Ensure the latest Software/Drivers/Firmware is installed to your PC and Devices.
- Unplug any other devices (outside of KB/Mouse) plugged into USB and retest. (May require a shutdown and restart)
- Check the order of the devices listed in Game Controllers view in Windows (type 'game' should bring it up from Start Menu). This should show the Joystick first, then Throttle, then other devices. If in wrong order it can cause issues from my experience. If so unplug everything and one by one add them again. Again may need shutdown and restart.
- Check any errors being returned in the printout of the script run, can give a clue to the issue.
- Test everything is ok in Device Analyzer before script run (ensure devices are recognised and functioning correctly).
- Try different USB ports or USB controllers (ie if plugged into USB3 ports, try USB2 ports etc)

Found quite a few users have some initial teething problems with Warthogs, but once good they are solid. Hopefully its something simple.

Regards, AD

Hey AD,

thanks for the quick response this seems to work flawless ATM. Cheers.

Another Problem i'm encountering is your Keybind File in Combination with Voice-Attack and Singularity

Code:
Keyboard bind missing in Elite: Flight throttle: Forward only throttle reverse
Keyboard bind missing in Elite: Weapons: Secondary fire. Previous profiles used mouse2 but Singularity requires this to be a keyboard key
Keyboard bind missing in Elite: Elite keybind not setup: Galaxy Map:Galaxy cam yaw right cannot be the same as Interface mode: Next panel tab if you want full route plotting to work.
Keyboard bind missing in Elite: Elite keybind not setup: Galaxy Map:Galaxy cam translate right cannot be the same as Interface mode: UI panel right if you want full route plotting to work.
Keyboard bind missing in Elite: Galaxy Map:Galaxy cam translate backward cannot be the same as Interface mode: UI panel down if you want Elite bookmarks to work.
Keyboard bind missing in Elite: Galaxy Map:Galaxy cam translate forward cannot be the same as Interface mode: UI panel up if you want Elite bookmarks to work.
Keyboard bind missing in Elite: Drive throttle: Forward only throttle reverse
Keyboard bind missing in Elite: Free camera: Attach/Detach camera
Keyboard bind missing in Elite: Full Spectrum system scanner:Leave FSS

Any idea on how to solve such things as "Weapons" or "Drive throttle"

Cheers,

Disi
 
Hey Disi,

VA seems to be getting fussy these days lol :p

VA keybind issues for the 4x Galaxy Map binds was reported previously. I have these updated for the next release. In the mean time, you can change the current mappings in ED to CTRL+(Current Mapping), which should fix it. I've updated all the Galaxy mappings to CTRL+(Current Mapping) now.

I guess for the Weapons, you will need to remap the secondary fire, secondary mapping from Mouse2 to something else not currently used. I don't think there is a spare button to map to something else without removing this one. Shouldn't really need Mouse2 mapped anyways except if you use Mouse in Multicrew perhaps.

Reverse key should be mapped to Modifier 2 for when Forward only is set in bindings file, but that is not an actual keybind so may showing up as missing. You can use the Throttle Presets built into the script and the digital reverse thruster mapping on the front hatswitch on the Throttle as an alternative. If you use full range throttle then should be able to ignore (I hope). **Edit - I have checked the mapping and see its missing a keybind. I have added CTRL+R in the vacant binding for next release**

Also, I have added a key mapping for Attach/Detach Camera to CTRL+C for the next release.

Leave FSS, I think I have mapped to the UI Exit (squeeze Mod 1 + Mod 2) plus the same Enter FSS mapping so either key can be used. Both are DX mappings so will not register as a key. Will need to remove one of these mappings to remap to something else, for example CTRL+E.

Cheers, AD
 
Last edited:
Hey Thanks for the advices and your awsome support, i appriciate that very much!

I've setup everything you said and it works great :)

I've getting a little bit confused regarding the VoiceAttack and Discord/Teamspeak toggle feature.
As far as i understand the FLOWR-Toggle switch on the throttle is used to change between integrated (ED) and External Voice Coms. I've binded that toggle Mic in Teamspeak and the Recognition Hotkey in VA to ALT+F2 but nothing seems to happen.

Any ideas on that?

/Edit

Hmm still not getting it

m7gfw0


Its using L-ALT + F2 + / (\)

Code:
define ExternalMicCombined	1						// For OPEN Mic Toggle Switch on Throttle Base; combine 2 External Voice Channels to One Toggle action: 
														//	Options:		Separate Channels = 0 (default),	Combined Channels = 1 	(Remember: Set your Keyboard PTT/Toggle Mappings in your External Programs)
define ExternalMicInverse	1						// For PUSH-TO-TALK Mic Button on Throttle Arm; changes behavior to inverse the external channels on PTT button between VoiceAttack & Discord (or your preferred external comms). When enabled '1' and button pressed, VoiceAttack will mute and Discord channel will open, ensuring no voice commands are sent while conversing with friends. When button is released, VoiceAttack is activated again & Discord channel is muted.
														//	Options:		Two Independant Ext. Channels = 0 (default),	Inverse VA<->Discord Activation = 1
														// 	[NOTE 1: To ensure proper alignment, ensure Listening is enabled in VoiceAttack before your first Mic press.]
														//	[NOTE 2: Set 'MicExternalAction' to 0 and enable PTT in Discord/Comms (map to '~')]
														//	[NOTE 3: Enabling this option will also inverse the Internal Comms Channel with VoiceAttack]

define MicExternalAction	0						// Define Main External Voice Software Behaviour: 			(If your software is Toggle action (On/Off) = 1 (default), If it's Hold action (PTT) = 0)
define MicExternalActionALT	1						// Define Alternative External Voice Software Behaviour: 	(If your software is Toggle action (On/Off) = 1 (default), If it's Hold action (PTT) = 0)


Hope you can clearify it to me
 
Last edited:
Great! Glad to help.

There is the Modifier 3 (Mic) mapped on one of the Throttle base toggles. That should need to be set to External (down). Leaving Internal (up) should enable the standard internal mic controls.

(Forget what I wrote before if you read it)

Cheers, AD
 
Last edited:
I think i figured it out quite well now, its not alt+f2 like in the documentation its zerkumflex ( ^ ) on a german keyboard. I've set the keyboard via the config file already ... maybe a bug?

Is the only way to disengage Hyperspace holding modifier 1 or 2 und push the throttle all the way up?

Cheers,

Disi
 
Last edited:
I think i figured it out quite well now, its not alt+f2 like in the documentation its zerkumflex ( ^ ) on a german keyboard. I've set the keyboard via the config file already ... maybe a bug?

Is the only way to disengage Hyperspace holding modifier 1 or 2 und push the throttle all the way up?

Cheers,

Disi

Ahh, have you also changed the keyboard layout to GER? I always forget to consider different regions. ;)

If you have Supercruise/Hyperspace on the Throttle, then you are correct, you will need to perform the same action taken to engage to disengage. The way the speed scales you will find it doesn't impact flight at all really even when approaching stations and the like, but can feel counter-intuitive to start with. You can disable Supercruise/Hyperspace on the Throttle if you prefer, and it will move it to the China hat switch on the side of the Throttle (moves a few other commands around too, to fit it in).

Fly Safe CMDR, AD
 
Hi AD,

yeah you're right the throttle still feels counter-intuitive but it doesn't effect things as i thought. Its quite unfortunatly that with the german keyboard the "^" is used ... could you change it to alt+f2 too?

Cheers,

Fyl Safe CMDR
 
Hey Disi,

Can you confirm that you have changed the keyboard layout in the settings file:

define KBLayout KB_ENG

to

define KBLayout KB_GER


That should align things from what I understand. VA is already mapped to ALT+F2 in the script. Had a quick look and do not think there is anything with the other symbol ^.

Cheers, AD
 
Last edited:
Ah ok, sorry I wasn't sure. Strange that it does not line up then as that should occur when KB is set correctly.

I think if I change that to ^ then all English users would need to change it as well in VA (correct me if I am wrong as I no longer use VoiceAttack myself, but thought ALT+F2 was the default key).

Script maps to ALT+F2, but if you press the same thing to remap the hotkey command in VA, what does it set? Does pressing ALT+F2 actually display ^ in a notepad for you?

Alternatively, you could also remap in the script to SHIFT+6 (^) instead as a workaround.

Cheers, AD
 
Hi AD,

pressing the button in VA and Notepad as well as some other tools like teamspeak and co alwys result in "^".

Where do i remap the button in the script?

If you don't use VA anymore is there an alternative you are using?

Regards,

Disi
 
xAWeE37m.jpg
jCvSJm0m.jpg


Decided to make my own legend plate :)

Never have managed to get your script working :-( half the time I load elite it fails
to recognise the stick :-(

Anyone have ideas on why when I run the script Elite fails to see the controls?

Works fine with no Target running, but when target is running its 50/50 on seeing it in game

o7
 
Hi AD,

pressing the button in VA and Notepad as well as some other tools like teamspeak and co alwys result in "^".

Where do i remap the button in the script?

If you don't use VA anymore is there an alternative you are using?

Regards,

Disi

Hey Disi,

To remap the VA mapping in the script, open the AD_EDKeyMap file and change:

define ToggleVoiceAttackGlobal

For VA for me I always found it problematic, I assume its my accent lol. Having to say a specific phrase also drove me nuts. At the end of the day, its great for immersion but pressing a button I found to be faster and more reliable.

I don't really use anything else for voice commands, but I do use EDDI for voice responses. EDDI is fantastic addition, really does bring the cockpit to life. Can't live without it these days :) Can be used in conjunction with VA too.

I use a voice called Ivona Text-To-Speech (British - Amy voice) to make it sound very similar to the default cockpit voice. Have to buy it though.

Decided to make my own legend plate :)

Never have managed to get your script working :-( half the time I load elite it fails
to recognise the stick :-(

Anyone have ideas on why when I run the script Elite fails to see the controls?

Works fine with no Target running, but when target is running its 50/50 on seeing it in game

o7

Hey CMDR Delmonte,

That is Awesome!! Nice work! How did you go about doing that?

Your issues sound similar to what Disi was originally experiencing, where the virtual device isn't creating successfully. I put forward some suggestions in #722 reply a few replies above. If they do not work, performing a full uninstall, unplug all USB devices you can, restart, and then rerun through the latest installation may help fix it. Ensure you check your firmware too, as there was an update not long ago for the Joystick. Could also try running via the Target GUI (if you haven't already). Remember hearing that some found it worked better there (not sure why).

*Edit* - Also worth a try just for testing; copy all your bindings to a backup location and delete any except for the 3.3.0 binding files (just in case its an older binding causing it not to show properly)

Cheers, AD
 
Last edited:
G'day AD,

Not sure if you gave up completely on the whole Wing Beacon ON/OFF macro.
I just noticed after the last patch...they've moved it yet again...it's now back on the left side of the panel again.

I've adjusted my macro and it does work for me.
Here it is in case you are interested in having another look.

Code:
// NAV Beacon - ON

mNAVBeaconWing = CHAIN(				// MACRO: Toggle 'NAV Beacon' ON 
// 4, e, e, e, right, down, down, down, down, down, spc, down, spc, up, up, up, up, up, left, q, q, q, 4
	LOCK+PULSE+SystemPanel, D(250),	
	PULSE+UINextPanel, D(),			// Limitation: This will only work correctly if Target Panel cursor in
	PULSE+UINextPanel, D(),			//			   default/orig position, else will be misaligned.
	PULSE+UINextPanel, D(),
	PULSE+UIRight, D(),
	PULSE+UIDown, D(),
	PULSE+UIDown, D(),
	PULSE+UIDown, D(),
	PULSE+UIDown, D(),
	PULSE+UIDown, D(),
	PULSE+UISelect, D(250),
	PULSE+UIDown, D(),
	PULSE+UISelect, D(250),
	PULSE+UIUp, D(),		 		// send selector back to home position when done
	PULSE+UIUp, D(),
	PULSE+UIUp, D(),			
	PULSE+UIUp, D(),
	PULSE+UIUp, D(),			
	PULSE+UILeft, D(),
	PULSE+UIPrevPanel, D(),
	PULSE+UIPrevPanel, D(),
	PULSE+UIPrevPanel, D(),
	PULSE+UIBack, 
	LOCK);

Code:
// NAV Beacon - OFF

mNAVBeaconOff = CHAIN(				// MACRO: Toggle 'NAV Beacon' OFF
// 4, e, e, e, right, down, down, down, down, down, spc, spc, up, up, up, up, up, left, q, q, q, 4

	LOCK+PULSE+SystemPanel, D(250),				
	PULSE+UINextPanel, D(),			// Limitation: This will only work correctly if Target Panel cursor in
	PULSE+UINextPanel, D(),			//			   default/orig position, else will be misaligned.
	PULSE+UINextPanel, D(),
	PULSE+UIRight, D(),
	PULSE+UIDown, D(),
	PULSE+UIDown, D(),
	PULSE+UIDown, D(),
	PULSE+UIDown, D(),
	PULSE+UIDown, D(),
	PULSE+UISelect, D(250),
	PULSE+UISelect, D(250),
	PULSE+UIUp, D(),		 		// send selector back to home position when done
	PULSE+UIUp, D(),
	PULSE+UIUp, D(),			
	PULSE+UIUp, D(),
	PULSE+UIUp, D(),			
	PULSE+UILeft, D(),
	PULSE+UIPrevPanel, D(),
	PULSE+UIPrevPanel, D(),
	PULSE+UIPrevPanel, D(),
	PULSE+UIBack, 
	LOCK);

Cheers
Clicker
 
Last edited:
Back
Top Bottom