Jump to content

H-J-P

Members
  • Posts

    539
  • Joined

  • Last visited

Everything posted by H-J-P

  1. @JAT thanks for the bug report. I'll have a look. Please keep in mind that this module is not finished yet. There may still be various errors. Please report them all. :thumbup: What I can improve here, I will do.
  2. @Sobe, change the X position to 1920 so that the Ikarus cockpit appears on the right monitor. Then it should work. Did you mean that?
  3. Sorry, this assumption is wrong ...
  4. Upload Version 1.4.5.3h Development Build. Graphics for RWR FA-18 and M-2000C
  5. Did you read our wiki? https://github.com/s-d-a/Ikarus/wiki Of course, this is possible if a panel is mounted over both monitors. Usually you do not do it that way. First monitor for DSC. Second monitor for Ikarus. Just move the panels to the second monitor. How to do that is in the wiki. This is very fast and it is easy to set.
  6. Ahh now I understand. For example, the RWR screen content can not be mapped via a network. That's so. Somebody would have to develop software.
  7. @JAT Yes that is normal. There are various forums that deal with how this works. I do not have a good link right now. Can anyone help here?
  8. @Guppy If you use your own xml file, then you have to change it yourself. The effort is low and fast. Do you have the right version? I use notepad++ for something like that.
  9. @Sobe 4. The rings on the RWR do not show up. I don't know if this is a graphics issue with DCS or Ikanus. This is pure graphics. I have to paint it.:smoke:
  10. Version 1.4.5.3h upload done.
  11. I found the problem. The DeviceID for DcsID 140 -148 should be 34. This is defined in the file "FA-18C_hornet.xml". I have corrected this. Upload follows afterwards.
  12. I use Photoshop with layers for the positions or Affinity .....
  13. No question. We get that. Just give me some time. Step by Step .... So you build a cockpit. Looks good. Go on ....
  14. Thanks for the bug report. I take it for granted. Please keep in mind that the F / A-18 does not even have beta status. It will take a while until everything works.
  15. I think I'm done with the displays now. Thank you Micha. That was fast ... :pilotfly:
  16. Both sizes are o.k. So when switching only the different PNG files are made visible or invisible. Nothing more. Which graphic tool do you use? Do you use the same DPI per png?
  17. Interesting. Sorry, I do not change sizes while switching. That could be an optical illusion. The base size is given by the png - files. The size change is done via scaling. What size in pixels do your png files have?
  18. No, that's not just a picture. The two needles are animatable. However, the IDs are not yet documented.
  19. I forgot one thing. The notation in the Input field is for example: FF9430, 11BBFF12, FF808080. It also works without specifying the alpha channel. The separator is the comma character.
  20. I finished it with version 1.4.5.3g. ARGB for Font, Background and Border. Have fun with it. Thank you for the praise. Yes, I also need more time for the graphics than for the configuration. That looks very good with you. Keep me up to date.
  21. It gets a little more elaborate because I have to remain compatibel with the other cockpits. One more thing. WPF uses ARGB.
  22. my problem is just to keep comform with the existing cockpits. That's the challenges.
  23. I'll check. Which bottons do not work? You have to give more details, please. Which version of Ikarus do you use?
  24. Would that help you? About a third parameter, I still think ....
  25. Unfortunately, that can not be changed from the outside. This is determined by design. For the black background, I could imagine a second parameter.
×
×
  • Create New...