Simpit Software from SDA

[H-J-P]

It would be unthinkable to lose the W7 user. These are the cockpit builder and can not move now to W10.

Edited January 28, 2018 by H-J-P

[H-J-P]

I'm in the same boat. The newest version that can save without crashing I found is Ikarus-1c10159b8f7ddf9f31c3dffa6d3184b0d856abd6 from September.

Strangely enough it says version 1.2.1.4h, the same version as Ikarus-e878a4570d9e9944cd40e7f14e5ccd50faa45eaf from October, but that version doesn't work.

 

 

 

Regarding instructions and usability and such:

The only instructions that did not come in english was really simple to follow for a noob like me after using Google Translate. If you feel lazy, here it is. I could not possibly realize it being an automated translation if I was not aware of the fact.

The instructions are good enough for me as a noob with little programing skills to actually find a small error in the Ka-50 profile (ID fct for ADP_4_min_achieved_acc being 1 instead of 3) while reading the instructions for the first time, and correct it (needed to do it with Notepad++ due to the save bug, but easy enough).

And no need to enter exact positions for gauges and buttons, just to use the mouse an move it where you like it, even resize with the wheel. Moving the panel to another display and everything connected to it will follow.

 

The only request I can agree on promoted by "some guy" earlier is the relative resizing of all gouges and buttons when resizing the panel they belong to, to keep aspect ratios and relative locations. And possibly the ability to resize panels with the mouse. But no big deal if it won't be implemented for whatever reason.

 

Thanks for the quick test. That was the check against VS 2015 and VS 2017. It works with VS 2015.

Edited January 28, 2018 by H-J-P

[H-J-P]

One thing is strange, not all Windows 7 users have this problem.

[Holton181]

So, playing around with the Ka-50 panel I have so far identified three issues.

1) The SwitchOffOn for the UV-26 Amount flares counter/Programming [DCS ID 37] look very strange and I can't do anything about it, have resized, moved and rotated it but to no avail. Changing it to like an SwitchOnOffOn and it looks OK. The SwitchOffOn switches that exist on the main panel do look OK though.

2) The rotary ABRIS - Cursor control [DCS ID 518] doesn't work properly. The cursor on the ABRIS only move to the right (or up after pressing the ABRIS - Cursor control (push)) no matter on what side (red square) of the knob I click. I have played with the Input/Output values and got some even stranger behavior.

3) The CLOCK_flight_time_meter_status [DCS ID 75] are not in sync with the one in the cockpit. The cockpit start as white, while in Ikarus it start as red. Pressing the left button in cockpit to start the mission timer and it turns red in cockpit but divided in Ikarus. Press again and cockpit turns divided and Ikarus white, third pres one gets white and red respectively. If Ikarus started as white they would be in sync. I have searched for the images involved in the Ikarus clock animations, and found everything except for the CLOCK_flight_time_meter_status.

 

A suggestion for enhanced usability:

As it is now, we have 'Pos. X', 'Pos. Y', 'Size px' and 'Rotate' for all objects. I would like to suggest to split 'Size px' into 'Whith' and 'Height', aspect ratio can still be fixed (even if there might be situation where changed ratio would be desirable). The reason is I noticed when rotating a switch for example 90 degrees, the 'Size px' can not be used for calculating exact horizontal positions relative to the RIGHT side of the panel. Or when not rotated one can not use 'Size px' to calculate exact vertical position relative BOTTOM of the panel. Now one needs to use trial and error, doable but a little bit tedious.

 

 

EDIT:

4) The Flight Time Status [DCS ID 56] for the Mi-8 also behave strange. Stranger than for the Ka-50.

Edited January 29, 2018 by Holton181

[H-J-P]

So, playing around with the Ka-50 panel I have so far identified three issues.

1) The SwitchOffOn for the UV-26 Amount flares counter/Programming [DCS ID 37] look very strange and I can't do anything about it, have resized, moved and rotated it but to no avail. Changing it to like an SwitchOnOffOn and it looks OK. The SwitchOffOn switches that exist on the main panel do look OK though.

2) The rotary ABRIS - Cursor control [DCS ID 518] doesn't work properly. The cursor on the ABRIS only move to the right (or up after pressing the ABRIS - Cursor control (push)) no matter on what side (red square) of the knob I click. I have played with the Input/Output values and got some even stranger behavior.

