jjohnson241

Download and use Thrustmaster's TARGET software. You can map any key to a HOTAS button or switch. I use TARGET and have a map for each aircraft I fly. The only module I don't own is Combined Arms.

Thanks all for the input. Had not considered using the G940 for prop aircraft and Helo's and the WH for jets. Interesting idea.

Reemit, Thanks for the input. Tell me, have you had many problems with the G940?

Hi, I've been using a TM Warthog for a few years. No problems to speak of with the Warthog. Just after purchasing the Warthog, I came into possession of a Logitech G940 FFB HOTAS rig. I had it connected for a brief while just fooling around with it but I never got serious about configuring it with DCS (or any other Sim for that matter). Lately, I've gotten curious about FFB in the Sims I fly which include DCS, CloD, BOS and Xplane. So, question for those who use a G940 and for those who may have an opinion on the Warthog vs. the G940 in DCS: Would it be worth the effort to switch to the G940, considering the much aired and various problems with that rig? Thanks for the input.

Skull, The attachment didn't make it. :mad:

Applied update and can't start Quick Missions. "Fly" button does not show. Also, Menu after hitting "ESC" does not respond to mouse. Have to exit mission using Task Manager and ending DCS task. Solved: Latest Nvidia driver screwed up down sample settings and effectively clipped monitor resolution. Restored settings and everything OK.

Never mind.

Ok, I'll accept that but the point is there has been no information on the status of the current OB release (38601) either moving to "public" or otherwise. All I'm asking for is a little communication./

Exactly!

What Happened to Open Beta 1.2.16.38601? Hi, Open Beta Release 1.2.16.38601 was implemented on April 3, 2015. I've seen nothing regarding status. When will the 38601 release be implemented in the "public" version of DCS? Thanks

+1 on the Windshield shape. All pictures confirm that the DCS version is too wide at the top. + 1 also on the location of the compass. My gut feeling is that there is no "right" location for a given variant. Common sense however suggests that no pilot would want the compass to interfere with the FOV in combat. I would imagine they would have the crew chief by his neck until he relocated the compass to a location to not interfere with his FOV. Now with all that said, I agree with your assessment on the possibility of correction. This vendor has not impressed me with their support of their beta products. I could be wrong and hope I am.

Thanks. I doubt he have a problem using his files but you never know. Not sure how often he gets to this end of the forums but can you ask him (or perhaps a PM)?

Good Job Uboats! Saved me the agony of Russian language school. Question though; Mainstay did a mod that tweaked several textures in the cockpit. Mod here: http://forums.eagle.ru/showthread.php?t=139805 I had his mod installed until your English version came around. Is there anyway you could work with him (and/or his mod) to combine the two? I don't know what the protocol is but I sure would appreciate it if the mods could be combined. Thanks again for your English effort. :thumbup:

Mainstay, I had your mod installed until UBoats published his English Language cockpit mod (http://forums.eagle.ru/showthread.php?t=141289). Alas, I can't use your mod as it modifies some of the same .dds files as the English cockpit mod and I need "English". :mad: Could you combine your mod with UBoats English Cockpit mod? Thanks.

Joey45, Re-read my post. The first thing I did was disable mods. The problem in this case was leaving the visibility slider on to "Very High" while disabling the "More Visibility" mod. I forgot to turn the slider down. The slider in question is in the Options - Graphics tab. I've had the "More Visibility" mod in the game for some time (at least 2 updates) and never had the problem. I've always disabled mods (I use JSGME) before any update.

Dingo Bob, More Visibility was the culprit. I had the mod disabled to apply the 1.12.16 update but I still had the Option set at "Very High". I'll have to file that one away in the cause and effect bucket. Thanks for the help :thumbup:

Instant Action Mission: F-86 Runway Take Off: Note Airport Objects and Colors. Tried Repair, same result.

The MoreVisibility mod is the culprit. The latest version of the mod (V1.4) corrects the problem.

Today marks the 50th Anniversary of the Vietnam War. To all other veterans of that war (and to Veterans generally), Welcome Home and Thank You for your service. :thumbup:

As "useless" as the A-10? Hard to believe you said that. If that's your take, I know a few thousand grunts that would love some one on one time with you to discuss that.

Well I have the Hawk and C-101 and was arguing with myself as to whether or not I'll jump for the L-39. The Hawk and C-101, at this point at least, fly the same. The C-101 is slightly more interesting regarding avionics and will probably remain that way when the CC version is released. You make a good point regarding the multi-crew and DCS at l;east initially having an edge there. We'll see.. (continuing to argue with self) Thanks.

Per Wags in the February News Letter, the next module to be released by DCS will be the L-39. Aside from the Authors, what is the material difference between the Hawk, the C-101EB/CC and the DCS L-39? I'm having a hard time figuring that out. :huh: Thanks.

Tango, The C-101EB is good to go using a combined controller map. The 101's .lua files are coded as Flagrum suggests they should be and your instruction to me in this thread, i.e., assign the keyboard keys using the keyboard in the Options menu, got me past the problem I was having. The Hawk's LUA's do not follow the convention of including the all Joystick LUA definitions in the Keyboard LUA, hence using a combined map and assigning keyboard keys for functions not defined in both Joystick and keyboard LUA's is not possible.

I don't use Target's scripting language. I only use a "simple" map created in Target's GUI. No scripts. Aside from my blunders, I've never (repeat never) had a problem caused by a Controller map, combined or otherwise. I use Target maps for all aircraft in DCS.

I've never had a problem using Target to create profiles for DCS (or any other Sim for that matter). Amazes me what folks come up with to justify what is basically a personal preference. :doh: