Jump to content

Silhou

3rd Party Developers
  • Posts

    165
  • Joined

  • Last visited

Everything posted by Silhou

  1. Hey! Thank you for your report. I tracked it internally as DCSF14-528 for the team to look into
  2. Hey @MRSHADO @Kondor77! Thank you for the additional details. I'll add them to the report.
  3. Hey! Thank you for your report. I tracked it internally as DCSF14-523 for the team to look into.
  4. Hey @Fisherman82! Thank you for your report. I tracked it internally as AJS37-399 for the team to look into when able.
  5. Hey! Sure I'll track it internally as a suggestion, thank you!
  6. Hey @Ghost79! Thank you for your report. Tracked internally as AJS37-398 for the team to investigate.
  7. Hey! Thank you very much for your report. I'll reopen the issue for the team to look into it and add your data there.
  8. Hey! Thank you for your suggestion. I tracked it for the team to look into.
  9. Hey @Dannyvandelft! Thank you for your report. I tracked it internally as DCSF14-516 for the team to investigate.
  10. Hey @Bunzy! Thank you very much for your report. Our apologies for the inconvenience. I want to assure you that the problem is tracked (DCSF14-503) and the team is looking into it. Our apologies once again and thank you for the heads-up.
  11. It is tracked internally as DCSF14-413 already. Thank you for the heads-up!
  12. Hey @nikoel. I'll check in with the team about it. But if it were implemented, you would see it in the changelog. So the problem is probably still being investigated. Thank you for the heads-up and sorry for the inconvenience
  13. Hey! Thank you for your report. I tracked it internally as DCSF14-512 for the team to look into.
  14. Hey! I tracked it internally as DCSF14-511 for the team to look into. Thank you!
  15. Hey! Thank you for the heads up. I tracked it internally for the team to look into.
  16. Hey! Thank you for the heads-up. This one is known and tracked already
  17. Hey @TOViper! Thank you very much for bringing it to my attention. I tracked it for the team to look at
  18. Hey @TOViper! I don't see it tracked. But now it is. Tracked it internally as AJS37-386. Thank you!
  19. Hey @cyber79! Thank you for your report. It is already tracked and the team is investigating.
  20. Hey! Thank you for your report. Tracked internally as DCSF14-505 for the team to look at.
  21. Hey @MBot! Thank you very much for your report. I tracked it internally as AJS37-385 for the team to look at when able.
  22. Hey @Swiss-Sim! Thank you for contacting us. We would kindly ask you to forward your problem to the HF8 directly. They will likely be able to help you with the issue
  23. Hey! It is already tracked internally, but thanks a lot for the heads-up
×
×
  • Create New...