JG14_Smil

Most issues resolved. See later post.

H-J-P: Will give you exact details soon. Thanks very much. jonsky: You look at the mainpanel_init.lua for your aircraft, located within the Mods folders in DCS. You can learn the export ID number there and sometimes make your own gauges from another plane's gauge art.

Thank you for this mod. Relearning about the L-39 pit-build after my hiatus and those gauges were driving me crazy.

It is bugged. I would be happy to tell you about each bug, but I get different bugs from the 3 versions of Ikarus I have, which can run 3 different versions of the same file name stored in different folders. Please fix the latest version. As far as I know, the only bugs are two missing gauge messages. Will use the 2017 version and delete all the rest (including the version you pointed me to). Oh, the radio channel digital readouts do not work in the latest version. I did see them working in one version, but without proper fonts.

Hello, L-39 is missing from latest build. L-39 build from a month or two ago (great new gauge art!) has several bad bugs: - Engine RPM needles do not work. - Radar alt does not work in any form. - Oxygen blinkers don't sync with DCS. - I note the metric IAS did not work when I tried switching to it. These go across all L-39.ikarus versions. I can run my Ikarus version from 2017 and everything works (but no new art for gauges). Thanks,

Hello, I haven't flown lately, but updates move replaced files to a backup folder. I just move them back afterwards and have no troubles, even with Ikarus, Ivibe, SRS (and hopefully now DCS_BIOS). I only fly one plane though... good luck.

What he said. I also find the ALT F1 view to be a bit sickening.

First time does take a long time but 30 minutes should have been good to build the shaders. Whenever I have repeating MP trouble, first thing I do is delete all trk files in the MP folder. I've seen it cause hangups when joining before. It should be done regularly, actually. good luck,

Hello, I'll be starting work again on my L-39C cockpit this year and I've started learning about DCS_BIOS and Kagga's L-39ZA profile. I've started fixing copy/paste errors and populating the module's unfinished lib\L-39ZA.lua file. I have two questions: Question 1. The clickabledata/.lua uses if/then/else statements for different functions between the 39C and 39ZA. if L_39ZA then elements["START_MODE"] = default_3_position_tumb(_("Engine Start Mode Switch, FALSE START/START/COLD CRANKING"), devices.ELEC_INTERFACE, electric_commands.L39C_Command_EngineStartModeSw, 322, false, false, 1, {-1, 1}) else elements["START_MODE"] = default_3_position_tumb(_("Engine Start Mode Switch, START/FALSE START/COLD CRANKING"), devices.ELEC_INTERFACE, electric_commands.L39C_Command_EngineStartModeSw, 322, false, false, 0.1, {0, 0.2}) end Can or do I need do this within the lib\L-39ZA.lua file? Simple example please, if so. Question 2. Kagga's profile has no 3 position switch examples, so I took one from the /lib/ka-50.lua file: defineMultipositionSwitch("OP_NAV_LIGHTS", 45, 3004, 146, 5, 0.1, "Overhead Panel", "Navigation Lights 10% / 30% / 100% / Off switch") I don't have my Ka-50 loaded, so I can't check these values.. how do I get the "5, 0.1" values from the above 3 position switch examples? I hope I am clear enough for what I am asking and thanks in advance for any help.

Got it working with ZA and C versions. I am thinking I had issues with multiple DCS_BIOS install/version conflicts. Did not have to edit address.

Found DCS-BIOS/Lib/addresses.txt and all addy's are listed. 0x5400 is the Spitfire address. tried going higher but not getting any in/out when in the "C". Works fine in the "ZA".

Replace 0x1234 with a base address for your module. A base address is the address in the DCS-BIOS export address space where the data from your export module starts. Choose it in a way so the address space occupied by your module does not overlap with any other export module that is active at the same time. Ideally, choose it so you do not have an overlap with any other export module. As a rule of thumb, take the highest base address of an existing export module (except MetadataEnd) and add 1024 (0x400). 1 KiB of address space should be more than enough for most aircraft. Largest address I find is the P-51D with 0x5000, so I will try 0x5400.

Hello, I am working on a module for the L-39C. Kagga's L-39ZA .lua starts with this line: "BIOS.protocol.beginModule("L-39ZA", 0x3200)" How do I find, or could someone tell me, the address in red for the 39C? Thank you in advance.

https://forums.eagle.ru/showthread.php?p=3854907#post3854907 Get it together guys... :) Latest release was posted in the wrong thread too.

Been there, done it. :) Best of luck with your build.

Really great work. What part of the world do you live?

The pilot (and the person that paid the money) should have final say in how they want to fly their L-39. Many mission creator's just throw the L-39's in without much thought. I agree with Dehuman 100%.

Your data makes my eyes glaze over. I just don't pay attention to that. Second monitor is no performance hit at all.

I concur. Would love to use my Phidget board's again. Best wishes,

Nope. Most pilot's don't even know how to operate it or what it is for, or even how to look at it so you can see the setting either, so asking another person to go back there and set it is not easy. Moot point as magnetic correction is kind of borked in DCS and not as in real life (if I remember it correctly). I truly miss flying my L-39. New system after Christmas...

Try restarting DCS with your saved games folders renamed. It will rebuild the shader's and hopefully fix you up. You can move your important files back in to get your saved options back.

You are still in Window mode. Just Alt Enter and you will see.

"Adjust desktop size and position". That is on Nvidia.

check for multiple axis assignment.

Hello, I am surprised at how flight simming has become one of my favorite and longest-lived hobbies in my entire life. It started 50 years ago as it helped me learn to read and continues to this day in my retirement. The L-39 is a wonderful plane, it is the only one I fly, but the English translated manual is quite difficult to learn from. Just keep that in mind if things seem strange. Best of luck and enjoy,