Nereid

Well, it's early access. So something like this is to expect in early access. I'm sure ED will add them later. But yes, a lot of key bindings are missing. More important is that they add both not just toggles but also ON/OFF keybindings. Some of us bought expensive gear with all those fine switches and buttons we want to use. For the autopilot there are several buttons for ON/OFF in the cockpit. So I do not think there will be a toggle in the future. The HOTAS has to toggle itself (CH gear can do it, and the virpil gear can do it). Yes, that is indeed a must have.

Currently there is just a toggle for the main weapon safe switch. For important switches like this I would wish there would be a binding for UP/DOWN (safe/armed) as well. I would actually like that for all switches with multiple positions. There should be both: a toggle and bindings for every position.

There is a keybinding for the engine cutoff/stop levers (RCTL PGUP/PGDOWN), but it just opens the valves by pushing the levers down. Another press of RCTL/PGUP (or RCTL PGDOWN) will not pull the lever up and there doesn't seem to be another keybinding to do this..

Current Open Beta (2.7.0.5659) The binding (LCTL+LSHT+U) for "Arm/Safe Bombs Emergency Jettinson Switch LIVE/BLANK" does nothing. There is no keybind for the "RKL-41 ADF Outer- Inner Beacon (Far-Near NDB) Switch": Solved. It's just not correctly Labeld in the config

This is just not true. I have done this a few days ago by opening a ticket. After the (long) weekend I got a reply from their support that they changed my address for the order (but it was just a minor change).

Great. After a long time, I returned to the Gazelle, adjusting all input curves as suggested by others, and was pestet by the same effects. But without FFB it seems to work fine.

TY. That is exactly what I experience.

In the persian gulf map (and maybe in other maps too) the trails of non stationary ships are flickering if I fly at medium to high altitudes. This happens in open beta and release (but its a while since I tested it in the release version). They look rather ugly and are partly visible (sometimes with gaps in them) even at great distances at which they should not. Is this a known problem that just has to get fixed or is there something wrong with my graphic settings? I already tried to solve it but without luck so far.

Is it planed to remove this behavior? I would call a necessary dead zone just to activate an autopilot a bug. And a dead zone for the stick is a no go in my oppinion.

If you KNOW they were there for sure. Pilots do have good eyesight and those are moving objects against a static ground. What part of "I don't like the idea of labels or any sort of artificial helper like dots over planes" did you not understand? "mathematically correct" does not mean much in this context. Even 1+1=0 is "mathematically correct" in some cases. And exactly this is one of my complaints. But wait.... you said "mathematically correct". So is it or is it not? Face it: Quite a few complain about visibility.

Its even hard to see anything in 2K (1980x1080). Even zoomed in against clean background (sky, water). I don't like the idea of labels or any sort of artificial helper like dots over planes. But spotting planes should be a bit easier as it is now. Currently I will have to put my eyes just a few centimeter in front of my monitor to get any chance of spoting a plane even in perfect visibility conditions. And even then its impossible against the ground at distances above 3 Km. Camouflage is fine, but this is a bit to much.

Ah. Does it just work in OpenBETA? I thought it would in 2.5, too. The updater told me it was up to date.

Does anybody else have problems downloading this campaing, too? I always get the error "Unknown module L39_KURSANT_campaign".

Yes it is working - partially. If you use the CH manager outside of DCS its fine. All is working and I never had any issues in Win10 so far. But using it while DCS is running results in a loss of all sticks/throttles until next reboot. This happens not every time but often. I'm not sure but this did not happen a few months ago, so it could be caused by a Win10 update, or it could be a problem with DCS. Unfortunately I doubt there will be any update from CH anymore. So I'm waiting what VKB will deliver and maybe I will give the modern combat stick a try.

Thats why I got confused in my first missions. I got permission for startup and then in my startup procedure I turned the switch in the upper position and I never got permission to taxi. It's a while since I have flown the Mi-8 and I have only tested it every then and now the last weeks. Thanks for clearing this up. :thumbup: Unfortunately its not covered in the manual. :joystick: I have noticed that it has to be in the upper position for contact with the ground crew if the engines are running. This seems to be new, too. Its quite strange that ATC didn't worked anyway because I'm 99% sure that I didn't touched any switch after I got airborne and suddenly there I got no response from ATC. That was quite frustrating.

Ok, I did a repair and now all seems to work fine - except a small glitch I do not understand. There is a switch called "Laryngophone Microphone" labeled MIC on the right triangular console. I remember a startup procedure where this switch has to be set to on (upper position). But now ATC won't answer if it is set to on. Switching back to off (lower position) ATC will respond just fine. This could explain at least about a half of my no-response-experience. But yesterday I checked this without touching anything but the stick after ATC had responded at least once. And ATC stopped to respond a few minutes later. I don't know in which position the switch was but it was untouched after the first response from ATC. This is gone now. So, is this the expected behavior? MIC has to be on the lower position (OFF) for speaking with ATC? Has the switch changed a while ago?

No. Just a few skins (just for the AJS 37). Its a complete fresh installation just a few weeks old. And because its a new computer and DCS was not on the top list to test, I have not tried it that much - until last weekend. I willy try it. But it seems there is something broken with my installation or my system.

Strange. Maybe an update went wrong and I should do a reinstall of DCS and all modules... There are quite a few crashes every then and now anyway. What exactly means slow? I have waited about 60 seconds for a response but nothing... And even later there was never a delayed response anyway. After landing (without permission) I just got the usual "...parking area..." messages. On my old rig a few weeks ago all was working fine. :cry:

Engine and generators are running. Rectifiers are enabled too. APU is off. Battery: Dunno. I switch them off sometimes but this shouldn't make any difference. BTW: Squelch gives a nice noise every time. So the radios do have power.

"Radio Trigger - Radio" And maybe that has changed. I have deleted my old joystick config and DCS has bound all Buttons 1 on all devices to "Radio Trigger - Radio" on the fresh config. Maybe that was different on my old installation. I have tried the coms menu (key \) too and it didn't work either. EDIT: This config should be correct. The other buttons are not mapped on my sticks anyway. And I tried it again: got taxi to runway, got takeoff permission but in flight just 2 km from the runway I got no response. Again after a few minutes. ATC is completely dead then. I will check other modules tomorrow.

Easy Communication is OFF. I hav tested it again. This time on Kutaisi. The same again: At first all works well and after a few minutes: no response. I can ask for takeoff multiple times, no answer. I can abort the takeoff, no answer. Nothing on the radio was changed. Frequency is the same, it's still on manual, its still the 863... On my last installation a few weeks ago all was fine and on my new system it just won't work... ... and this is a quite fresh install of 1.5.6. It seems I will have to test other modules if they are affected, too. Questionable, because i'm still on ground. Only a few minutes (less than 5) have past.

Are there currently major issues with ATC in DCS 1.5.6 and the Mi-8 or in general? Communcations with ATC works at first but after a while I get no response. This happens every flight with at least the Mi-8. Is this a bug with the Mi-8, DCS in general or is there something wrong with my installation?

There are three positions for nav and formation lights: bright/off/dim Position OFF is self-explanatory but the others seems to be identical. In both positions nav/formation light do have the same brightness. Is this WAD or a bug?

I was a bit surprised that its possible to extract the landing gear over 600 kn without any major impact an flight performance or any damage. Is the real F-5 really immune to the expected turbulences and is the landing gear really that sturdy an did not get damaged in any way? Or is there some room for improvement in this module? ;)

LOL. I thought nearly the same. I was thinking: "okay, the have changed the window reflections and are still in the process of tuning". :doh: Ok, a bug then...