somiller

ChasePlane provides the body movements etc. and the amount is selectable. You can assign your keyboard shortcuts to the views in ChasePlane but you'd probably have to do it individually for each aircraft. Admittedly I haven't spent a lot of learning many functions of CP, but I use it every flight and have custom view settings for every aircraft.

Don't give up. I installed 2024 for the first time less than 6 months ago and after about 30 days I finally got the courage to uninstall 2020. With correct settings 2024 looks so real it's almost hard to believe. You have a strong system so pay attention to shadow, reflection, ambient occlusion and raytrace settings...turn them up - they make lighting of objects look very real. You won't believe how good the PMDG flight decks look when you get your sim lighting settings right.

No, I think you're the only one. Nice of SWS to make an aircraft just for you.

Flightplans go here: C:\Users\YOURUSERNAME\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\pmdg-aircraft-738\work\Flightplans and weather/wind files go here: C:\Users\YOURUSERNAME\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\pmdg-aircraft-738\work\WX

I just wish they'd give us an option for UI location on the monitor - sometimes it pops up on the left side, sometimes it pops up on the right side. The other issue I have now is most functions in the UI require that I try 2 or 3 times or more before my request is acted on - never experienced this before the latest hotfixes.

It is but I've found it worth the effort. AIG installer is a lesson in how NOT to build a user interface. It has to be the most confusing, backward UI of any software I've ever used outside my job at UPS - now THEY know how to create garbage UI's.

I had the same issue last night RT Direct. Started PSXT and it just sat there...didn't connect to MSFS 2024, didn't verify RT license...nothing. So I switched to RT App, restarted PSXT and started RT App and same thing. Then I wanted to switch back to RT Direct and it was greyed out and I couldn't change it. Closed and restarted PSXT, then I could select Direct and then it connected to MSFS 2024, verified RT license and all worked perfectly. My issues occurred around 0100 UTC. Never seen this before last night.

Good to know - I'll make sure to kill my saved panel states and recreate them. As a matter of fact, did that just now, and in options.ini I replaced my custom startup state with COLDDARKGPU which is a PMDG installed state.

What is this Gemini of which you speak? More broadly, what is the subject of this post?

The windscreen window fit/alignment is terrible on the -700. Also on the pillar exteriors between the glass there are remnants of low-res screws. Has to be one of the laziest efforts at high detail I can imagine - what a joke. I bought it since I owned the 2020 ver. and it was only 30 bucks - good thing I had no expectation regarding the "high detail". The downside is that it is less performant on my rudimentary system. I get great performance with the -800 and -900 and would GLADLY trade their definition of "high detail" for that performance.

I've highlighted in yellow what SAP is looking for, specifically: 1.) "wgs" folder 2.) "Microsoft Flight Simulator 2024" folder 3.) "OneStore" folder 4.) "Community" folder Select the 3 dots at the end of each field and navigate to and select the folder indicated. If you have selected the wrong folder, or an invalid path, the text in the field will be red. For each path that is correct the text will be white. That should be all you need...but of course I have assumed you have the MS Store version...if not simply do the same thing for the Steam fields.

Nope, still now idea what you are carrying on about...looks like another opportunity to use the ignore function so kindly provided by avsim!

Try starting a new flight and prep the flight deck for departure, including aligning the IRS's - see if that generates an "options.ini" file for you. When you open Packages\Microsoft.Limitless_8wekybed8bbwe\LocalState\WASM\MSFS2024\pmdg-aircraft-737\work folder - do you see all the other files and directories as they appear in the image I posted above?

That's interesting - I have a PFP 3N and it works with PMDG 777-300, including the screen. My problem is that no matter what I have tried using the PFP 3N with PMDG 737-900 crashes MSFS 2024. Works with the -800, iFly Max, and 777-300.

Great question because I have an "options.ini" file in C:\Users\Owner\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\pmdg-aircraft-737\work.

Oops, thought you had posted that you were using ChasePlan, but since that is not the case, I guess my settings will be useless to you.

Other than maybe 16GB DDR4 I don't see any problem with those specs - look at my specs in my sig - and I get pretty darn good performance even at some tough airports, but I'm using DynamicLOD Reset edition (AutoFPS is an alternative) and Lossless Scaling - which is just the medicine my system needs to run MSFS 2024 really well with mostly high and ultra settings. 2024 really is amazing for it's ability to be run on sub-standard systems like mine - just requires a couple of crutches (DynamicLOD and Lossless Scaling).

You need to "adjust" camera position in ChasePlane. Try these for aft wing views: Left Wing Aft Right Wing Aft

I've had several flights where I bumped against VRAM saturation with my 12GB RTX 3080 running 1440P. Considering a new system with RTX 5080 but thinking I might never be satisfied until I jump to the 5090 - the problem is new systems with a 5090 are running $6000 and up.

It is all very interesting. I fly the PMDG 738 and 739 almost every flight I make and have had exactly 1 WASM crash which occurred about a week ago. I import Simbrief plan using the EFB and autoload into the FMC using the request flight plan (or whatever it's called) function. I use current Navigraph data for 2024 and all PMDG aircraft. I have always set the transponder to TA/RA, but since that crash I now usually set it to TA only as it has been suggested that WASM crashes are less likely with it set to TA only. The only consistent issue I have with any PMDG aircraft is an MSFS crash that happens if I try to use WINCTRL PFP 3N with the 739 - I can use the PFP 3N with 738 and 773 with no issue...still haven't figure this one out, but it is repeatable, and no amount of uninstalling/reinstalling the 739, or SimAppPro, empty community folder etc. has fixed the problem.

$2000.00 for THAT?!

You people don't have enough to do. Are you not able to use aviaworx products with your PMDG aircraft...of course you can with the FMS they were designed to be used with - the FANS 1A. No support is necessary.

Ignore is such a great feature on AVSIM!

what freezes - the hardware FMC, SimAppPro, the aircraft, or MSFS 2024?

Michael, Great minds think alike - Last night I bit the bullet, installed MobiFlight, and downloaded the very profile you recommend. Am I to assume you use MobiFlight as the interface for WINCTRL hardware?