jjohnson241

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?

So, Testing found the problem, reported it and ED released anyway? Why did that happen?

CofCorpse, We have no idea other than "the end of November" when the update will be available. That's three weeks away. Any chance that you could post the fix here for application prior to "the next update"?

http://forums.eagle.ru/showthread.php?t=127998&highlight=f-86+sound Sound bug first reported in these threads and "fixed" in 12.10. Apparently files excluded in one of the updates. Again apparently, same problem occurred with this update.

I just tested the Cold Start mission. I can't be sure but I think I've got engine sound in the inside cockpit view but no sound in the external view. Is that what you guys are seeing (Hearing)? Thanks

Thank you Sir. I interpret your answer to mean I'm OK (as far as DSR is concerned) :smilewink:

I'm running a GTX 770 and a BenQ 27" gaming monitor with a default resolution of 1920x1080 @ 120hz. When I adjust the DSR factor to 2x standard resolution and 33% smoothing, I get a screwy resolution of 2715x1527 available to my games. Should not the "adjusted" resolution be 2x standard (or 3840x2160)? Anyone have an idea as to how Nvidia is calculating the "super" resolution? Thanks.

Thank you Sir! Looking forward to the "bug" fix update.:joystick:

I updated to 1.2.10 32275 Update 2 today (9/24). Your rev level and timing of your bug fixes confused me as I'm sure it confused others. Can you confirm what fixes made it into the "Update 2" update and what changes remain pending? Also, it would be helpful if you could use the same DCS version nomenclature, in this case 1.2.10 32275 Update 2, when referring to your updates. Avoids confusing the masses. Thanks.

Any word/status on the fix? Thanks.

Well if it wasn't for Colseg's original post I would have never noticed the Aircrafts vs. Aircraft folders. I'm apparently not the only one with the two folder syndrome. Anyhow, thanks for the feedback.

Colseg, In my installation the main DCS directory\Mods contains an "Aircraft" and an "Aircrafts" folder. The "Aircraft" folder was apparently installed when I downloaded the MIG-21 using module manager. It contains the MIG-21 sub-folder. The "Aircrafts" folder is original I believe to DCS and does not contain the MIG. Your default config for the joystick is installed to the "Aircrafts" folder and the game is not reading that folder after the last update. Can I just change the destination folder to "Aircraft" rather than "Aircrafts"? Do you have both folders in your installation? Thanks.

I get it. Thanks for the help.

Thank you Sir! One of my pet peeves is the absence of a key mapping list from the developers (of any module). Could you describe the method by which you created the PDF? Thanks again.

Like I said.. Two Weeks :doh:

Cobra, I noticed the language changed from "soon" to "in the near future". I'm not sure I can define either term aside from the fact that they are both relative terms and could mean anything from the next 10 seconds to a light year away. Wake me when you want me to buy something. :joystick:

ROTFL! I read somewhere on the forum that the "intelligent" guess for the release of the MIG 21 was mid-September, based on the historic interval between the release on ED stores and the release on Steam. However, I'm checking here multiple times daily hoping to see the release. The mid-September date seems reasonable but I'm still in the "check often" mode. Is there a head doctor in the group that can explain my behavior? :cry:

Thanks for the response Guys. Had me talking to myself (more so than usual) until I remembered the "sync" option. :doh:

Here's a Track of the mission and what I'm seeing re: Autostart "stopped". Have no idea why it's not completing the startup. Thanks for looking. Edit/Update: Solved. For some reason, the Autostart command doesn't like the "Sync Cockpit Controls with Hotas" option, at least on my setup. Cleared that option and Autostart works. Go figure. autostart.trk