Grodin

Turning off easy comms fixed my problems too - thanks a million!

Tracks are horribly broken, as always :music_whistling: Carrier launches seem even worse, they seem to fail about 100% of the time but i'd guess it's a known issue by now.

Add "Exclude(&TFRPRudder);" so it looks something like this: Figured out you can do this the same way, add this line:

Yeah, this file will bypass that 32 button limit. You can assign any button anywhere you like, or even all of them to a single button. I have over 100 buttons bound on my throttle.

Many bugs and problems with TARGET. Even the saitek profiler does better job than this. I would guess you need to tinker with the hid.tmh file to only map the throttle, i dont think my script has any control over that. No need to change or add anything, just remove those 2 bottom lines. This information is already mentioned in the original post. Changing the axis names only defines if its a rotary or not, but the game doesnt care, it works the same.

I don't understand the question. You can map all of the DX buttons to any button in the script. You can make a single trigger press push 120 buttons if you want to.

Yes, i start on the ramp with cold plane, and when i push throttles forward they move to idle from off position without having to go back and forth. I don't have launchbar mapped, catapult launch key seems to work it automatically. Buttons 77 and 78 have the same output in the script, theres a typo, to fix it you can change the following line in the 120 button hack: "define DX78 3076" to "define DX78 3077" otherwise i have no idea about MFD, unfortunately i dont have those

Just place waypoints around the carrier at correct altitudes and enable waypoint makers with a trigger to get a pathway. Did a mission like this for a friend with many different kinds of approaches to airfields and carriers, really helped him notice how much he was wandering around when he was supposed to fly straight. They dont move with the carrier so it needs to be stationary, but anyone training crosswinds or moving carriers should already be proficient enough to not need waypoint markers to find the deck. Hardest parts for me is matching my last turn in the pattern so that i end up perfectly behind the flight deck without having to make too much corrections. 300 landings and starting to get a feeling for the turns now:pilotfly:

Hope they will add keybinds later, its the only keybind i was unable to find so far.

Neither actually! You want to map the command that is called "Throttle Left OFF/IDLE" and "Throttle Right OFF/IDLE". This makes the throttles go off when you lift the throttles back over idle detent, and it makes them go to idle when you push them forward over the detent to idle. Basically it locks the throttles to off position when it detects the switches inside the throttle being pushed (when you pull back over detent) and release them idle if not. Just need to have hotas sync option enabled for it to work.

Still using this, i'm almost running out of binds now, i'm at 109. Found a typo in the definitions that causes one button to not work: define DX75 3074 define DX76 3075 define DX77 3076 define DX78 3076 define DX79 3078 define DX80 3079 I assume that is supposed to be 3077 :thumbup:

Atleast i'm unable to go full afterburner on carrier launch unless fingerlift is being pressed. So i configured it to be up all the time.

Confirmed. Control options does keep up even with fast flicks, but for some reason the hornet does not register too quick flicks of the switch. No issues in A-10. Happens with all 3-position switches if moving from one end to the other too quickly, but only in the hornet.

Yes, you either need to edit a lua-file to do it or bind U key to a joystick via joystick software. C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Input\FA-18C\joystick\default.lua Adding line: Somewhere in that file, for example under "Special input for 3-pos 2-signals switches on joystick" should make it bindable under "Special toggle" and "special for joystick" categories and the command will be called "Catapult - Warthog". Feel free to name the command and categories as you like but make a backup of the first before modifying.

AFAIK there are no default binds for the F-18 yet, it's not yet a final product. You have to map it yourself. See the other topics on the forum for help with mapping :thumbup:

