darek

Thank you for your reply, I really appreciate this.

Hey, your work on the roadmap is amazing BTW. I went through it yesterday and if ED would add some dates (even with quarterly resolution) that would be exactly what I was looking for. That would be a thing that would mean a lot for impatient hot-heads like me. I simply wait for the engine overhaul since circa 2016 The additional performance drop was very visible around beta builds from 2017/2018 - before that I got a mission with 50 WW2 warbirds furballing in 2 teams on the sky. Great perception training After the changes everything was down to 5 fps from 60 fps.

Fair enough, let's bury the hatchet

First of all. My rant is because I care. And I really love this game. First wrong assumption you made: I'm not a new user. Second one: what are your actual qualifications, so that you think you can asses my proficiency in software projects management? I'm in this business for 25 years, don't be rude.

I just hope that ED focuses on finishing multi-threading engine first and deploy it to production ASAP. Next VR as more and more users are using it (no turning back after you took a flight in VR) and it still falls behind competing product performance-wise. IMHO Vulcan could really wait for the next iteration of the engine. DCS is shinny enough now, it just crawls like a snail.

Thank you for posting this. Looks like this was missed from weekly newsletters as I don't recall anything like this and I'm waiting for this info impatiently as you can see as frustration took over Still no dates nor release milestones declaration, though. Info looks good any way and implementation details look promising.

Dear ED, It's very, very disappointing... Buying several modules, learning F/A-18 and F-16 in some smaller missions to be battle-ready you launch some of the more complex official available missions, with more enemies. And you got glitch after glitch in the same parts of these missions. I got a real-deal rig with 3080Ti, 100 GB of RAM, 12 cores and it's hardly utilized during these glitches. There are hundreds of similar opinions all over the Internet... It looks like your engine is extremely inefficient and gets blocked by some parts of the simulation. How much fun do you think it is to fly the 2vs2 missions over and over again when there are really polished ones with plenty of targets. Why, instead of producing yet-another module ED won't focus on the BASE of the game and only then build on top of it? More and more people migrate to the new IL-2 which in terms of fluency and hardware utilization does circles around DCS... I was always a big fan of DCS, but after all these years of stagnation and unfulfilled promises of delivering engine optimizations I have enough. DCS adds "bling" and new modules whereas the base of the simulation is still ridiculously inefficient for users who have already invested money and trusted in your platform and promises. I saw the roadmap. But it looks like the communication around multi-threading and Vulcan is non-existing. Is it even happening? Any tech-demos? What's the FTE allocation of your team to this comparing to rest of the features? What's the roadmap and milestones for these improvements? When will this happen? I literally stop playing DCS last year waiting for something to happen, to prevent frustration from spoiling my love to this game.

@BIGNEWY do you think someone from the DCS VR dev team could take a peek at this and provide some feedback? I would really appreciate that... That might help people with neck issues or those who due to different issues cannot play in 90-degrees sited position.

zhukov032186, FYI subject of my post might by a little bit off, as I'm not considering it a DCS bug but rather a field for a nice improvement. Simple floor-height orientation setup would not address this. The whole "forward" projection vector needs to be tilted, by offsetting gyro readout. From the DCS engine point of view, I think this could be handled via the before-mentioned configurable tilt angle applied to the projection pipeline. Are you part of the DCS development team so that your negative answer is based on actual deep technical knowledge of the engine? If not, I would really appreciate the get some feedback from the dev team

Hi, today, when you fly in a reclined position with Oculus (e.g. sitting on a recliner chair etc) you cannot force center of view to be in front of your eyes - you have to lean heavy forward to see the cockpit. It looks like the "center VR view" allows only for horizontal re-orientation on Oculus, not vertical. According to this thread: this works properly on Oddyssey+, but not on Oculus.

So i guess that has to be addressed on an DCS engione level. I wonder what's the best way to push such a feature request to the DEV team...

Nope, I tried and it functions similarly to Oculus' settings default behaviour - it adjusts horizontal direction only. What I want is to adjust vertical tilt as well - so that I can tilt on my chair backwards and still have cockpit centered in front of my eyes.

Hi, I'm using a slightly tilted/reclined chair for comfort - the problem is that when I rest my head comfortably my view-port is aiming in the sky and to see the cockpit instruments I have to tilt my head down significantly thus straining it uncomfortably. Is there any way to force the center of view to be tilted slightly backwards? "Reset the viewport" in oculus menu solves misalignment in horizontal axis and it looks like gyro input are taking precedence over any viewport settings. Looks like only offsetting the gyros by some angle would help... Any idea?

That was it. Slider "got" assigned to it and was affecting radar elevation. Thanks for spotting it, it was in front of my eyes yet too many things to learn still :)

Hi, please see attached both screenshot and the trk file. Somehow I cannot make a better screenshot using PrtScn, but the yellow range numbers on the slew cursor on the radar strangely show "-99" and "-99" (in both RWS and TWS modes). 2 bars should be enough as bandits are almost on the same altitude as I am, but switching to 4B did not fix anything anyway... NOTE: the same problem appears in the latest stable DCS version as well, so this is not only beta-specific... radarBVRProblem2.trk