jellef

No, this only displays a part of the screen. It doesn't solve the problem. As this is true for all aircraft with G1000 instruments (including all Carenado and the P3D default Mooney's) it must be a generic v5 problem. For most planes, especially the Carenado's) the display in 3D are unusable.

[Vcockpit03] Background_color=0,0,0 size_mm=512,512 visible=0 pixel_size=1024,1024 texture=$Panel_bon_4_N gauge00=rxpGNS2!GNS_430_1, 165,67,339,171 gauge01=rxpGNS2!GNS_430_2, 165,247,339,171 gauge02=BA36!gem, 8,354,154,154

I have no chance to test this in FSX, but in P3D I use this for the VC: gauge00=rxpGNS2!GNS_430_1, 165,67,339,171 gauge01=rxpGNS2!GNS_430_2, 165,247,339,171 All buttons and knobs (right and left side and bottom) are working. The only ident working is 794, as used in [Windows00], so it definitely looks like this is hardcoded. I experimented with a different number in [Windows00] and in the popleft call in RealityXP.GNS.ini (both in the GNS_430_x sections). Also the ident=GPS_PANEL does not work. So the only option left is configuring both 2D cockpit lines in [Windows00] and setting popleft=794 in the .ini file. This shows a good popup for both GNS_430 simultaneous. Jelle

I'm afraid you are right. Ident 794 is the only instance that is referred to for a popup. I have configured multiple Carenado (and 1 Alabeo) aircraft meanwhile, they all work with 2 GNS430's with an individual popup with different id's. One strange thing: when I first tried your solution it worked. Immediately I set it up with an additional window section (deleted the gauge01 from window00) with a different ident, configured the .ini file for it and it worked. When copying the concept to a different plane I editted the wrong panel.cfg and saw it too late. I tried to recover it but never succeeded in getting the desired result. Now I'm seriously thinking I saw something that never could happen. Was it a fata morgana? I'm not willing to spend many more hours in chasing the impossible. If someone has the solution, please tell us.

Found the cause of the problem: X, Y, W and H parameters of the rxpGNS2!GNS_430_x parameters. Most likely they did not match with the bezel and so the clickspot shifted. Find a strange problem with the panel.cfg ident parameters. The popleft parameters in the .ini file do not match with 2 separate Windowsxx sections in the panel.cfg. Only the default Windows00 section is found and so it is not possible to configure a undependant popup for both GNS430's. I suspect a problem while loading the panel.cfg due to an error, but haven't found it yet. There is a possible mixup with the panel for for the old and the new Bonanza. I will try to fix this either. Jelle

Hi Bill, I copied your panel.cfg and RealityXP.GNS.ini files 1-to-1 and now its works! I will take some time to debug and if I find the cause I will report it here. Thanks, Jelle

I have been updating a number of my planes in P3D v4.5. With the Carenado A36 Bonaza I have a problem in the VC gauge that most of the knobs are functioning (on the left and right side of the bezel), only not the bottom row: CDI, OBS, MSG, FPL and PROC. Whatever I tried, I can't get it to work. I found no answer on the other forum items. The knobs on the popup (2D) gauge do work correctly. I have 2 versions of the Bonanza: the original one supplied with the P3D package and a newer version bought from Carenado. Both versions have the same problem. Most other Carenado planes do not have this defect. Anyone with an idea how to solve this? Cheers, Jelle

Keven, thanks a lot. That's what I call a quick response! Cheers, Jelle

Just updated to 0.4.82. When adjusting a camera setting I normally used tye 'V' icon in the menu bar to update the current preset. Now it adds a preset without updating the one I was using. This is annoying because you have to delete the original preset. If you are not aware of this error and you press the icon multiple times you end up with a list of new presets.

Just disable fuselage shakes in EZdok. See: https://www.prepar3d.com/forum/viewtopic.php?f=6312&t=126999 This solves all problems.

