JG14_Smil

Thanks grunk! So QFE is different than the way we do it here... OK, so I can correct the variation? Please note I only fly online and don't get into the back seat much. I know there is correction back there.

Link to GitHub and the Ikarus files. https://github.com/H-J-P/Ikarus

Here is a fully working L-39C gauge profile for Ikarus. All sensors and scales seem correct with the sim. Ikarus is a great help for DCS and a cockpit builder. I can't believe I stumbled into it from an obscure thread. It really helps when flying the '39. Note: Ikarus has a few bugs. When you check "Instrumentation", be sure to "close and show" cockpit (to refresh changes and see all your records). L-39C oil temp zeroes at "1" when in the sim. Unable to change it. All other temps seem to match. Max G meter pipper is untested. Under "configuration" tab, choose "editor mode" to change position of gauges. Edit gauge size under the "Instruments" tab, then "transmit". Most are not set to exact position or scale of the sim. I have added a couple indicators. These are temps to help me until I make my cockpit lights. oh, you need at least one other monitor. I am running four. Edit gauge monitor position in the Ikarus configuration file. Ikarus is easy to setup and use, and is very reliable in DCS. See their website for DL and instructions. I'll add it in a bit... Unzip my file into the Ikarus Master/Ikarus folder. You put these folders where you like.

Hello, The barometric altimeter reads "0" at mission start. This should only be happening at sea level. It is displaying AGL altitude. There is another gauge for AGL, they are two different readings. Runways are named for a reason. "Runway 25" should not be dead center 270 degrees. Bug?...feature?... you tell me. :) thanks.

Yeah, it has been mentioned. L-39 needs a central bug thread. The throttle hides a lot too and I wish I could hide it.

OMG I fixed it. I went into the C:\Users\CS\Saved Games\DCS\Scripts\DCS-ExportScript\ExportsModules\L-39C.lua file and found the ID numbers for the VD-20 baro altimeters, (53 and 52), entered them manually into the Ikarus configuration screen and the gauge now works. "NeedleAlt100" DCS ID 52 "Alt 10000" DCS ID 53 Let the build begin...

Hello to all, I just found out about Ikarus today and it is a great help for my next cockpit build, the L-39C. I have Ikarus working but I am unable to get a working barometric altimeter. I was just wondering if anyone was familiar with the Ikarus L-39C profile and had some advice on how to get it running. I should note: I reaplaced the original altimeter (which did not work) with the L-39C "Alt20". This gauge has the two needles required and I can manipulate them from Ikarus.

Yes, this is new behavior. My cursor shows up in my left wing monitor, but it shows up right at eye level and it is quite distracting. Have to hide it now. Probably an easy lua edit.

Hello, If you want multi monitor experience, one big monitor for DCS and one for gauges gives best FPS. Adding the third one is where it starts dropping fast. I run 4 at 6000x1920. I have an old i-3779k and original Titan. I am smooth in flight. Big slow turns will make it chug in a helo or taxiing, but I just ignore it. I have to say I love the huge screens and run it approximately life sized. I'm not into combat anymore and just enjoy my flights, so take it with a grain of salt... Best of luck with your rig,

TeamSpeak will work without a PTT, but you have to set your gain correctly. I can promise you no one wants to listen to your breathing. ;)

I doubt it. I was thinking it could be exported and shown on the number one screen, but probably won't work with your VR thingy. You're stuck with it. Can't even use a real watch.

Hello, One of the cool things about a Helios setup on a second monitor is you can set your gauge positions the way you want it. I know there is no L-39 yet, but perhaps in the future there will be. I switched the VVI and G Meter in my Ka-50 pit. No help to you I know... :) Might be able to export it(?).

Bad thread, disregard. trying to delete it...

Hello, Page 193. Regarding navigation into and entering a landing path: Figure 153: Landing pattern using GLIDE PATH and LANDING modes 1. Descent in cloud penetration mode; 2. Altitude - 600 m. D= 21±3 km. end of «GLIDE PATH» mode; 3. Altitude - 600 m. D = 15 km. speed - 330 km/h – retract landing gear; 4. Speed - 280 km/h – extend flaps at 25º. 5. Altitude - 600 m. D = 12 km. Radio glideslope entry point. 6. Altitude - 300 m. D = 6 km. speed - 280 km/h – extend flaps at 44º. 7. Fly over outer NDB, speed - 260 km/h, altitude - 200 m. 8. Fly over inner NDB, speed - 230 km/h, altitude - 60 – 80 m. Should be extending gear at this point, not retracting.

I am a long way off from needing the module. What I would really like to learn is the "Plane ID" that the export uses to get arguments for the L-39. As I look at your panel, I see three sizes of gauge types. The fuel gauge, EGT, V/A meter, ect are the smallest. The diameter here would help me. I'll then size everything else to them. May I suggest posting your question with the arcaze cards to the input/output forum. Might get seen more than in here. Thanks and best wishes,

kadda, I am envious of that great simulator. I'm starting a scratch-built one myself. Could you please share your DCS-BIOS module for the L-39? Also, if it is not trouble, a dimension or two on the gauge bezel diameters would be interesting to know (I am guessing small ones - fuel gauge, ect, - are around 60mm?). thanks so much,

Don't like the zoom. :) The edit above works great.

Any MP you join will override your offline ARK 22 channels (if they edited any).

Hello, I'm really enjoying the L-39. Page 131, regarding the VD-20 Barometric Altimeter: ------ Figure 109: VD-20 barometric altimeter 1. Outer scale, indicating altitude in meters 2. Inner scale, indicating altitude in kilometers 3. Barometric pressure window 4. Barometric pressure / QFE adjustment knob, for setting the altitude pointers to “0” 5. Pressure correction indexes, for landing at high altitude airfields, where pressure is less than 670 mmHg. The indexes are moved by the knob. ----- Outer scale is not meters, the numbers are "meters x 100" and the tick marks are "meters x 10".

It's a simulation. They have to model the switch covers too. It's not hard to open both. Helios can do it and a simple keystroke sent will do it too. Send the switch command twice and it will open it. Most normal people use a mouse to run the sim. Oddball pit builders like you and me must find different ways. I put a normally closed button under my switch cover to work. You do know we are wasting our time with this request? :)

Did you save a profile? Mine was in the root DCS folder.

It can be done as Helios has bindings for each, but you would need a separate switch lead for each command. That may not be possible as you may already need hundreds of switch leads to make a cockpit. No reason you can't do it if you have the outputs. I just use three outputs for my rotary knobs and use code to send the commands you don't like (up and down). It gets used so rarely that it doesn't go out of sync with the sim. Works fine in either direction with code. If you are using DCS BIOS, good luck. Report your findings when you learn how. I believe it is just a value you set that controls how far the switch moves. You may want to post this in Input Output forum.

Link for BUO836A I posted this link so we all have it handy. Which specific card do you have? Check to see what Windows says in hardware about it. Check another USB port. Make sure you diodes are in correctly if you use them on your switches. See what the configuration.exe software does.

Get your multi meter out and start tracing. Understood on Helios - we'll cross that bridge later. I'll have a look at any troubleshooting info I can find as I sip my coffee...

Interesting thread. I note I get 100% more FPS in 1.5.5, but I can't say it is smoother. If anything, 1.5.4 felt smoother for me before the update. I recently flew in 2.0 again and it feels like glass. Probably apples and oranges and I note my 6000x1920 res is very taxing on framerates.