jjohnson241

Ok, Tango. That appeared to work. Are you using a combined map with the EB? Thanks for the response. :D

The Hawk has issues with 12.15. They still can't get the thing full integrated in DCS. Amen on the standardization.

If you have the Hawk, same problem. I'm not a LUA expert. Both the Hawk and the C-101 appear to have butchered the default Keyboard and Joystick LUA files from other aircraft. The one thing that's common between them is that neither assign keys to the controls that can't be implemented on the throttle. I always thought that the Joystick LUA mirrored the Keyboard LUA and added/modified key commands as necessary. Neither aircraft follow that convention. Frankly, I don't know what the hell is wrong.

I put together a combined map for the A-10 some time ago. I don't recall having any problem. Do you happen to know what the problem is and how I get around it (mod or otherwise)? Thanks.

I use a combined map for all the aircraft in DCS. Target allows me to configure and print the map for reference. Also, I don't mess around with "clickable" cockpits. I prefer to map controls to a switch.

I'm trying to use a combined controller (joystick and Throttle) map with the C-101EB. Apparently the default LUA (joystick and keyboard) will not support a combined controller map. No keys can be assigned to the throttle in such a map. The same problem exists with the Hawk. All other aircraft in DCS however support a combined controller map. I know because with the exception of the CA module, I have a combined map working for all other modules. Note: by combined map I mean under TM Target Software, the drivers for the controllers are combined to look like one device to DCS. I working with VEAO now to address the Hawk. I need your attention to this. Thank you.

Tango and JuanOscar, Let me take a breath and just recognize and express appreciation for your efforts. Your both in on Sunday responding to posts here and doing whatever has you working on Sunday. Excuse my venting and frustration. :pilotfly:

I've been patient for over a month waiting for the "beta" copy of the EB. I'd like to see the beta copy of the EB more finished than it is and certainly before we see the CC. You apparently feel otherwise. I don't need your lecture about patience. I'm sure you don't want to hear my lecture on commitment and priorities.

Add implementing the Kneeboard to the list. I understand working on the CC. I paid for the EB (and CC, and EFM). If you were in my seat, you would expect the features and functions of the Beta EB be somewhat complete upon delivery. What we got was an incomplete version of the EB with key mappings thrown together so the module could be flown. We also go a promise that that situation would be corrected "soon" (your words). You know, it's not worth my time and aggravation. Fix it when you get around to it. :(:(:(

While the "Custom" controls section was removed, complete key mapping for all clickable cockpit elements, e.g., those required for engine start, are missing from the default Keyboard controls. Complete key mapping is required to map controls to a HOTAS or otherwise key/button equipped controllers. I requested complete key mappings in earlier posts. When will this be implemented? Thank you. Edit: See Thread (prior to 12.15); http://forums.eagle.ru/showthread.php?t=138634

Two questions: 1. Is there a keyboard assignment for the "Battery Switch"? 2. What is the keyboard assignment for the "Cabin Pressure Valve"? :book: Thanks. Edit: For those of you who are trying to set up the start procedure in your HOTAS, 1. (above). The Battery switch is in fact the "Accumulator" switch (go figure) , and 2. The Cockpit Pressure Valve is in fact the Cockpit Air Valve in the keyboard assignments.

+1 Repair after the update is all that's required. :joystick:

I too had the Mig-21 screwed up after the update. The Repair function fixed the problem. I don't run the Open Beta. I read with great interest the problems encountered with the Mig-21 after 12.15 was applied to the OB. I had hoped that the problems would be corrected before the release of 12.15 in the public version of DCS. In fact, one of the moderators commented that the "reason for the Open Beta was to find problems". That's almost funny at this point. :(:(:(

I hope they get to it period. The performance of Belsimtek in addressing bugs such as this one is dismal IMHO. I'm curious, have they acknowledged the problem? I've created a JSGME mod for ammo level and firing rate of the 50's. I can live like that until Belsimtek decides to fix it. :joystick:

The cockpit is not in English. I repeat my suggestion that an option should be available to "present" the cockpit in English. If you think such an option would be unrealistic, then don't use the option.

I don't think any pretense is necessary. My suggestion is a set-up option to select either the "home" language or English if the product is sold in an English speaking country.

If DCS and/or a third party wants to do business in English speaking countries, then produce an English speaking product.

Air Wing Huh Chief? Well Semper Fi anyway :smilewink:

Title says it all. By Beta I mean the version that has the complete key mappings (including all clickable cockpit functions mapped to a key command). Thanks.

Hi, As AvioJet creates key bindings for the Beta C101EB (and CC), please insure that all clickable cockpit controls have a corresponding key binding. Doing so will enable all cockpit controls to be mapped to either the keyboard and/or buttons on a HOTAS setup. Thanks! :joystick:

Bignewy, Have you heard anything as to when the F-86 fix will be available in public version? Thanks.

Anyone heard when 1.2.11.34087 will be available for public version?

For over 33 years, I directed complex software/system development for a large business in the states. I'm "familiar" with the processes that surround software development. I'm not going to continue arguing. I'll just close with this observation: The "No Sound" bug was initially detected and reported when the 12.11 OPEN BETA was released. In my book, there was more than ample time to correct the problem in the public release of 12.11. If it was a conscious decision to not include the fix in the release I'd like to hear that and the reason from ED and/or BST. My suspicion is that the testing, configuration management and internal communication processes at ED are broken to the point that the quality, i.e., performance related to accuracy of the code, is either not there or inadequate. Regarding what is "affordable", very few businesses survive with recurring problems with their product. So, what is the true price of quality?

What I'm proposing is that if in fact they take the time to test and a problem is detected, THEN FIX THE DAMN PROBLEM BEFORE RELEASING. If they are not going to do that, then don't test. Obviously it's a waste of time.

I don't find anything funny about this thread. What is suggested is that the going forward with the Release is a priority above testing and "bugs" identified.' So why test?