Gizzy

I had issues with installing 1.5.2.48726 and modules... seems there was an issue with either DCS server or my system DCS torrent updater. Run from a command window within the BIN folder of DCS World 2 OpenAlpha.. i.e. C:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\bin DCS_updater.exe install UH-1Hand then re-run if necessary to clean up. If unsure about command windows, this will explain http://forums.eagle.ru/showthread.php?t=114030 References... http://forums.eagle.ru/showthread.php?t=157236 http://forums.eagle.ru/showthread.php?t=157336 May help...

For info, For me... DCS Version 1.5.2.48726 (NOT BETA) ILS Horizontal steering bar not indicating - tested @ BUTUMI on 110.30 ILS Vertical steering bar is GOOD....

This intrigued me a bit so I had a look, I fly mostly the Huey at the moment. You are right Precog. Having a quick jump into the A10c, the 3 crew Mi8 and then the 2 crew Huey I reckon its to give perspective taking into account the width of the cockpit that is modelled. A10c, one pilot cockpit, hence you go to the left and right of the cockpit, equidistant from cockpit centre, before you find the 'invisible barrier' limits. Jump into the Pilots seat of the Huey and the left 'invisible barrier' will be near the middle of the cockpit, on the end left side of 1 mans 'space' so to speak. Switch to the co-pilots seat and the 'invisible barrier' is at the end of his 'space', on his right side, near the centre of the cockpit, On the Mi8, sit in the engineers position and you have 2 'invisible barriers' left & right at the extremes of his 'space' At least that's my take on it and of course it could be a load of boloney :huh:...

A great resource light app... works a treat in the latest DCS World 1.5 (not beta) Sincere thanks to all involved and everyone have a great 2016 :)

For info... I think your server is shutting down after just 1 module install and the installer then fires up a new autodate log file. I disregard it and re-run the install... it finds the old torrents of the installed module and asks to delete... once deleted it checks and then starts another.... then closes down... re-run etc.. etc No probs I'll get them all done in the end... Thanks again..

Thank you both for such a prompt response... Initial Post edited... blues... you know what I mean... Very impressive customer service, thank you...

SSD is getting congested with all the DCS versions. Tried the 1.2 upgrade to 1.5 path but DCS was not stable with various crashes that may of been MOD related so went for a virgin 1.5.2 install. Uninstalled 1.5 via W10 program manager. Deleted 1.5 directory in c:\Programs Deleted Saved Games 1.5. DCS 1.5.2 Virgin Install..... DCS installed fine. GREAT... Logged into Module Manager, it pops up and says to install L-39, VEAO_HAWK, F-86F, FW-190D9, MI-8MTV2, UH-1H, A-10C, P-51D & KA-50 Okay, Good... This procedure started but only installed just the L39C. The rest are not recognised as being purchased. No amount of logging out, logging in or rebooting changes anything.... Chizh in releasing 1.5.2 states So now what? Log File attached. It would seem that torrents shut down on the Hawk module... Happy New Year.... autoupdate_log.zip

Snipped from their web site... PAYMENT : When product is ready to ship (Invoice will be sent 7 days ahead ) Hope this helps...

You can just double click on the .tmc file and it will start OK in the script editor window. Then, manually fire up TRACKIR and DCS - obviously .tmc before DCS.. :) For me this uses about 80mb of memory. Starting it from a command line, as in a bat file, reduces overheads and it uses about 35mb memory. If you intend to use it regularly, use a .bat file to start and to save memory if desired. CD\ CD "C:\Program Files (x86)\Thrustmaster\TARGET\x64\" start "Gizzys Profile" TARGETGUI.exe -r "C:\Program Files (x86)\Thrustmaster\TARGET\x64\Gizzys-profile.tmc"If ever you want to start TRACKIR and DCS in the same bat file then I find putting a pause between each start line helps. There is no pause in W10 that I am aware of so use ping > null command to do the same thing. CD\ CD "C:\Program Files (x86)\Thrustmaster\TARGET\x64\" start "Gizzys Profile" TARGETGUI.exe -r "C:\Program Files (x86)\Thrustmaster\TARGET\x64\Gizzys-profile.tmc" ping 127.0.0.1 -n 2 > nul start "Gizzys Profile" "C:\Program Files (x86)\NaturalPoint\TrackIR5\TrackIR5.exe" ping 127.0.0.1 -n 2 > nul Start "" "C:\Program Files (x86)\VoiceAttack\VoiceAttack.exe" ping 127.0.0.1 -n 2 > nul start "DCS" "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS_updater.exe" Hope this helps some..

All I can say is they certainly worked for me now, very nicely... on 1.5b. Addition: Just checked, for the Huey, there are 2 profiles, HT UH-1H.xml and HT UH-1H-all.xml. The second allows 2 clickable pages, one for for the pilots side and 'tother for the co-pilots side... Takes a while to work it all out and get things positioned but it is good and lightweight on resources... Hope this helps....

