Tweety777

Hahahaha Actually, it's my bad and some issue with the Mission Editor. After looking into it again I found that I actually had put in 2 carriers though I couldn't move the second carrier but clearly the game has no issue with having 2 units in mostly the same location.

I'd say the screenshots speak for themselves. At first the 2 copies had a bit of space between the 2 of them. Map is Marianas WWII. Just for the fun of it.miz

Hello JMax, My pedals work pretty smooth in my opinion. I didn't try any lubrication. There are 2 rails on the bottom plate under each of the pedals, so it's a double track per pedal. Mounted on the pedal or 2 sets of wheels on the outer edges of the frame holding the pedal which roll through these rails. I don't know if this is any help to you but now at least you know.

I took my pedals apart, and you were half right, 2 of the 3 wires on the potmeter had completely broken free. I soldered them back in place and now it works fine.

Except for doing what in slow motion I've done, that cannot be explained by a cut wire. In that case the response would be erratic, going all over the place and doing that continuously so, not quit registering anything whatsoever all together.

I also still run into this issue every single mission in VR (I only play in VR). At first simply reloading the mission solved the issue but now nothing has helped for months on end. I do use like 2 downloaded missions a lot which I modified as well (ACM and BFM against the F5, I changed the weather and some skins and missile loadout). All these missions have the same issue. This is my system: AMD Ryzen 5700X3D, RX7900 XTX, 48GB 27" 1440P monitor and Oculus Quest 2. WinWing Orion 2 w/ FA18 throttle, VKB Gladiator EVO w/ F14 grip, Logitech G rudder pedals, TrackIR 5, WinWing MFD (2x), WinWing UFC and Voice Attack.

Since this afternoon my Logitech rudder pedals suddenly stopped responding in DCS. Using Adjust Controls I found that it accepts 1 input full right, then sometimes very slowly does what I'm doing in multitude with the pedals and seises to input anything after that. This only applies to the rudder, the brake pedals work fine. I did a repair and I just installed the latest patch DCS and still no difference at all. What is going on? Since it is sometimes registering something I assume this is a DCS issue, not a problem in my pedals.

I share your careful approach in this, even though I can use the beneift of EU rules in this regard. I do think there is a big difference between the likes of Asus and Pimax which is why I'm willing to give the benefit of the doubt, Asus got well established, got greedy and fell for it, where as Pimax seems to be a new company which quickly appears big in a market which is still small but growing and quite possibly having had to cut corners in order to be able to offer a product compelling enough to be noticed next to popular products like the Quest series. I might well be wrong here, my only reason for even replying here is in the hope to find out what state Pimax is in because I quite frankly don't have a clue.

After reading the entire communication between Pimax and Mark I'm left wandering what is so bad about the way Pimax handles the issues. Yes, the first headset has been bricked by them, but rather then offering to fix the issue remotely they offer a replacement, where I believe it would be well possible to solve this issue through software. And then there is the replacement Crystal that doesn't work properly where they seem to forget the product is only months old rather then over a year. In Europe where I live warranty counts for when the actual product is actually received, even if this is a replacement under warranty, then the warranty date changes with the new product and also repairs come with a warranty on the repair itself. Besides this, in cases like this where solving the issue takes so long that the warranty period expires while looking for a solution then actually the warranty remains in effect because it was reported within the warranty period. When I look into this further I see no reason why there can't have been any honest mistake with regards to the warranty period on Pimax's side, because they simply didn't get the time to reply to Mark about this before Mark uploaded his video. Also, every message from Pimax ends with the note that the costumer can escalate the issue but nowhere do I see any steps in using that option. Just to be clear, in my opninion Pimax can learn from this costumer experience and things can be more costumer friendly (a happy costumer is better for business then a couple unhappy customers no matter what outcome), but I don't see a reason for the timing of this video. After having reminded Pimax of the actual warranty period of this product and the fact that the issues started within the warranty period and thus need to be solved according to being within the warranty period if Europian rules apply for Mark as well and Pimax not accepting these facts I can understand these issues. As it is right now I feel that the long delivery times for new headsets appear to be the most important reason for the frustration and this 1 reply from Pimax hitting a trigger. I can understand the frustration on Marks side and I feel that Pimax could've done more to take away the frustrated feeling but I still feel this video i a rather sever escalation and not so much a justitfied attack towards Pimax. Not taking away from the fact that Pimax does need to learn from this situation. I myself am considering upgrading from a Quest 2 to Crystal Light in the future so I'm quite curious about this situation because I cannot afford spending that amount of money on a product that causes as much issues as Mark discribes here. In my decision making proces to go buy myself a Crystal Light or search for an alternative will also be depended upon whether or not this story is, for my decision, negatively impacted but other rules regarding warranties in the USA, something I can work around by buying it localely rather then through Pimax themselves.

