RAZBAM_ELMO

My thoughts exactly. I will be working equally alongside bignewy and tea_cypher over the coming weeks to sort through, manage and prioritize bugs mentioned here with ED's internal tick system and adding them to RAZBAM's internal tracker for the team to see. From there it is a matter of the team looking over what are the most glaring issues and then prioritizing the most important ones or those that require minimal time to fix.

With most of our cockpit textures moving to SVG format, we are looking to update and upgrade cockpits in the future. As the majority of us don't use VR at this time and with other tasks ahead in priority this may take time to address. I like tea, do not have VR so cannot confirm it personally. The team will be made aware of this issue but again, it may be lower on the list of priority tasks at this time.

@LastRifleRound can you provide the evidence (bearing in mind rule 1.16) from where you believe this to be correct behaviour? That way we can reference our sources and SME to confirm

If anyone who is experiencing this problem can take a quick video of the sounds as well as a trk file we will investigate this.

Can you quickly check if you have the cockpit sounds volume turned down at all, try turning it to max and adjust? If the problem still persists post back here but I've been flying for a while this morning and did not notice. Ill check again tho. If that fails, try a repair and try again for me. Sent from my SM-N960F using Tapatalk

Hey guys. So to answer similar questions in one. Yes we have an internal bugtracker to help accumulate and assign bugs to. Its also split into which versions of DCS they are in, being put through the ropes by the tema and ED CB testers. I am currently forming a PoA with the team and ED Beta testers to organize what exists at this time (coordinating whats on the forums and what is internal). If after this is done and problems with organization/ efficiency still exist, then we may move to a different system. ED has their own internal BT system for themselves and adding all or a 3PD to that would just add to the confusion. Having that separation allows us to differentiate our problems and theirs. If that happens, allowing public access or public input to it would have to be decided on by the team, because right now some stuff on future projects exists within the internal tracker which I know you lot would love to see but RB does not lol. Cause it are sekrit. I hope that answers those questions, keep the ideas and suggestions flowing tho, I appreciate the calmer and more surgical approach were all taking on this issue. I may not always like you, but I will always love you( as my late grandmother put it). Sent from my SM-N960F using Tapatalk

Great to have your input guys. No I won't be looking at completely deleting the previous threads that took everyone so long. I simply received various suggestions from people and wanted to see what others thought. The post titles and suggestions were simply made to create the conversion. I love the response you guys have given and it will all be taken into account when I press forward with talking the bug threads. Sent from my SM-N960F using Tapatalk

Positive approach is my intent and I hope everyone can see it as a mediating factor. I need everyone's help to accomplish this and I think we're all ready to do so. Sent from my SM-N960F using Tapatalk

Just letting you guys know I'm going through stuff and having a look at things. This might not be a #1 priority for th team but know that I am looking into EVERy issue reported.

Thats why I want to open the discussion. I want to know where peoples thoughts on the matter are or alternatives to what exists to better help the community make sense and the team better focused. I appreciate the work and effort everyone is putting in. Many hands make light work. However I want to find a solution that doesn't have too many foremen and not enough workers if that makes sense. Ill take a look at that thread and see what I can make of it. Sent from my SM-N960F using Tapatalk

Good evening everyone Zack ( aka Elmo here. I have a question for all of you and I would like your feedback on. As many of you are aware in the forums some bugs can be pushed down the line as repetitive reports come in. This can be quite alot for devs to handle even as as Community Manger. For an easier and simpler way to go about this Id like to know if you thing that we should spend the time and go through each and every post to address or acknowledge the issues at hand, OR should we wipe clean the threads ( or archive) completely and start new after the next patch. I'd like to hear what you guys think would be easiest. Perhaps we don't and I spend hours going through and rechecking every post as needed which would take time. Perhaps we wipe whats there and have you guys resubmit old bugs or new ones from scratch so theres no denying that they are still there after the patch? Maybe we make three completely separate sections per module for new / existing bugs, solved bugs, or bugs that may not necessarily be bugs and require a more in depth response to explain why they exist. I look forward to reading your responses and have a poll up to show if people want to see change or whether we should carry on and use the system in place as is. This way you the community can work together to help us make the experience here better.

Thanks everyone. I hope that the new strategy will clear the air. Also SGT Coyle I semt you a PM if you could please get back to me when and if able. Sent from my SM-N960F using Tapatalk

I fell like timing the update and my plan to the community is better together. That way its a one stop source for how ill proceeding going forward. Sent from my SM-N960F using Tapatalk

Man keep the memes rolling I had some good laughs at breakfast. Yes my new strategy will be announced after the new OB update. I look forward to the challenge as due to my current job I'm not being paid to do this. It is simply a voluntary passion job. Everything should be addressed and anything that isnt or needs clarification in the future will be addressed. Many factors played into how previous situations were handled but were turning a new page and looking forward not back. Sent from my SM-N960F using Tapatalk

Hey guys. Yes new CM here and I will be addressing everything after the next update. So standby, hold orbitals wait for further talk on. Sent from my SM-N960F using Tapatalk

I've found Etsy to be quite easy-to-use. Alternatively you can set up an Ebay shop. Also check your email i recently send you a message regarding cougar stuff. Sent from my SM-N960F using Tapatalk

Question @Reflected , is this campaign multiplayer playable if we each have purchased it?

Hello @rel4y I sent you an email regarding parts. Sent from my SM-N960F using Tapatalk

Really loving the -19P, just wondering when the signal flares will have a key binding. Most of us flying in cold war or 70s-80s scenarios typically use these in lieu of flares.

Perfect thanks man Sent from my SM-G930W8 using Tapatalk

Where can I find my logs. I seem to have an issue and cannot solve it. Sent from my SM-G930W8 using Tapatalk

Two more weeks@tm after that No no I think it's ok where it is lol Sent from my SM-G930W8 using Tapatalk

So this 430 is available with which aircraft? Sent from my SM-G930W8 using Tapatalk

Just letting you know that I can build that model for you on commission if you'd like. Visit Instagram or Facebook ZMSC Modell Works Sent from my SM-G930W8 using Tapatalk

Is there an install tutorial for this? Sent from my SM-G930W8 using Tapatalk