Jarhead0331

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.

One more question...does VAICOM look for any files in the DCS users/saved games folder? I have a new rig and for some odd reason I have a duplicate user folder in there on the C drive. I've never seen that before. One folder is my user name and the other is my user name with the name of the desktop pc. It is that second one that is set as my DCS saved games folder.

Before I do all that, let me note this for the record. When I tried to install vaicomPro, the install file could not detect my installation of voice attack, which is the steam version. In order to get Viacom to install I had to install the free non-steam version of voice attack and then redirect the install location to my steam directory. Why was it not able to locate my voice attack install in my steam directory? Could this have something to do with my issue? also, I think once installed, I may have loaded the .vap. Before enabling plugins in settings. Could 5is have something to do with my issue? Thanks.

There is a thread about this somewhere else in the forum, but it belongs in here since its clearly a VAICOM issue. The Comm menu just keeps popping up, closing and then a few seconds later, popping up again. This problem is driving me up a God damn wall. I have tried EVERYTHING. Resetting lua, deleting export file, shutting down DCS and VA and reloading, rebooting, checking to make sure no keys or buttons are assigned to mic transmit commands, repairing DCS...nothing works, even if I disable menus in the config, it still happens!...what the hell????

This problem is driving me up a God damn wall. I have tried EVERYTHING. Resetting lua, deleting export file, shutting down DCS and VA and reloading, rebooting, checking to make sure no keys or buttons are assigned to mic transmit commands, repairing DCS...nothing works, that stupid menu pops up, then disappears, then pops up...what the hell????

Very interesting. Thanks for the insight. CLX tech support was telling me that it is surprisingly common for GPUs to be DOA. I was skeptical, but they seem to have been correct here...

Same card, different manufacturer. They are both 6900xt cards, but the old one was XFX and the new is ATI. I was surprised by the difference too.

Thanks for checking in Leg2ion. The retailer sent out a new GPU and since installing the new card, the system has been working. No green screens, no artifacts, no reboots or loss of signal. I’m not calling it a victory yet, but so far, so good. When replacing the old card with the new, I noticed the slot lock in the back of the pcie slot was missing. I don’t know if this could have been playing a role in the old card not being seated properly or not, but it is not impacting performance of the new card, which happpens to be noticeably smaller and lighter than the old. In any event, thought I’d mention it.

It is a reverb g2, so it has AC power and plugs into the gpu with a display port and a usb-c. I’ve read about possible conflicts with reverb g2 and AMD MOBOs, so this could be causing the issue too, but the symptoms of that issue seem to be different from my own, so I still think it is gpu or psu related.

OK...I am now willing to bet that this is a VR related issue. There do not seem to be any problems until I plug in my headset and run Windows Mixed Reality. I do not know if it is a GPU or a PSU issue, but it has to be one of the two and it is triggered by the VR Headset and/or WMR.