The Cat playing on the Kola map

Hi all, About 2 months ago I upgraded my GPU to a 7900XTX hoping that I would be able to play DCS in VR comfortably. Though it certainly got a lot better then when I used my RTX 2060 things didn't improve as much as I would have expected from a powerhouse like the 7900XTX. I know the 7900XTX can benefit from a higher PCIE then my B450's PCIE 3 but up to now it would seem that the USB speed is the most limiting factor. Therefore I just got myself a USB-C card which should be able to run at 10Gbp/s, but the Quest software indicates no more then 380Mbp/s rather then the 2,2Gbp/s straight from the rear Type-C from the motherboard. Just to be clear, I do intend to upgrade pretty much everything but the GPU, using this topic I'm hoping to put my bucks where they count the most and currently I'm completely at a loss as to what I need to do to get better performance out of my GPU. Lets summarize what I consider to be weak parts of my current rig: USB speed last rated at 2,2Gbp/s B450 motherboard (I can't seem to figure out what USB speed it can support per port. Currently I have only 1 of 7 ports empty, with 6 flight peripherals all connected to a 3.0 10 port hub and I use a USB headset Ryzen 5 5600G CPU, though this usually runs even slower percentage wise then the GPU (most of the time I can see it runs at around 40-ish% compared to the 50-ish% for the GPU) Perhaps the DDR4 memory? Given above specs, what do you guys think could be the problem? Let's also state the Quest 2 settings, graphics settings in DCS are at about the highest possible, image quality is therefore really good, going lower seemed to have very little effect. 5408x2752 (1,5x) resolution 72 Hz Quest link with original USB cable Just to be complete below the list of what I intend to upgrade to: Ryzen 7 7700 CPU Asrock B650E PG Riptide WiFi Thermalright Phantom Spirit 120 SE Corsair Vengeance 64GB (2x32) 6000MT/s, CAS latency 30, true latency 10,00ns I already have 2 2TB NVME GEN4 hard drives which will be reused in the upgraded rig Thanks for any help you can give me.

My experience with Kola on my Quest 2 powered by a 7900XTX gives me fine results at very high graphics settings, and I might add that it is stunningly beautiful to fly through though there is room for improvement outside the well detailed areas. Only problem I have is that flying my wingtip almost into the mountain at like 500knots feels almost like driving past it at say 100 knots. In terms of performance, I must start by saying that my current motherboard is not capable of fast enough USB speeds so my GPU and CPU usually run at about 50%, then I get between 36 and 72 FPS, the latter being the refreshrate of my Quest 2 during testing.

Well, I hoped the update would by here today, but I'd rather wait a few more days for a properly working update (even though the work around I found is giving mixed results, I now have a HUD but I need to restart a couple of times before it actually works) then having an update that also gives me problems. I'm thankful ED takes the time needed to come up with a really working solution even at the cost of disappointing all of us.

Well, you are not retarded, this topic is all about the 7800XT, regardless of which GPU I put into my PC. I just tested with VR in multiplayer, this wasn't playable on the RTX 2060 but now with higher graphics settings I still get above 60FPS even starting from a carrier. First attempt ended in the ocean right across the deck from where I spawned because the image in the VR froze even though my PC was rendering images at above 60FPS still. If your signature is up to date my PC will be very similar to yours in the near future, so sharing information on our VR experience would be greatly appreciated, though I have a Quest 2 and you a Quest 3.

Well, this is much better then a game that doesn't even start. I also noticed that my CPU and GPU are not even running at half power while reaching above 60FPS high in the air already. I noticed that during the stutters the game does continue in sinlge player, that never happened with my old RTX2060. Could a WiFi 5 connection be causing this problem?