Lange_666

The real A-10 Stick sits on an extension, the TM one does not. Also, i'm pretty sure the real A-10 doesn't have that crappy plastic gimbals like the TM one does. So far for the "exact" copy.

Yes, it still shows OpenVR as runtime. PS: I returned my Pico 4. One needs more then a 3080Ti to run it decently at native refreshrate. ASW is just plain horrible compared to a headset with a display port + way to many artifacts caused by streaming. Not good enough for me.

Your talking about the base, not the stick on itself i guess. Yes it's that stiff (and the Cougar was even stiffer). There are options to make it lighter, like sanding and re-greasing and/or use a different spring (the green one): https://warthog-extensions-by-sahaj.com/my-products/#about-springs . There are also video's on the tube about replacing the countersprings the get less tension / friction. But that doesn't overcome the entire friction problem you might encounter. I couldn't get used to the Warthog base after using a Uber2 mod on my Cougar. I just replaced the Warthog base by a Virpil WarBRD base and put the stick onto that. It is just way way better and smoother then the Warthog.

Only happens with OpenXR as runtime.

It's all about what's available and the investment to get a decent experience. Upgraded PC late last year, all fine then my Rift-S (probably the cable) died. Wanted a new headset really bad because i like VR for flying heli's. Went for the Pico4 because of the exciting reviews and tube video's ignoring the fact that some mentioned one needed a beefy PC. Mine (AMD 5800X3D, 3080Ti, 64GB Ram) turned out to not have enough beef to run the Pico4 to get a decent experience. Only at medium quality and with a streaming rate of around 80Mb/s i was able to keep the FPS high enough to not go below native 72Hz refresh rate. And then this only on simple missions. At this setting the visual quality is even less then the Rift-S. Going higher mend using ASW which only works with Virtual Desktop (Pico's Streaming Assistant has also such an option but that doesn't work). But since the interpolation frame is generated by the headset (as i did read), for me it created way to much ghosting on medium to far distance objects (close by is just fine, don't understand why). Also moving my head quickly resulted in the image not following fast enough in the corners resulting in brief black borders on the edge of the FOV. Horrible experience. The Rift-S ASW worked 10 times better. Having a VR session in Elite Dangerous yesterday closed the door on the Pico 4. Just rolling the space craft created double stars everywhere. Just not fun. I could have kept it until the next PC upgrade but it would lay there gathering dust most of the time until then and maybe by that time some more interesting headsets could enter the scene. Until then...

Gonna put VR on hold for a while.

Pico 4 is on it's return. Not good enough, need something with a proper display port.

Event Viewer?

It ain't bad framerates. These are pretty constant. Besides, it's mostly visible at a +30° view from the frontview when the aircraft gets rolled (or to lesser extend when it's pulled up). The bigger the angle (with max at 90), the servere the ghosting is (or can be).

I have a 3080Ti. I can't run VR with no reprojection (or ASW or SSW), not even on 72Hz. In certain scenario's (low object and simpler maps) i can keep the FPS rate up just above 72Hz which is enough to run with no reprojection but it often dips below 72Hz causing stutters. Complex scenario's and more detailed maps a just a no go without reprojection. And then that's on low settings, not high ones. Since i changed from a display port connected Rift-S to a stand alone Pico 4 i see much much more artifacts and anomalies under certain conditions, looking at 45 to 90° angle and rolling the airplane results in minor or major ghosting on medium to far distance objects. The closer to the ground the bigger effect is. For me it's a deal breaker. This is with reprojection on. It doesn't happen with repro off and if the FPS stays above the refresh rate but that's hardly reachable.

The same effect is noticeable on the ingame FPS or message window. If you roll the plane with the FPS indicator visible, it will very slightly ghost and the window + text will become a bit blurry. The moment you stop the roll, it's gone (with SSW on).

I ran SA as test yesterday but the ASW setting in there doesn't do anything + i have more performance loss with SA the with VD. With SA i can't even reach 72 FPS (when the headset is set to 72Hz refresh) on my testruns turning the experience into a stuttery mess. Never been able to make any sim run stutter free in VR if not running on either native refresh or with ASW forced to always on. Putting ASW on only when FSP dropped below the native refresh of the headset always resulted in stutter, let it be the Rift-S or the Pico 4. I also see it when looking at a 30° or 45° angle but less pronounced. What bugs me is that on close by objects it doesn't happen even when looking at 90° and flying low over the terrain so when rolling, the terrain/objects move quickly, even faster then the distance objects move but on the distance objects the effect is visible + it happens only when rolling or pulling (or pushing) the stick, not on a straight flight. The moment the roll stops, the effect is gone. It's just weird but a big show stopper. I just ran another test at 72 Hz with ASW disabled and the settings turned down a bit to be sure to keep the 72FPS all the time. Then there is no such distant ghosting when rolling the airplane. So it's def an ASW thing. Need to decide what to do with it, i only have until Thursday to return it and from this afternoon until Tuesday i'm not at home.

Could be a setting then, or a combo. But i don't know what because i tried everything i know of. Went through quite some different settings again yesterday before i wrote the post. I see it with different runtimes so that ain't it.

I have this both on ST and MT and in other sims too, therefore it's not a DCS issue. I'm looking forward to the Rift-S test.

Yep that's what i mean. Looking directly in front i don't see it. I forgot to mention it's not always visible like when i start a flight, the first 30-60secs it isn't there, then it starts. It can get worse or even almost disappear some time later. In extreme cases the far away objects can all of sudden shift even a cm to re-align again. It's not a DCS problem because in IL-2 and MSFS i see it also. I can't remember i had that in the Rift-S and if it would, i'm surely would have noticed. I guess it's more a stand alone headset issue...

With ASW enabled, there is always ghosting on fast moving objects. The faster it moves, the more the ghost image lags behind the non ghost image. This is so for both the Rift-S and Pico. The effect i talk about is different. It are only object at medium to far distance that are ghosting extremely when the airplane is rolled. Once the roll stops, the ghosting stops. It's even visible when in a very slow roll. Another thing i'm having problems with is that sometimes certain textures (like different textures on 2 different parts of the terrain) start to shake. It happens on one texture but not on the second making some (small) parts of the terrain look like it's becoming liquid for a while. Moments later it's gone again. These could be compression artifacts, i don't know but it's annoying. Can't remember seeing any of these things in my Rift-S.

Virtual Desktop (in SA ASW doesn't work).

I'm on the edge of returning mine. After 3 weeks of playing around with it I'm not impressed. My biggest gripe is the ghosting with ASW on on objects starting from medium to far distance when the airplane is rolled. Pointing a wingtip to the ground and then pull the stick makes the image go by quickly and then there is no (or almost no) ghosting problem. But simply flying straight, looking out of the cockpit at an object in the medium to far distance, let it be a tree, building or a target and just pull up or roll the aircraft and all the objects just ghost and shimmer until the roll stops. And the speed of the roll doesn't have to be that quick, just a very slow roll already shows the effect. I don't understand why it is happening and I have this in DCS, MSFS and in IL-2. It's just annoying. It's there in OpenVR or OpenXR. The effect vanishes when ASW mode is disabled but then even a 72Hz refresh rate is impossible to keep up, even on my system. I'm not sure it comes from ASW because on closeby objects it doesn't happen, not when moving slow, not when moving fast. I'm open for idea's...

I'm on the edge of returning mine too. I'm not impressed. After playing around with it a lot, tried about every setting, my biggest gripe is the ghosting with ASW on on objects starting from medium to far distance when the airplane is rolled. Pointing a wingtip to the ground and then pull the stick makes the image go by quickly and then there is no (or almost no) ghosting problem. But simply flying straight, looking out of the cockpit at an object in the medium to far distance, let it be a tree, building or a target and just pull up or roll the aircraft and all the objects just ghost and shimmer until the roll stops. I have this in DCS, MSFS and in IL-2. It's just annoying. It's there in OpenVR or OpenXR. The effect vanishes when ASW mode is disabled but then even a 72Hz refresh rate is impossible to keep up, even on my system. ASW mode is simply not good enough on the Pico 4 compared to a Rift-S which i had before.

When it comes to PC's, networking and everything that comes with it is my weakest link. Little history: Old setup Rift-S VR headset with display port Old setup: - Modem/Router (Docsis 3.0) located in garage <--> ethernet cable <--> PC - Headset connected to USB 3.0 and display port New setup Pico 4 VR headset which is standalone 1st setup: - Modem/Router (Docsis 3.0) located in garage <--> ethernet cable <--> PC - Headset <--> Wifi <--> Modem/Router (Docsis 3.0) Problems: - Modem/Router to far away to get stable Wifi signal to headset. Signal mostly strong enough but lots of fluctuations. - 5 other devices share the same wifi connection. 2nd setup: - Modem/Router (Docsis 3.0) <--> ethernet cable <--> Linksys router on desk <--> ethernet cable <--> PC - Headset <--> Wifi <--> Linksys router Problems: - Wifi connection much more stable but still fluctuations in signal although wifi router allmost next to headset and even if it's the only device connected to the router. 3th setup: - Modem/Router (Docsis 3.0) <--> ethernet cable <--> Linksys router on desk <--> ethernet cable <--> PC - Headset <--> USB-C cable <--> PC In this case the linksys router isn't really needed since the needed initial wifi connection to get going can go over the modem/router in the garage. This gives a steady 1200Mhz connection. Problems: - Connection with USB-C link, need to swith on/off USB thetering, use ADB commands (through bat file), windows creates a new network each time this happens which needs to be set to private, need to turn wifi off after that, all of this is a bit clumsy. 4th setup: - Modem/Router (Docsis 3.0) <--> ethernet cable <--> Linksys router on desk <--> ethernet cable <--> PC - Headset <--> USB-C cable <--> USB-C to RJ45 adapter <--> Linksys router on desk. This latest setup is the best option so far, gives a steady 1200Mhz connection and is just plug and play. Problems: - Only little problem is that the headset isn't charged with this option. An option is a USB-C to RJ45 adapter with charging port but i did read a lot that this doesn't allways work well (charging just stops after a while) + i don't want to fix the adapter to the headset like a lot of people do because this sits in the way of my headphone. Then it got me thinking that, since i don't need the Linksys router anymore in setup 3 and 4, about replacing my router with a switch with POE capacity to keep the standalone headset charged instead of a USB-C to RJ45 adapter with extra changing port. But then yesterday i did read that hooking devices up to a switch can cause drops in data and the need for resending that data if the devices on the switch are demanding the same lines at the same time (PC and VR headset). This got me worried about data fluctuation to the headset. Question: Is it possible to change the router with a switch or will this lead to possible data disturbance like i did read a few times?

Because you can only send one keystroke at the same time, just try it with your keyboard. If you press q and w together, you get qwwwwwwwwww or wqqqqqqqqqqqqqq depending on what key you pressed first (or last). It's either q or w. With DX you can output all of them at the same time.

Correct me if i'm wrong but you still need something to get you into VR. Virtual Desktop will just put up a Virtual Desktop inside your headset. If you launch DCS from there without SteamVR or Oculus opening up, it will be in 2D.

This evening i took some time to set up the direct USB-C connection following the video (had seen that before). - Quite a bit of clicking and pointing to do before it ran but when it did, 1200Mhz connection all the time! Then took the effort to set up a connection through an ethernet cable plugged into the router and from there to an RJ45 to USB-C adapter. - This is simply the the best solution to get a wired link set up. 1200Mhz steady all the time! + (and a big + actually), the less point and click because Virtual Desktop sees this as an internet connection so no need to have it first connect through Wifi where then the Wifi can then be turned of like with the USB-C cable but just Wifi off in the Pico all together. - RJ45 to USB-C adapter in the ethernet port of the router. - USB-C into the Pico - Switch Wifi Off in the Pico. These 3 steps above need to be done only once. To play: - Start VD on PC - Start VD in the Pico - Connect to the network like you always did, works now even with Wifi on the Pico OFF. - Start SteamVR in VD (outside VD it often does not detect the Pico) and then DCS ST in OpenVR mode (best option regarding stutter so far, OpenXR in ST and OpenXR in MT give more stutter). You don’t have to download or run any external program neither on the Pico, nor on the PC. Overall a lot smoother experience then through Wifi. Next up: Replace dedicated router by a simple Gigabit switch.

Thanks for the link but Discord is just a jungle of messages for me where i just can't find my way. When somebody's says it's on Discord, i'm over and done.

Do you have a link to that video? I might give OpenComposite a go tonight. Yesterday i also had it with the Pico, DCS didn't ran smooth, terrain sometimes shows a wave effect when quickly rolling the airplane, sometimes terrible ghosting, quite some stutters when frametimes start to show little spikes etc... Not good enough. Was thinking about returning it. But then last flight all of sudden was OK. Didn't change anything settings wise but played around with the runtimes. Last one was OpenVR. So this morning i did another flight and the smoothness was gone again but still OpenVR. Don't know how this happens. Stream seems to be steady a 866Mhz... Running in MSFS isn't smooth either, lot less ghosting but also stutters (but then i had that with the Rift-S also). Then i ran IL-2 and much to my amazement it ran supersmooth (through SteamVR), back to DCS, same as before, not good. Back to IL-2, smooth again... Then decided to run a few others that i still have installed. Elite Dangerous, same as IL-2, smooth run. Same for Assetto Corsa. Back to DCS, again not good. So it's not the headset but more of a DCS thingy... (ST runs better then MT though).