Hi Mark, You are right, the displays depend very much on the size of the window. Full screen (1920x1200) the electical panel display is OK, the Cabin Pressurization Panel display is still poor. If I resize the window height to about 80% this panel is much better. However, the electrical panel display is a bit less crispy, but still acceptable. Horizontal size doesn't affect the display quality. This solution will do. The behaviour of the circuit breaker knob is like you describe and this functionality is ok. CONT CAB, FWD CAB and AFT CAB. Only the panel knob does do nothing, in both directions. So if I set it in the VC and L-click on the overhead panel it doen't respond. Regards, Jelle P.S. I send you the screen hots by PMl, did not succed in inclusing it here.

Mark, fantastic job. The overhead panel is a very nice extension. If it runs on a tablet, just like the CDU, it would be even greater (although you need a rather large size tablet). On a system with a little lack of CPU power running this together with PMDG consumes just too much power (about 3-5 FPS loss), but on a networked system this is no problem; simserver alone does not contribute much here. I find a few problems with the overhead panel: - the cabin pressurization panel displays for FLT ALT and LAND ALT are poorly visible. In fact, to ajustt the settings you have to verify on the plane's panel. - the display on the elctrical panel is poorly visible - circuit braker and panel lighting dials are rotating, but immediately return to the center position. The settings does not align with the knobs in the cockpit. - this also occures on the knobs for CONT CAB, FWD CAB and AFT CAB. Maybe I have forgotten something, but please look into the issues. That would improve the product even more. Thanks, Jelle

The problem has been fixed with a new installer. PMDG support responded with this reply: "We believe we've identified and fixed this issue now. The original version of the dual P3Dv3 and v4 NGX installer was installing only a 64-bit version of our licensing service, regardless of whether v3 or v4 was selected. We've corrected this in an updated installer that uses the 32-bit version of the service when the v3 version is installed. Follow these steps to get the updated version: 1. Uninstall your current version from Control Panel\Programs and Features (Win 7) or Settings\Apps & Features (Win10) 2. Log into your account at our store, click View Previous Orders, and then redownload the installer from the original link to get the updated version. 3. Reinstall from the new installer. " I followed the instruction and voila, the P3Dv3 opens the 737NGX without any activation request. Thanks PMDG for the excellent support! Jelle

PMDG has confirmed the issue for P3D v3 and is now testing the solution in beta. Probably next week the fix will be available. I appreciate the quick response to the problem by PMDG, top quality! Jelle

I believe this is a typical problem for the 37NGX in P3Dv3. I installed the latest version in both v3 and v4. Only slecting this aircraft in v3 request validation and it fails. In v4 it runs without any problems. Strange. See my topic in Jelle

Is there anybody out there who installed this new version in P3Dv3 with succes?

After the release of the new installer for the PMGD 737 NGX I downloaded it today. I followed the instructions and uninstalled the older version for P3D v3. When running the installer I choose to install both v3 and v4 at the same time. The NGX runs ok in P3Dv4, but not in v3. After starting the sim and selecting any of the PMDG aircraft I get a window with this: ERROR: Activation library handle creation failed. Manually entering the right code in the popup window fails. I checked the FlexNet service but it seems ok. Reinstalled PMDG for only v3 and for both v3 and v4, nothing helps. Strangely v4 never complains about the activation code. Any suggestions?

Hi Mark, I sent you the logfile per email. Were you able to investigate it? Kind regards, Jelle

Just downloaded v 2.2 (November 23rd, 2015) for which I hoped connection problems with Prepar3D V.3 were solved. Unfortunately for my situation this was not true. This is how I can reproduce it: - start up simserver - startup P3D with a loaded PMDG flight - test working remote CDU -> OK - reset the scenario or load a new one (any major change in the current scenario will invoke this). - the remote CDU will display a lost connection - when P3D has been restarted with the selected scenario a display appears on the remote CDU, but this is not in sync with the CDU in the sim. No keys will operate on the remote CDU. The problem is only solved by completely exit P3D and restart from scratch. Jelle