flyblueskies

BBcode works too: [img]

In Imgur, right click on the image, then choose Copy image link...this works everytime for me...I am using DuckDuckGo instead of Edge though. I don't think that will make a difference, but I thought you should know. When you paste the link, use the plain text choice.

Or using Postimages:

Here's how I did it...I went to imgur, right clicked on the picture or image, use the copy image link (provided in the right mouse click), then simply past the link in your avsim post. For reason, the grab a link does not work in avsim.

"What the heck is going on here where's it at?" It's in the beta branch. You have to log into the beta branch to get it, which is located on the FSHud website.

I use it and find it useful. I setup commands to get into VR, go to settings, turn on or off the parking brake, reset the barometer, choose options 1 or 2 when the menu appears, and set com frequencies. I also set up checklists for different airplanes. It is well worth the $10. In non vr, I also use to reset my Track IR, stop Track IR or start Track IR. I hope this helps.

I just took a flight from Canberra (YCBR) to Sydney (YSSY). There are several ways, either over the mountains or head over to the coast and fly up to YSSY. Both ways have good scenery.

Does this update still have the FSHud version?

OK, I have this working now. I loaded the stock Cesnna 172 (glass version), then created a flight plan from the EFB. I loaded the EFB flightplan into MCE and it's now working.

I really appreciate this, but I'm not able to communicate with Native ATC. I have MSFS 2024 at version 1.6.34.0 (not the beta) I updated MCE to version 3.1.49. I copied the new Simco64_ldr.exe (v2.3.9.8) into C:\Program Files (X86)\Multi Crew Experience (I renamed the original). MCE automatically loaded a SimBrief flightplan. The ATC tab under flight info, shows the flightplan, but VHF contact states 'Not Established'. In the MCE.ini file, I have UseWithVoxATC=0 (I did have it set to 1 as I used it with FSHud).

...for MCE integration? With all the talk of BATC and Say Intentions for VFR, I'd like to try MCE again for Native ATC VFR flights... I currently have MCE v 3.1.41

Could this one-time option change to allowing to try both? That way, if I'm not sure and I can try both ways before deciding which is best for me.

This sounds very good...so basically I get all the features of VR Auto Optimizer along with all the goodness of AutoFPS.

Just wondering how your latest version of AutoFPS compares to VR Auto‑Optimizer...does the latest AutoFPS basically incorporate the same features as VR Auto‑Optimizer?

I originally had two monitors and moved Auto_FPS to my second monitor. Now, I only have one monitor and I cannot see AutoFPS on my only monitor. I think AutoFPS is on my "second monitor", which is no longer there. If true, how can I setup AutoFPS to show on my first monitor?

Me too...started just a few minutes ago for me.

🙂

Well, what I posted is "and you said no (and not possible)". What I mean by this, is that you previously said "By design, the NVIDIA app overlay (Alt+Z) and its performance metrics (Alt+R) do not appear inside a VR headset; they are rendered on the standard 2D desktop monitor.". What I'm really trying to find out, is how can I show FPS in VR as you have shown in your screen shot above.

This picture looks like it is showing FPS in VR...is that true? I know I asked you in another post, and you said no (and not possible), but this picture is definitely showing the camera menu in VR...

It turns out, there was more to the story. Of course, frame gen must be off for smooth motion to work. But, frame gen and overclocking of my 5090 was not the culprit... It turns out that running TechPowerUp GPU-Z along with MSFS_AutoFPS BEFORE starting MSFS 2024, is the real reason FS24 CTD with Smooth Motion ON. I tested this several times, and if I start GPU-Z and MSFS_AutoFPS before starting FS2024, it will CTD with Smooth Motion ON. If I do NOT start GPU-Z and MSFS_AutoFPS before FS2024, it does NOT CTD with Smooth Motion ON. Interestingly enough, once FS24 boots up OK and I spawn into an airport, I can start GPU-Z and MSFS_AutoFPS without issue.

It's a combination of seeing the control accessories when I fly and also reading my texts on my phone. I can do all of that without either taking my headset off or lifting it up to peak underneath. So, yes I do miss the great color passthrough. As far as comfort, the Quest 3 is a little lighter than the Pimax Super. But, not enough to really make a difference. I don't know about the Crystal Light because I've never had one. Yes, I really wish Pimax would add a color passthrough as good as the Quest 3.

Well, I started with the Quest 3 and just went to the Pimax Super recently. I debated on keeping the Pimax, so I used the Quest 3 again for FS 2024. I much prefer the Pimax Super over the Quest 3. I only either of them for MSFS 2024. I do like the Quest 3, it has a very nice color pass through, which I really miss. And using Virtual Desktop via Wifi is really nice too. But, the Pimax Super is the one I'll stay with.

So, I don't understand, how did you get your screenshot in 3D showing FPS?