3) The CLOCK_flight_time_meter_status [DCS ID 75] are not in sync with the one in the cockpit. The cockpit start as white, while in Ikarus it start as red. Pressing the left button in cockpit to start the mission timer and it turns red in cockpit but divided in Ikarus. Press again and cockpit turns divided and Ikarus white, third pres one gets white and red respectively. If Ikarus started as white they would be in sync. I have searched for the images involved in the Ikarus clock animations, and found everything except for the CLOCK_flight_time_meter_status.

 

A suggestion for enhanced usability:

As it is now, we have 'Pos. X', 'Pos. Y', 'Size px' and 'Rotate' for all objects. I would like to suggest to split 'Size px' into 'Whith' and 'Height', aspect ratio can still be fixed (even if there might be situation where changed ratio would be desirable). The reason is I noticed when rotating a switch for example 90 degrees, the 'Size px' can not be used for calculating exact horizontal positions relative to the RIGHT side of the panel. Or when not rotated one can not use 'Size px' to calculate exact vertical position relative BOTTOM of the panel. Now one needs to use trial and error, doable but a little bit tedious.

 

 

EDIT:

4) The Flight Time Status [DCS ID 56] for the Mi-8 also behave strange. Stranger than for the Ka-50.

 

Could I get a trk file for the KA50 and the Mi-8 with these failures? Then I'll look at it here. At the moment I'm not flying helicopter yet. That would be very helpful.

 

There is a known problem with the rotations of object and position it after that exacly.

So far, I have not found a really good solution for these usercontrols. A rotation around the center would actually be the solution. Unfortunately that does not work. Because the position and rotation is determined by the top left corner.

Edited January 29, 2018 by H-J-P

[H-J-P]

Maybe McMicha will answer as well. He built the KA-50 cockpit. We'll see.

[Holton181]

Could I get a trk file for the KA50 and the Mi-8 with these failures? Then I'll look at it here. At the moment I'm not flying helicopter yet. That would be very helpful.

 

I hope I understood you correctly now.

Attached are five tracks.

 

Ka-50/Mi-8 Clock n Mission Timer: Manipulation of the mission clock. It start inactivated with the flight time status indicator [DCS ID 75/56] as white. Pressing left button starts the timer and the status indicator turn red. Second press and the timer stops and status indicator turn half red, half white. Third press the timer is reset and inactivated, status indicator turns white again. In Ikarus this behavior is shifted for the Ka-50, inactive=red, started=divided and stopped=white. The status indicator in the Mi-8 behaves wrong but differently in Ikarus than in the Ka-50.

 

Ka-50 Abris Cursor control: Abris cursor manipulated in game.

 

Ka-50 Abris Cursor control Ikarus original values: Abris cursor manipulated in Ikarus, all values in Ikarus are as in original profile. When the cursor moves I press the same side of the knob in Ikarus. Pauses of the cursor indikates that I still continue pressing the same side for a while, i.e. cursor standing still even if I still moving the knob. When the cursor start moving again I have switched to the other side of the knob until it stops again. Switch side and it moves a bit, and so on. Always to the right or up (after pressing the center of the knob).

 

Ka-50 Abris Cursor control Ikarus Input [-1.0,1.0,0.1]: As the name states, input values for the knob in Ikarus [DCS ID 518] are slightly changed. Repetitive pressing on either side of the knob will move it away and back before it stops. Change side and the cursor move to the other side and back, and so on.

 

I also attach a picture how the Ka-50 UV-26 switch look.

Ka-50 Abris Cursor control.trk

Ka-50 Abris Cursor control Ikarus original values.trk

Ka-50 Abris Cursor control Ikarus Input [-1.0,1.0,0.1].trk

Ka-50 Clock n Mission Timer.trk

Mi-8 Clock n Mission Timer.trk

[H-J-P]

Wow, many thanks Holton181 ... I'll have a look.

[McMicha]

Hello,

 

Hotfix for the crash when saving a profile.

 

Please open the confic.xml file in a text editor and delete the pink lines so that there is only one <File> ...> </ File> entry left.

 

 

Or donload the modified file.

 

Sorry for this error...

 

CU Micha

[H-J-P]

A first look at SA342

 

[760mm]

Dear developers, for some reason you ignore my posts. I said something wrong?

I noticed some inconsistency between DCS and Ikarus in the Su-25T profile.

Namely: altimeter, pressure of the hydraulic system, SPO Bereza, bearing.

