Jarhead0331

I totally have to agree on this point, and I mean it respectfully...But I ask a direct question like, "so does this mean February is off the table?" and rather than a direct answer like, "yes" or "no" or "maybe", I get "before end of Q1 2022". Then, once I've had to assume based on the ambiguous response that February is off the table, we get something like "release is imminent..." I am hard pressed to believe that this ambiguity and mixed signalling is anything but purposeful. Why do it? I don't understand it, and on the off chance that it is careless or inadvertent, you should try to do better because you know your passionate fans are going to analyze and parse every single word. This is said with all due respect and understanding that we are technically owed nothing, but why not just be direct and consistent?

I'll take that as a "yes". Thanks.

So, like, is release by the end of February totally off the table now?

It's been awhile since any update to the open beta too, or any news. I thought I read something that said 1/14, but obviously nothing dropped. Maybe they are delaying that for the Apache EA release? If not, anybody have any news on the next OB update?

I've tried this on two different rigs and I notice the same problem on both. Clouds now look flat and there are some strange lines along the edges of the clouds. It is hard to describe, but I'm not sure how to get a good screen capture in VR. Does this sound like a known issue? Thanks.

This is absolutely NOT the reason for the drop. MSAA has always been an extremely demanding option. I have always had to fly with it off. I had MSAA off before the patch and with it still off after the patch, I'm still having reduced FPS.

My uneducated hunch is that they can’t simply ”roll back” a single feature from a patch without rolling it all back or rewriting an entirely new patch without the suspect feature. Probably a lot of work to do something as drastic as that.

I now have this issue for the first time after the last open beta update. Anybody else?

OMG. I'm April 2021...how many years before mine ships?

Any updates on where things stand on the shipping process? Have website orders begun to ship yet? Thanks.

I don't understand...my customer service experiences with HP have all been dreadful. I've been on the phone with them for 45 minutes now and been transferred to five...that's FIVE different departments trying to get this simple replacement cable. I'm presently on hold for number 6. WTF???

My God, you may be correct. I just checked and somehow parallell projection was checked on in the common setting. I unchecked it and quickly looked at the SteamVR per eye resolution and the scale appeared to be back to normal with 100% showing 5xxx x 3xxx. I'll check within DCS asap and report back.

There is your problem. Render at 1,5 is a multiplier. But it has always been set at 1.5 in the pitool and this never effected the steamVR setting like this before. The entire per eye resolution scale in steamvr has changed. The pitool render resolution of 1.5 has remained constant.

I will double check, but I don’t believe PP is enabled. Render is set 1.5 in the Pitool.

I’m currently using a Pimax 8kx. Yes. Per application is set at 36% or 3320x1664, basically per the advice of a Pimax representative. However, that is before the global per eye scale popped off the chart.

I believe 100% used to be 5898 x 2962, so it would seem that the per eye resolution is being double rendered or something. How the heck do I get it back to normal???

I have no idea what the heck happened, but my SteamVR resolution settings have entirely changed and I am not sure why. It has also impacted resolution and performance within DCS. The only thing I did before loading DCS was I swapped the OpenVR_mod.dll for the latest version of the FSR mod. I changed the two zip files from version 1.0 to 1.1. I made no changes to anything anywhere. The Steam VR per eye resolution settings are all screwed now. The scales are off the chart. 100% is now 11796 x 5924! What!? In addition, the VR view on my desktop when running DCS is now a full window, rather than just an image of one of the eyes. I tried swapping the old OpenVr.dll file back but there is no change. What the heck got borked!?! Any ideas would be appreciated because I’m at a total loss. Thanks.

I was in the same boat as you…built a new rig with a 3080 and after 60 days, I got sick of waiting for a 3080, so I switched to a 6900xt. After having 2 cards DOA, I finally got one that works and I’ve been happy. My first AMD set-up in over 20 years. My approach is totally different to some of the suggestions above. I’m using the Open VR FSR mod and have Steam VR global resolution set to 36% and per application setting set to 100%. I’ve bumped PD to 1.5 to compensate for image degradation caused by the open VR file and I get steady FPS in the 50s and 60s. I’m currently using a Pimax 8kx, but also run a G2. Processor: AMD Ryzen™ 9 5900X 3.7GHz 12-Core Motherboard: MSI B550-A PRO - ATX Memory: G.SKILL Z Trident Total 64 GB Dual Channel Memory Graphics Card:AMD Radeon™ RX 6900 XT, 16GB of dedicated GDDR6 Operating System Storage: 1TB Patriot P300 PCIe 4.0 M.2 NVMe DCS storage: WD BLACK SN850 NVMe M.2 2280 2TB PCI-Express 4.0 x4 3D NAND w/ Heatsink. CPU Liquid Cooling: CLX Quench 240 Closed Liquid Cooler Secondary Storage: 4TB 3.5in Seagate Barracuda HDD Chassis Selection: Set Eclipse P400S Mid Tower Black/Red Chassis Fans: CLX Red Ring Fan Power Supply: EVGA 850 B3 - 80+ Bronze 850W

On second thought...I'm not the best swimmer. You can just ship it. Hope it's getting close. I ordered from the website in early April. Thanks.

Hey Miles...you still in CT? I'm in Suffolk County...mind if I swim across the Sound to pick mine up? Thanks.

Wonder when we'll get Cyprus and the Marianas...

^Well, sweet baby Jesus! That's good news!

I don't think this update is going to include the Hind. Wouldn't there have been an announcement with respect to the pre-order discount ending? I would love to be wrong, but I'm just not feeling it.

Seriously...they definitely have all hands on deck for the Hornet. Would have liked to see more work on the Viper and, well, I'd be lying if I said I wasn't disappointed to see no Marianas or Hind even though I knew that was a pipe dream. Still...any update is a good update!

I think I may have discovered (and hopefully solved) the problem. I was looking through the Vaicom config options and saw the one to set a custom DCS folder path. I read further about this in the manual and saw that sometimes the registry location is incorrect. I recently transferred my DCS installation from a mechanical drive to a new SSD. So I figured, maybe the registry got borked when I did the transfer. So I set the custom path to the new drive location and loaded up. No comm menu! does this make sense? Is there anything else I should do? What about using the fix registry option? This makes me a little nervous though.