Simpit Software from SDA

Hi Micha,

I appreciate you letting me give feedback here. I enjoy experimenting with this. :)

My setup is pretty unique. I use Ikarus for only outputs. Gauges for now and LED/ 7 segment outputs when I get my Arcaze cards next month. I am looking at a near life-sized view of DCS, but cockpit is hidden by my portrait, landscape, portrait monitor configuration. 4080x1920 DCS, 6000x1920 Windows.

1.5 DCS is affected by the config.lua change, but not 2.0.

config.lua set to false.

mirror on - 88 fps

mirror off - 105

config set to true:

mirror on - 4X-5X

mirror off - 5X-6X

It's not just a number either, it is noticeable by eye as soon as the auto zoom in takes place when entering cockpit.

I'm glad your numbers are OK and it is just me. I will say I've never seen such good DCS performance (with gauges). I'm very, very happy.

Micha

Any ETA on the Viggen profile?

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:

Thanks for your reply and especially for your very nice work on Ikarus!

See below for some additional feedback / foundings. I'm glad if it is of any help;

Tachometer RPM - scale off - shows too much at very low rpm, too little at high rmp.

1000 RPM, Ikarus shows 1500

at ~ 1900 RPM, cockpit and Ikarus show same 1900 RPM

2500 RPM, Ikarus shows 2100 RPM.

3000 RPM, Ikarus shows 2300 RPM.

Boost - okayish - seems to show just slight variation to cockpit instrument. Just a notch too little in Ikarus.

Voltmeter - OK

Oil Temp - seems ok.

Rad Temp - ok at high temeratures (115°C), but when engine cools down during dive w low settings, it shows temperatures as too high. Cockpit 70°C, Ikarus shows still 95°C.

Fuel amount - OK.

Oli Pressure - OK

Climb indicator - OK for climb, but does not show decent at all, just zero when decending.

Turn and Slip indicator;

Side Slip - OK

Turn Indicator - shows turn in wrong direction.

Artificial Horizont - Ikarus even more off and drifting than the Spit Cockpit one.

Directional Gyro is off / wrong scale;

Cockpit shows 0°, Ikarus shows 0°.

Cockpit shows 358°, Ikarus jumps to 180°.

Cockpit ~45°, Ikarus ~25°.

Cockpit 90°, Ikarus 45°.

Cockpit 190°, Ikarus 90°.

Cockpit 270°, Ikarus 135°

The Compass - seems ok, although the Spit Cockpit one is so difficult to read for me, that I really can't say for sure ;-)

Airspeed Indicator; shows too little at higher speeds.

in game 400 mph, Ikarus 220 mph, in game 320 mph, Ikarus 195 mph or in game 180 mph, Ikarus shows ~145 mph.

too much at very slow speeds. in game 90 mph, Ikarus 100 mph.

Elevator Trim Indicator - seems ok, a bit slow and jumpy in reaction though.

Clock does not work.

Break pressure indicator wrong needle moving and would be nice if you can combine this to a single instrument as in the Spit Cockpit.

Also it would be nice to have the

- gear indicator light

- fuel pressure warning light

- supercharger gear warning light in Ikarus.

Micha

Any ETA on the Viggen profile?

At the moment we solve the last problems for the L-39. The next module will be the Spitfire. Then hopefully the module for the Viggen will be ready for as.

I already have the graphics for the Viggen. Thanks to Andreas for this.

Thanks for your reply and especially for your very nice work on Ikarus!

 

See below for some additional feedback / foundings. I'm glad if it is of any help;

 

Tachometer RPM - scale off - shows too much at very low rpm, too little at high rmp.

1000 RPM, Ikarus shows 1500

at ~ 1900 RPM, cockpit and Ikarus show same 1900 RPM

2500 RPM, Ikarus shows 2100 RPM.

3000 RPM, Ikarus shows 2300 RPM.

 

Boost - okayish - seems to show just slight variation to cockpit instrument. Just a notch too little in Ikarus.

 

