Fropa

This one is pretty simple. The wind reading on the Apache TSD is displaying the direction the wind is travelling to. This is wrong. It's supposed to be showing the pilot the direction the wind is coming from. Please fix. Thanks.

Apologies if I'm posting in the wrong place here, but I'm not sure where else to ask... how do I find my ucid? I'm exploring running my own server and got slmod, but I have no idea how to find people's ucid, so I figure I'd start with my own.

I've been trying to join the ED discord but it keeps saying "Unable to accept invite". Can you help me? Thank you.

I've been trying to join the ED discord but it keeps saying "Unable to accept invite". Does anyone know why this is? Thank you.

It does look like the wake has finally received some of the love it needs. Now it just needs to be longer and have a greater contrast with the sea, especially from a distance. Thank you ED for continuing to work on this. We are definitely heading in the right direction!

Thank you for linking this. Now that 3 months have passed since it was last brought up, I'm hoping someone from ED will have an update on ETA.

In light of the recent announced updates coming to the Supercarrier module, I'm wondering if the ED team will be improving the way the carrier's wake looks. It is quite different from how it looks in real-life carrier landing videos, and in my opinion, is one of final remaining things that is lacking visually in the carrier landing experience. Other than that, everything carrier-related is quite the thrill and I'm looking forward to upcoming updates and improvements.

Will there ever be native support in DCS for the HP Reverb G2? SteamVR crashes all the time and I'm looking for the first opportunity I can find to ditch it. Thanks.

Hey Wags. It's been a while, and I noticed there is still no native support for the HP Reverb G2 in DCS World. Will this ever happen, or is it dead? Thanks

What happened to native support for WMR users? Is it not happening?

Understood. I apologize for making that assumption.

As stated above, ED provides exceptional customer service, and I stated why, so we disagree on that point, and that is ok. You just need to remember that we all do not have the information that you probably have access to as a DCS Ground Crew member. As to your second point, I am aware of this. Having owned the A-10C Warthog module for quite some time, I've been through it, and it's really not that bad. That's because ED is excellent at communicating on a regular basis, including timely responses to issues brought up here on the forums.

Edit: FWIW, before reading the reply I wrote below, I have participated on ED's side of the early access program (as well as the public open beta program) since the Hornet came out in 2018, and I am well aware of the pitfalls of early access, and the patience required to wait out fixes. What makes this worth it is ED's emphasis on communicating issues on a REGULAR BASIS. Even if it's to say that the issue is known, a solution has not been achieved, but it is still being worked on. Unfortunately, I agree as well. Even more frustrating is the lack of any regular feedback from the Heatblur team here on this thread, even if it's to say something to the effect that the problem is still not solved, but continues to be worked on and they are reminding ED of this issue regularly. I can easily say that if Heatblur was half as good at customer service as they are at making truly great modules, the frustration level would be minimal at worst. This will definitely be the last time I purchase a Heatblur module in early access. Next time, it won't be until the module is fully released, regardless of how long that takes.

This is still happening despite an extensive changelog for the F-14 in today's patch. It would be nice if a member of the Heatblur team would comment to let us know that this issue is still getting the attention it deserves.

EDIT: Another freeze has occurred since the message below was posted. Log is attached. It looks like I was premature in saying this problem was fixed as I'm getting freezes again. I'll be attaching additional logs to this post each time I get a freeze so you guys are able to analyze the problem and see what's going on. Thank you for working diligently to address this issue in a timely manner. dcs 6-7-21.log dcs 6-16-21.log

I am happy to report that I have not had any freezes since the latest patch, so things are looking better. Thanks again for all the hard work!

Understood. Thank you very much for your response, and I'm glad that it is being looked into. You guys created an amazing product in the F-14, and I look forward to this issue being resolved.

A lot of people are having this issue, so, FWIW, I don't think ignoring it, or any other problems your paying customers bring to light, is the correct thing to do, regardless of where the issue lies. Moving on, what should we do? We've brought this up with ED, and a member of the testing team said to bring it here to the Heatblur team.

Finally got a response from a member of the Heatblur team, Cobra847... "FWIW we don't believe this to be on our side currently - hence why this has gone "ignored". Those texture asserts are errant." I'm not sure how to proceed.

Cobra, I apologize for trying to get your attention in this manner. Unfortunately, this bug thread urgently requires the attention of the Heatblur team, as it represents a game freezing issue that others and myself have been experiencing when loading into the Tomcat since the move to 2.7 (including the latest patch). My post includes a full description, system specs, and log files of each freeze as they occur. Any help in resolving this issue is greatly appreciated. Thank you.

I edited my post in the thread you said to post in with a 2nd log since it happened again. Not sure if anyone on the team has seen it yet. Thanks.

Posted. Thanks for the response!

UPDATE 5/24/21: It just happened again. 5th log is now attached. See original message below. I keep getting game freezes (not responding) whenever I hop into the Tomcat (pilot seat) in multiplayer AFTER first hopping into a different aircraft. This does NOT happen if the Tomcat is the first aircraft I hop into on multiplayer after first initializing DCS. Not sure why this keeps happening, but this problem has been consistent throughout my flying in 2.7. This includes the latest patch. Log is attached. System Specs: ASUS PRIME Z490-V ATX, ARGB Intel i9-10900K (3.70-5.2GHz) 32GB DDR4/3200MHz Dual Channel Memory GeForce RTX 2080 SUPER 8GB GDDR6 1TB Patriot Viper Gaming VP4100 Series (PCIe Gen4) NVMe M.2 SSD Windows 10 Home 64 bit Version 20H2 HP Reverb G2 HMD dcs.log dcs-5-22-21.log dcs 5-22-21-2.log dcs 5-23-21.log dcs 5-24-21.log

Ah Frederf beat me to it. Happy flying!

Thanks for all the hard work in putting this together, Chuck!!