Simpit Software from SDA

Sully_pa:

 

On your Mainpanel:

 

Click 'Detail'

 

Pos X 1920, Pos Y 0, Width 1440 Height 900

 

Transmit

 

close cockpit/open cockpit

 

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

 

To edit locations of gauges:

 

Configuration tab:

 

Editor Mode.

 

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.

Thanks appreciate it! I'll give this a go when i get home from work ...

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.

Yeah I know. But the Mirage HSI is special and, in my point of view, doesn't work like the other HSI already present on Ikarus.

For now all I could do is animating the heading of the HSI.

Other than that I've already finished placing and animating the gauges (I wanted) of the plane.

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.

I got it going! Your explanation is what was missing ..you gave me enough info to be dangerous :) ....In order to get it on the 19" dead center and make it fit I had to go x=1920 Y=180 w=1920 H=1080. This enabled me to grab what gauges could only be partially seen and drag them in ..... I only have it set up for the Saber at the moment ....looking forward to the rest of my aircraft and to figure out how to get mdf's out to 2 touch screens .... Again thanks for the help...much appreciated

Good work, continue so!

DAC Su27

Hallo Heinz/Micha,

You know my Su27 cockpit already, and it's working90%.

Still the Annunciators for Engine start and afterburner won't lit, is this aDCS thing or are there any changes in your software to make it work? (DAC)

I see there are other instruments gauges created for Icarus, but my question is: can the English tekst on the Su27 instruments be altered in Russian?

I know my way in Adobe Illustrator maybe i can draw my own?

Greets,

Wasserfall

Hello Wasserfall,

this would of course be possible. However, there are still other cockpits at the moment. This is also more of a question to our artist Andreas. He could help you there for the first steps what I need.

Which instruments are important to you?

Hallo Heinz/Micha,

 

You know my Su27 cockpit already, and it's working90%.

Still the Annunciators for Engine start and afterburner won't lit, is this aDCS thing or are there any changes in your software to make it work? (DAC)

 

I see there are other instruments gauges created for Icarus, but my question is: can the English tekst on the Su27 instruments be altered in Russian?

I know my way in Adobe Illustrator maybe i can draw my own?

 

Greets,

 

Wasserfall

Hallo Wasserfall.

Hmmm... I missed some cyrillic Text on my SU-27 Gauges? What a shame!

To long ago - i will check this.

To provide all Vector-Parts with the correct cyrillic text, is no big deal (*).

But i'm not sure how many ours are required (Heinz) to change them. :music_whistling:

(*) I still have problems with some cyrillic letters. They are different with my Fonts. So some cyrillic letters could be the wrong one (there are a few extremely similar-looking).

I remember the Lights for the after-burner was working in the beginning of our Projekt.

Micheal found a working calculation.

But unfortunately there was an update stopping this workaround. :(

MANY things in FC3 are depending on the creativity of michael.

And on the updates from ED of course.

The Annunciators for Engine start... hmmm.. thats realy difficult i think.

THX

Tomcat

SDA

Yeah I know. But the Mirage HSI is special and, in my point of view, doesn't work like the other HSI already present on Ikarus.

For now all I could do is animating the heading of the HSI.

Other than that I've already finished placing and animating the gauges (I wanted) of the plane.

Hallo TheKenji2221,

i haven't invested many time in the Mirage-Gauges atm.

So i thought the HSI for the Mirage ist pretty the same.

Just the DME (distance) is displaye in the Gauge - and there should be

such an Gauge in our Russion-Collction (SU-25T?).

Only the display of the active HSI-Mode (Navigation / Tacan ....) is missing. And yes the flags of course.

But for now it should be possible.

PLEASE TELL ME IF I'M WRONG!

THX

Tomcat

SDA

Hallo Wasserfall.

 

Hmmm... I missed some cyrillic Text on my SU-27 Gauges? What a shame!

After a quick-check i found the missing cyrillic-Version for the Altimeter.

And I yes added a english text in the Radar-Altimeter...

Many of the Gauges didn't have text...

And most of this is already cyrillic.

Can you tell me exactly what else i have lost?

THX

Tomcat

SDA

(Do you know the cyrrilic Version of "Radar-Altimeter"? :music_whistling:

Hallo Tomcat!

Well for the whole picture i like Russian Cyrillic intrument text, but if there is no text at all on the reall instruments than i prefer that:)

In The Export Lua, the Led's for Engine start and Afterburner can be programmed in DAC, only it is not working when i launch DAC.

Could be an ED thing though.

Hallo Tomcat!

 

Well for the whole picture i like Russian Cyrillic intrument text, but if there is no text at all on the reall instruments than i prefer that:)

 

