DutchCoolHand

that is an interesting setup. It seems to be able to adjusted. I currently use my son's next level racing stand combined with Foxx mounts for my TM stick and throttle. The throttle pushes my left left in and it uncomfortable and I am not aligned with the rudder pedals. see my picture. I think you might have giving me an alternative to buying an expensive 80/20 setup. I need to figure out how to integrate my Playseat and a monitor. I want to make a VR specific setup. I now have to drag everything to my desk. it takes about 15 minutes to setup and get everything connected. keep us posted!

And you get used to it. in the first week I thought the same and reduced the level. Later I increased it again. Secondly you can adjust the individual events that trigger them. I reduced the engine from 50 to 35.

Yes that has been mentioned as a problem so no placebo! I do it every time now.

there are user of this that put up a board to have the tactile feedback. I dont need it, to me this feels real. will it get better in the future? I am certain and so says Miles

I mentioned that had some link disconnections and crashes but only after one flight. Yesterday I did a mission on the Nevada map where you have to stop the tank column. Flew 20 to 30 minutes flawlessly. For my second flight I decided to reboot just to see if that would make a difference. It is did not second flight 5 minutes in the link disconnected. Although I can reconnect and DCS continues I don’t see the image. I upgraded to 461.33 as people reported it fixed their micro stutters. I hav not seen a difference. Next step, I will reboot the headset after my first flight. It is must strange how the first flight goes perfect no matter how long it is but the second one gives problems.

Can confirm it does not work yet. not Miles fault. the mouse works weird in MSFS2020

No expert, but this is what I posted yesterday in the VR Issues group. Very different settings but they work for me and I have a lower system than you.

I have been working on settings since I got the Quest 2 about 10 days ago. I was about to give up reasoning that my hardware was not enough for the Quest 2. For my Rift S it is fine. Then today I saw the video by VR Flight Sim Guy https://youtu.be/29zJa9e_rG4 He has been trying for 2 weeks for MSFS202 and made great strides. I followed his directions for MSFS2020 and saw an improvement buit MSFS2020 is hard on systems. I decided to start DCS just to see how his settings looked and I have to say I am blown away. The clarity in the cockpit is amazing compared to the Rift S. and I am getting 30+ FPS in the air which is fine for me and about 20-25 on the ground. I tried it first with the Sandy CSAR mission for the A10II and it ran fine for the duration of the mission. After that I ran the winter Instant mission on Caucuses and I had a link disconnection twice. I lowered the link bit rate to 450 from 500. But still have a disconnect. I have had 2 DCS crashes not sure why as mentioned the first mission ran fine for over 30 minutes. So I will have to tinker some more but to finally see the crew on the carrier deck completely clear was amazing. It does run at 14FPS on the deck but that is not a big problem for me as I am starting up and taxiing. As soon as I was airborne I got 30FPS. System: Ryzen 7 2700 OC 3.45 32 GB @2866mhz. 2070 @1950ms ~70% load Here are my settings: https://imgur.com/gallery/nKfPv6a Sorry I can't seem to get the images in as normal. One interesting setting Mirror FOV. I have it set to 0.70. When hovering over this setting it states that it has not effect on the image in the headset. But I do see an effect. I am blind in my left eye and decided to reduce the left FOV to 10% as it improves performance. The Q2 has a wide FOV and reducing it to 0.70 or 0.80 is fine and you don't see the edges. But when I went into DCS with the 0.10 for the left eye I only saw a small vertical bar as a result in my VR view. So it does affect it. I have to do some more testing to see how this parameter works. I will still plan on a Ryzen 5 5600x with a 3070/3080Ti or a 6900 GPU in the future but for now I can use my Quest2. Just need to figure out is causing the link disconnections. Has onyone tried the wireless link with DCS? PS I have PD in DCS at 1.5. Peter

Well I am not impressed yet. I have spent a few hours working on settings and watch videos and read pages. I think my hardware is not strong enough for the Q2. It is fine with the Rift S. Waiting for a new cpu, MB and GPU. any tips? I have increased bit rate and have been testing with resolution in the oculus settings and asw

Microcenter had Quest 2's available this morning and I got one with the link cable. I can see the image quality difference. I do get the microstutters. what can be done? and how do you set or see the data rate of the link cable?

I understand what you are saying.

Wolf it takes 5 seconds after getting into the menu for the seat to stop vibrating. I would not call this nasty.

Same here.

Hi Pride, you are correct. I saw yesterday’s video too.

Another question, how is the battery life of the Q2. Does it get power through the link cable too? Peter

That is what I did RBW and it worked. I can't fly high enough to drop the CB87/97 because of the SAM. I tasked my wingman to attack ground targets but he went straight after the SAM and died. I was trying to have him/her attack the convoys but no luck.

Hi Tazz, looking at your config file, I saw this line options.graphics.stereo_mode_use_shared_parser = true . What does it do again? I have it in mine and if I remember correctly it had something to do with VR right? I am also trying to solve the TGP white out issue. I did figure out to switch to dark hot allowed me to see the vehicles under the smoke again

that could be it, I probably come in at a too low of an angle, this causes the drop line not to go solid before getting too low. Secondly, in the mission there is a S15 on the other side of the hill so I come in lower. I will beat this mission. I think I am going to try to get the Sam first

I am flying the Sandy CSAR mission with the new A-10C II and when I want to drop a CB-87 I get an error on the HUD stating Invalid Fusing. I read Chuck's updated A-10C II and I checked the settings needed and I think I have it set correctly. But the manual does not say if it has to be nose, tail or nose/tail. I tried all three but keep getting the error. I am trying to drop them in CCIP mode. What am I missing? BTW I can drop them fine in another mission.

I get it Norbot, being flying for many years but I had not flown the A-10 for a long time. I remembered using autopilot in the past so I was looking for the keybinding as I changed sticks in the last year. I think the A-10 is one of the most HOTAS heavy planes.

Thank you, do they both work?

I have to check tonight, I am working again after a nice long holiday break. Although I can see my flightsim setup right next to me I have to be strong and wait

Thanks Norbot! Sorry I did not understood your advice.

Ok that is the name of the pinky button right? I am sorry if I was not clear. I am trying to find the autopilot function to bind the HOTAS Left Throttle button to.

I wanted to engage the autopilot yesterday but I could not remember which button to use. The manual shows the pinky button, but going into controls I can’t find the function, I went through the whole list, searched for autopilot. But no luck. what am I missing?