Simpit Software from SDA

[JG14_Smil]

Feedback regarding use of the new displays.

 

I am testing the latest L-39C.ikarus file and the new "Instrument" examples (which don't work correctly). The example has a "Name" of "R_832M Channel" and "Class" of "Display7Segment".

 

For "Instrumentfunctions",

 

ID:18 , ID Fct: 1, Name: R_832M Channel, DCS ID 2001*, ASCI V, Input: EFEFEF, Output: 2.

 

This did not work and produces "0." on the display, which is a counter and not a 7 segment display type.

I edited the 2001 (and forgot the original value!) to 189 to try a test with the RSBN Navigation channel.

 

This produced "0." on the display and did not seem to work.

 

I edit output value to "3" in Instrumentfunctions.

 

This produced "0.0" on the display and did not seem to work.

 

I edited value to 4.

 

This produced "0.00 and counter now works, however DCS RSBN counter starts at "01", hence:

 

01=0.00

02=0.01

03=0.02

 

etc.

 

Variable is one number off as this counter needs to start at "01" and not "00".

 

How is format changed? Decimal point is not needed here, but will be needed in other variables.

Edited March 28, 2017 by JG14_Smil

[H-J-P]

I think that's something for Micha. He supervises the forum. We may still get incorrect data today or we have misunderstood the data. Thanks JG14_Smil !

Edited March 29, 2017 by H-J-P

[McMicha]

Hello JG14-Smil,

 

we have found the problem and are working on a solution.

 

CU Micha

[JG14_Smil]

Oh, no problem. :)

 

I just discovered another item in the L-39 profile. For the barometric altimeter, the class "L39_Alt20" uses an improper QNF scale and will not display the correct value. Using the class of "WPALT20" for this gauge will make it work correctly with the sim.

 

Note this is for using metric units with the Ikarus profile, not the default knots/feet.

[SGT Coyle]

I seem to be having difficulty with the monitor configuration. This is what I have set up:

 

3 27" monitors @ 2560 x 1440 each.

 

Configured like this:

 

http://imgur.com/a/EdSyk

Monitor 2 is 1440x2560

Monitor 1 is 2560x1440 (what I play the game on) and is my main monitor

Monitor 3 is 1440x2560

 

total combined res of 5440 x 2560

 

this is my Monitor setup .lua

_  = function(p) return p; end;
name = _('TripleTEST');
Description = 'TEST with LMFCD,Center,RMFCD'
Viewports =
{     
       Center =
       {         
                x = 1441;
                y = 1120;
                width = 2560;
                height = 1440; 
                viewDx = 0;
                viewDy = 0;
                aspect = 2560/1440;
             }
}
LEFT_MFCD =
       {     
              x = 674;    
              y = 1800;     
              width = 650;    
              height = 650; 
       }
RIGHT_MFCD =
       {     
              x = 4125;
              y = 1800;     
              width = 650;
              height = 650;
        }
CDU_SCREEN =
       {    
               x = 4860;  
               y = 500;    
               width = 530;    
               height = 530;
        }

UIMainView = Viewports.Center

 

That Works fine, but as for setting up Ikarus, panels don't like my left monitor

 

 

 

 

Edited April 4, 2017 by SGT Coyle

[JG14_Smil]

Hello Sgt Coyle.

 

Monitor setup lua is just for viewports from DCS. Ikarus is not affected by that.

 

In Ikarus, Main Panel Pos X and Pos Y will make your Ikarus gauges go where you need them. Change the numbers, transmit, then close and show gauges.

[JG14_Smil]

I was able to create working brake pressure gauges for the L-39. I created new Instrument records using the L39 volt/amp and fuel gauges. I used DCS exports 98, 99, 100 with output 0,60. They match the DCS gauges performance perfectly.

 

All you would have to do is update the artwork for these gauges and rename them for the L-39 for a future release.

 

I found I could also create the main/aux hydro gauge from the L39_voltampere gauge using exports 198 and 200 0,200.

Edited April 5, 2017 by JG14_Smil
another gauge

[H-J-P]

With the next update you will get the L-39 pressuge gauge. Perhaps too the hydro.

[Fakum]

Thank you JG14_Smil & cichlidfan for directing me to this post. I have been a user of Helios for many years, I look forward to setting this up as well and giving it a spin! Thank you for your contributions.

[Snacko]

This is great!!

 

I would give Rep to HJPuhlmann, but the forums won't let me!?

Sorry, you cannot give reputation to this post.

