Bearfoot

Hi Miles, If this has been covered in a tutorial video, please point me in the right direction. From the documentation, it appears we will have: left click, right click, and scroll wheel. Does the last include a (middle) click? I find double middle-click useful for turning the mouse cursor on/off. It is by default bound to a hot key (L-ALT C), but of course, it would be really convenient to activate/deactivate this using Point Ctrl.

Or, you can use this: https://forums.eagle.ru/showthread.php?t=218861

Ah, that IS useful! Thanks!

+1 Or at least, some way to copy them in bulk from one unit to another. I tried modifying your Case I trainer to have some F-14's take-off from the ground by switching out some of the Batumi Hornets to Tomcats just by changing aircraft type of the unit. Everything reset to F-14 defaults. And SUCH a pain to update all the radio presets! Made worse because you cannot cut and paste entire freq sets, so you have to write down dozens numbers and then individually type them in.

Does it need a chair with a central post? I use just a regular 4-legged dining chair ...

Thanks. I'm running at 4Ghz. So worth a shot ...

From promo screen shots/videos, it seems it is going to be a WW2 map

Nvidia image sharpening in DCS

So I have a: i7-4790K, 16GB RAM, 1080Ti 16GB .... Do you think I can take a HP Reverb? I run Rift S at 1.5 SS tolerably well ...

Thanks for looking into this folks! @Bankler: I will see if I can reproduce the issue when switching from the Hornet. It's possible I got confused (I tried numerous variations to see if I could pin it down). But good that you figured out a consistently reproducible case. A reproducible bug is a dead bug --- it just does not know it yet! Once again, appreciate everyone's efforts in this!

It does ... but it does not fix the numerical digit drums in the barometric altimeter that was the reason for my post. So while it works for other folks, it does not help even if it passes IC. The other mod (Drunken Sailor) DOES help, but it does not pass IC. Anyway, for future reference, the solution I went with was ... the Rift S. The bump in clarity is not just significant and noticeable, it allows me to read the instruments. Still need to lean in to read the digits, but this is so much more manageable than leaning in AND zooming in terms of time, mental effort, and minimizing disorientation.

