POLARIS1

You're welcome will :) As for why the devs didn't...it's simple...if they would have they would have faced with endless requests, debates, nay sayers and what not from their customers whom they would have had to satisfy. The relation between customers/ colleagues and volunteered work is quite different in its nature. Enjoy :)

Maybe it should be. Before all the profiles were given, for all the HOTAS types, each and every player had to read the manual, understand the plane, fly it and establish his or her profile. That meant that each one became very good at DCS from the grounds up. The problem with it is the crazy learning curve that involves DCS and its modules. So...I, as others, have chewed most of the important stuff that deals with the HOTAS configuration and though there are a few bites left one can swallow mostly as is...

Dinger, As a proud owner of the MFG pedals I must say that the two sets complement each other quite nicely!

Simple answer: Yes! In almost every aspect. The only "problem" with it is its hefty price tag.

Leadlag, Thanks ! Gospadin, Thanks...and...there aren't any plans at the current time. Regards

Let's start with the logic of custom controls. The way most switches in most modules are programmed (except for the Hog and the KA-50) is: Switch is turned on (up) > a circuit is closed > electricity > a acommand is registered which can be assigned to a switch. Regular commands don't/ aren't programmed to register/ recognize a switch down action/ state. EG when electricity is switched off. If the programmer made a few states for a certain cockpit switch one can use a certain state as up and in the same line add a down command/ state. In short: Pre change: a switch has to be toggled (up for on and then down and agian up fir off). 2 way switch: up for on and down for off (added a down state in the mod). Now we come to the 3 way switch. It has a forward position, a middle position and an aft position. You can look at it as 2 switches joined in the middle: forward is up 1 and middle is off and aft is up 2 and again middle is off. So...I made two commands: Forward middle: you assign the flaps fully retracted. Aft middle: you assign the flaps landing position. In both cases it is programmed within the mod that moving the switch to the middle position (from either forward or from aft) to put flaps at stage 2. I hope it makes sense :) I could show you a simple picture with my actual DCS settings but I rather you understand the logic and hense continue to use the idea as you see fit in other planes as you wish.

Seems like I also have this menu flickering virus. It appears everywhere except for flight. I tried uninstalling and installing and it did no good. It seems like it's some sort of an NVidia issue. Any advices?

Every single profile is made only after extensive knowledge and experience with its module. Without the help of those who publish newer modules it's more than a challenge... Therefore, the package shall remain as is basically with most modules covered and a base to build upon. Sorry for I tried but couldn't succeed.

Sad.

Oops...: 1. Freeze your trackIR before you set and save. 2. Change zooming outside from TrackIR.

Oydoron, I have seen this phenomenon happen once with someone who has a Saitek x-55. Different dates and two of each for each controller. That's about all that I can say about it for I don't know the implications...other than to assume that it shouldn't be that way.. Best of luck mate ...

Thanks mate ! When this project started it was meant to be a starting point from where it shall be easier for users to go on their way into separate modules. As more and more modules were added our, and the community's, appetite grew ;) We would very much like to do all other modules in DCS...but...we lack the knowledge and experience in order to make professional profiles for them. Each profile already made has countless hours of flying with and after extensive research and personal knowledge concerning each aircraft and aircraft's system. There might be another way at it...and we shall check it out. We would love to give the community a full set of profiles for all current and future modules and we hope we shall manage it... Polaris

Hawkwind, First a simple explanation of how DCS stores your personal inputs nowadays... Each time you assign a new command, wether it be to a joystick, throttle, or any other controller, DCS stores it in a new difference lua file, for the specific module you're dealing with, in the saved games DCS input folder. This file has only the difference from the original lua stored for that module and which contains all the original assignments made by the module builder. A file we don't touch. What you find in the downloaded package are all of my inputs from the saved games DCS config folder, which contain the difference luas for the modules I published. Now that this is explained...what you actually do is not break each module's difference lua into small bits, but: 1. Go into your saved games folder and delete or extract or backup your (for example) F-15C folder which is in the saved games DCS config input folder...and...replace it with the one you downloaded. The whole F-15C folder from within the downloaded input folder. Another way at it, if you're beginning from scratch, is to replace your whole input folder, within your saved games, with the input folder you downloaded. 2. Open DCS and within its settings clear the current F-15C categories' assignments and load the new ones from the C disk's saved games folder (again, from within DCS input settings). As for clicking FC3 cockpits...it's still a dream mate ;) Hope it helps Polaris

Oops...took me too long to come here so I ask for your forgiveness :) CJS, When I started this project my intention was, and still is, to help new comers but not to hand feed them...meaning...one should invest time and effort in reading the manuals and learn them. Still, I find that your remarks are to the point and some explanations are not clear enough. If you shall be kind enough to make a PDF manual with pictures and taking it step by step I would appreciate reviewing it with you and adding it to the package. As for the curves...the curves I'm using are quite minimal due to the extension and the current pedals I use. If that is not clear enough I shall emphasize it in the next update. As for making them straight...I use a very small curve of 5 in all my modules for the HOTAS, a different curve for the Mig-21 as per the manual's advice and different minimal pedal curves for different modules (choppers, WW II, jets). So...I just give what I use. Hawkwind, I think the problem you have comes from the fact that you didn't clear all your input categories (stick, throttle and pedals) before loading the new inputs. Do try that and get back to me if that helps. As for the current state of how the sim's input works... This thread came to life following an argument discussing how difficult it is to learn the logistics of DCS and to operate them, and, especially how hard it is on new comers. I found that thread to be counterproductive...while not disagreeing with what was written. It's ED's sim and we can ask them to make changes. It is up to them to implement what they sim fit. Now, we can get angry when we don't get what we want and either leave...or...stay and make it better. For us and for others. So...in short...I thank you deeply for your appreciation of the work done and I hope that you figure out the problem you have with the inputs. As for me...I shall be content if new comers shall find it much easier to come into DCS and stay through the help of this thread and others' help. As for the more seasoned members...I'm truly glad you find it helpful (again, to my utmost surprise) and if you could help in making the inputs even more professional and accurate through advices here I shall be appreciative. Polaris