Hogtouch as sorted by Simpit Dec Ass. https://github.com/s-d-a works very well..... http://forums.eagle.ru/showthread.php?t=142521 also has some info... Hope this helps...

No, there is no need being with the joystick independent of the throttle all switches are by default single DX push and release compared to a toggle which is either DX ON for one state and nothing for the other.... or 2 ONs and nothing for a 3 way - the off state being selected at a time determined by you rather than a default OFF such as a push button type.... Yes, you can modify in script, (TARGET GUI will not accept DX codes & keyboard input for one switch) but then you will not have the concept of being able to assign any function to any switch state within DCS, for any aircraft, at any time, without messing with MODS or changing the TARGET file... I was toying with the ideas of putting in layers within the script, having alternative commands available for long pushes similar to the coolie hat function within A10c but I would rather be flying... if DCS 2.0 was out and stable, I'll probably just edit the lua files... it is cleaner...

Thanks for coming back BN... Intel®Corei7-4710MQ @2.5Ghz 8GB RAM, NVIDEA GeForce GTX765M Yeah, its a laptop but it happily drives 2 large monitors (DCS on one only, HT on another) at an average 50-60fps on 1.5 with most settings at high. I spend a lot of time abroad... in the sun :) I haven't discounted the hub side and will try the TRACKIR straight into a main port. With 1.2 all is good though... With regard to DCS and entering new settings, using a TMWH switch or button, its rather hit and miss, as if DCS is having issues polling the controllers... once it working though, in game all is good...

Using W10. TMWH, Saitek C. pedals & TRACKIR all into one powered USB hub fed to USB2 port. TRACKIR is randomly (around 1 in 20 starts) not picked by DCS on DCS start - alt tab to TRACKIR and appears to be good although dead in DCS. Restart DCS normally fixes. Keys often not recognised in control assignment, manual selection works fine though. Very occasionally, rudder not working in DCS. Control viewport shows 2 rudder indicators, 1 red, 1 white... Reboot fixes. All issues duplicated although random, using TARGET software or not... DSC restart generally sorts.

Original Files have been updated. Script file changed slightly. In response to PM's PDF set up help file with screen shots now included. Explanatory Video now included. *** INITIAL POST REVISED **** Hope this helps....

Any grief just shout... :)

The 'HOLD' and 'PULSE' function is set in TARGET - when using DX codes 'HOLD' is good... DCS just recognises the switch state, there is no buffer unlike in the keyboard, which say if a character like 'h' was continously pressed or in 'hold' mode.... then sure you could have issues... For the shifted DX codes, the keyboard 'shift' key is used, hence only a 'pulse' is sent. So far all is working fine for all my models... the only issue is configuring a switch within DCS, normally select the control and move the switch and DCS selects the DX Code or keyboard key pressed. With 1.5 beta this is flaky, at least with me on W10 it is..., but there are drop down menus which are easy to use and select the right input...

BitTorrent or not, the download is crazy slow.... for me, 30kb/sec... Hit the cancel button and retry overnight later when sleeping ... A standalone update seeded and pulled via software of choice would be so much quicker..