[JG14_Smil]

It works. You may be trying from an old post. Try his latest post. It worked for me.

[H-J-P]

Since I changed my name, a lot does not work anymore. Tips?

[H-J-P]

JG14_Smil,

 

please send us a picture of your solution.

Edited April 6, 2017 by H-J-P

[JG14_Smil]

Hallo Heinz,

 

I'm sorry, which solution, digits or the gauges?

 

Unsure why things don't work, but I was able to give rep to H-J-P. It says I can't give it to you again. You have a whole new account and not a renamed original.

[McMicha]

Hallo Heinz,

 

I'm sorry, which solution, digits or the gauges?

 

Unsure why things don't work, but I was able to give rep to H-J-P. It says I can't give it to you again. You have a whole new account and not a renamed original.

 

Digits and gauges please....

[H-J-P]

Hallo Heinz,

 

I'm sorry, which solution, digits or the gauges?

 

Unsure why things don't work, but I was able to give rep to H-J-P. It says I can't give it to you again. You have a whole new account and not a renamed original.

 

I want my rep back from my old account. Maybe something went wrong. I do not like that and no one helps me. But that is not so important at the moment.

Edited April 7, 2017 by H-J-P

[JG14_Smil]

Micha, thanks.

 

I've learned how to fix the missing export for the HSI Arritir lamp in the xml file. I'm quite excited about that. :)

 

If you give me some time, I will create a full generic L-39C profile (gauges and lamps). I will then note each issue that arises to see if you want to address it. If you like it, you can rename it to the default L-39C profile. Someone else could add the clickable controls (I don't use these).

 

What I wish I could do is artwork. The L-39 background could use some improving. Just a simple rounding of the corners of the blue/gray gauges panel would help a lot.

 

========

 

Suggestion discussion time!

 

The Ikarus gauges have red overlays for gauge glass. These are triggered automatically if I remember correctly. They are toggled with the "Gauges Backlight" option box while in the editor.

 

A, dare I say better, approach would be to have one overlay toggled over the entire panel. Instead of toggling this option with the-hour-of-day lua code, you can use the export for the cockpit lighting. The red/white modifier could toggle overlays to make the cockpit appear in night lighting.

 

Like I say, I'm just discussing as idea here and I haven't even tracked down the cockpit lighting routine.

 

Heinz, you have to PM a mod for things like that. Best of luck.

[JG14_Smil]

One more huge issue about Ikarus:

 

Ikarus its setup to auto load a profile when a plane is entered. This is a very good thing and works perfectly, once all profiles are setup. However, there needs to be a way to "set as default" in a profile.

 

When I enter a L-39C, Ikarus loads "L-39C.ikarus" (and the associated L39C.xml). Lets say I edit this file and get it just the way I like. You post an update and my work gets over-written. Unacceptable.

 

I do a "Save as" and create a custom profile. It saves a L39C_custom.ikarus file, but it does not save an associated xml file. You cant add custom items to your file without an associated xml file, so I copy/paste the original L39C.xml and rename it to L39C_custom.xml. I can now edit items to my profile properly.

 

Yay! excellent! I start DCS and enter a L-39C. Ikarus loads the original L39C files, not my custom profile. ^%#$%$#!

 

To get around this, I delete the original L39C.ikarus file. My custom profile loads when I start the DCS L-39C. Perfect.

 

If I move the original L39C.ikarus file back to the folder, the DCS L-39C defaults back to the incorrect Ikarus profile again.

 

The way Ikarus is setup, you're expecting everyone to use the exact same file name.

 

--- other side of coin ----

 

You need to update the xml files to add new code and features to Ikarus, so renaming the custom xml file would need to be done after each update. This is why you need people to use the exact filenames.

 

If you could add a routine to set a profile as default, while it still can be renamed and associated with the original xml file, this would be a great addition.

Edited April 8, 2017 by JG14_Smil

[JG14_Smil]

I am on a roll, so..

 

How to fix a missing lamp export in Ikarus

==========================

 

Lamps are added from a list. If you don't see your lamp listed, you can add it. You need just Notepad++.

 

You edit the xxxx.xml file that is associated with your xxxx.ikarus file with Notepad++. Find and copy the following chunck of code: (it can come from anywhere in the file. It does not need to match this exact example.)

 

<DCS_ID>

<ExportID>63</ExportID>

<Description>RV-5 DangerRALT</Description>

<ExportIDWithDescription>63 - RV-5 DangerRALT</ExportIDWithDescription>

<Type>Lamp</Type>

</DCS_ID>

 

You will paste in a copy directly under the code you copied.

 

<DCS_ID>

<ExportID>63</ExportID>

<Description>RV-5 DangerRALT</Description>

<ExportIDWithDescription>63 - RV-5 DangerRALT</ExportIDWithDescription>

<Type>Lamp</Type>

</DCS_ID>

<DCS_ID>

<ExportID>29</ExportID>

<Description>KPP_Arretir</Description>

<ExportIDWithDescription>29 - KPP_Arretir</ExportIDWithDescription>

<Type>Lamp</Type>

</DCS_ID>

 

Note edited red text changes. I found the DCS export ID and name in the following file:

 

C:\Program Files\Eagle Dynamics\DCS World\Mods\aircraft\L-39C\Cockpit\Devices_specs\MainPanel\lamps.lua

 

Saving the xxxx.xml file will now allow you to choose the KPP_Arretir from the list and it can now be used in your profile. It will even work. :)

 