Voltmeter - OK

 

Oil Temp - seems ok.

 

Rad Temp - ok at high temeratures (115°C), but when engine cools down during dive w low settings, it shows temperatures as too high. Cockpit 70°C, Ikarus shows still 95°C.

 

Fuel amount - OK.

 

Oli Pressure - OK

 

Climb indicator - OK for climb, but does not show decent at all, just zero when decending.

 

Turn and Slip indicator;

Side Slip - OK

Turn Indicator - shows turn in wrong direction.

 

Artificial Horizont - Ikarus even more off and drifting than the Spit Cockpit one.

 

Directional Gyro is off / wrong scale;

Cockpit shows 0°, Ikarus shows 0°.

Cockpit shows 358°, Ikarus jumps to 180°.

Cockpit ~45°, Ikarus ~25°.

Cockpit 90°, Ikarus 45°.

Cockpit 190°, Ikarus 90°.

Cockpit 270°, Ikarus 135°

 

The Compass - seems ok, although the Spit Cockpit one is so difficult to read for me, that I really can't say for sure ;-)

 

Airspeed Indicator; shows too little at higher speeds.

in game 400 mph, Ikarus 220 mph, in game 320 mph, Ikarus 195 mph or in game 180 mph, Ikarus shows ~145 mph.

too much at very slow speeds. in game 90 mph, Ikarus 100 mph.

 

Elevator Trim Indicator - seems ok, a bit slow and jumpy in reaction though.

 

Clock does not work.

 

Break pressure indicator wrong needle moving and would be nice if you can combine this to a single instrument as in the Spit Cockpit.

 

Also it would be nice to have the

- gear indicator light

- fuel pressure warning light

- supercharger gear warning light in Ikarus.

Thanks for this error report. That helps us a lot and I'm sure we can correct that.

Hello,

we have again made a few small additions and bugfixes on our software.

DCS ExportScript

• Optimizations data processing in the receiving direction
  
• UH-1H Export revised
  
• L-39 Export expands (RSBN NAV and LAND Channels)
  
• Spitfire Export expands (Clock)
  

Ikarus

• L-39 new gauges added (various pressure gauges, RSBN air pressure, ...) and profiles adapted
  

DAC

• Bug fixes on the UH-1H file
  

CU Micha

Hi Micha,

 

I appreciate you letting me give feedback here. I enjoy experimenting with this. :)

 

My setup is pretty unique. I use Ikarus for only outputs. Gauges for now and LED/ 7 segment outputs when I get my Arcaze cards next month. I am looking at a near life-sized view of DCS, but cockpit is hidden by my portrait, landscape, portrait monitor configuration. 4080x1920 DCS, 6000x1920 Windows.

 

1.5 DCS is affected by the config.lua change, but not 2.0.

 

config.lua set to false.

 

mirror on - 88 fps

mirror off - 105

 

config set to true:

 

mirror on - 4X-5X

mirror off - 5X-6X

 

It's not just a number either, it is noticeable by eye as soon as the auto zoom in takes place when entering cockpit.

 

I'm glad your numbers are OK and it is just me. I will say I've never seen such good DCS performance (with gauges). I'm very, very happy.

Please test the new versions.... and reports on the results!

Hi !

I chatted with H-J-P so he could help me with the creation of a Mirage 2000C profile on Ikarus.

Thanks to him I've got a file with lot of DCS IDs (that I have to understand to know what goes where)

But I have a lil trouble.

The ADI of the Mirage is a ball. So I took the one of the Viggen. And even tho it moves smoothly, the angles are all wrong.

Of course the solution would be to modify something in the export file but how do I do it ?

I've tried something but it didn't work

Here is the export file I made if you wanna have a look at it

M-2000C.lua

