Jump to content

H-J-P

Members
  • Posts

    539
  • Joined

  • Last visited

Everything posted by H-J-P

  1. Go to Monitor 1 and uncheck make this to your primary. I see this checkbox in the picture.
  2. I still have an idea. Always save it with the DCS module file name. Just save the old file under a different name. That could be the understanding problem. The file with the changed name will never be loaded. Only this ensures that Ikarus loads the right module if you do it in DCS. OK. I'm flying some modules per job. This is the only way to ensure that the communication is safe. But it is not yet documented, as I currently see. Of course it was like that for us. Sorry.
  3. You can change this in Monitor Setup. Which one is my primary monitor and which one expands that. There is a checkbox. But that's not really important. It is important which position Windows determines for the X / Y position. If you arrange the monitors correctly, then it should work. I use the Ikarus panels distributed on 3 monitors without a problem. I can change that at any time. It is important to save the new configuration before loading a mission into DCS. I hope it helps something.
  4. What you get is open source and not something you have to pay for. Any help is welcome.
  5. How did you do that? And yes, you always need a panel for the switches, displays and so on.
  6. Sure, if you want it. This is not a problem. We are open source .... Any help is welcome :-)
  7. It's about understanding and not just applying it to us. That was actually our goal.
  8. Have fun
  9. Wow, I like that. Very good Terminal. Thanks, but your link points to my development version. It changes daily. That overwhelms every normal user. Please change that. Ever thank you. May we take this as a quick guide to the wiki? Is that ok for you?
  10. Please read our wiki https://github.com/s-d-a/DCS-ExportScripts/wiki
  11. H-J-P

    Ikarus for M-2000

    I think we have found someone who will identify the IDs. He has already done that for the Harrier. Too bad that it does not come from developers .. I do not like such a thing ... But we will do it for you!!! We could use a few beta testers. Who wants ... PM me!
  12. The Harrier is almost completed and currently in beta testing. I think until next week is completed. Maybe even until next Friday.
  13. I know this bug. Actually, I thought I had solved the problem. I'll look again. Thanks. I'm using only the mouse..
  14. Thank you. Maybe we can solve that. It's more a question for McMicha. FC3 modules are just unreliable.
  15. 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.
  16. Please read our wiki https://github.com/s-d-a/DCS-ExportScripts/wiki
  17. 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.
  18. 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.
  19. 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.
  20. Thank you BravoYeenk4. :thumbup:
  21. Thanks, Micha...
  22. 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.
  23. 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.
  24. Termal, many thanks. We like to read something like that. Have fun. :thumbup:
  25. Is built in but not yet tested with DCS. You can find it on Git, if you want.
×
×
  • Create New...