I am in the camp of a non-adaptive Jester menu. The small convenience of sometimes Jester saving you a click by opening a submenu instead of a top-level menu is outweighed by the confusion of never being absolutely sure what menu Jester opens up with. I think it is a basic principle (albeit oft-violated) of good UI design that your menus should always be consistent. I think being able to count consistently on a menu structure (such that the key sequence "a221" ALWAYS gets you the same place will immensely help not only muscle memory but also make for MUCH easier scripting for both macro keybinds and voice profiles.Not to mention the mental taskload of opening up Jester and reading it and saying, "oh, I am in the BVR menu but really what I want to do is to <something else> so ...". But even when Jester has correctly anticipated your need and opened up the correct submenu, it takes a few microseconds for you to check to see you are in the correct place before proceeding. None of this can be learned because it always changes dynamically. Another example: set A/G mode and open up Jester and you will be in the ordnance page ... IF you wait a little bit. Otherwise you are in the top menu or something else depending on the situation. So I'm never sure which menu I am going to see when issue the voice command.

Would it be possible to have them available for aircraft in a special region? E.g., like how now there is an area for guns-only and another area for missiles + guns? Maybe the area can be one for all advanced missiles on both sides? Failing that, I would vote for keeping them off the server (far more sporting, and that is after all why we are here). Even when I go in the F-18 in SP, I find the Aim-9X not just that interesting to use. Removes the whole challenge ...

This is briefly covered here

Gazelle is a light armed scout helo. Not really a dedicated attack helo, even if it can be used to deliver the boom boom. What we lack is a Western heavy attack helo. Like the KA 50 or Mi 24. Big difference in not just capability but mission types. On a side note, IIIRC the US army has retired it's light armed scout help (Kiowa), with role being taken up by Apaches and RPVs for now. I believe there is a competition ongoing for the us scout help role. So funny how DCS world jets are so US/west centric/heavy but helps are East centric

Agree with all the others about the Saitek/Logitech being crap. The design chews out wires on the throttle as you move it back and forth. The result is not so much death, but bit-by-bit organ failure. Buttons stop working. Or worse, give off ghost signals meaning you have to disable the mapping which makes them just as useless. Your plan for a replacement assumes (hopes) that the failures start cropping up within 3 years. They may. Or they may not. Depends on frequency or amount of use and luck. Mine (X-56) with very heavy use start giving problems 8 months in. Maybe you will be very lucky. As for Logitech getting it right? Would not count on that. Logitech has really made large cosmetic improvements (or changes anyway), but AFAIK the internals have not changed one bit since the Saitek days half a decade ago. But again, maybe you will be very lucky.

Once again --- LOVE this trainer! I have noticed two bugs, one of which is really easily reproducible. No big deals, as there are easy work-arounds, but thought I would report them here in case there is interesting in squashing them. To be honest, I'm not sure if the issues are with the mission, DCS, or the module (F-14). Or maybe they are designed? Bug #1 Symptom: instant CADC / auto wing-sweep failure on an air-started F-14. To reproduce: (1) Start mission. (2) Select ANY slot EXCEPT for the air start F-14's. E.g, any Hornet slot or any carrier launched F-14. (3a) Quit, and select an air start F-14. And you will find your auto wing sweep does not work and the CADC and wing sweep warning lights are on. Now here's the weird thing --- quitting the mission completely and starting a new one, and then jumping directly into an air start F-14 does not "reset" things! The CADC error and wing sweep still does not work. You actually have to quit DCS entirely and restart it to get back to normal. Work-Around(s): (1) avoid selecting any other slot but an air-start F-14 once the mission is launched OR (2) restart DCS Bug #2 Symptom: Barometric altimeter stuck at 000 (pointing up) on air-started F-14. To reproduce: I don't know how! Sometimes it happens even on a fresh air start, i.e., without any other slots or aircraft selected first/ Work-Around(s): Luckily, simply restarting the mission cures this.

No worries. Appreciate your busy schedules, and just as importantly, appreciate all the things that you are doing that make you busy! LOVE this module.

Thanks. Appreciate the challenges with a universal solution. Mods help out, but perhaps if the devs could provide support for custom cockpit mods like this one: https://www.digitalcombatsimulator.com/en/files/3304383/ so that they do not fail the integrity check it could help out a lot?

Yes, this solves the issue. Thanks! But, as you say, fails integrity check for multiplayer :(

https://forums.eagle.ru/showpost.php?p=4065763&postcount=4

Maybe, but it does not enhance the brightness/contrast/clarity of the digits in the embedded drums.

Hi Relic, I am no expert in missiles combat, not even not in IRL but also in the game. But I do find the AIM-7 pretty decent when launched within parameters. For SP, In the Nevada Constant Peg as well as Normandy DACT Instant Action, for e.g, or even the PG "BFM Lion and Sun". In the second, I have to deliberately choose NOT to use the Sparrow before for the first merge otherwise the battle will almost always be over instantly. The Sparrow can even be pretty good as a WVR/BFM weapon (at least in the game) IF you can get a little bit of separation. Key is to not fire in a situation where you are pulling a lot of G's or the missile has to pull a lot of G's (as when the bandit is going to pass you or is in a tight turn and you are too close. What does not work well is F-pole type stuff where you are turning to keep the target in gimbal limits. You will lose lock because TWS auto is not implemented.

As the title says, it is a bit difficult. Especially the numerical/digital drum embedded in the barometric altimeter. I need to use zoom and lean in. The issue is that the numbers/background are lower contrast and dim. I understand that this is the authentic look. it would be nice if we could dial it up in brightness to accommodate desktop visual realism (while the colors/brightness/tone might be objectively correctly rendered, this does not map to realistic perception?). I am aware of some mods that brighten the labels. As far as I know they either: (1) fail IC (2) do not change the dials/instrumnets (3) or both For the devs: is it possible to allow cockpit mods to pass IC so we can read the dials? For the community (including the devs): does the Rift S provide enough of a improvement over the Rift non-S so you can read the instruments (reference benchmark: the 1000's and 10000's numerical drum embedded in the altimetere) without leaning in? Other than that, just want to say (again) to the devs and support: THANK YOU! I have not touched anything else since it came out. I am not just LOVING but LIVING this module!

A-6 first! Tomcat-escorted Intruder strikes would make for fun times.