Simpit Software from SDA

Termal, many thanks. We like to read something like that. Have fun. :thumbup:

Hello Regnad517,

 

our DCS ExportScript cannot export screens like MFCD or RWR and transfer them via network.

That would be the best solution. Sorry, that that is not possible. :( I would support that immediately.

I do not currently see any network support with UltraMFCD on their homepage.

So I have noticed a bit of a lag as flight goes on so I am curious about putting Ikarus on a LAN machine and running it from its own dedicated computer. I am curious though as to how to export the RWR and MFCD viewports I will need for the A10C?

I have an idea there. If you have more than two CPU cores using DCS, then it should be possible to run Ikarus on a different core. Go in that direction. Ikarus only needs the CPU.

That would be the best solution. Sorry, that that is not possible. :( I would support that immediately.

 

I do not currently see any network support with UltraMFCD on their homepage.

This was once written in their thread.....

How would this UltraMFCD work in vr?

How would this UltraMFCD work in vr?

Why would you as a VR user want to export something to a another monitor? Not trying to be rude, just curious. Perhaps I misunderstood your question.

It would be really awesome with an updated version of UltraMFCD with support for more modules and a network client. Having both Ikarus and that on a second PC would be great.

I also want to say that your software and the support of it is great, even with some limits in documentation and functionality. What it can do it does in a good way. Loved Ikarus since day one and I have never looked back (i.e Helios) :thumbup:

Hello,

we have made some optimizations and bugfixes on our software again.

DCS ExportScript

• Troubleshooting in connection with the F-86 Sabre and Multiplayer
  
• Added help function for UTF-8 text editing
  
• Ka-50: Ekran Text export is now UTF-8 compatible, so the Russian text is also displayed correctly
  
• A-10C: CDU Display has new ID (2030 to 2039)
  
• UH-1H: small bugs fixed (thanks to Vulpes for the detailed bug descriptions)
  
• UH-1H: new ID added: VHF_ARC_134 Frequency ID 2003, UHF_ARC_51 Frequency ID 2000, VHF_ARC_131 Frequency ID 2002, Flare Digits ID 2005, Chaff Digits ID 2006
  
• all files set to version 1.0.1
  

Ikarus

• Change to version 1.2.3.1n
  
• some optimizations and bugfixes at the buttons and rotarys
  
• UTF-8 data processing, e.g. Ka-50 Ekran display
  
• A10-C CDU display equipped with the new ID
  
• Bugfixes in the UH-1H XML file
  
• SA342L/M/Mistral profiles added
  
• F-5E profile and gauges reworked (thanks to danvac for the help)
  
• several profiles reworked
  

DAC

• Bugfixes in the UH-1H XML file
  

The ExportScript is compatible to DCS World Version 1.5.8 and 2.5.0.

CU Micha

Thanks, Micha...

Thank you BravoYeenk4. :thumbup:

Maybe I was mistaken in its use the youtube seemed to be using a single display and for of the lack of correct terminology they would pop out an gauge (weather display like mfd or rwr gauge size to desired size us it then return it to standard size the pull up the lt and rt mfd and car console use them return to norm etc. I was thinking that having the gauges enlarged that are the most important to you at that time would be great also being able to move it where it is in your preriffial view in a size where you can quickly tell the reading would be greate but if it’s just a flat panel tool so be it but being able to build your custom hud display in vr would be great.

Maybe I was mistaken in its use the youtube seemed to be using a single display and for of the lack of correct terminology they would pop out an gauge (weather display like mfd or rwr gauge size to desired size us it then return it to standard size the pull up the lt and rt mfd and car console use them return to norm etc. I was thinking that having the gauges enlarged that are the most important to you at that time would be great also being able to move it where it is in your preriffial view in a size where you can quickly tell the reading would be greate but if it’s just a flat panel tool so be it but being able to build your custom hud display in vr would be great.

I understand you. Sorry, Ikarus don't support VR. But we have thought about it before. That would be something new and then I need a VR - equipment. But it is doable. It would be a beautiful, pretty small project.

I will not implement that in the near future. I think it will not work well with DCS. Use VR or Ikarus. Either ... or. It does not really make much sense for me either.

So I have noticed a bit of a lag as flight goes on so I am curious about putting Ikarus on a LAN machine and running it from its own dedicated computer. I am curious though as to how to export the RWR and MFCD viewports I will need for the A10C?

I do not see a perfomance problem here with Ikarus 1.2.3.1n and DCS 2.5 or 1.5.8. Everything works smoothly.

I am a bit confused with this software, but it could be that I have zero experience exporting displays from/in DCS.

Let me explain my setup. I have 1x 34" curved monitor and 3x 8" displays. I would like to have one display have the F-15c Radar, one to have F-15c RWR and finally one to have the ADI.

I understand operating the software itself, that is, I get how to add and insert various displays. However, where I am getting hung up is the pre-setup that I am assuming that needs to occur.

For example: I'm instructed to download both "Ikarus-master" and "DCS-ExportScripts-Maser". What do I do with these export scripts, specifically in the "DCS-ExportScripts-Master"? There is no documentation, that I can find, that explains what to do with these other than to download them. Should I be copying and pasting these into a particular place in my DCS folder?

I might be looking in an incorrect place, but right now I'm really lost.

I am a bit confused with this software, but it could be that I have zero experience exporting displays from/in DCS.

 

Let me explain my setup. I have 1x 34" curved monitor and 3x 8" displays. I would like to have one display have the F-15c Radar, one to have F-15c RWR and finally one to have the ADI.

 

I understand operating the software itself, that is, I get how to add and insert various displays. However, where I am getting hung up is the pre-setup that I am assuming that needs to occur.

 

For example: I'm instructed to download both "Ikarus-master" and "DCS-ExportScripts-Maser". What do I do with these export scripts, specifically in the "DCS-ExportScripts-Master"? There is no documentation, that I can find, that explains what to do with these other than to download them. Should I be copying and pasting these into a particular place in my DCS folder?

 

I might be looking in an incorrect place, but right now I'm really lost.

Please read our wiki https://github.com/s-d-a/DCS-ExportScripts/wiki

As far as I know, exporting these displays to the F-15 is not possible because it is an FC3 module. However, I do not really know that because I never tried it. Good luck.

Hi guys,

I think I have encountered a bug - I am running 1.2.3.1r (released yesterday) and it was also evident in 1.2.3.1n.

I have a second touchscreen, where I export the MFCD's and have an Ikarus front panel with the OSB buttons.

The issue comes where, if I click with the mouse - or touch the screen with a quick, brief "on", the OSB does not properly register, the text for the MFCD OSB button gets a persistent purple box, and eventually the MFCD says "STUCK KEY" in big yellow letters.

I then need to mash on the stuck button to eventually unstick it.

Its an ugly screenshot, its the default, original install of Ikarus, with the panel on the main screen. Not using the touchscreen at all.

Here you can see MSG and ACK buttons in the stuck state:

I cannot replicate this using the DCS Clickable Cockpit. I can mash those OSB buttons, only using the Ikarus Panel do the buttons stick.

Normal behavior is when you see an Ikarus button depress, the clickable cockpit button is pulsed as well.

When an OSB button sticks - the Ikarus button is seen to depress, but the clickable cockpit does not - but the onscreen text will get a purple box.

Seems like a timing issue - where, with Ikarus, you can generate a short enough "momentary on" to confuse DCS.

Its a bit harder to replicate with the mouse - I have to try hard to make very short mouse clicks. My touchscreen however seems to love making short clicks, which is what has lead me down this path.

Have you guys seen any similar issues like this?

SPO-15

First off, great job SDA! The Ikarus project is just brilliant.

About the RWR in Russian FC3 craft- I understand that the offset is a known issue, as in the attached picture. Realistically, is this going to be resolved any time soon? Is there anything we can modify after install to get it to work?

First off, great job SDA! The Ikarus project is just brilliant.

About the RWR in Russian FC3 craft- I understand that the offset is a known issue, as in the attached picture. Realistically, is this going to be resolved any time soon? Is there anything we can modify after install to get it to work?

Thank you. Maybe we can solve that. It's more a question for McMicha. FC3 modules are just unreliable.

Hi guys,

 

I think I have encountered a bug - I am running 1.2.3.1r (released yesterday) and it was also evident in 1.2.3.1n.

 

I have a second touchscreen, where I export the MFCD's and have an Ikarus front panel with the OSB buttons.

 

The issue comes where, if I click with the mouse - or touch the screen with a quick, brief "on", the OSB does not properly register, the text for the MFCD OSB button gets a persistent purple box, and eventually the MFCD says "STUCK KEY" in big yellow letters.

 

I then need to mash on the stuck button to eventually unstick it.

 

Its an ugly screenshot, its the default, original install of Ikarus, with the panel on the main screen. Not using the touchscreen at all.

 

Here you can see MSG and ACK buttons in the stuck state:

[ATTACH]182183[/ATTACH]

 

I cannot replicate this using the DCS Clickable Cockpit. I can mash those OSB buttons, only using the Ikarus Panel do the buttons stick.

 

Normal behavior is when you see an Ikarus button depress, the clickable cockpit button is pulsed as well.

 

When an OSB button sticks - the Ikarus button is seen to depress, but the clickable cockpit does not - but the onscreen text will get a purple box.

 

Seems like a timing issue - where, with Ikarus, you can generate a short enough "momentary on" to confuse DCS.

 

Its a bit harder to replicate with the mouse - I have to try hard to make very short mouse clicks. My touchscreen however seems to love making short clicks, which is what has lead me down this path.

 

Have you guys seen any similar issues like this?

I know this bug. Actually, I thought I had solved the problem. I'll look again. Thanks. I'm using only the mouse..

Is built in but not yet tested with DCS. You can find it on Git, if you want.

Tested this weekend. Works perfectly. Thanks for your work.

Hello, is the Harrier still in the works? If so, any timelines? Thank you kindly sir.

The Harrier is almost completed and currently in beta testing. I think until next week is completed. Maybe even until next Friday.

Oh WOW! Thats better than I expected. cant wait, thanks

Im new to Ikarus, been using Helios. I went to the link on page 1 and it is a bit confusing to me as the statement on page 1 states to download Ikarus and the export file, but there a load of individual files on that same download page : https://github.com/s-d-a/Ikarus.

 

I have been reading all over this thread but I dont see any installation guidelines? I seem the readme.md file on that page but nothing really caught my eye as instruction guideline. any direction would be appreciated, thanks

The export script package is divided two major areas, the program logic and the module-specific logic. The scripts "Config.lua" and "ExportScript.lua" under the path "%USERPROFILE%\Saved Games\DCS\Scripts\DCS-ExportScript"

C:\Users\<USER>\Saved Games\DCS\Scripts\DCS-ExportScript\

and the scripts "Tools.lua" and "genericRadio.lua" in the local folder "lib" are responsible for all the control and logic of the data export. The module-specific scripts are in the folder "Export Modules" in the path "%USERPROFILE%\Saved Games\DCS\Scripts\DCS-ExportScript\ExportsModules"

C:\Users\<USER>\Saved Games\DCS\Scripts\DCS-ExportScript\ExportsModules\

In the "Config.lua" file the basic settings are made.

 

also:

Installation:

 

 

• Please download Ikarus and unzip it.
  
• Download DCS-Exportscript from there:
  

https://github.com/s-d-a/DCS-ExportScripts

Copy the script folder to your folder:

C:\Users\YourUsername\Saved Games\DCS

After that, start Ikarus and DCS and have fun ....

Guys, forgive me for referencing these old posts but I too am having trouble getting Ikarus to work and although I have searched this thread for 'manual' and 'instructions' I cannot find anything to help me get this running. I am running it on a spare monitor on the same PC/graphics card. I can open Ikarus, load cockpits (I am trying to get the Spitfire working as the first one and very nice it looks) but when I load it, show the cockpit and start DCS the instruments do not respond when I load a flight, e.g. Instant Action Spitfire Free Flight.

I am actually quite PC savvy but I am not familiar with Ikarus specifics. What I need is a simple full set of instructions on installation and setup. The OP instructions don't help me. For example:

"Copy the script folder to your folder:

C:\Users\YourUsername\Saved Games\DCS"

What 'script' folder?

Also sobe you mentioned:

"The module-specific scripts are in the folder "Export Modules" in the path "%USERPROFILE%\Saved Games\DCS\Scripts\DCS-ExportScript\ExportsModules" " But that folder isn't there, it's actually buried lower down which is obviously the result of development but I'm not sure what I am to do with that information. I suspect you are giving some helpful insight into Ikarus but I don't need to do anything there.

My point is that how to use Ikarus is unclear to we lay-dweebs.

Back to:

"Copy the script folder to your folder:

C:\Users\YourUsername\Saved Games\DCS"

In the OP download link there is no top folder named 'script'. There is one named 'DCS-ExportsScripts-master' and one below that named 'Scripts'. Am I to use the latter or am I to rename the former to 'DCS-ExportScript' which is a folder that is mentioned in a few random posts and I can see and in an image of the Ikarus 'Control Panel'?

I chose to rename the 'DCS-ExportsScripts-master' to 'DCS-ExportScript' but the instruments still don't respond.

I found an image in a post that shows how to change the IP address in the CP and I have tried both the original on (127....) and the IP address of my PC on the network. I have been careful to save the profile when changing IP and then reloading it. No joy, the instruments still do not respond. (and I now forget what the original 127 address was :( )

I don't know if I am to open the the Ports in my router or if they are default open ports.

I don't know if I am to load Ikarus first (I think so) and then start DCS.

I don't know if I can switch cockpits without restarting DCS.

Guys I can see that some people have asked for a short set of step by step foolproof instructions. Some may have been a bit rude about it and have been flamed for being ungrateful and not working it out. Well, I hope I'm not being rude but I can't work it out and what is the point of giving us this excellent utility if we don't know how to use it? Not everyone is as PC savvy or intuitive as some others here and we could really use some help. A decent set of instructions in the OP would make all the difference.

Is anyone out there able to help?