Nereid

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...

The keybinding for emergency braking on/off (default LCTL w) just enables the emergency brake but never release it. Disabling/releasing the brake by clicking in the cockpit seems to work.

I was just stumbling over this myself... Yes, we can remap them. But changing the default main keyboard shortcuts in the sim that controls view and view modes is very bad practise. What comes next? Changing the ESCAPE key for some Mig specific purposes? Please don't do this in your next module.

Well.... buy a better joystick then. Any good HOTAS will give you the option to map keys or a combination of keypresses and releases in any order to any button of the stick or throttle.

Track recording is still broken in the current build.

DCS World 1.5 beta Maybe it's not only an issue with the L-39 and I'm in the wrong forum but I have noticed that any track I have recorded when I do a cold start of the L-39 and using the keybord shortcuts for the APU start cover, APU start button, and the counterparts for the engine start button the track is broken (it doesn't reflect opening the button cover or pressing the button and therefore wont start the engine). If I do the same by clicking the controls directly in the cockpit the track is recorded fine.

I disagree completely. The current method won't work at all. This module is prefixed with "DCS" and this feature is a violation of this. Let's hope there is a mod someday that disables this switch.

Navigation is similar to other modules. Just search for tutorials on youtube and adapt it for the Mig-21. But you look for a way to find a ground target? Won't JTAC work with the Mig? Otherwise as YoYo said: RSBN+ARK+VFR.

If this is your argument in this discussion... well it tells us much. It seems we need a realism option for some people here: "[ ] gun cam switch affects existence of gun cam". Some (like me) want more realism and some are happy with less (I don't understand the point in playing a simulation then, but that's not my part to criticize).

Better a pointless button than a button that does things that it shouldn't do. What's next? IFF switches that changes aircraft skin in flight? A button for refilling fuel in flight? This switch is incorrectly modeled. It does things the real thing in the Mig-21 won't to. because this module is a DCS level module it's just done wrong. There is not much room to argue and it's just ridiculous to defend this. In other threads we are discussing way less important things (exact missile behavior, not enough or to much smoke,...) but regarding a switch that creates components in flight out of thin air we are accepting compromises? And some people are telling something like "to much realism"... really? This is a simulation, btw. We WANT realism, there can't be to much... Signed. One of the best options to implement it. If it's there and blocking sight, it should do exactly this: blocking sight. Turning it off should not remove this obstacle. If someone won't want it to block sight, he should just not load it. "turning it off and pretent it wasn't there" is cheating and not some kind of argument to retain the switch the way it is.

Thats not the point. The point is cheating, because thehe told us, "he pretend it wasn't there". thats cheating, nothing more. And the switch has a bug: It causes the gun cam to appear, which it should not do. In your words: Just remove the gun cam completely or implement it the correct way. period.

No. DCS is a simulation. Its simulates the real world up to a special degree. DCS simulates the aircraft and its systems but not external support or manpower for rearming (at least in its current state). So the current rearming of the aircraft as it is modelled is acceptable. But DCS standard simulates the aircraft systems and the cockpit. There is a switch called "gun cam". So what does it in the real plane? It provides power to the gun cam. Does it install the gun cam? NO. So if flipping this switch causes a gun cam to appear is not a simulation of this system/aircraft and therefore some kind of a bug - even when if it's intended by the devs. Again: No. DCS imulates the real world up to a special degree. DCS simulates the aircraft and its systems... but I'm repeating myself. Regarding the "pausing" and other things. There is no switch that pauses the game. If there were any, I would call it a bug, too. Pausing the game is done on a meta layer of the simulation and not in the simulation itself. And yes: if pausing were possible in multiplayer for some and not for other players, I would call this a bug,too. Summary: The gun cam switch is currently simulated in an incorrect way. There is not much to discuss here. It's just a bug or some kind of "broken by design", but its not a well done implementation. You could just argue, that these critics are nitpicking in some way. Yes they are. We are criticizing this module at a very hight level. But we all (including the devs) want a module on DCS standards and this switch won't comply with these standards at the moment.

Ok, I would like a switch to kill an enemy. In multiplayer too, please. And after I have used it, I pretend it wasn't there. Trust me, without much training I would be one of the best pilots out there. Among thousend of other pilots. All are the best of the best, all with very short lives. So, lets transfer DCS into a shooter...

Well, you like to cheat? because removing the gun cam in flight with a switch is some kind of cheating...