Heres a warthog TARGET script that will do the following: Every position of every switch on the throttle unit is mapped, even spring loaded ones returning to middle. DCS will see a joystick button being held down in every position of every switch. (With one exception, i did not find a reference to L/G WRN button when it is not pushed down, this button sends a button press only when pushed, not when letting go). Keep in mind that if you are binding a spring loaded button you have to hold it down when you click OK in the options because when you let go of it, it will change to a button that reflects the position where button spring returns it. This profile also converts the TDC hat to joystick buttons so you can map it to the F18. You can return it to a regular axis hat by removing bottom 2 "KeyAxis" lines from the script. And a tip for fingerlift/afterburner problem: Map the spring loaded china-hat middle position or maybe AP DIS to fingerlift, that way your fingerlift is always up when you are not actively pushing the button :thumbup: Also, when active, the script will replace the original seperate warthog joystick and throttle controllers so DCS will only see a single "virtual controller", this way when you mess around with the script it will not tamper your original warthog keybinds in any way. In addition to my attached profile file you will need to extract this "120 button mod" to your C:\Program Files (x86)\Thrustmaster\TARGET\scripts folder. https://forums.eagle.ru/showthread.php?p=2855428 1: Install the above file 2: Run my target profile script 3: Rock on! To be clear, this is used with the TARGET Script program, not the GUI program. I'm figuring out how to make a shortcut that will automatically activate the profile and start DCS to simplify things, will update when i figure it out. Changelog: V2: Joystick and throttle sharing same hats and buttons fixed. Joystick binds map: Warthog_BindAll_dx128_V2.rar

And heres a target script version :thumbup:

#70608 Finland

Most buttons on the warthog throttle actually only have 1 button. Putting a switch up pushes a button and putting it down releases it. Until they add A-10 kind of hotas support to the module you have to do it manually from the joystick config file. Basically it makes a keybind that does 1 thing when you push a button, and another thing when you release it. Heres some examples of mine. Also required if you want to bind catapult launch "U" button to a joystick. And theres also 2 commands to hold finger lift up all the time.

Where in the editor do you find those floating helpers or gates that are used in some of the training missions?

Yeah, often regular vsync causes horrible input lag and genrally reduces performance. I'm not sure how freesync works but for gsync you should disable vsync ingame and turn vsync and gsync on in the nvcp. This allows very high framerates without the input lag from normal vsync or tearing from having no sync at all. And if you don't have freesync/gsync monitor you likely get better results by capping framerate to your refresh rate (60, 144, whatever) with software like rivatuner instead of using regular vsync.

Hey! I'm having trouble getting mouse look working smoothly. Both interior and exterior views when panning the view with my mouse its acting very wierd. For a while the view barely moves at all, then it suddenly moves like it should, and then back to barely moving at all. Almost like the mouse sensitivity is adjusting itself all around the place by itself. I had this problem with my previous installation too, now i have a fresh OS and DCS install and its still happening. Dont have freetrack or such to mess it up either. Mouse works perfectly in menus or when clicking buttons in the cockpit, its only the view panning thats buggy. Any ideas?

Anyone got this working with 2.0? And a slightly offtopic question, is it possible to temporarily disable trackir while flying in such way that you can use snapviews or mouse to look around in the cockpit? Pausing or stopping tracking just forces the view to stay still.

Whats your resolution? This doesn't seem to be GPU issue, and on another note, ATI has nothing that comes even close to 1080, you are aware it's way more powerful than titan, and ATI has nothing that compares even to that...? http://www.game-debate.com/blog/images/_id1463131026_343178_1.png You quoted someone else, im not looking to run VR, im running triplescreen. Edit: But for comparison, 1920x1080 with everything maxed out, even view distance, gives 90-100fps when not limited. Also, if using "1 screen" option instead of "3 screens" with 5760x1080, performance is good, but image is stretched - 3 screens option renders correctly but hurts fps.

Seems like a CPU bottleneck and i'd say view distance is the main issue. Flying level on the edge of vegas, looking towards the center from a10c cockpit. All settings off or on the lowest possible: Extreme view distance: 44fps Ulta: 48 High: 51 Medium: 55 Low: 60 FPS stays same even if i pause it. GPU Usage 35-45% on all of those. So low visibility setting is the only smooth playable one. Maxing out all the graphics settings (AA 16Q, everything to extreme or highest possible except depth and lens effects) fps still 60 and GPU usage goes up 20% to around 46-65% So regardless of other settings, i have to keep view distance on low. Other settings dont matter, can max them out. Guess we need some watercooling and +5ghz cpu if that would fix it. 5760x1080 resolution, 4690k@4.5, GTX 1080, 16gb RAM, normal 1TB HD. No stutters, tearing or slowdowns. If only we could use higher view distance it would be perfect :joystick: Edit: Yeah, RTSS is locking FPS to max 60 to keep things smooth so any results over 60 don't show up here.