Jump to content

Cobra847

3rd Party Developers
  • Posts

    3547
  • Joined

  • Last visited

  • Days Won

    26

Everything posted by Cobra847

  1. checking; apologies if it still does not work
  2. Of note for the future is to not use the OpenXR framework currently. It is causing some sort of issue and can leave to a halving of VR FPS. Thanks!
  3. Your crash logs seem to indicate some sort of memory allocation issue, which is odd. Does this happen on all maps?
  4. And does this happen every time now?
  5. Thanks, we'll think about if about how we can solve these massive transient forces in Multicrew when there's a lagspike
  6. Does this happen if you kill another type of jet? E.g. F-15E or F-14?
  7. This is based size; so yes, in perfect conditions and a very large aircraft he can spot it at the max range. Are you finding this with smaller aircraft currently?
  8. This feature is coming. Altitudes too.
  9. We're hotfixing a few issues in the radar that cause a massive drop in very very busy scenarios, as found on ECW. Hopefully a hotfix will be available soon.
  10. First, we'll ship our hotfix which should improve radar CPU performance impact - then we will circle back and try to find these hotspots for everyone.
  11. We had some testers using a 7700k and it ran fairly well; so there's something else at play here. Also; can you try turning on the "Reduced Tickrates" option in the special options?
  12. Will upload flacs or wavs somewhere, dw.
  13. Logs logs logs, please! Will help a lot. Thank you so much! The reason I ask is that the stack above seems very odd (it indicates a crash in something that would be very very surprising)
  14. You never know in a coffee fueled development cycle I will check it again, as I was worried I had it wrong, but then checked against windsocks and was confident everything was working correctly.
  15. Thanks for the report! Can you check the windsock whether this error is also present with that? I thought I double and triple checked that they match.
  16. Can very likely confirm this is a bug; fix in progress. Thanks again for reporting!
  17. Thanks for the report - will definitely take a look
  18. Thanks for all the crashlogs, we're looking at them Can I ask you to potentially send in more crash logs? It will be very difficult to find this otherwise; as the logs above are not supremely helpful and I wonder if its just one thing or several causing this.
  19. Thank you! This will help.
  20. Thanks, this is odd as this system should be kicking in fully. We'll take a look!
  21. Thank you, will fix. This was an optimization but it seems the bounding box is not calculated perfectly on VR.
  22. Thank you for the report!
×
×
  • Create New...