Simpit Software from SDA

[Guppy]

Hello -

 

On the Display7Segment for the hornet... the box that they always populate in is black with a light grey border. Is there a way to change this color/image? I cannot seem to find where it is located to change that setting.

 

Thanks.

[H-J-P]

The color of the sigments are changeable. In the Instrumentfunction tab, in the Inputs field, defines this color in hex (for example, ABF9AB) for displays.

[Guppy]

The color of the sigments are changeable. In the Instrumentfunction tab, in the Inputs field, defines this color in hex (for example, ABF9AB) for displays.

 

I mean the where the 7Segment sits in. I see the hex color, where you can change it. I’m talking about the actual box/frame which is black with a light grey border. I can’t figure out how to change that.

[H-J-P]

Unfortunately, that can not be changed from the outside. This is determined by design. For the black background, I could imagine a second parameter.

[H-J-P]

Would that help you? About a third parameter, I still think ....

Edited August 13, 2018 by H-J-P

[Guppy]

Yeah it would be super helpful to be able to change the following:

1) text color (already have)

2) border of box color

3) box fill color

 

I think there is a border color but I’m not at home to look (#2 above).

 

Also randomly testing thing this AM and I noticed buttons on the hornet aren’t working. That is when I push them in IKARUS they aren’t translating to DCS. Lamps work perfectly though.

[H-J-P]

I'll check.

 

Which bottons do not work? You have to give more details, please.

 

Which version of Ikarus do you use?

Edited August 13, 2018 by H-J-P

[H-J-P]

my problem is just to keep comform with the existing cockpits. That's the challenges.

[Guppy]

Sorry - none of the UFC buttons or the DDIs were working... I'm going to give it a shot and try again. They don't register in the sim.

 

v1.4.5.3e

[Guppy]

I had IKARUS/DAC set as false to send data. Whoops. Fixed!

Edited August 14, 2018 by Guppy

[McMicha]

@H-J-P:

this can be implemented as it is now with the text color.

If a value is specified, then it is used, otherwise the default value is used.

 

Example: Input: ABF9AB;BBFF12;BEF547

 

The first value is the text color, the second the background color and the third the border color.

If only two values are specified, the frame color has the default value.

 

And it would be even better if besides 6-digit hex code for the color also an 8-digit hex code with alpha channel is supported, i.e. besides RGB also RGBA.

 

Then 000000 would be black and 00000000 transparent or 00000088 black semi-transparent.

 

Transparent background and frame color would be very interesting in any case, but also a transparency setting for the text color would be good.

 

 

Edit: XAML also knows the alpha channel, but this is given first: ARGB

Edited August 14, 2018 by McMicha

[Guppy]

@H-J-P:

this can be implemented as it is now with the text color.

If a value is specified, then it is used, otherwise the default value is used.

 

Example: Input: ABF9AB;BBFF12;BEF547

 

The first value is the text color, the second the background color and the third the border color.

If only two values are specified, the frame color has the default value.

 

And it would be even better if besides 6-digit hex code for the color also an 8-digit hex code with alpha channel is supported, i.e. besides RGB also RGBA.

 

Then 000000 would be black and 00000000 transparent or 00000088 black semi-transparent.

 

Transparent background and frame color would be very interesting in any case, but also a transparency setting for the text color would be good.

 

 

Edit: XAML also knows the alpha channel, but this is given first: ARGB

 

I support transparent backgrounds!

[Guppy]

Worked on the UFC a bit this AM. Using this tool is quite easy. Most of my time is spent making the images and figuring out coordinates. very much love it!

 

 

[H-J-P]

It gets a little more elaborate because I have to remain compatibel with the other cockpits. One more thing. WPF uses ARGB.

Edited August 14, 2018 by H-J-P

[H-J-P]

I finished it with version 1.4.5.3g. ARGB for Font, Background and Border. Have fun with it. Thank you for the praise.

 

Yes, I also need more time for the graphics than for the configuration. That looks very good with you. Keep me up to date.

Edited August 14, 2018 by H-J-P

[H-J-P]

I forgot one thing. The notation in the Input field is for example: FF9430, 11BBFF12, FF808080. It also works without specifying the alpha channel. The separator is the comma character.

Edited August 14, 2018 by H-J-P

[Guppy]

Got it - thanks.

 

Also, in the Hornet Module in Instruments there is an FA18C_Engine as class. I cannot figure out what this does. It seems like its just an image.

[H-J-P]

No, that's not just a picture. The two needles are animatable. However, the IDs are not yet documented.

[Guppy]

I think I found a bug in Ikarus on the following switch:

SwitchOnOffOn

 

The off position, in this case, mid. Is increasing the pixel size. wwhen selecting the Up/Down in resizes to the correct pixel count. I have the size set to 80. Here's a screen shot of each - any ideas? I've validated that each image is the same size.

 

[Guppy]

I got it to work! FUN!

 

@H-J-P:

this can be implemented as it is now with the text color.

If a value is specified, then it is used, otherwise the default value is used.

 

Example: Input: ABF9AB;BBFF12;BEF547

 

The first value is the text color, the second the background color and the third the border color.

If only two values are specified, the frame color has the default value.

 

And it would be even better if besides 6-digit hex code for the color also an 8-digit hex code with alpha channel is supported, i.e. besides RGB also RGBA.

 

Then 000000 would be black and 00000000 transparent or 00000088 black semi-transparent.

 

Transparent background and frame color would be very interesting in any case, but also a transparency setting for the text color would be good.

 

 

Edit: XAML also knows the alpha channel, but this is given first: ARGB

Edited August 15, 2018 by Guppy

[Guppy]

Here's an update!

 

 

[H-J-P]

Interesting. Sorry, I do not change sizes while switching. That could be an optical illusion. The base size is given by the png - files. The size change is done via scaling.

 

 

What size in pixels do your png files have?

[Guppy]

Interesting. Sorry, I do not change sizes while switching. That could be an optical illusion. The base size is given by the png - files. The size change is done via scaling.

 

 

What size in pixels do your png files have?

 

So the original size, that I had issues with, was 80x209 and i set the size to 60 in Ikarus. I then upped it to 112x313, which is the file size you use, and there is minimal size change, but it still occurs...i size it to 60 in Ikarus.

[H-J-P]

Both sizes are o.k. So when switching only the different PNG files are made visible or invisible. Nothing more.

 

Which graphic tool do you use?

Do you use the same DPI per png?

Edited August 15, 2018 by H-J-P

[Guppy]

I found 3 bugs going through this:

1) HUD DAY/night Switch is linked to master arm

2) ALT BARO/RDR switch is mapped to Right Inner button

3) ATT INS/auto/STBY mapped to right outer button