Silhou

Hey! Don't worry about the numbers. We keep track of everything in there, including suggestions, tasks, etc., etc., and that's why it seems like too much. Moreover, a lot of tracked bugs were already resolved from that list. So number here is just so both you and the dev team could easier understand what exactly is the conversation about

Hey! Tracked internally as AJS37-383. Thank you

Tracked it internally as AJS37-384 for the team to look at. Thank you!

Hey! Thank you for your reports. Tracked internally as DCSF14-491.

Hey! Thank you for your report. I tracked it internally as DCSF14-483 for the dev team to look into.

Tracked this one too as DCSF14-482. Thank you!

Hello! Thank you for your report. Tracked internally as DCSF14-481 so the dev team could investigate.

Hey everyone! We're really sorry for the lack of feedback on this thread. I've tracked the issue internally as DCSF14-475 and the dev team will look into it when able. Thank you very much for your reports!

Hey @joker62! Thank you very much for your report. I tracked it internally as DCSF14-474 for the dev tram to look into.

Hey! Thanks a lot for your report. I tracked it internally as DCSF14-473 for the team to investigate.

Hey @Linbei! We're sorry for the inconvenience that this bug still causes you and thank you very much for the heads-up on it. I just wanted to let you know that it is not ignored by us. It is tracked in the internal tracker and is being investigated by the dev team. I will for sure add your report there. We're sorry for the lack of feedback on this thread and thank you in advance for your patience and understanding

Hey @B-Omega. There was no patch, so the fix is not in yet. But it will be out soon, don't worry

Hey. It was me tracking it and tagging it for the development team then to look at, investigate and decide if bug or not. And looks like I was too fast with the 'bug' tag on this one. I'm sorry for that.

Hey @Elliot! Thank you very much for your detailed report. I tracked it internally as DCSF14-471 for the dev team to look at.

Hey, @draconus. Yep, I tracked it internally as DCSF14-470 for the team to investigate when able. Thank you!

Hey! This one is known and tracked already, but thanks for the heads-up, it's appreciated

Hey @some1! Thanks for the heads-up on this. It's a known issue and the dev team is looking into it

Hey! Thank you for your report. I tracked it internally as DCSF14-468 for the dev team to look at when able.

Hey @AliceDerg! Thank you for your report. I tracked it internally as DCSF14-466 for the team to investigate.

Hello. Thanks for the report. Tracked as DCSF14-462 internally for the team to look at when able.

Hey! Thank you very much for your report. I've tracked two issues ("Jester having difficulty to find and lock ships with LANTIRN" and "Jester overrides point track, lasing etc set by player when switching back to front seat") as DCSF14-456 and DCSF14-457 accordingly for the team to investigate.

Hey @Stain! The issue has been reported already. But I added your information to it. Thank you very much!

Hey! This one was already reported and is most likely a DCS issue. But never hurts to check again. Thank you for your report, I'll add this information to the existing one for the team to look at when able.

Hey Temetre! Thank you very much for your detailed report. I will track this internally for the team to investigate when able

Thanks for the heads-up on this!