Jump to content

yoadknux

Members
  • Posts

    26
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Did you see any ghosting in profile K? With profile J, clarity is much better compared to profile F, but ghosting is worse. I'm wondering if I should give profile K a chance.
  2. Profile J is an eye candy for sure, allows you to take down PD by 0.1-0.2 and still get good clarity (you can turn up other settings thanks to the lower PD too) but it has bad ghosting. You won't feel it if all you do is fly solo and admire the scenery, but once you start interacting with the enviorement (other planes, missiles, scrolling through MFDs etc) it becomes very noticable.
  3. I suggest your next test to be around the Cyberpunk dll ("transformer model"). It offers a huge boost to clarity even without increasing PD. Ghosting is still there though: Better than the original profile, worse than MSAA (or DLSS off).
  4. What is the optimal OS for DCS? My Win11 has been bad since 24h2, but in general this OS has been through CPU change, RAM change, GPU change... think it's time to move on. But can't decide about 10 vs 11. Any insight?
  5. This is a great thread you sure are a dedicated person. I'm kinda through with all the min maxing of the settings, I just focus on playing even at lower settings. One thing for certain though, I wish I had an x3d processor instead of my 14900k.
  6. I asked Meta to allow rollbacks. What makes you think I didnt? Whatever, this is just another absurd issue of the "sim experience" where you spend more time troubleshooting or waiting for fixes than playing
  7. This mentality is exactly why this field will never grow and remain a niche, expensive and time consuming segment in PC gaming. Imagine buying a shooter game, and the shooter game works, but one day it stops working with Logitech hardware. So the game launches but the keyboard doesn't work. Or a game that launches only with an AMD GPU and not NVIDIA GPU. A "few weeks" is a very long downtime in PC gaming, enough to make any average player move on. And the fact that there's no official acknowldgement nor a date for a fix just make this issue worse
  8. I understand that its temporary, and like I said, personally I was lucky enough to come up with a roll-back method while it was still possible, so I'm unaffected But how in the world would I recommend ANYONE to spend thousands of dollars on equipment that just becomes incompatiable for nearly a month with no date for a fix? This is NOT the "nature of PC gaming". In PC gaming there are things like driver incompatibility, in which case you can roll back. Or degraded performance. But I've never seen in my 25 years of gaming a long-term update that causes things to stop working alltogether. I'm sorry but this is unacceptable and further alienates casual players from going into sims
  9. I have a friend who wants to copy my exact same setup after seeing it in action, with the exact same DCS modules, specifically because of VR performance. After this recent bug, I really don't know what to tell him. How can I recommend anyone to spend money on a high end PC, HOTAS, DCS modules and a VR headset knowing his setup can become completely useless in the blink of an eye?
  10. Working in the software industry means you can't communicate with your users? Does the average player have to go into DCS forum -> DCS 2.9 -> Bugs and Problems -> Output and Visual bugs -> VR bugs to figure out why his game no longer launches? Two weekly newspapers were released since the bug was introduced, no mention of this giant incompatibility issue.
  11. honestly I'm surprised this wasn't patched yet, let alone acknowledged in a weekly newsletter or some way the casual player can see it. It left a really bad impression on me and on my will to continue investing in new DCS modules as well as continuing the upgrade path for VR. I'm not angry at Meta or ED, but rather about how inflexible they are towards each other: Meta for not allowing official rollbacks and ED for not releasing a hotfix. The Rift, Q2, Q3, and QPro are some of the most popular VR headsets in the world. They're essentially the Thrustmaster of VR. Imagine if one morning all the Thrustmaster devices stopped working natively with DCS, and you would need an emulator or new software to make them work with degraded performance. that would be completely unacceptable, and that's exactly what happens with the Meta headsets at the moment. I'm one of the players who was affected by this. In the end I managed to come up with a v62 rollback method that still works in my system, but many players are not as fortunate. Still, I can't help but think: I bought the most high-end PC available, invested in HOTAS and pedals, invested in a VR headset, bought modules in hundreds of dollars and I woke up to a non-working setup with no official date on when it will be fixed. That's really frustrating.
  12. I guess enabling auto-updates through the software should work, but I'm not sure. We'll wait and see
  13. I'm glad I was able to help. I'm happy to say that since I've written this post, my Meta Link App Version remains at 62, and everything works as it did before. I think outsiders don't understand how crippling this issue is. I felt completely helpless.
×
×
  • Create New...