How do you manage in MSFS to have the mouse operating in each window? How do you move the mouse between the windows?
In my cases the MSFS VR mouse cursor “stays behind” the windows displayed by OVR Toolkit.
For some reason at the moment it’s in a hidden menu - you need to go to the Device settings and then ctrl+Q and you’ll be presented with (from memory) a few options, something like off, balanced, highlights and extreme.
You can change settings in runtime and see the effect immediately so fairly easy to experiment with.
Alternatively you can actually go and edit the config file and set for example local dimming to 0.01 (extreme would be 0 where the blackest is fully off) which gets you fairly ok contrast without any halo/bloom, but will not reach that proper black black that “extreme” will hit.
I just use alt-tab to switch to overlay window session to use mouse and alt-tab back to cockpit.
Another thing, I was wrong about ability to create multiple window overlay sessions.
There is only one overlay session window, you can run multiple apps within that overlay windows.
So you bring the entire Windows desktop to VR, not the individual windows for the individual apps?
This is the way in which my mouse works, if I bring the individual apps to VR is separate windows I can’t move the mouse to them.
But entire desktop in VR is nice as well, I bring the desktop of my secondary display for which I can lower the resolution, to limit the FPS impact.
ALL IN ONE works perfectly and I already explained the reason why your icons were disabled. I explained it to you on Discord, so the tablet doesn’t fail if the user’s settings don’t change, as I demonstrated by leaving the tablet running. The tablet does not fail and works perfectly, in your case it is that you had changed to a new computer.
In addition, as a result of your case, we have developed a new option so that users can restart their profile in the event of a configuration change.
About configuring the VNC app to work with your new glasses, I didn’t tell you that it has a low priority, but that since we don’t have those glasses, the first thing we will have to do is reproduce that behavior in ours, which is not easy, because it’s not that the app doesn’t work, it’s that it doesn’t scale to the entire tablet screen, but it works.
Any comments here without measuring may influence our currents and future users, I hope you understand.
You can exit of window SIM pressing CTRL+ESC into your VR session. Then move the mouse to the other app and when you want come back, click with the mouse into the window SIM again.
For those of you interested in bringing Windows desktop to VR in Crystal (for example to run SkyDemon):
OVR Toolkit is super mature tool allowing this, way more refined vs. for example FSDesktop. However, it requires SteamVR. SteamVR works with MSFS and Crytsal, producing ca. 10% less FPS vs. PimaxXR. However, PimaxXR produces more fluid image, especially when looking to the side in low flying VFR GA plane. FPS - not so much difference. But smoothnes/fluidity - noticeable better with PimaxXR. SteamVR is not so fluid, even at relatively high FPS (ca. 35-40 FPS). There are no noticable jumps or jerks, but the impression of movement in just not so fluid like in PimaxXR.
So I have difficult choice now:
- fluid PimaxXR but without the ability to see and operate Windows app like SkyDemon,
- or not-so-fluid SteamVR, with OVR Toolkit.
For those of you equipped with the graphics tablet (e.g. Wacom) I highly recommend (following the suggestion of @mbucchia) OpenKneeboard:
It allows perfect integration of the graphics tablet. With your hadset donned, you can make notes in fligth, your tablet stylus and tablet drawing area will be perfectly aligned with the image of the kneeboard you will see in VR. You can even map your Wacom tablet buttons (great with your muscle memory while in VR) to actions like:
- next page, previous page,
- hide/show kneeboard,
- zoom (enlarge)/unzoom kneeboard,
- recenter kneeboard location in VR cockpit,
- and more.
I happy to report that VNC feature of All In One v. 3.0:
https://www.flightsimulator.me/
works properly now with Pimax Crystal (I received custom version of VNC for the remote PC from @ErDebugger, I hope it will be soon available as the part of the installer of the All In On v. 3). No more issues with desktop scaling.
With VNC I can bring to VR in Crystal the desktop of another PC (old notebook in my case) and control with 3D mouse in MSFS VR the applications running on the other PC, for example SkyDemon, vPilot, PDF reader, web browser.
This has another benefit of offloading some processing (like running SkyDemon) to another PC, while the main sim PC must only (?) display the desktop image streamed from the other PC. I still need to test the FPS impact vs. the size of the streamed desktop, so far looking good (small impact on FPS).
It works much, much better than FSDesktop which is still at eraly development state. And runs on PimaxXR, unlike OVR Toolkit which requires SteamVR, which in my case results in not so smooth movement in VR as provided by PimaxXR. Also with PimaxXR I have better FPS (45) compared to SteamVR (40).
Thank you, @ErDebugger
Pimax just wrote me that shipping of my headset is delayed at least a week. I confirmed my address a week ago. Paid on 1st of July, ordered late May. No explanation given for the delay. They have given me a discount code for buying accessories, which I find a bad way to make up for this. I need to spend more money and give them more for late delivery. I am keen on getting a faultfree headset with the amount this costs, that’s the most important thing!
I experienced strange phenomena with Crystal and OXR Toolkit. I used standard keys for the Toolkit (Ctrl-F2, Ctrl-F3) and this resulted in increasing (washing out to complete whiteout after a couple of keypresses) or decreasing the image in the sim. This change of brightness persisted even after switching to 2D. So it wasn’t a backlit control in Crystal.
What could be causing this? Any standard keybind in MSFS?
I applied workaround - remapping the OXR Toolkit keys, but I wonder about the root cause. Possibly I would need to check keybinds in MSFS, but this behavior emerged out of the blue, I never noticed anything like this before.
Out of the blue today my crystal has had intermittent bright flashing of the screen, weird wobbly artifacts behind the arc of the prop (despite not using Motion Reprojection), artifacts on the trailing edges of the tailplane etc and a periodic 2 second or so stutter that showed up on all the traces on the dev mode FPS counter…oh and reduced FPS performance. Totally unplayable. This was in PimaxXR mode with the Toolkit. Disabling the Toolkit partially fixed it but not completely.
Using SteamVR was far better, but still with some wobbliness behind the prop, for example the compass on top of the instrument panel on the C172 bouncing around all over the place. Really not impressed with this sort of rubbish. I never really know what’s going to stop working next with my Crystal.
That Green drop in frame times was rhythmic in between really crummy frame times. Yesterday I was getting 70fps with the same settings. Grrr.
Can I ask a question (off-topic for this thread but…)?
When you say you can control the VNC with the 3D mouse - does this work with VR controllers?
I tend to use those instead of the mouse when in VR, so interested to see whether the “native” capability of remote controlling VNC would work with the VR controllers?
Thanks.
I saw that you mentioned in an earlier post that you connected a USB cable via an iPhone charger to the headset that provided double the power than the Pimax hub.
Did Pimax state that this is safe or do you think that providing the extra power to the headset might be the source of the issue?
I got that delay-mail last Friday and yesterday I got a shipping confirm and "We wanted to be extra careful with the assembly and testing of this new and exciting device so we added new layers of testing that caused a small delay. It is very important we get this right as nothing is more important that delivering you the best headset experience we possibly can. "
I don’t use the controllers. I use my yoke, throttles, DIY knob/switch/button panels and (rarely) a mouse. The All In One Panel by Flightsimulator.me is great, offers many functions in VR, costs 20 EUR (if I remember correctly) I recommend to try it
Yes it’s a known thing, in MSFS “drone” camera mode, those keys are used by the game to adjust brightness.
You probably enabled some options that don’t like each other. Someone was telling me about the flashes, I can’t remember what option cause that, perhaps “double turbo mode”
if you accidentally enabled Turbo mode in both PimaxXR and OpenXR Toolkit?
Which Turbo is better for Crystal and MSFS:
- in PimaxXR (prefer frame rate over latency)
- or in OpenXR Toolkit?
They’re not meant to be different. Really the idea behind it is that some people do not use OpenXR Toolkit (because they don’t want to or also because OpenXR Toolkit isn’t 100% compatible with all apps), so it makes sense to have this option directly in the runtime for them. But in reality, they do the same thing. Just don’t use both at once, because then you have two things trying to predict the next frame display time on top of each other, with each one adding their own prediction error!
Because the Turbo in PimaxXR is baked into the runtime, I expect that it would be more stable, but unless you have experienced crashes with Turbo in OpenXR Toolkit before, this might not even matter.
Thanks for the information. Wonder why they just don’t write that. Let’s see when the send mine.