I'm having an issue on the configuration end that I hope i can sort out ....I have a 32" main at 1920 x 1080 and my secondary monitor is 19" 1440 x 900 ...when i start Ikarus most time the pit shows up on the secondary but very large and off center and I can't seem to move it ....other times it just shows up on the main screen covering the game and unmovable ....I'm not clear as to what I should edit or look at to try to resolve this issue ....I use devicelink in CLOD but this is a little tougher to configure .....thanks for any help.

Hi again,

In the end I've been able to fix the ball.

But I have an another problem now. I can not assign any light. And that really bothers me.

I create a light, but I can't click on Details or assign any function... And I have the DCS ID for the lights I want.

Is there any way to fix it ?

Hello TheKenji2221,

Hi !

 

I chatted with H-J-P so he could help me with the creation of a Mirage 2000C profile on Ikarus.

Thanks to him I've got a file with lot of DCS IDs (that I have to understand to know what goes where)

 

But I have a lil trouble.

The ADI of the Mirage is a ball. So I took the one of the Viggen. And even tho it moves smoothly, the angles are all wrong.

Of course the solution would be to modify something in the export file but how do I do it ?

I've tried something but it didn't work

 

Here is the export file I made if you wanna have a look at it

To change a value, you can easily convert that.

E.g. Rotate by 90 °, DCS value * 0.25, or for the other direction DCS value / 0.25

The whole should be calculated in the function "ExportScript.ProcessIkarusDCSConfigHighImportance", since this is most frequently executed.

E.g.

ExportScript.Tools.SendData(318, (mainPanelDevice:get_argument_value(40) * 0.25))

It is also important to exclude the value in the table "ExportScript.ConfigEveryFrameArguments".

Otherwise, the original value and the corrected value are sent.

Hi again,

 

In the end I've been able to fix the ball.

But I have an another problem now. I can not assign any light. And that really bothers me.

 

I create a light, but I can't click on Details or assign any function... And I have the DCS ID for the lights I want.

 

Is there any way to fix it ?

The IDs for the lamps also belong to the table "ExportScript.ConfigEveryFrameArguments".

For lamps it is important to specify "%.f" as format string. Then the result is always 0 for off or 1 for on.

The ids for switches and other things that do not need to be timed are included in table "ExportScript.ConfigArguments" or in function "ExportScript.ProcessIkarusDCSConfigLowImportance" (if corrections still need to be made).

You can check the DCS ExportScript Wiki, there are many explanations.

CU Micha

I'm having an issue on the configuration end that I hope i can sort out ....I have a 32" main at 1920 x 1080 and my secondary monitor is 19" 1440 x 900 ...when i start Ikarus most time the pit shows up on the secondary but very large and off center and I can't seem to move it ....other times it just shows up on the main screen covering the game and unmovable ....I'm not clear as to what I should edit or look at to try to resolve this issue ....I use devicelink in CLOD but this is a little tougher to configure .....thanks for any help.

Please check here, there are examples.

Hello TheKenji2221,

 

 

 

To change a value, you can easily convert that.

 

E.g. Rotate by 90 °, DCS value * 0.25, or for the other direction DCS value / 0.25

 

The whole should be calculated in the function "ExportScript.ProcessIkarusDCSConfigHighImportance", since this is most frequently executed.

 

E.g.

ExportScript.Tools.SendData(318, (mainPanelDevice:get_argument_value(40) * 0.25))

It is also important to exclude the value in the table "ExportScript.ConfigEveryFrameArguments".

Otherwise, the original value and the corrected value are sent.

Hi !

I fixed the ball axis like that and now it works perfectly with the Viggen ball ! :smartass:

ExportScript.Tools.SendData(316, string.format("%.4f", (mainPanelDevice:get_argument_value(318) * -1)))  -- Heading
ExportScript.Tools.SendData(317, string.format("%.4f", (mainPanelDevice:get_argument_value(316) / 2)))   -- Pitch
ExportScript.Tools.SendData(318, string.format("%.4f", (mainPanelDevice:get_argument_value(317) * -1)))  -- Banking