In The Export Lua, the Led's for Engine start and Afterburner can be programmed in DAC, only it is not working when i launch DAC.

Could be an ED thing though.

That is more a question to Micha. The IDs could be incorrect.

Our big problem is just, that some teams do not finish their products. This costs us a lot of time. Often they are not even documented.

Hallo Tomcat!

 

Well for the whole picture i like Russian Cyrillic intrument text, but if there is no text at all on the reall instruments than i prefer that:)

 

In The Export Lua, the Led's for Engine start and Afterburner can be programmed in DAC, only it is not working when i launch DAC.

Could be an ED thing though.

All the FC3-Modules are using one VERY simple group of IDs.

ED dosen’t provide an ID for this annunciators.

I think Michael faked an extra ID by checking the Engine-RPM as workaround for the AB-Lights.

But after one of the ED-Updates the RPM-Value changed and this workaround dosen’t work anymore. :cry:

=> I think the AB don't ignite on one exact RPM anymore... but I'm not sure.

Tomcat

SDA

Hello folks,

We have an update for Ikarus on version 1.1.0.6.

This version now includes a complete and functional Spitfire profile.

The DCS ExportScript and DAC have not changed.

The current version of Ikarus can be downloaded here.

If you still find any mistakes, please write here a bug report.

CU Micha

PS: there is already the first preparatory work on the Viggen Profile.

...

In The Export Lua, the Led's for Engine start and Afterburner can be programmed in DAC, only it is not working when i launch DAC.

Could be an ED thing though.

Hello Henry,

I will look at it again.

Unfortunately, some exports to the Flaiming Cliffs aircraft are no longer working correctly.

Among others, the warning lamps and the whole print advertisements are incorrect.

Previously, the turbine speed was up to 110%, with everything being over 100% with afterburner.

Today, the turbine speed is only 100% and I have decided that from 99.95% the afterburner lamp is lit. Otherwise there is unfortunately no special value for this.

CU Micha

Thanks for the explanation guys!

Guess i have to do without it then, but hopefully Micha has one trick upon his sleeve:)

Regards,

Henry/Wasserfall

@Tomcat/Micha

Fur was es wert ist, ich hab was fur euch nachgemessen:)

Nachbrenner zundet bei 99,9-100%

Gruss,

Henry

All the FC3-Modules are using one VERY simple group of IDs.

ED dosen’t provide an ID for this annunciators.

 

I think Michael faked an extra ID by checking the Engine-RPM as workaround for the AB-Lights.

But after one of the ED-Updates the RPM-Value changed and this workaround dosen’t work anymore. :cry:

 

=> I think the AB don't ignite on one exact RPM anymore... but I'm not sure.

 

Tomcat

SDA

That's exactly why I wanted to make the FC3 modules.

That's exactly why I wanted to make the FC3 modules.

Hallo Heinz.

YES – that’s a big problem indeed.

Much more hassle with the FC3-Modules.

And some dissatisfied users - who doesn't understand the big difference to

the other more complex and perfect modules.

=> Bad deal. :music_whistling:

MANY THX again for doing all your efforts nevertheless!

THX Heinz!!

Tomcat

SDA

Hi Guys

Just a quick note of thanks for the awesome add-on, installed and worked like a treat first time. (using it for Huey in both DCS 1.5 and DCS 2.0 beta)

Cheers

Peter

Thanks bnepethomas. Have fun!

The Viggen is almost finished. It already works for all important instruments.

The Viggen is almost finished. It already works for all important instruments.

Sounds good. Thanks for your efforts everyone involved. Please let me know if you want me to help out with beta testing again.

The first picture:

Enthusiasm is different. Let's see ....