Be sure to make a backup of your xxxx.ikarus and xxxx.xml in a safe location so it won't be over-written in an update.

[H-J-P]

smil,

 

I get from Micha's export script the modul file name. After that, I load the ikarus and the xml file.

For most users this is the best way. Please save you files and insert this to our DL.

 

I'll think about it again.

 

Thank you for your cooperations. That helps us a lot.

[McMicha]

Hello,

 

We fixed a few reported bugs.

This applies especially to the XML files for DAC and Ikarus and a few gauges in Ikarus.

 

Updated files:

A-10C.xml

F-15C.xml

F-5E-3.xml

Ka-50.xml

L-39C.xml

L-39ZA.xml

UH-1H.xml

 

Added files:

SpitfireLFMkIX.xml

MiG-29G.xml

 

Changes Ikarus.exe

Bug fixes in Class L39_BrakeP and Class L39_Brake

 

 

Changes Ikarus profiles:

L-39C-RED.icarus

L-39C.ikarus

L-39ZA-RED.icarus

L-39ZA.icarus

L-39C.xml

L-39ZA.xml

UH-1H.xml

 

 

Please check the changes before you overwrite your files.

Use For this, the overview of the Commits in GitHub, or you make a comparison with you on your computer, e.g. With the Compare function of Notepad++.

 

Changes in DAC

 

Changes in Ikarus

 

Download DAC

 

Download Ikarus

[RedShoes]

Hi,

 

thanks for the nice cockpit SW. Really like Ikarus.

 

Just tried it out with the Spitfire. Unfortunately several Ikarus indicators are showing wrong values. e.g.;

 

Tachometer in game full 3000 RPM, Ikarus tacho shows only 2300 RPM.

Air speed indicator in game 320 mph, Ikarus air speed indicator shows only 195mph or in game 180 mph, Ikarus shows ~145 mph.

Ikarus Vertical speed indicator shows only climb, points at 0 during decent.

Dicectional Gyro heading in game 180°, ikarus shows 90°.

 

Is this something you are already aware of and are still working on or could this be some configuration problem on my side?

Is there an easy method of fixing these values with the Spit Ikarus config files / lua script?

 

Other than that, the Ikarus Spit cauges look great!

 

Cheers,

 

Red

[H-J-P]

Hi,

 

our vision of the Spitfire is a alpha vision. Actually, it should not yet be included in the DL.

 

Please report every thing you found. This will help us. :thumbup:

[JG14_Smil]

Hello,

 

Please note that in 1.5 DCS and using Ikarus with my L-39, I was able to almost double my FPS by editing a line in the following file:

 

C:\Users\CS\Saved Games\DCS\Scripts\DCS-ExportScript\config.lua

 

-- Ikarus and D.A.C. can data send

ExportScript.Config.Listener = true -- false for not use

ExportScript.Config.ListenerPort = 26027 -- Listener Port for D.A.C.

 

Setting this to "false" gave a big increase in the FPS. It is only needed of using Arcaze controllers. If yours is false by default, disregard this. The gauges work fine without this enabled.

[McMicha]

Hello JG14_Smil,

 

Thank you for the note.

 

But the config switch "ExportScript.Config.Listener" is for D.A.C AND Ikarus.

If the value is set to False, then no input from Ikarus will work (for example the almost complete porifle for A-10C or Ka-50).

 

How are your FPS with the True and the False setting?

I have hardly any messy differences.

 

I'll think about how I can improve that.

 

CU Micha