Jump to content

Raven (Elysian Angel)

Members
  • Posts

    2433
  • Joined

  • Last visited

Everything posted by Raven (Elysian Angel)

  1. There have been several official announcements about the shaders working on both Vulkan and DX11. Is that purely to ensure backwards compatibility then? For example, from the 2023&beyond newsletter:
  2. T.Flight? Did you double-check the throttles are configured correctly in your DCS settings: go to "axis settings" and double click the axis you want to check.
  3. Yup I encountered campaign missions that were set in Winter, and snow reduces my framerate to sub-20. Not exactly pleasant in VR...
  4. It's not unheard of for a 3rd party to develop something that makes it into DCS's core - if Heatblur can do it with RWR libraries then RAZBAM should be able/allowed to for IFF
  5. Did you check your axes to see if some other device is perhaps causing constant yaw input? Are your pedals properly centred?
  6. Perhaps not in 2D, but for VR it will be a game changer simply because the game engine will no longer be required to render every frame from scratch twice: it will be able to skip a few steps for the 2nd “eye”, if that makes sense. Say if it can skip 50% of the render steps taken, instead of 100% for 1 eye + 100% for the other it would be 100% + 50%. That’s already a very substantial boost right there. Also, MT should work quite a bit better with Vulkan than it does with DX11, especially when it comes to scaling on large core count CPUs.
  7. That is probably the plan, but since Vulkan and DX11 are going to co-exist for at least a while (same as currently MT and ST co-existing) we don't know how ED is going to implement things - at least initially. But it's safe to say if you want to run ST, Vulkan won't be available as MT is a prerequisite.
  8. Yes obviously but as stated earlier even default ED missions have that issue, and that is up to ED to fix.
  9. Not me, mine works just fine. Try re-installing graphics card drivers and perhaps WMR?
  10. Yup: deserves a BUMP. It seems whomever at ED last saved this mission, used a livery we don't have access to.
  11. Give it a a hug from me, and tell it is just constructive criticism because I am very well aware of the deep lurking potential I’d love a full-fidelity Su-25!
  12. Yup I’ve hit 8.6g in a dogfight - I only noticed after it was over - and 9.7g during a high-altitude 180 degree turn at M1.4.
  13. You’re probably right, and you’d need a pressure suit as well at that altitude to prevent your blood from boiling
  14. When I ran my test to damage the undercarriage on purpose, it was the right main gear that was damaged. The left was fine.
  15. My cheap attempt (I don't really know anything about RL climb profiles which might get used for proper altitude records):
  16. I haven't flown the F-16 since the patch, but you can see the reflections in the video posted in this thread:
  17. Yes I don't like it either. I'm hoping for Vulkan to bring enough headroom to do something about that. But as far as I understand MSAA is an extremely outdated technology since it was designed for games that primarily use geometry for their graphical fidelity, instead of more advanced post-processing techniques. People have been bugging ED about replacing MSAA by a better post-process AA method ever since DCS 2.5 came out, because MSAA is incompatible with deferred shading. I'd suggest playing around with Pixel Density instead, or upping the render scale in your headset's software.
  18. To be fair, in a real aircraft you probably wouldn't be able to hear your own engine - only the Environmental Control System.
  19. Fair enough. I assumed there would be a library of pre-rendered reflections, and then they would show in your cockpit depending on the circumstances... I'm happy to be wrong, and even more happy that they don't seem to have a noticeable performance impact!
×
×
  • Create New...