jjohnson241

That video brought back memories, some good.. most bad. Thanks for sharing.

I'll jump back in here to agree with Cali.. I had no issues with the accuracy of the CH gear I used for years. Also agree that CH needs a general update of their consumer controllers. One thing to consider.. CH makes controllers for the industry/government market. The gear they sell to the government features hall sensors, metal construction and "state of the art" design. However, they have not opted to make that gear available to the consumer market. IMO, that is a business decision that considers the ever-shrinking marketplace for consumer flight sims. Whether or not they intend to stay in the consumer market remains a good question.

u I've had the Thrustmaster HOTAS Warthog for nearly two years and I fly all my flight sims with it. I've had no problems with either the hardware or the TM Target software. The Target scripting language (LUA) has a learning curve but it can be mastered. Prior to purchasing the Warthog, I had a full compliment of CH gear (Fighter Stick, Pro Throttle, Throttle Quatrant) and I loved it. I did not like the CH Pro Pedals as the width between the pedals is too narrow for my taste. The CH Control Manager software (used to produce profiles for the ch devices) is very powerfull and the support for both hardware and software is top knotch. I used the Saitek Pro Flight Fighter Rudder pedals with both the TM and CH gear and had no problems. Neither TM or CH is force feedback capable. I don't think there's a quality FFB HOTAS on the market currently. Logitech is dropping their FFB HOTAS rig. Frankly you can't go wrong with either TM or CH. If money is the issue, then CH is the way to go. If I were making the decision today, I'd go with the CH gear for the HOTAS and the TM MFD's for extra control (Key) input. Good luck

AceViper, Can you confirm the path for installation? Included in the .RAR is a Sound folder and 3 additional files plus a Readme. Sound folder is straight forward.. but where do the 3 additional files belong? Thanks, JJohnson241

RecoilFx: Interesting solution, trading a stretched neck in favor of the microstick. WildBill: I'll try to contact PeterP. I've noticed his view "mods" here and agree that if there is a solution to be found, that's the place to look. Does he answer his PM's here? Through all this I have to wonder how real P-51 jockeys dealt with this "problem". I would assume that they would have adjusted their seat to effectively place the sight in the center of the reflector (or wherever they wanted it). The manual mentions that the seat is adjustable to accommodate sitting on a chute. Strange that's not modeled in a sim of this fidelity.

Roger the long week. I'll play around with "centering" and post an update. Thanks.

Scrapple, You must be referring to the A-10 or another aircraft. The P-51 has a hand crank for cockpit close and no switch for seat adjustment. Thanks anyway. Foul Ole Ron, When TIR is centered, the "view" is the default cockpit centered snap view. I'm not sure how to change that other than changing the center snap view (lua) in the game. You have something else in mind? JJohnson241

Scrapple, Thanks, I'll look for the switch and give it a try. JJohnson241

Suchacz, I can lower my head and center the sight within the reflector. Problem is that is extemely unconfortable (for me at least). I searched the forum and found several posts indicating the default snap view can be edited. I tried that without success.. the sight is still too high in the reflector. Thanks anyhow for your response.

Need some help guys.. I fly with TIR and I find that the forward view in the cockpit places the gunsight on the upper edge of the sight reflector. Any upward movement of my head immediately sends the gunsight upward and off the reflector. I need somehow to lower my seat position (or effectively the view) so that the gunsight is centered on the reflector. I'm wearly of crunching my head downward to center the sight. Can someone help me understand how to "lower" my default forward cockpit view? Thanks, JJohnson241

Railfidude, Thanks but I never have used a profile for the stick or throttle in A10C. I use the default HOTAS assignments. I'll play around with it.

ZaltyZ, By gosh your right.. I have the idle detent intact. Off now to try to start the A-10's engines with the throttle. Thanks.