Is there a way to fix this bugs?

Edited February 4, 2018 by 760mm

[Hellcat]

Still using Ikarus with great results can't stand flying without it. Thanks again for all your work ....I've been away for a bit and was wondering if the Gazelle has been added yet? If not is it still in the works? Again thanks ......

[McMicha]

Dear developers, for some reason you ignore my posts. I said something wrong?

I noticed some inconsistency between DCS and Ikarus in the Su-25T profile.

Namely: altimeter, pressure of the hydraulic system, SPO Bereza, bearing.

Is there a way to fix this bugs?

 

Hello 760mm,

 

These are known bugs and affect all Flaming Cliffs aircraft, see here.

 

Only the mistake with the wrong course in the HSI I have to look at again. This mistake is a little strange.

 

CU Micha

Edited February 5, 2018 by McMicha

[McMicha]

Still using Ikarus with great results can't stand flying without it. Thanks again for all your work ....I've been away for a bit and was wondering if the Gazelle has been added yet? If not is it still in the works? Again thanks ......

 

Thank you.....

the Gazelle gauges are already there, but not calibrated yet.

In the next few days there will be a new version, including a Gazelle Profil.

 

CU Micha

[760mm]

Hello 760mm,

 

These are known bugs and affect all Flaming Cliffs aircraft, see here.

 

Only the mistake with the wrong course in the HSI I have to look at again. This mistake is a little strange.

 

CU Micha

Thank you! I can do some tests if it's necessary.

 

Отправлено с моего Lenovo P2a42 через Tapatalk

[Hellcat]

Thank you.....

the Gazelle gauges are already there, but not calibrated yet.

In the next few days there will be a new version, including a Gazelle Profil.

 

CU Micha

 

 

 

Sweet! ....Thanks ..you rock!

[H-J-P]

Dear developers, for some reason you ignore my posts. I said something wrong?

I noticed some inconsistency between DCS and Ikarus in the Su-25T profile.

Namely: altimeter, pressure of the hydraulic system, SPO Bereza, bearing.

Is there a way to fix this bugs?

 

@760mm

 

With a FC3 module, it's just not possible to do all that we can do for the A-10C, for example. We just don't get the necessary data. That is the problem. I'm not a fan of FC3. What McMicha is doing for you is commendable.

Edited February 5, 2018 by H-J-P

[760mm]

Thank you!

 

Отправлено с моего Lenovo P2a42 через Tapatalk

[IDFPilot]

Hi

First of all, dear developers, thank you very much!:thumbup:

I am so dissapointed, that I wasted quite a bit of time on playing with Helios, before I got to know about Ikarus... Now I am happy.

Great week for me, DCS 2.5 is out and I met Ikarus.:pilotfly:

[Fakum]

Now that I have the Harrier, maybe i will try again to see if I can get this to stay on my 2nd monitor? Maybe I can get it to work this time? I gave up 4 months ago,, sure would like to get it working.

[Holton181]

Now that I have the Harrier, maybe i will try again to see if I can get this to stay on my 2nd monitor? Maybe I can get it to work this time? I gave up 4 months ago,, sure would like to get it working.

Just in case, one of the things not really described in the instructions that I discovered by trial and error, was that the profile you want to use for a particular aircraft must:

1) have the exact same name as the default profile that comes with the install

2) be located at the same location as the default profile

I.E. either modify the default profile to the 2nd monitor or move/delete it and create a new one with the same name.

You probably know this already but I figured it wouldn't hurt to share it just in case.

Also, if Ikarus crash when you save, you probably use Windows 7 and nothing will be saved obviously, but download an earlier version as described by myself and others earlier.

[H-J-P]

Hello,

 

Hotfix for the crash when saving a profile.

 

Please open the confic.xml file in a text editor and delete the pink lines so that there is only one <File> ...> </ File> entry left.

 

 

Or donload the modified file.

 

Sorry for this error...

 

CU Micha

 

Please follow these instructions ...

Edited February 8, 2018 by H-J-P

[H-J-P]

Great Tool

 

any one made it work with the Gazelle ?

 

yes, we are there ...

 

Edited February 8, 2018 by H-J-P

[H-J-P]

Any step by step instructions for non programmers?

 

Yes, we have that now:

 

https://github.com/s-d-a/Ikarus/wiki/Documentation-in-English

[Fakum]

Sorry, I just realized this does not support the Harrier.