Version 9.5 update - Ka-50 zoom view input reversal fix. - UH-1H throttle switch Up and Down directions. - UH-1H cleared slew control from camera vertical and horizontal views. - FW-190D pedal brakes reversal fix. - Added a blank graphical layout. - Custom Controls updated to latest DCS version 1.2.16.

CJS, 1. "Perhaps offer 2 levels of profile.... One a flight, basic instrument controls and DCS functions such as zoom kneeboard etc all married to function - and then another level geared towards say combat with all the additional controls and sights." - sounds interesting. 2. "The included instruction text could be more informative" - what exactly do you find lacking? 3. "A generic blank pdf layout for written amendments may be useful for those who do not have PS" - a very good suggestion! It shall be added to the next update. Thank you for your continued review, thoughts and offer of help! KaspeR32, My biggest surprise from this thread is that while it is aimed at new players veterans find it useful. Thank you for your kind words and I'm glad it helps you. As for your offer of donation I can only say I deeply appreciate your thoughtful offer !!! As it is I'm giving back to the community what has been given to me since I first ventured into these pages. Starting from flight advices, tactics, armament, SOP, graphical alterations and so many mods...so many who have been giving and making our DCS flying so much better and without asking anything in return. In short...your appreciation is a better currency for me :)

CJS, First of all thank you for taking the time and giving a feedback, as well as how the profiles assist you ! 1. TARGET: there are those who find the TM software to be superior regarding ease of use and capabilities. I took another route. 2. "For me I would say that the P51 flaps lever needs revisiting for any realistic use. To cover all 5 static flap positions you could link it to a springed rocker switch using the keyboard character or, as it is also an axis, to the friction slider but I understand this will not fit the ‘generic’ model." A lot of thought and testing revolved around the Mustang's flaps. More than that...in dogfights flaps are used very often and ease of use is of the maximum importance. I started with the original flaps switch and found it lacking. Then I used the friction slider until I moved the zoom view from TrackIR to the slider and had to move flaps control back to the flaps switch. As it is with the current graphical engine DCS uses...zoom view happens to be one of the most important controls in the simulator and especially in dogfights. As for a spring rocker switch...since those in the throttle section have springs only one way one would need to use two switches... In short...I agree that the current flaps location is a compromise, but it is the best compromise I could find. As for 'generic' location of switches...it's important for moving from one module to another with the utmost ease...but...it by no means takes precedence over logic, human engineering and operation of individual aircrafts. Did I find the most logical solution? I think I found the best logical solution my logic could find ;) If you could find another solution I would be more than glad to try it. 3. "I could not find the 10c input profile folder - there is a 10a and a default?" I just tried downloading the file myself and the A-10C folder is present in the Input folder. Do you mind checking again? Again...thank you! Polaris

PimpFinger, 1. Zoom: I did that on purpose after lots of testing. Use what is good for you. 2. Throttle - indeed I think you are right and it's more logical with China Hat forward being Throttle Down and aft Throttle Up. It shall be part of the next update. 3. Slew control: Camera Vertical and Horizontal View in the axis section were assigned to the slew control by mistake and should be cleared. It shall be part of the next update.

Sobe, I checked it and all seems to work just fine. Just to make sure...there are two assigned commands for brakes: 1. Wheel Brake Parking/ Lever+CMS left: each single one click changes its position from locked to released or vice versa. It moves the actual joystick lever in the cockpit from the locked position to the open position or vice versa. 2. Wheel Brake/ CMS aft: each continuous pull on the CMS applies brakes which stops the aircraft. Release of the command releases the brakes. In short...if you wish to roll you need to first release the parking brake. Stop when needed with regular wheel brakes. Hope it helps Polaris

Night :) And I'm sorry...but...this thing is kinda addictive... ;)

I think that what happened is that you didn't load the profile (assuming you placed the new input folder in the saved games root). After you put the input folder in the right place you go to settings>controls>choose a certain module> clear each category completely (joystick, throttle, rudder and TrackIR)>load new profile into each one of the categories from the new folder from within the setting menu and...that's it.

:)

DCS Warthog HOTAS Profiles by Polaris & Schnix I shall have to look into it for it sounds like a profiling issue on my part, if it is an issue. This module has no mod/ custom controls and therefore the issues do not relate.

Thanks...and...you're welcome :)

Lever/ shift key is the actual lever just behind your pinky on the stick. As for the TrackIR...I use a script through AutoHotKey which enables me to use Lever+DMS down short for recenter and Lever+DMS down long for pause. So...the Lever does nothing when pulled alone and keeps its shift action while DMS down has dual layers with the shifted one being TrackIR. There's a link I gave a few posts before that explains it all.