I've been playing around with various settings and in the Axis Tune and the one thing I noticed is that at least with the Simped rudder pedals/toe brakes, the brakes appear to perform just fine when tested in the "Tune Axis" window. However, when tested in the Sim (P-51D in my case) using Control+Enter, the brakes hang at about 25% of the axis value when released. The aircraft also behaves as if the brake is partially applied. The "hang" can be cleared by momentarily depressing the full brake key (I believe it's the "W" key in P-51). I using "Slider", no dead zone and the brake axis is not inverted (the Simped pedals do not require the brake axis to be invested). All tests were performed in the P-51D Real sim. I hope this info helps the Developers track this down.

ZaltysZ: I reversed the detent that is physically under the plate that is under the throttle arms. Reversing that detent (it's a small piece of plastic) removes the stop and afterburner detents that are the "normal" configuration of the throttle. You can find this described in the Hotas Warthog manual that ships with the device. Re: the assignments.. that's a bummer. I guess I'll have to create a profile or continue using the keyboard commands to start/stop engines. I was trying to stay away from yet another hotas profile as the A10C sim does just fine (with a few exceptions) with the native hotas assignments for the Warthog Hotas. Thanks for your help.

LXSapper, Thanks for the response. I don't fly with the Warthog throlle detent "active". This means that I have to use key commands to start/stop the engines in A10. As far as I can tell, the ignition switches on the Hotas throttle are not mapped in the game. Therefore they are available and I want to map the engine start/stop command to the ignition switches on the throttle. When I go to the Options menu to do that, I can't assign the start/stop functions to the ignition switches because those functions are "blued out", i.e., not assignable, in the controllers main window.

I have a Thrustmaster Hotas Warthog and fly A10C using the default key assignments (no Target profile). I've reversed the detent on the throttle because I fly other sims and need full throttle range. I want to assign the Left/Right Start/Stop Engine commands to the ignition switches on the throttle (using just the joy button id's). When I attempt to do that in the Options/Controls menu, the GUI will not let me assign those commends to the throttle. The related throttle fields are (blued out) and can't be modified. Strange because the GUI will let those commands be reassigned to the Joystick and to the Cougar MFD's but not to the throttle. Does anyone have any idea what the problem is in assigning those commends to the throttle? Thanks.

Skate Zilla: Thanks for the path info but somehow I've become lost in terms of what a modified LUA in that directory would do for me. I started this journey by attempting to understand why I could not use the auto-load function of TIR with DCS World. Thanks to your (and others) explanation as to how World to communicating with TIR, I understand that the situation is due to what (or what isn't) passed to TIR via the registration that takes place when World begins to execute. I looked at the LUA that is in the directory you identified and they are identical for each aircraft. And I think they should be because the LUA is defining the axis commands for TIR. They should all be the same. Nowhere did I see the Aircraft (module) name in the LUA. That means (to me at least) that the LUA has no bearing on the module name passed to TIR. It also has no bearing on the Hot Key assignments that are used in a TIR profile, namely Center, Pause, etc. Those hot keys are included in the TIR profile which is an XML document generated by the TIR software (GUI). So, forgive me but I'm lost with what a modified (somehow) LUA would do for me. Somewhere in World there is code that "registers" the sim with TIR. I assume that the information contained in the aircraft LUA is included in that "registration" process. From what I can see though, the TIR hot key assignments are not part of the LUA (and they should not be as that info is set in the profile by the TIR software). I appreciate your help but I think we're barking up the wrong tree.

FrogPrince, Welcome to the DCS club. This thread is discussing an apparent problem in DCS World wherein the sim is not communicating with TIR correctly resulting in the inability to use TIR's autoload featuyre for unique TIR profiles for each module (aircraft) in DCS World. You're certainly welcome to monitor the discussion here but given your newess to the sim, I suspect that you would be better served by starting with the wealth of information found elsewhere in this forum regarding setup, controls, operation, etc., for the aircraft you're attempting to learn. Not tirvial are the manuals provided for your study. This sim has one of the steepest learning curves of all the flight sims out there and it is easy to become lost, confused and discouraged. But the rewards are great as you'll discover. Good luck and use the reference material and this forum for assistance. JJohnson241

