Polychop Simulations

We'll look in to this report but what MPalmer said is correct. When you switch to IR, make sure it has cooled for at least 3 minutes. Having an all white screen sounds like the IR system wasn't cooled yet.

Dear community, With the end of the year fast approaching and still a lot of work to do, we have come to a point where we have to accept that a 2020 release of the OH-58D Kiowa Warrior module is no longer feasible. We want to release a module that we feel is feature complete, mission ready and a true tribute to the men and women in army aviation. That is not to say no extra’s will be added later on. Even though we’ve been crunching the past months, we simply aren’t there yet. We can imagine this is a disappointment to all who look forward to the OH-58D Kiowa Warrior module and we hope to make up for this with the polished release the module deserves. We’ll be working hard to get you the OH-58D Kiowa Warrior module as soon as possible.

Will try to replicate this today. I'm on paternity leave though so I'm not around as often as I'd like / used to. Will let you know whether I can confirm this as a bug and what the follow up steps will be.

We were able to replicate the issue and had ED developers look in to the cause. They suggested a method of fixing this issue which will be tested this week. The bug was introduced with the implementation of rain drops. If the suggested method does not work we can disable raindrops (by temporarily removing the needed geometry in the 3d model) until we fix this. Thanks for reporting!

Sitrep 11-04-2020 4th of November OB patch. In the OB patch released today the following fixes are included: Fixed RWR symbology Fixed TV targeting symbology Fixed laser rangefinder symbology All mentioned systems should now be functioning as they should again. Further work is being done together with ED on getting rid of some graphical bugs that appear on the glass surfaces of the Gazelle in certain light conditions. ED developers are analyzing the model and textures at this moment. NS430 integration Even though we finished integration for the NS430 module quite some time ago, the actual Gazelle specific NS430 module has only recently moved on to the testing phase by ED's internal testers. This is due to the fact we had to create a new testing build of the whole module to support this process. We hope now that the NS430 is in the actual testing phase, ED can release the module very soon. Slow progress I'd like to apologize for the slow progress over the past 2 months. For me a lot has changed in my personal life. I transferred to a different unit in a new function and I have been blessed with the birth of my daughter. It has taken me some time to adjust to both these life changing events and find the correct balance. Rest assured though that things will speed up especially after the release of the Kiowa when the whole team can and will spend time on bringing the Gazelle up to the level where we want it to be.

Yeah it's being tested by ED internally. We can't wait for it to be released either, it's been a long time since we integrated support for it. :)

Screenshot of the week

Hi Japo32, this is most likely caused by a mod (vehicles or objects) that use the same texture name as the one for the ADF radio glass. Simply removing the mod or the mod's texture will fix it. Try running DCS without any mods and see if the issue still persists.

The RWR bug, along with the laser range finder and viviane symbology have been fixed internally and the fix should be available in the next patch.

Hi Big-Foot, When it comes to multicrew we're eagerly awaiting the multicrew implementation for the UH-1 by ED. If this new method proves to be stable and working we will look in to adapting this method for the Gazelle. It makes little sense to reinvent the wheel when ED is working on this feature as well. We hope it won't take much longer. As for a bug tracker, we do not have a public version of this. Instead we use these forums and discord to take note of the bugs reported by the community and another internal system where bugs get reported and tracked by ED's internal testers. When a bug is posted on these forums we try to post and acknowledge the issue in the very same thread. This is something we can improve by maybe editing the title of the thread with an assigned status like [Fixed internally], [Verified] etc.

Screenshot of the week

No problem Donglr! Files /fixes have been submitted and should be merged with the upcoming regularly scheduled patch ASAP.

Hi Adam, We'll announce a timeframe when we reach the final stretch and a release date when we are certain of one. We'll be doing more videos, posts and streams in which we'll certainly mention the state of development once the flight model is completed.

No problem Tugais, we have a short line of communication with the author of SRS and we can always make suggestions. When it comes to multicrew we're eagerly awaiting the introduction of multicrew for the UH-1 by ED. From the way they implement it we can work out a way to improve the deteriorated state the Gazelle multicrew is in now.

Screenshot of the week

Hi Crash and CHPL, I'm trying to reproduce the bug but I have a hard time doing so. I probably know why this is happening though, it has to do with the compression format of the texture. Still, in order to verify my fix works I need to reproduce the bug unless you are willing to test the newly compressed textures. Could you send me a screenshot of your graphics settings, a track file or a miz file? Even better if you could contact me on the Polychop discord channel so we can troubleshoot in real time, but I'd understand if you prefer not to.

I don't want to go in to the way things work behind the scenes as that is covered by an NDA. But what you have to understand is that there are many phases before a patch release. At some point submissions for an upcoming patch have to be closed down so everything can be compiled, tested and made ready for release. For planned patch releases these timeframes and deadlines are clear. For hotfixes not so much, they are pretty much ad-hoc and you're either lucky you make the deadline or you miss it, they are simply not planned. When we talk about patches, you can pretty much assume we mean the regularly planned patches for Open Beta, I can imagine that wasn't very clear before.

Hi Hunter_5E, We do not usually post about setbacks like this but this one in particular was and is more serious than you might anticipate. The fact that we have identified the issue and found a solution with ED's help, it still requires several days to implement the adjustments to the code. For the Gazelle 8 lines of code were affected by this change of the SDK and we were able to fix this within minutes after identifying what was causing the issue and the method of fixing it. For the Kiowa, with 2 multifunction displays a radio screen, many pages and subpages, the amount of code that has to be adjusted runs up into thousands of lines and many days of work. That on top of the time the development was halted brings us close to 2 weeks of development time in which there has been no progress. While we still aim at a 2020 release, setbacks that take 2 weeks are quite a big deal. I made a promise for us to be more transparent towards the community and letting you guys know about issues like these make sense to me.

Screenshot of the week

Gazelle symbology bugs have been resolved internally. That means the fix for the RWR and TV screen read outs (laser range finder, camera deviation and heading) will be in the next patch. Sorry for the inconvenience, it took us by surprise as well. We took this as an opportunity to streamline communication between ED and Polychop to prevent such things from happening in the future. While no guarantees can be given that nothing will ever unexpectedly break again, we feel we've made some serious progress in establishing more efficient and direct lines of communication. ED has been of great help and assistance in solving the issue and we thank everyone involved for that. When it comes to the Kiowa Warrior, the same methods that have solved the symbology issues on the Gazelle will have to be applied. Due to the sheer amount of on screen data and symbology displayed on the MFD's and radio panel, implementing the fix will take up to a few days after which the normal development process will resume.