JG14_Smil

Don't force it... use a bigger hammer. :)

Great to hear, Los. I'm trying to get one of my pilot sht buddies to come and fly it with me.

Hello, I have a cockpit with hundreds of switches. Heavy-duty toggle switches are a pain in the butt. I will never incorporate them into a pit again. Just throwing that out there for you... Best of luck on your build.

Thanks, that option might not work anymore... will look into it. Just sayin, but why would you not have this option when buying? It is more money for ED. Thanks everyone. Yeah, Santa is bummed!

Thanks Dr Arrow, I understand everything in that topic. I was never hitting the second SDU switch. Should be what I was looking for.

Hello, I did a search and it appears buying a module as a gift is no longer allowed(?) Just wanted to make sure. Thanks for any answers.

From the Manual, Page 191: "When distance of 21±3 km is reached, then in front and rear cockpits, the END OF DESCENT (Cloud penetration is finished) signal will be on and glideslope deviation pointer show airplane position relative to altitude of 600 m, set speed of 350 km/h" I am following instructions for use of RSBN navigation, Glide slope and Landing procedures. Things go well when using RSBN navigation mode and early on in the glideslope mode. At 21+/-3km from the field, the glide path altitude indicator should take you to 600m alt and "End of Descent" light should come on. Instead, I see it taking me to 300m and no light coming on. I never see any ILS flags change or any Landing ILS changes on the HSI. Proper switches have been made and all beacons are properly working, but no joy. If anyone is bored and is interested in this aspect of the L-39, can you verify this as happening. I just want to make sure it is a bug and not some feature. Might even make an official bug report if so, although the Ka-50 has taught me it is a waste of time doing it. On another note, regarding the RSBN beacon being off center from runway. Is it even possible to do a zero, zero, blind approach in the L-39? From what I read (and the way it acts), it seems as it is designed to just get you close enough for a visual. thanks,

That's how it starts.... Looks great, thanks for sharing, enjoyed seeing it.

I have found an issue with Ikarus L-39 HSI. I am no programmer, but I am guessing there is a number rounded off incorrectly and once export starts it shows up. Please note the following photos: Photo above shows enlarged HSI with only Ikarus running. Course pointer and RMI are 'in-line' and pointing at 180 degrees. Both ends of pointers are lined up correctly (North). This photo shows HSI after receiving export from DCS (1.5 or 2.0). Plane is on a runway at Mozdok. RMI and course pointer are pointing at 088 degrees. Note that opposite end of pointers are now 2.5 degrees apart. Pivot point for course pointer art has shifted, hence my guess of a number rounded off and creating math errors. Shut off DCS and both pointers jump back into alignment. This error affects how the ILS works and it would be wonderful if someone much smarter than I took a look at the cause.

Found a work-around for aligning the RMI and HSI from the front seat. Have not tested it online yet. Right, rear side: Pu-26E panel. You can set it to gyro instead of magnetic compass, then use the heading switch on the PU-26 to align the HSI and bring the ILS into the proper azimuth. In theory, I'm hoping it will be like removing the error bug and manually aligning the gyro. I doubt there are five people in the world that care... :)

Works flawlessly in DCS. A bit buggy in the configuration side, but once you learn to work with them it is great.

I've done some experimenting on the Mozdok runway. I'll enter the sim with the course pointer at 82 and the RMI at 88 degrees. Course deviation flag is off center. I jump in back seat and deviation dial is set to +6 or so as it should be. I change it to +12 or so and hold correction button. RMI lines up correctly, still at 88 degrees. I dial the course pointer over to 88 degrees and course deviation flags center. Forget the fact that the deviation scale is off, my ILS should now line me up correctly. Here's the bad part: Even if I map keys for changing the deviation dial, I cannot do it from the front seat. I cannot get into the back seat while flying MP, which is really all I fly (no one has ever said "hello" in SP). I think one can't eject also because of this issue(?) It would be nice to be able to fly from the #2 seat while in MP. This aircraft is all about that ILS working correctly, that is it's job as a trainer.

Still works. I think I used this line edit to move my indicator to my Ka-50 cockpit monitor. base.init_pos = {4.24,-(-.65- 1.5*size)} In the example, 4.24 is X position and -.65 is Y. Experiment with small moves until you get the hang of it. IF you go too far, you'll never see the indicator. Don't use my numbers as I have 4 monitors.

Hello, Did you try and manually set the button ID even though it did not sense it? Are you sure buttons that high are assigned to be an analog output in your TM config? Controllers can have 128 buttons in Windows. Also, when I can't get DCS to sense a button or axis, I note I am sitting in an airplane. If I exit the plane, then use the main UI control editor, it will then sense the buttons. Not sure if it will be the same for you, just throwing it out there to try.

I assigned it to a physical switch in my cockpit in the usual way. You would need a toggle switch on your controller, then just look in the control setup under "left console" and find left/right pitot heat. Hopefully, it will be fixed soon.

Created the My Cockpit category and it works fine. Thanks again guys.

Thank you guys. All of this gets re-written in an update, so I see no long-term harm. I'll have to give it another try.. had no luck with the "My Cockpit" edit. Probably my fault.

Number of pulses almost doesn't matter, so if you can only get encoders with 20 pulses go ahead and use them. DCS just sees and uses it as a single button pulse that repeats. Lua can be edited for the amount each button pulse affects the sim (in many cases). So in regards to DCS, it doesn't matter. To you and how you want it to feel.. that's another matter. More pulses does not equal more precise (in DCS). Lua sets precision. great luck on your build.

As a test I assigned the pitot heat to a toggle in my cockpit. I flew to Mozdok in the AO server. Very cold, clouds over the mountains and no troubles. It's a work-around but it will get me through until they fix it.

Confirmed. Button acts as a momentary press and release.

No difference for me @ 4080x1920.

Hello, Is it possible to create a 'category' so that all your modded switches are listed in one location (in DCS control setup). I use "xxxxxxxxxx" at the end of my lines to make them easier to see, but I still have to go to all the different categories to assign them. For example: "My Cockpit" could show them all at once. Sorry if I asked prematurely, I'll have a look and see how it is structured after a couple coffees.

Yep, just a trainer. Guy in back can mess with systems to create problems for the pilot in front. I stopped letting people ride un-announced because of it. It is a great plane though.

forgetful old S.O. ..... To make Ikarus work, you also DL and place the "DCS ExportScripts" folder in your users/saved games/DCS/scripts folder. Ikarus works well with all other exports. Use their export lua or paste the following line at the end of your current export.lua (use Notepad++ and copy it from the Ikarus file). -- load the DCS ExportScript for DAC and Ikarus dofile(lfs.writedir()..[[scripts\DCS-ExportScript\ExportScript.lua]]) Works in both 1.5 and 2.0, just edit both export.lua files.

Forgot to add... You edit monitor position in the Ikarus master/Ikarus/config.xml file. Use Notepad++. You need at least one other monitor. I run 4. hope it helps..