One think I've found in the past and forgot to mention is that calling up or getting rid of things using ctrl+F1 only works for me if I've set my win10 keyboard as a US keyboard.
This normally happens if you accidentally press ctrl+F1 or ctrl+F2. Try pressing either one of these to make the command lines disappear.
Personally I skip all dual rates and just apply Expo to all my controller surfaces with advanced controller settings. Applying 30% expo is about equal to 50% rates around centre stick but still allows full travel at full stick positions.
Your ws2000 dongle only supports 8 channels so you may need to make some changes in your dx6 Tx in order to honour some switches/axsis commands. Maybe have a look/google ws2000 setups with Realflight RC sim. These should be similar to what you may need to do with RC8.
I use a usb Spektrum Interlink dx controller with my win10 pc and this works very well with rc8. Not sure if it would work with a mac or not though. I have used a ws1000 dongle (older version of ws2000 but no real difference) in the past with my dx18 tx but found this a pita to setup and use.
Only these two advices : better install Runtime Windows Mixed Reality OpenXR and when starting in Steam don't choose Oculus, works better with "normal" AFS2 VR mode :
I'm just questioning you recommending that Windows Mixed Reality OpenVR be installed for Aerofly FS2. You do not need this with any VR headset and you do not need to use the WMR OpenXR with an Oculus headset. With the current v32 Oculus desktop app you just need to select OpenVR default on settings/beta tab. The only sim that currently utilises OpenXR is MSFS2020 and turning this on does not seem to have any effect with any of my other flight/racing sims.
The fact that there appears to be 3x versions of OpenVR also makes this a bit confusing right now; WMR OpenXR, Oculus OpenXR, and SteamVR (which is OpenXR compliant). Maybe it's use will become clearer in the future when more apps use OpenXR.
Anyway, no big deal. Maybe I'm just missing something that got lost in the translation, lol!
Windows Mixed Reality OpenXR does nothing with the Oculus Quest 2. That's only applicable to WMR headsets like the HP G2. with msfs2020. I agree that starting up in SteamVR mode is still the way to go if you want to use Vulkan rendering.
There should not be too many differences (refer to the aerofly website) but it seems that Steam versions tend to get updates a bit quicker. You may want to contact aerofly and see if you can transfer over to Steam. They may provide you with a Steam key to do this.
Thanks, must be a problem with my setup then. For some reason it still isn't working. I still get excellent performance without using Vulcan though so it's not exactly the end of the world.
I actually just tried this out again today and for some reason(s) FS2 Vulkan is not working again with my Q2 using Link or Air Link. Maybe because of a win10 update or the small addon to v31.1 update I got on my Q2 yesterday. Who knows, lol! Vulkan works fine started in SteamVR mode so no big deal for me. Also, for the most part I use my Vive Pro with most of my flight/racing sims.
A bit off topic but the Aerofly's RC sim RC8 also does not work in Vulkan (which is still beta in this sim) with my Q2 and I need to use the default OpenGL. Like FS2 vulkan it's fine with my Vive Pro.
Just wondering if there's been any progress fixing the problem with Vulcan not working with the Quest 2. I reported the problem a few months ago and it seemed at the time that it was affecting other if not all Quest 2 users.
I have not had any problems for a while now (since v28, now v31) running my Steam version of FS2 Vulkan with my Q2 using either Air Link or official Link cable. Using Steam version with oculus runtime option. Prior to this I needed to startup with SteamVR runtime. Actually not much difference either way imho.
However, I was over at a friends house a couple of weeks ago and with his Q1 we found he needed to still use the SteamVR runtime. Both of us using latest nvidia driver 471.41.
Bellah1w I went from a gtx1080ti to a rtx3090 and I think it has been a significant improvement on everything. Especially with my wireless Quest 2 because the rtx2000/3000 havew much faster encoders. Your rtx2080ti is still a very good gpu imho. If you have money to burn go for a 3080ti or 3090. Either that, or wait for the nvidia 4000 series (2023-2024?). Personally, I'm hoping my 3090 tides me over until the 5000 series. I like to try to buy the best of any series then skip the next one.
VR works best in 4D sceneries and we even thought about limiting VR to these 3D rendered scenes only but decided not to.
In panoramic sceneries both eyes see the same background image and if you see the rc model in front of that background your head assumes it is as far away as the shadow it casts on the background. This visual illusion is tricking you into thinking that it's floating above the runway.
We could disable 3D all together in panoramic scenes but that defies the purpose of having VR in my opinion. It works great as long as you fly above you or if you can ignore the shadow or relation to the ground.
Ya, this is a pretty well known issue. It does not effect my VR enjoyment since the 4D flying fields are already very good. Maybe there should be a note somewhere that suggests that you will get the best results in VR using the 4D flying fields. I love RC8 in VR!
Hi Tom. I find in VR that if I open both eyes with an aircraft up to 50 feet away it looks to be out of perspective and hovering above the ground but with just the left or right eye open in VR it looks ok. Is there a setting to correct this?
Honestly, I do not see this issue with any aircraft in VR. If I hover a heli close in or far away it looks perfectly fine to me. This is with my Vive Pro, Quest 1, and Quest 2 VR headsets (all currently using the default OpenGL rendering). The only things I can suggest you do is adjust your headset's IPD and play around with your faceplate head placement. This should help keep the headset's sweet spot even between both eyes which should help. I don't know if any of the in-game graphics setting would cause this issue but you may want to contact RC8 support and ask them. I hope this helps. Good luck and cheers mate.
Edit; Also make sure that in VR you are using 4D flying fields. Using other fields will make aircraft float above ground surfaces close in. This is probably the cause of your problem. Cheers.
I have the direct download version and I think it’s great, especially in VR. Looks to me like the Steam basic plus dlc1 would give me the all I need and would cost a little less. Plus I could then also use it on other pc’s without needing another license.
Don’t believe every review you read on anything imho. With Steam you can find out for yourself and get a refund if you’re not happy with it (less than 2 hours use and less than 14 days since purchasing it).
So, from the Steam forum it looks like you have solved this by opting onto beta. Have you found this positional locator useful or not? Cheers.
As always please upload the tm.log file from your user documents Aerofly FS 2 folder. Do you use Vulkan or OpenGL and does it change when you switch the renderer?
I only use Vulkan and VR so I cannot say for sure. I've never used OpenGL nor do I ever want to, lol! Next time it happens I'll try to remember to forward my tm log file. Cheers.
Ya, I often find this happens in VR with both my Vive Pro and Quest 2. If I wait long enough it sometimes (30-50% of the time) comes back about 10,000ft high. But generally I have to use task manager to kill it and start again. At least it's a good incentive not to crash, lol!
Maybe a better thread title would be useful for people wanting to search for this later?
I don’t see this problem with either monitor or pcvr with my Vive Pro, OpenGL or Vulkan. Latest win10 updates and nvidia 417.11. With rtx3090, stock clocks.
One difference is that you have a Steam version and I have the direct download version. This should not make any difference but who knows?
Personally I don’t find this position locator option useful. Why do you find this important? Just curious, nothing else.
Hopefully rc8 support can help you. Good luck mate.
Personally I'd feel a lot more confident in trying this out if it was actually endorsed by Aerofly fs2 or any other flight sims. I guess if that was the case it would already be included in the base software or added as a paid option imho. Seems a bit fishy to me.
Sorry but I think that the Alienware Graphics Amplifier (AGA) is a pretty poor choice for good PCVR. Been there and done that with my old Alienware 17r4 and gtx1080ti in an AGA. Originally with a Dell WMR headset btw. I ended up replacing this with an Oculus Rift cv1 and Vive Pro. I'll never go back to WMR ever again, lol!
First thing you need to do is make sure to use an external monitor and use win10 display settings to only display to it (not your laptop screen). Your best bet in the long term is to do what I did and build/buy a better desktop gaming PC (in my case, i9 9900k water cooled, 32Gb 3000 ram). I did this 2 years ago and moved my 1080ti into it and got about 2x the performance in PCVR than I did with it in my AGA in my 17r4 (i7 7700hq, gtx1060 6Gb, 32Gb ram). I've now replaced it with a rtx3090 and of course am currently getting even better PCVR results with both my Vive Pro and Quest 2.
In any case, I kinda find it hard to believe that msfs2020 works very well in VR with a gtx1070. It does not even work very well with my rtx3090, lol! After a month of trying the Steam version of msfs in VR (Vive Pro and Quest 2) I have uninstalled it for now. Way too many large updates that do not seem to help much and a very poor user interface imho. I'll probably give it another go in the future when it matures and includes stock heli's.
I tried it too - ReShade_Setup_4.9.1
But now my VR doesn't start anymore, probably also because I've already exhausted pretty much everything in the game.
Maybe a stupid question now, but how do I get ReShade completely deleted from the simulator?
Thanks and best regards,
Sorry but like I already said, I have not actually tried it. You are probably best to go to the forum link I provided and ask there. Maybe also try asking at the ReShade website. I would have thought that simply uninstalling Reshade would be all that is required. Maybe you can try a win10 Restore to a point prior to when you installed Reshade? Good luck mate.