H-J-P

Maybe you do not understand the technical cohesion. Go with Helios ....

I do not let myself be provoked ... who are you?

---

---

OK. I will now compile all new future versions with VS 2015. Thanks Deezle, that was a good cooperation. Unbelievable, how can something like that be ... Microsoft ...

I thought so.

I changed the development environment from VisualStudio 2015 to VisualStudio 2017 during this period. That could be a cause. But please answer my question.

Which operating system do you use? I am using Windows 10. I think you use Windows 7.

I see here no problems with 2.2. The data exchange takes place via UDP. The DCS version is not important to me as Ikarus developer. It can only be because our export script, that develops McMicha, is installed in the wrong place or you use a older version. Please check that for 2.2. It will soon be easier with DCS 2.5. Then, we will only support 2.5 for future updates from Ikarus and our export script.

Gekauft. Endlich ....

Very strange. You get the File Save dialog and then Ikarus freezes after you have pressed the Save button?

Have you a partition D: ? Try it there ...

You do not have the right to save it there. Did you get a error message from Ikarus?

That is too little information to help you. Sorry. Maybe the download was corrupt. Try again. What do you mean by different folder? Everything has to be saved in the Ikarus folder.

Change the location from the Ikarus - folder

Then you do not have the right to save it there. This is not an Ikarus problem.

2.5 is now beta? For the AV-8B I hope so. It depends on what data we get from this module. Otherwise it will be very costly for us. But let's have a look.

Which version of Ikarus do you use?

Use the 6 buttons down from the main screen.

Did you solve the problem yourself? Which version do you use?

In principle this could work. Ikarus can do this without problems. By the way, this is more of a question for McMicha and his Export - script.

I changed it now, on my side. But the error could also be in the script or in the module documentation. We'll see. Thanks Smil

:thumbup:

I'll look at it, of course. But we have a summer break now. :thumbup:

Sobe, nice it works now also for you. What was wrong? Was it the position of the second monitor?