The IDs for the lamps also belong to the table "ExportScript.ConfigEveryFrameArguments".

For lamps it is important to specify "%.f" as format string. Then the result is always 0 for off or 1 for on.

Yeah but my problem is on Ikarus side. When I create a new lamp I can't do anything with it. I can't click on Details (the window doesn't open) or manually assign a function.

I created the Mirage profile from scratch.

I'll try to redo it from an another plane profile to check if it does the same.

The ids for switches and other things that do not need to be timed are included in table "ExportScript.ConfigArguments" or in function "ExportScript.ProcessIkarusDCSConfigLowImportance" (if corrections still need to be made).

 

You can check the DCS ExportScript Wiki, there are many explanations.

 

CU Micha

I'll keep that in mind. Thanks for the tip

UPDATE :

I duplicated the F-15C profile and renamed it M-2000C.

It does exactly the same. I can't edit the lights on Ikarus

Copy the F-15C.xml file and rename that to M-2000C.xml. Then correct it with your values for the lamps.

Copy the F-15C.xml file and rename that to M-2000C.xml. Then correct it with your values for the lamps.

Yep it was the solution :D

Talking about that, other than the lamps, what is the point of the xml files ? Cause I never had to use the F-15C's one :huh:

(I saw all the IDs and all, but other than that ?)

For Ikarus, it is for the definitions of lamps and switches.

If you use DAC also, then there is much more. The whole configuration of your hardware cockpit.

Great Tool

any one made it work with the Gazelle ?

Sorry, but I have not this module. Maybe later.

Oki I see !

The cockpit is advancing so far but as you may know, since there's no gauges for the Mirage I have to use whatever I can find ^^'

Sometimes it works pretty well like the ASI.

Sometimes less well like the ADI (which needed some tricks)

And sometimes the gauge I need doesn't exist on Ikarus. Which is the case for the HSI.

Is there any way I can make my own HSI for the Mirage ?

That would be neat

Originally Posted by Sully_pa View Post

I'm having an issue on the configuration end that I hope i can sort out ....I have a 32" main at 1920 x 1080 and my secondary monitor is 19" 1440 x 900 ...when i start Ikarus most time the pit shows up on the secondary but very large and off center and I can't seem to move it ....other times it just shows up on the main screen covering the game and unmovable ....I'm not clear as to what I should edit or look at to try to resolve this issue ....I use devicelink in CLOD but this is a little tougher to configure .....thanks for any help.

Please check here, there are examples.

Well i tried and failed miserably tried changing the res settings as per the the documentation but no matter what i did ...the P39 came up on the 19" to large and the F5E never would come up on it but on the main screen instead ....I may give it a go again later but i think I'm missing something in translation :dontgetit: Thanks for the help and your work though :)

If a gauge is missing, you can use another one with exports for the plane you are flying. Just edit the DCS ID with the export listed in the mainpanel_init.lua.

This can work until proper gauge artwork is complete and you can find one that looks close enough for you.

Res setting works fine. Position setting works fine.

If you are making a custom Ikarus program, you need to delete or move the default Ikarus program that is getting loaded when you get into your plane.

IF your position settings are not working correctly, look into scaling of your desktop monitors.

Sully_pa:

On your Mainpanel:

Click 'Detail'

Pos X 1920, Pos Y 0, Width 1440 Height 900 (Pos Y will depend on how your monitors are situated. I am assuming top edges are lined up).

Transmit

close cockpit/show cockpit

save if you like it. Beware of file location as it will change if you have searched anywhere else, for anything else (this is a bug!).

To edit locations of gauges:

Configuration tab:

Editor Mode. Drag and drop to position the gauges.

To edit size of gauges. Instrumentation tab.

If it does not show all you gauges, click Instruments tab, then back to Instruments Functions tab.

Clicking a gauge will highlight what to edit. Edit size just as you edited position.

You can drag and drop gauges and Ikarus items. Always close/show cockpit to reflect changes.

Save when done.