Simpit Software from SDA

[H-J-P]

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

 

That's a little too early. But I can already tell you that we are working on it.

[H-J-P]

I think you have no idea how many hours it takes to implement a cockpit.

 

Especially if not the necessary data is delivered, as now for the Harrier.

 

I only do it, because I want to fly that part.

Edited February 8, 2018 by H-J-P

[Fakum]

Sorry , I was not being critical. I do have an idea of how long it takes, and I am one of many who are truly grateful. Please do not misunderstand, I was apologizing because I simply thought it was already supported, then I simply realized it was not. My bad

[H-J-P]

Sorry , I was not being critical. I do have an idea of how long it takes, and I am one of many who are truly grateful. Please do not misunderstand, I was apologizing because I simply thought it was already supported, then I simply realized it was not. My bad

 

No problem. But I just had to say it.

[Fakum]

Its a misinterpretation,,, probably just the language barrier. If you look back in these posts, I have been a big supporter of your work when the bashers have come in here running off at the mouth.

[vvm13]

Thank you very much for your amazing program.

I would like to ask you for two things.

 

1. Show the coordinates of the mouse cursor in edit mode. This makes it easier to determine the coordinates of viewports for things like ABRIS and Shkval for further editing of lua scripts.

 

2. Take account for Unicode in EKRAN string (Ka-50). It has problems with original (Russian) language now.

[H-J-P]

Its a misinterpretation,,, probably just the language barrier. If you look back in these posts, I have been a big supporter of your work when the bashers have come in here running off at the mouth.

 

Thanks for your support. Please test Ikarus, only this way it will be even better than it already is. Thanks to you all.

[H-J-P]

Thank you very much for your amazing program.

I would like to ask you for two things.

 

1. Show the coordinates of the mouse cursor in edit mode. This makes it easier to determine the coordinates of viewports for things like ABRIS and Shkval for further editing of lua scripts.

 

2. Take account for Unicode in EKRAN string (Ka-50). It has problems with original (Russian) language now.

 

To 1.) I could certainly do something. Good idea, by the way ....

 

To 2.) That is something for McMicha ... let's see ....

[vvm13]

Big thanks.

 

I think Unicode must be supported in .exe-side. I think your export.lua sends utf-8 string from EKRAN to Ikarus.exe. My experiments with my custom export.lua show that thing. Because nature of utf-8 you can't see he problem because you use latin characters.

[H-J-P]

I'm just looking at it quickly .. yes that could actually be. Do you have a solution for C#?

[H-J-P]

I have not thought about that yet. Tomorrow more. That should be really easy.

[vvm13]

Do you have a solution for C#?

I am sorry. I have no experience with C#.

 

In Java this is like

String ekranMessage = new String(byteArrayFromExportLua, "UTF8");

[McMicha]

...

2. Take account for Unicode in EKRAN string (Ka-50). It has problems with original (Russian) language now.

 

Due to the limitation of the fonts there can be problems with special characters and NOT latin writing system (eg Cyrillic).

 

For example:

Display7Segment with Digital-7 Font.

 

MonitorDotMatrix with LED Board-7 Font.

 

But I'll check again if there are any problems with the export.....

 

CU Micha

[vvm13]

I see from your links that LED Board 7 supports Cyrillic ;-)

[H-J-P]

I think it's up to my listener. I'll change that to UTF8.

[H-J-P]

After changing the listener all profiles seem to work. That is already as expected. McMicha can you test the Ekran please?

[H-J-P]

Thank you very much for your amazing program.

I would like to ask you for two things.

 

1. Show the coordinates of the mouse cursor in edit mode. This makes it easier to determine the coordinates of viewports for things like ABRIS and Shkval for further editing of lua scripts.

 

2. Take account for Unicode in EKRAN string (Ka-50). It has problems with original (Russian) language now.

 

With the next update you get it all :thumbup:

[vvm13]

Thank you!

[McMicha]

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.

 

 

Hello Holton181,

 

Points 1 and 2.

The errors with the switches and Rotary are common bugs.

We are currently working on a solution to this problem.

 

Point 3.

Unfortunately, I cannot correct the error.

The game supplies three different values for the display, but each time the assignment between the value and the display changes.

 

CU Micha

[Holton181]

Points 1 and 2.

Thanks!

Point 3.

Okay, strange. It's not possible just to have the panel start with the indicator as white instead of red? For me the behavior of the indicator is consistent, if it would stat as white it would be all fine for the Ka-50.

The Mi-8 should work the same way, but has different symptoms, would most likely not work only with the correction suggested, if that would work at all for the Ka-50 that is.

[H-J-P]

Please kindly. You do not even know how much free time we spend to give it to you.

Edited February 16, 2018 by H-J-P

[Vulpes]

Hi HJP,

I retired Helios and am now using your great tool. I have also been in contact with McMicha in the German thread.

One helpful function would be to duplicate records. So instead of adding a new record and having to enter all the information, duplicating a record would take all the information from an existing one except maybe the function. This would make it easier and faster to add similar switches.

 

Just an idea.

Keep up the good work and thank you for your efforts!

 

Vulpes

[H-J-P]

Hi HJP,

I retired Helios and am now using your great tool. I have also been in contact with McMicha in the German thread.

One helpful function would be to duplicate records. So instead of adding a new record and having to enter all the information, duplicating a record would take all the information from an existing one except maybe the function. This would make it easier and faster to add similar switches.

 

Just an idea.

Keep up the good work and thank you for your efforts!

 

Vulpes

 

Yes, I've thought about that before. But how often do you really bump that? That's why I've put that back at the moment. If I look back, I might have missed it 3 times. It works without it.

[H-J-P]

It would be nice to have, but it is not really necessary. But I have it on my list.:thumbup:

Edited February 20, 2018 by H-J-P

[H-J-P]

Hi HJP,

I retired Helios and am now using your great tool. I have also been in contact with McMicha in the German thread.

One helpful function would be to duplicate records. So instead of adding a new record and having to enter all the information, duplicating a record would take all the information from an existing one except maybe the function. This would make it easier and faster to add similar switches.

 

Just an idea.

Keep up the good work and thank you for your efforts!

 

Vulpes

 

I just thought it over again. Where does it make sense from your point of view?