Jarhead0331

^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.

The plot thickens...I had another crash and/or loss of signal not long after plugging in my VR headset. I don't know exactly what happened because I left the room briefly to take out the damn garbage and, of course, that is when the event occurred. Regardless, I'm thinking one of two things at this point. It either is another bad GPU, or perhaps the VR headset adds to the power draw and there is an issue with the PSU? As I said above, CLX is confident it is not the PSU, but I don't really know what to think at this point.

I'm not breaking out any cigars by a long shot, but I did a manual install of the AMD drivers through the device manager and so far the system seems to be running stable. I've watched some youtube, loaded steam and downloaded a file. Otherwise, just let the thing idle on desktop and so far so good. I still only have one monitor plugged in. Next I'm going to plug in my VR headset and see if anything changes. Then, I'll run DCS and see what happens. Why would installing the driver directly from the device manager, rather than through the radeon install program, which gives me the option to just install the driver make a difference?

For the record, I did try installing only the AMD display driver without all the bloatware. Still, no dice. Green screen of death. Very very frustrating.

I've run the DDU many times. Also, as noted above, this is an AMD card. Not Nvidia.

I don't think taking the GPU caused the problem, per se. The problem existed before I did that, but the DDU and re-install of the radeon software seemed to correct it, or at least stabilize it. Once the system is "corrupted" so to speak I can get green screen crashes, reboots, artifacting and no monitor signal at random times...even from the desktop with nothing running. Really the only time it will be stable and trouble free is if I boot it in safe mode.

I'm really not convinced this is a DCS problem, but DCS always seems to trigger it. Maybe some of you guys might have some ideas. I recently received a new build from CLX with the following specs: 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 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 Shortly after installing DCS and running it in VR, I started getting green screen crashes followed by reboots, artifacting or signal loss to all monitors. Eventually, I sent the system back to CLX and they replaced the GPU and reinstalled windows. When I received the system back, and ran DCS, the same thing happened. Green screen crashing, artifacting and sometimes signal loss. CLX had me run DDU and do a fresh install of the Radeon software. This seemed to solve the problem and everything was running great....until this week. I put in a second SSD and to do that, I had to take the GPU out. As soon as I put everything back in and went to run DCS, same damn problem. CLX insists it’s a GPU problem and they are sending me another one. When I express disbelief that two GPUs can go bad, they claim that it is an industry wide problem due to covid shortages and work restrictions. QA has been very poor and parts shortages are requiring manufacturers to source from more questionable sources, and they are seeing record numbers of bad cards as a result. They claim this is a problem with AMD and Nvidia. They had me run my card with furmark under full load and they do not believe this is a power issue. What else could it be? MOBO? Ram? I’m getting to my wits end. CLX customer support has been great, but this is getting old. I've spent more time on the phone with tech support than I have using this $3200 system.

Sorry for the stupid question, but how do you communicate with the ground crew on cold start using realistic comms? Thanks. NEVERMIND...ugh, the airbase was set to neutral. Sorry for taking up space.

I've been giving some love to the FC3 aircraft just for a more relaxing change of pace and I've been running through some great training missions for the F-15C. I can't help but notice that the needles on the analog RPM indicators appear to be backward. In other words, when I apply throttle, the nozzles and RPM readouts get smaller toward zero, rather than getting higher. Is this a known bug or is it something in my setup? Thanks.

Looks great, although the Viper guys are going to be pissed!

So I got my Jet Pad about a month ago, almost to the day, and it just inexplicably died a few days ago. I thought maybe it was a loose or bad connection between the EU plug and the US adapter I was using, but I just ordered a few more and the unit is still non-responsive. It is not detected by Windows, or the Simshaker software and the green light on the hand controller is out. I've checked all the connections and they are tight. I've tried different electrical outlets and different USB ports. Nothing. Andre...I emailed you to discuss my options. This is pretty frustrating. Thanks.

Just got my Simshaker Jetpad today. Seems to work great in game...and I'm embarrassed to mention this...but the massage function doesn't seem to work. When I press on the START button, nothing happens. It is obviously more important that it works in game, but I just want to make sure I've configured it properly and I'm not doing something wrong. Thanks.

Thanks for the feedback.... I designated the 01 - 12 keys as F1 - F12 in the Synapse software and it works in DCS. I didn't even need to configure them within DCS since it seems to be just emulating the keyboard function keys which are already set in DCS. I also designated the scroll wheel for typical mouse functionality, ie. scroll up and scroll down. It also worked in DCS without having to make any changes to the control settings. Is this how it should done, or is there some other way to configure the Razer keys directly within DCS?