For some time now I have been messing with various MODS and scripts to achieve some sort of commonality with my ever growing list of plane models. I have tried the very good ‘polaris_and_schnix’ suite of MODS and profiles and this came close to what I would like but still some of the switches are not the way I want them. Switch behaviour, mods and lua coding appears to vary from model to model and DCS or their partners. The recent updates to DCS 1.5 beta together with me forgetting to remove all the installed MODS with JMSME, caused some confusion and made me think about Thrustmaster’s TARGET again. TARGET configuration for each aircraft using the GUI is a real pain and there are issues although pilot error is often the cause, at least with me.... and although I have some programming knowledge I would rather be flying than scripting. To resolve this I have written ONE target script that will work FOR ALL switch states, buttons & axis for ANY AIRCRAFT model running in DCS. TARGET, DX Codes and Keyboard characters Without TARGET DCS will recognise the TMWH switch position by DX codes, that is, it will know when a switch is ON. A 2 pole switch has 2 states, ON & OFF and a 3 pole switch has 2 ON states with the middle position being OFF. DCS A10C is programmed to interpret all inputs correctly and switches ‘just work’ as they should. Other modules are different. You have to configure them in DCS. Some Aircraft model switches will recognise both DX states and the switch works, others do not and you have to move the switch twice to toggle it and 3 position switches are even more awkward. You can directly alter the .lua files and mod each aircraft switch behaviour separately by editing the LUA file and even then, correct switch behaviour is difficult to achieve. Often these MODS are overwritten on updates if not removed beforehand - in reality not a big deal if you are using JMSGE. With TARGET you can program a script to send keyboard characters or DX codes to DCS when you move TMWH switches. You need to be a little bit careful with how keyboard characters are sent to DCS, generally they not should in a ‘down’ state for long periods of time. With DX codes it does not matter. This target script is for the THROTTLE only and is written to send DX codes and keyboard Right Shift codes only. I have included a PDF diagram showing what is sent for each switch state. Example 1 Consider a 2 position switch such as EACON. For on (up) a DX25 is sent, and for off (down) RSHIFT + DX25 is pulsed. Example 2. Consider the 3 position FLAP switch. FWD sends DX22, AFT sends DX23 and back to MIDDLE send a pulse of RIGHT SHIFT + DX22. In DCS for any model, for any switch, you just configure how you want the switch to work. For say the Dora flaps, configure Normal flight to DX22, Take Off position to RIGHT SHIFT + DX22 and for Landing position, DX23. Your flap switch will now work correctly without MODs to any files. For say the Huey, there is a toggle for both opening and closing the doors. You can assign 2 inputs to one DCS control. Using EACON as an example, bind both DX25 & DX25 + RSHIFT so that moving the switch up - the doors open, move it down - the doors close. See the youtube video for an example. A10C Additionally because all the DX codes used in the script are the same as if TARGET is not being used, it will works fine with A10C straight away without any configuration. (The RShift inputs are ignored..) To do this you need to copy the file C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\A-10C\Input\A-10C\joystick\Throttle - HOTAS Warthog.lua to say your desktop, rename it to Thrustmaster Combined.lua and place it it the same directory, thus: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\A-10C\Input\A-10C\joystick\Thrustmaster Combined.lua RUNNING TARGET SCRIPT If you run the TARGET script from the command line via a BAT file, the memory used is very small. It is easiest if you place the file "Gizzys-profile.tmc" in the same directory as ‘TARGETGUI.exe’ A simple '.BAT' file for my system is included - you may need to configure it for your directories - in addition I use the same BAT file to start TRACKIR and DCS 1.5 OB. TO SUMMARISE ONE SCRIPT TO RULE THEM ALL - One simple script that will cater for all Aircraft models AND all TMWH throttle switch states and axis without code changes or MODS. · The TMWH Stick remains separate. · Run the script from a BAT file before starting DCS. · Configure all aircraft model switches within DCS as normal, when you need them, for ALL states. · A10C will run just fine, ignoring any of the RSHIFT + DX codes - BUT you can now switch to any aircraft model and continue. · 1 target script for all aircraft. The files have been updated. Slight change to script. Help file now has screen prints included and perhaps easier to understand. BAT file edited. Heres a simple video explaining setting up and configuring 3 different switch types. Any probs - shout... Hope this helps... [ame]https://www.youtube.com/watch?v=REfJKlzuLk8[/ame] PS: The video shows the .bat file command as [font=Arial][font=Arial][font=Arial]start "Gizzys Profile" TARGETGUI.exe -r Gizzys-profile.tmc[/font][/font][/font] This may cause complie errors, the tmc file if listed with path as shown below, will be fine... start "Gizzys Profile" TARGETGUI.exe -r "C:\Program Files (x86)\Thrustmaster\TARGET\x64\Gizzys-profile.tmc"The .bat file in the zipped download is good.... Gizzys Profile HELP.pdf gizzys-profile.zip

Many will often have different views depending on the input devices used, models flown and how much 'stuff' they want mapped to devices, keyboards etc.. You an use CAPS LOCK and TAB, generally without conflict if you want the to use the keyboard... Have a look at this link http://forums.eagle.ru/showthread.php?t=87543 - it will use function keys on your keyboard that are not normally used and assign them to a controller via a small prog with lttle overhead. Also, consider trying other profiles... this one originally from WAGS for me is the best, it really stopped a lot of re-centring in-game.. http://forums.eagle.ru/showthread.php?t=64447 Might help... :)

Looking at it further the NVidia driver is not making the switch from onboard graphics to the main GPU. I have a manual overide so thats a workaround for now....

Last update crashes Intel HD Graphic Driver for Windows 8.1 (even though it is W10 - thats the driver), it recovers then DCS crashes, every time.... Cant find the update version but downloaded evening October 14th. WIndows 10 Intel HD Graphics 4600 onboard vid & NVidea GeForce GTX765m 2gb. Being worjking a treat till now ....

Re-installed and problem solved.... looked like a corruption somewhere... but any way now looking good... 1.976a Windows 10...

AriesProtocol.exe TS seems to be crashing out an awful lot even without Aries .... On my W10 system AriesProtocol.exe is started with TS start even though Aries is disengaged in the plugin and the lua. Is this normal... Cheers...

Thanks Sabre - sorted...