Jump to content

-Rudel-

3rd Party Developers
  • Posts

    1844
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by -Rudel-

  1. Friday will be official fix.
  2. -Rudel-

    Gauge lights

    Nothing is wrong then... Friday's update will remove the dark shadows over the numbers.
  3. -Rudel-

    Gauge lights

    Look for MiG21Bis_CP_Gauges.bmp and delete that one too. There should be a MiG21Bis_CP_Gauges.DDS in its place
  4. 2.5.3.23954 - 2018 November 09 Fixed gauges from blacking out. Fixed smoothing groups on HUD glass.
  5. Please test file here https://forums.eagle.ru/showpost.php?p=3680773&postcount=9
  6. I am trying to troubleshoot with ED, but am not getting anywhere. No answers from them. This bug does not happen on my computer.
  7. As ED partner, maybe you can ask Kate or Matt for test access.
  8. 2.5.3.23788 - 2018 November 07 Fixed gauge lights. Fixed missing SPS/IAB panel texts. Adjusted suspension. Improved boundary layer blow system effects. Improved engine device code to reduce FPS stutters. Added navigation data for Persian Gulf.
  9. ED's DRM system doesn't allow us to give out keys. There is no way to bind them to a users account. :(
  10. no no no... I moved bug-ticket to 2.5.x branch.
  11. Yes yes!, many thanks, I will forward post to systems programmer! :thumbup: Great to know, thank you! We will try to communicate more here. :book:
  12. Is this for all modules you guys use?
  13. https://www.facebook.com/pg/muzeumVHTM/photos/?tab=album&album_id=1069209546424178
  14. It's actually an EFM. The webpage wasn't fixed after the new naming convention when PFM, EFM, AFM, SFM, SSM, and ASM were introduced.
  15. Many thanks! System programmer will be happy. Your English is well enough, for me to understand. I only wish I could read/write Russian for you guys. :book:
  16. The whole thing? ooof! : megalol: I think we need only the important parts to program correctly. Not whole thing.
  17. Was this test conducted just changing the planes in the mission?
  18. See notes: https://leatherneck-sim.mantishub.io/view.php?id=784
  19. I moved bugs to 2.5.x tracker : thumbup:
  20. I fixed all cockpit stencil that were reported on ED mantis. If there are more, please report on our Mantis, with screenshots and corrections. I will fix the external model too...in time. Laivynas provided corrections...many thanks!
  21. Please translate to English for our systems programmer. Many thanks. I have full SPO-10 tech manual too. 83-page PDF. Time to learn Russian language. :helpsmilie:
  22. 2.5.3.23225 - 2018 October 24 Reversed NPP localizer bar animation. Reversed Max G-load needle animation. Reimplemented vibration effects to Pitot while taxiing. Fixed hint typo on Mach test switch from 1.7 to 1.5.
  23. Dear All, In order to better accommodate both current and future project update needs, we'd like to urge all users to cease reporting bugs on the Bugs subforum (unless significant discussion is indicated) and instead help us out by registering a new account and reporting a bug on the bug tracker. This will allow us to more effectively receive bug reports from users, convey what is received and already fixed, as well as offer an insight into our post release support process. We also hope that the added transparency will better indicate how many changes are made that previously were not noted in changelogs. Bugtracker: https://leatherneck-sim.mantishub.com/ HOW TO REPORT A BUG Write an accurate and detailed report. Do not be vague, or leave simple things out. The more information that is presented, the better, as we can recreate the problem exactly as the user experienced it. Include all the steps taken to produce the bug(s). Attach Missions, TacViews tracks, and/or SARPP, dcs.log data files, and screenshots. Show real world data compared to the modules' data. Preferably in English or Serbian. Keep all the information presented in a neat, orderly easy-to-follow format. This will help us immensely in reproducing the issue and confirming it. You can also add further comments or updates on an issue after reporting it. Once a report is submitted, we will take a look at it ASAP. Please note that this bug tracker is separate from our internal one, thus issue statuses will not be accurate unless set to resolved or closed. If a bug that is reported is not seen, please add it. It's likely we are already tracking it, but better safe than sorry! Most of all; we'd like to thank all of you for taking the time to report bugs and help us build better products. Many Thanks, Leatherneck Simulations
  24. Dear All, In order to better accommodate both current and future project update needs, we'd like to urge all users to cease reporting bugs on the Bugs subforum (unless significant discussion is indicated) and instead help us out by registering a new account and reporting a bug on the bug tracker. This will allow us to more effectively receive bug reports from users, convey what is received and already fixed, as well as offer an insight into our post release support process. We also hope that the added transparency will better indicate how many changes are made that previously were not noted in changelogs. Bugtracker: https://leatherneck-sim.mantishub.com/ HOW TO REPORT A BUG Write an accurate and detailed report. Do not be vague, or leave simple things out. The more information that is presented, the better, as we can recreate the problem exactly as the user experienced it. Include all the steps taken to produce the bug(s). Attach Missions, TacViews tracks, and/or SARPP, dcs.log data files, and screenshots. Show real world data compared to the modules' data. Preferably in English or Serbian. Keep all the information presented in a neat, orderly easy-to-follow format. This will help us immensely in reproducing the issue and confirming it. You can also add further comments or updates on an issue after reporting it. Once a report is submitted, we will take a look at it ASAP. Please note that this bug tracker is separate from our internal one, thus issue statuses will not be accurate unless set to resolved or closed. If a bug that is reported is not seen, please add it. It's likely we are already tracking it, but better safe than sorry! Most of all; we'd like to thank all of you for taking the time to report bugs and help us build better products. Many Thanks, Leatherneck Simulations
      • 1
      • Like
×
×
  • Create New...