And the aircraft LUA would go where? I looked within the EA directory and in Users/Saved Games/DCS World. What is the complete path for each aircraft? Also, if all it takes is an unique LUA for each module (aircraft), why can't ED provide that modification?

Ebs, it's all good.. no harm..no foul. SkateZilla: When the DSC World GUI first loads, there is no indication from TIR that it's "talking to" a TIR compatible title (the LED lights on the TIR indicate that a TIR compatible title is executing.. no light comes on when the GUI first executes). The first indication that a TIR title is executing is when the DCS Splash screen appears after selecting an aircraft in the GUI. As you said, the GUI closes, splash screen appears and TIR communication begins. That leads me to believe that the TIR registration takes place in the code of the DCS Module(s). If that's a fact, then it should be possible for each module to register with TIR correctly as it begins to execute. Stated another way, the umbrella exe makes no difference because the registration still takes place in what was yesterday a stand alone exe that is now under the DCS World umbrella. Even with a common exe, the exe knows what aircraft is selected. Again, I think the default "Black Shark" regisitration entry is a carry over from the stand alone title days. It may take a few lines of code but it should be possible to register at least the correct title (Black Shark, A-10C, P-51D, etc) with TIR.

No I don't fly FSX or Prepare3D. I do fly ROF, CLoD and IL2. The difference in those titles in comparison to the modules in DCS World is that for each of those titles there are no key mapping differences between planes and one profile per title will work. Yes Ebs, I only have one head and right, right, right as an answer to your other questions. For those that offered thier setup and explanation, thanks. For those who compare DCS World with FSX, CLod, IL2, etc., I don't accept the comparison. Those titles have a key mapping common to all planes included as flyable in the sim. DCS clearly does not and it is also clear that the DCS World GUI effectively passes control to the module (aircraft) that is selected in the GUI. I don't know how this is done by it's obvious as the DCS splash screen loads after selecting the aircraft/mission, etc., in the GUI. The module load, however it's accomplished, is the opportunity to register the module correctly with TIR. That said, I'd rather be flying than arguing this point further.

Well that depends on your definition of "bug". The "assignment" of Black Shark as the name of the client software registered with TIR appears to me to be a carry over from the days when the now DCS World modules were stand alone products. I understand now the current situation but I disagree that the modules are all "DCS World". World is the GUI used to select the execution of a given module. It is reasonable (to me at least) to expect each module to "register" with TIR when it begins execution. It's clear that is not happening now. Whether that's a "bug", an oversight or whatever, the bottom line is that it's not working as it should and it should be made to do so.

Well DCS World should be passing the correct .exe name in the TIR API and apparently that's not the case. I don't know if the developers look at these "bug" threads so I submitted a Trouble Ticket. We'll see what response arrives. Skatezilla, I looked again at the TIR GUI and the files in the directory and I can't find anything that could be tweaked to modify the .exe name TIR is looking for.

Using the Black Shark profile as a common profile is possible I guess but the reason I created a seperate profile for A10 vs. P-51 is that the key assignments differ between the two. I use F12 to center the TIR in P-51. F12 is occupied with game commands in A10. F8 however is not used in the A10 game. I guess I could reassign the F12 Commands in A10 to F8 and use a common profile for both A10 and P-51 but I'm not sure if that creates conflicts with FC3 or other modules. It would be a hell of a lot easier if DCS just followed the Natural Point API and included the correct .exe name in the info passed to TIR. We'll see if Skatezilla comes up with something.

It's not that simple. The name of the exe is not configurable by the user as the title must be included in the TIR "title" database which is an integral part of the TIR software and included by TIR once the title is certified by them as TIR comparable (complies with the TIR API). When A-10C was a standalone product, the executable was included in the TIR database and the profile auto-loaded in the TIR software. Enter DCS World and now the profile doesn't autoload. Somehow the API got screwed up when A-10C was "moved" to execcute under DCS World.