Forgive me for my absence but life has a way of taking you away from the things you love to do to the things you need and have to do. Hopefully things have calmed down and I can get back to my simulator. I need help in setting up my CDU's. I purchased my CDU's from Flight Deck Solutions 15 years ago. They had VGA connections and were to be used with Project Magenta cockpit software. I recently have upgraded to ProSim 737 software. Based on my research it does not appear that my old CDU's would be compatible with ProSim737. Does anyone have the old CDU's from Flight Deck Solutions and is also using ProSim 737 software? If so how did you setup the CDU's? I am also using PMDG 737NG. Thanks.

Instructor Station new version released 3.56 !!

You can download the latest version here:
DOWNLOAD LATEST VERSION

Buy your license here:
BUY LICENSE NOW

Hi Steve
Of course grass blades moving in the wind are not top priority for c. builders.
MSFS goals are different.
Thank you for your input.
Jack

Hey everybody.  Surprised (a bit) that there has been no discussion of MSFS2024 here.  Maybe not so surprising since home cockpits and builders are not a priority at Microsoft.

After promising myself to wait a few months I caved and got FS2024 and installed it.  Install was fine and went easy and I have it on the same drive as fs2020.  I still have a full size twin engine turboprop simulator but I switched to VR completely a few years ago using a combo of flight sim hardware and an HP Reverb Gen 2.

First impressions:  not surprisingly I would consider this a late beta and a lot of stuff still does not work though I am sure that will self-correct over time.  Graphics are beautiful and very smooth in VR with the Reverb (using Mixed Reality and OPENXR toolkit) on an i9-10850k; 64 GB ram and an RTX3080.

Flight characteristics (so far) seem similar to FS2020.  I have not seen any major differences yet.  Also have not yet checked out my add-ons from FS2020.

ATC is terrible.  Sound is horrible, IFR flight plans not really working and controller in my latest flight in a Pilatus PC-12 kept looping and switching me between 2200 and 3500 feet in icing conditions....repeatedly all the way to the airport destination.

Anyone else have experience yet?  Thoughts?  I am not sorry I got it though I am disappointed though not surprised that it is not quite ready for prime time.

I am expecting to probably having to replace the Reverb within the next 12 months or so but, so far, it is working fine with the new sim.

Steve

So used Windows to re-orientate the lower EICAS monitor into portrait and reposition down under the other monitors.  Applied and all fixed.

Still not sure how to do it in the PM software but easy enough in Windows.

Ah right because has to match the digits requested in format on the FMC.

So quick observation: Since the ND display DOES seem to draw correctly based on the mileage in the FMC, do you think maybe updating the FMC software would potentially make it choose correctly which would then draw correctly?

I have been focused on the GC ND software not working correctly but maybe it is working and the FMC software is the one working in error. I have not gone down that path yet.

Just thinking outlaid...
 

Work for me when the WP is not in the database.
One thing also, the longitude (W/E) has to be 3 digits (for a 2 dig degree add a 0 in front.)

Will give that a try Jack this weekend.  I assume that should work correctly.  So more the question if ATC gives me direct PRADO in the airplane, why does the one is Spain get loaded?

Same question on the POM VOR versus the other one.  And I know when selecting POM it gives me 2 choices and I always select the first one with the 110.4 frequency next to it.

Perhaps because the version I am running is older and updated .exe would maybe work better.  Anyway, will give it a try.

Scott

Try creating a waypoint with the right coordinates that you will enter in the appropriate sequence of the route page.
Ex:PRADO (33°55'23.4"N  117°47'1.7"W) in SoCal.
Type in the scratch pad  N335523.4W117471.7 enter it (right LSK )in the route proper sequence. It should appear as wpt01.