dafyddp3d

Thanks for the heads up and for keeping your heads down! Looks awesome.

Not familiar with EPIC stuff, but opening notepad and operating controller should send key commands to notepad? More brutal, yank out the usb conn while on FS9 and see if it recovers! Also check that key commands being used are not being used by windows as shortcuts?

Might be worth checking that your controller software is not sending a continuous stream of key commands, and tying up the interface. Happened to me on my X52 till I figured out what was going on (on FSX at the time)

FWIW I'm using 361.75 on Windows 10 build 10586.71 and P3Dv3.1, driving both a GTX960 and a GTX780 (see signature), and have had no display problems (so far!). :smile: The GTX960 also has a reasonable overclock applied (I don't use NVI, just MSI afterburner, and NVidia control panel for 3D settings).

Thanks Robert, and to PMDG for all the hard work. P3D v3 is compatible with Windows 10 (hardware drivers being a separate issue!). Can we assume that the PMDG products compatible with P3D v3 also have no (known!) issues regarding Windows 10? Thanks Dave Nash

Yes, I suppose I have to admit it's a bit like a solution without a real problem! Sometimes curiosity gets the better of me! Thanks for the replies and suggestions, if I ever get to know I'll post it! Regards Dave

Hi Dan Sorry for the delay, thanks for the reply. I was just curious to find out what each line / parameter in the rte file represented (i.e. it's structure), in the hope that I could directly modify the file to insert fixes, waypoints etc, or possibly even write my own editing software. I'm aware that most flight planning software provide the facility for exporting a flight plan in various formats, and I thought that a simple editor could be quite handy instead of having to run the sim to edit and save through the FMS /CDU, or via a flight planning app. As I pointed out, the question has been raised before, with a hint that PMDG might issue some documentation, but I couldn't find anything. Since the export facilities are available, someone must know! Regards

Bump?

I've searched the forums for this but so far not found anything. Have PMDG produced any info or documentation explaining the structure of the .rte files used on the 737NGX, 747 and 777 series aircraft. I believe it was hinted at as far back as 2011........ http://forum.avsim.net/topic/325079-rte-file-format/ Cheers Dave

Looks fantastic! So glad you decided to support P3D.

It was probably Santa Claus's warp drive on test

Can't get P3Dforums or website tonight, anyone else confirm?

Thanks for the stunning previews! So glad PMDG chose to support all three platforms. Now where did I put my wallet! David Nash

Bham Uk 14:51 still down

Many thanks for allowing us all to take advantage of all your hard work!Dave Nash

Perhaps a better choice of words would have been 'short turnaround' and 'long turnaround'

You can fiddle it on the 737-NGX if you are happy to play around with the panel configuration file. I replaced one of the 2D panels with the entry below. It brings up a transparent square window and the HUD is superimposed on it. However the gauge only updates if the original panel is activated, which is no problem for me as it's far over to the left and doesn't interfere. Lines beginning with "//" are comments.(If you have a triple monitor setup, and you want to move your eyepoint to the right to be more central and avoid obscuring some of the MCP with the monitor bevels, and then activate the HUD panel (which will swing down far to your left), the knobs for the radio/baro minimums are disabled. The reason for this seems to be that they would be obscured by the HUD panel were you sitting in the default position! If the HUD panel is stored away, the knobs work again. Weird, but I can live with that!//// MYHUD////This panel inserted because I wanted to move my eyepoint to the right to be more central on triple monitors, and not have part of the MCP obscured by monitor//bevels//The PMDG HUD drop down panel is not moveable, but the hud gauge will move with the eyepoint!////Aspect Ratio (i.e.y/x) of gauge = 0.75////Aspect ratio of panel window = 0.75////The hud gauge is made active by calling the PMDG HUD drop down panel and leaving it in place////[Window08] //(SHIFT+9)Background_color=80,80,80size_mm=1024,768window_size=0.2,0.71position=1visible=1ident=22222alpha_blend=0.6gauge00=hud!hud, 25, 100, 1000, 750Hope this helps!