JG14_Smil

Here is a working line of code to allow mapping a button to this switch. It would be added to the ...\DCS World OpenBeta\Mods\aircraft\MIG-21bis\Input\MiG-21\joystick\default.lua. I hope it is included in the next release as it is a pretty important function and I detest clicking on switches. Apologies, but I do not want to join another website to report bugs.

My mistake. DCS cockpit lamp works correctly. I had an oddity in my cockpit that is now also working correctly.

I think it is a dummy switch. It is not mentioned in the manual at all, which is not a good sign. In DCS_BIOS, it makes a marker LED turn on in my pit, but I think that is not a DCS issue.

Yes. ARC works. Set proper zone, push channel button, then switch channel button, fly high, make sure RSBN/ARC switch is down in the ARC position. The RSBN/ARC switch has no binding but I created one so it can be programmed. The beacons are limited by line of sight (LOS). I am still learning how the near/far switch works. If i can fix it I will. Love the avatar. First flight sim I ever flew.

Just fly them... you'll see. Positions are all off, angles are a bit off. Very steep glideslopes at some field's. I actually have them all (except the the Lochini field's) working correctly by tweaking number's. I won't post it publicly, but I can now do no-peak PRMG approaches to a decision height of 100m (even less) without problem's. You wont like the math number's but I repeat I can now use them properly and that is good enough for me. RSBN glidepath mode to 1500-2000m, PRMG mode at <25 km. You must be in the proper area for PRMG to work (not a bug). Please note: this is all I do in DCS. Former pilot (PPL) and I know how to land.

I have not seen the Dangerous Altitude lamp work since the latest OB 2/20/20 update. Anyone else, or is it me?

It is a great map, better than the Caucasus, which is quite generic in comparison. Yeah, it is not served for free flight anymore and I don't understand why it is not even used in a mission rotation. I sure miss the AO Nevada server. Really, the whole idea of other maps is kind of moot. ED creates one and no one uses it. (public, free flight servers.)

Nothing different about it than the word. Just click it and set your function.

I found that some locations are worse than other's. I have started fine tuning the beacons with good results. Beslan was a tough one, but noticeable improvements there. When I get ll fields close to correct I will offer the OvGME ready mod.

Not many people spend as much time as I do practicing PRMG. This latest update made it worse than before. Practically unflyable as the glideslope just plunges too much. SDU is not fixed that I could see, either. Don't mean to complain but that is what I am seeing.

Yes! I eat my words.

Quite easy to see front/back. End with the circle on it is the reverse course. The flight director indicator's on the ASI are unusable. If you use the HSI PRMG indicator's things go much better for you. Barometer pressure is whacked. There is no way to properly set it when contacting the ATC. Performance of RSBN penetration mode and PRMG's is inconsistent, depending on the airfield. I don't like paying for bugs that don't get fixed.

Internet is getting hit harder than ever. Just the way it goes here. You aren't alone.

MIG21_RPM Instance #18 "ENGINE_RPM" DCS ID 50 does not work at all. "ENGINE_RPM2" DCS_ID 670 works correctly. Both have the same data numbers for input/output..

I just wanted to make an issue known here: Opening a profile on a monitor with different scaling than the original setup will send gauges off into the abyss, adding thousands of pixel's to the gauge position X and Y numbers. If I use Editor Mode, I have to set my main monitor scaling to 100% instead of my default 150%, make all my changes, save the profile, then go back to 150% scaling for my general use. It is one of the PITA quirk's of Ikarus that can turn people off from using it. I am starting to look at the Mig-21 Bis file, so I will eventually be reporting bugs again. LATER EDIT: I think I tracked this to 2 different monitors using separate scaling. Both monitors had to be at 100% scaling to work correctly when in Editor Mode..

Messed with it long ago. It can be sickening.

It is hard to say and depends on the latest version of DCS. I have seen FPS in the hundreds in the past with my 3 camera setup, but that was long ago. I wouldn't even consider doing it now. One big screen for DCS, one screen for gauges is what I run now. Bezel correction is just added dead space for the physical bezel's. If you want to see how it runs, just do it.

ikarus-master\ikarus\ikarus.exe That is where mine is located. You can place the ikarus-master folder anywhere.

If it is so easy, you better get started doing it You *should* have no trouble fitting it into your schedule. DCS has always been this way. New user's, new issue's all the time. If someone wrote the document you ask for, it would soon be outdated. Best wishes and enjoy,

Sigh... it is a shame we all have to do this. Here is your suggestion: https://forums.eagle.ru/showthread.php?t=89226 Not all fun and games building a cockpit.

It really needs to be on the Special tab instead of the Mission Editor. It should be the pilot's choice on every flight. Same with the hood. I hate that dang gunsight ruining my view.

Hello, I found one last issue with the L-39C.Ikarus file: Instrument Name "ZDV30" Class "L39_ZDV30", Instrument function Instance 24. Output was "0,10" and gauge did not work correctly. I entered the range of the gauge "64.0,79.0" and I have it working correctly, but the gauge moves more than one degree notch at a time. "64.0" is accurate, but "76.0"(DCS gauge) actually reads "76.12" (Ikarus gauge). Each notch on the gauge adds a little more error each time, and thus subtracts it in the other direction. I could not affect this by editing Input numbers. It is an important gauge as it set's the altitude of the landing airfield into the RSBN glideslope. Just thought I would let you know.

R SHIFT and R CTRL, combined with keypad arrow keys and * / keys move the camera exactly where you want it. R ALt and KP 0 then save that position. Very useful. Make sure it is enabled in game settings. Learn to make DCS your own.

What Rakamora said... use the keys to set camera where you want it, then save the position and you're done.

Keyboard default lua only works with keyboard. Joystick defaultlua is only loaded with a joystick. Your code examples do not have unique names, they have the default names, so your list is not updated with your new commands. 'example left" would be changed to 'example left nudge' or whatever. I find that editing a button press command works with a hard-wired button, but a virtual button produced by code (encoder sending a virtual button pulse for example) will not be affected. Good luck, I'm done here.