Simpit Software from SDA

[lesthegrngo]

fantastic, I'll take a look and hopefully it will all be self explanatory

 

Cheers for the fast response!

 

Les

[H-J-P]

Thank you Smil. I just uploaded the latest version. You need a complete update. A lot has changed since 2017.

[JG14_Smil]

LOL,

 

I have the latest version. Only using 2017 as an example.

 

Best wishes, :)

[H-J-P]

:thumbup: Thanks

[H-J-P]

Welcome Les.

[raymondabel]

v *.474 using A-10c profile is stable on MP an SP

 

many thanks !!

Raab

[H-J-P]

Who wants the F-16C in Ikarus?

Edited May 26, 2019 by H-J-P

[BULLITT83]

Hello

 

First thanks a lot for your job, i love IKARUS , myy F18 home made cockpit is strongly improved thanks to IKARUS.

 

Do you have some news about the F14 project for IKARUS ? what will be available ?

 

Best regards

[Marcq]

Who wants the A-16C in Ikarus?

 

What is the A-16C ?

 

Marc..

[H-J-P]

F-16C. Sorry ... :smartass: I guess I'm very A-10C minded. I bought it. Let's just have a look. I think the F-16C is just a must have.

 

@Bullitt83: It will be difficult to implement the F-14. But let's look deeper, perhaps later.

Edited May 26, 2019 by H-J-P

[H-J-P]

If no one wants the F-16C, I'll just put them on for myself.

[Guppy]

HJP - what makes the F-14 difficult to implement? I figured it would be no different than any other module (which I'm sure is difficult)? I've been patiently waiting for the IKARUS F14 :)

[H-J-P]

It is always difficult if e.g. in the clickabledata.lua or in the mainpanel_init.lua definitions are missing. On the F-14 these are missing in the mainpanel_init.lua for the whole Gauges.

Edited May 29, 2019 by H-J-P

[H-J-P]

It is always bad for us if we start too early, because many things change later. The status of the F-14 isn't even beta yet.

 

But we're already preparing the possible. Like the graphics for the gauges.

 

However, you will only see it when the status of the F-14 changes to "beta". Sorry ...

Edited May 29, 2019 by H-J-P

[harvesthunt]

Brand new to DCS and sims, but I AM a builder and often though of building a cockpit. Seeing this just blows my mind!!! I noticed in your github that you had an AV-8B harrier png file. Does this mean that the Harrier is supported as well?

[JG14_Smil]

Yes, it looks like the Harrier is supported... I don't have it to test.

 

Just noticed the release with L-39 fixes. Thanks H-J-P. Hope to test it sometime soon.

[harvesthunt]

Thanks JG14_Smil. The harrier does seem to work. I ALMOST have this working now. I have the instruments exported to a touch screen laptop (not the MFCD's though), center panel on large curved screen, and TRYING to get the MFCD's to work on the main screen.

 

The MFCD's only seem to show up when I'm outside the cockpit with the F2 Key. As soon as I go back into cockpit with F1 the screen goes black.

 

I'm slightly baffled. I have to admit though that I may be enjoying setting up the monitors even more that the flying. Ok....maybe not, but it is fun.

[JG14_Smil]

Hello,

 

Not familiar with that plane at all, but I think the viewports you mention are controlled by DCS and not Ikarus. There are old threads that explain what is happening (I have forgotten it all).

 

good luck.

[AndyPeacock]

Hi, I've just started to look at Ikarus as part of a small main panel I'm putting together and wanted to say how brilliant it has been so far. The way the gauges are build seems pretty intuitive and I've started to build my own gauges for the FA18C, starting with the ODU and scratchpad using the correct style of 16 and 7 segment displays. It's been amazingly straight forward to add these in and getting them working.

 

One question I have is the Ikarus seems to always set the size of a gauge by supplying a width in the config and the height is auto calculated. Is there any way to set the height instead and have the width auto calculate? I can't see anything in the code for this, but it would allow me to better size my ODU, scratchpad and radio outputs if I can set the height for these gauges rather than width. I hope that makes sense.

 

Here is a quick preview of my ODU output (I hadn't added support for all characters when this was taken).

 

 

Thanks again for the great work.

[JG14_Smil]

I ran into this also... Good point, Andy.

 

I reduced how the poor fit looked by using a background color to hide the mismatched size. Hope it helps.

Edited June 18, 2019 by JG14_Smil

[harvesthunt]

Outstanding. This was indeed discussed in another thead:

 

https://forums.eagle.ru/showthread.php?t=223962&highlight=viewport+works+cockpit

 

I needed to bind toggle views!!! One happy camper today

[harvesthunt]

If no one wants the F-16C, I'll just put them on for myself.

 

I'm with you for F-16. Simply love the viper. Enjoying your Harrier currently !!!!!

Edited June 20, 2019 by harvesthunt

[harvesthunt]

AV-8B

Receives info from DCS, updates gauges etc fine.

Sending key clicks TO DCS does not seem to be working though.

 

My guess is it's something I've done wrong, but unsure. Would you please test on your end and let me know if you have positive results.

 

My Ikarus cockpit is on networked touch screen laptop. Neither touch or mouse click appears to send.

[H-J-P]

It is important that you have copied the ExportScript to the correct place and that you enter the IP of your notebook correctly in the ExportScript.lua. The same is true for Ikarus. There you have to enter the IP of your PC. Don't forget to save.

 

Did it work locally on a PC? If this is so, then the export script is already in the right place.

[H-J-P]

Just send some pictures with the configurations you made. Thank you.