March 15, 20215 yr I followed this tutorial for the 530: I was able to get the GTN to display in the cockpit, however it does not register mouse clicks. The only way to interact with it is through the pop-up. Here is my INI: [GTN] ; comma separated list of gauges gauges = GTN_750_1 [GTN_750_1] ; comma separated list of render targets. drawto = WINDOW, PANEL3D ; is the master device if true. MasterDevice = true ; aviation db: 0: nav_db2_grm, 1: nav_db2, 2: nav_heli_db2_grmn, 3: nav_heli_db2 NavDbType = 1 ; connects to: 'PFC_GTN' or any '#PID' (#D067 for PFC_GTN) ; no value connects to first found, 'OFF' disables connection. HardwareDevice = ; hardware selector number or -1 to disable. HardwareIdx = -1 AutoNavGps = false UseAudioPanel = false AFMS.sel_crs_vloc = 0 AFMS.cdi_key = 0 [GTN_750_1.WINDOW] ; display window if true. visible = false ; show screen only gauge if true. nobezel = false ; display type: WINDOW,PANEL2D,PANEL3D,PANELS frame.type = WINDOW ; display position and dimension (left,top,width,height) frame.rect = 1090,997,830,790 ; screen only border size (pixels). border.size = 0 ; screen only border color (#RGB or #RGBA). border.rgba = #000000 ; enable mouse clickspots if true, disable if false (use SHIFT to override) usemouse = true ; left mouse button on the screen toggles popup window if true (requires SHIFT+left mouse button). popleft = false ; right mouse button on the screen toggles popup window if true (requires XP11.1). popright = true ; VR mode position and dimension (left,top,width,height) (requires XP11.20) vrmode.rect = 0,395,415,395 ; display as popout window if true (requires XP11.1). undocked = false ; display mouse tooltips if true. tooltips = false ; freeze display position if true. locked = false ; auto hide in external view if true. autohide = false [GTN_750_1.PANEL3D] ; display window if true. visible = true ; show screen only gauge if true. nobezel = true ; display type: WINDOW,PANEL2D,PANEL3D,PANELS frame.type = PANEL3D ; display position and dimension (left,top,width,height) frame.rect = 672,1148,667,809 ; screen only border size (pixels). border.size = 0 ; screen only border color (#RGB or #RGBA). border.rgba = #000000 ; enable mouse clickspots if true, disable if false (use SHIFT to override) usemouse = true ; left mouse button on the screen toggles popup window if true (requires SHIFT+left mouse button). popleft = true ; right mouse button on the screen toggles popup window if true (requires XP11.1). popright = true I used sim/view/mouse_click_regions_toggle to see if there's a click region on top of it, there isn't. Thanks Edited March 15, 20215 yr by RXP
March 15, 20215 yr If you have followed the tutorial, have a functional popup/popout, can change presentation on the panel screen via the popup/popout, you have done well. In your ini's [GTN_750_1.PANEL3D] section... ; left mouse button on the screen toggles popup window if true (requires SHIFT+left mouse button). popleft = true It should be popleft=false For the GNS530/430 V2, the screen area is only for viewing the data you have chosen to display. You can use a left click, right click or both to force the popup window to show. The GTN is different due to the screen area containing areas of focus to invoke commands...hence touch interface. We use left clicks of the mouse or finger touch to change functions. The popleft must be set to false or you will only be trying to invoke a popup every time that you click on the panel screen. Try popleft=false in your Panel section. Just curious, which aircraft did you place this GTN in?
March 15, 20215 yr Author 2 hours ago, Draggendrop said: If you have followed the tutorial, have a functional popup/popout, can change presentation on the panel screen via the popup/popout, you have done well. In your ini's [GTN_750_1.PANEL3D] section... ; left mouse button on the screen toggles popup window if true (requires SHIFT+left mouse button). popleft = true It should be popleft=false For the GNS530/430 V2, the screen area is only for viewing the data you have chosen to display. You can use a left click, right click or both to force the popup window to show. The GTN is different due to the screen area containing areas of focus to invoke commands...hence touch interface. We use left clicks of the mouse or finger touch to change functions. The popleft must be set to false or you will only be trying to invoke a popup every time that you click on the panel screen. Try popleft=false in your Panel section. Just curious, which aircraft did you place this GTN in? I tried popleft=false, still unable to click the screen. I'm trying to replace the co-pilot MFD in the dden challenger 300. Here is a screenshot of what I have so far: It controls the plane without issue and integrates really well, except I can't control it without using the GTN popup
March 15, 20215 yr Author Update: Flying around I noticed a reflection off the GTN screen, something that usually doesn't happen with the GTN. I've come to the conclusion that the way this plane is set up there's a piece of glass on top of the GTN in the 3D cockpit. Unless I can find out how to edit the obj and remove the glass, or if there's a setting for the GTN to capture mouse clicks through solid objects, I'm probably out of luck.
March 15, 20215 yr NB: with the GTN, because the left mouse button is used for interacting with the touch screen, the popleft= works differently than with the GNS. As indicated in the inline comments, with the GTN you need to press SHIFT+LMB (Left Mouse Button) for the popup function, whereas with the GNS you don't use the SHIFT modifier. As for the topic issue, I thank you for the picture because it helps me understanding the context better and I can see a few possible causes: The 3D gauge you're displaying the GTN above also has a click spot hard-coded in the 3D model and this one takes precedence. This is the most probable cause to me. You're using an XP11 version (say the latest "beta") and it has a bug What to test: Is this model offering popup gauges by default? Do they work if you also use SHIFT+LMB on the gauges (the defaults, not with the GTN retrofit)? If the defaults don't popup with SHIFT+LMB, is GTN popping up instead? (requires popleft = true) Edited March 15, 20215 yr by RXP
March 15, 20215 yr Author I found the glass to be an object attached in plane maker, removed it, still can't interact with the GTN. I am not using a beta version of x-plane, the model does have pop-up click spots, however when I show the click spots with the sim/view/mouse_click_regions_toggle command, there is none in the way. Using shift+lmb does not work, in fact nothing happens when clicking anywhere in the area with or without shift. At this point I am stumped.
March 15, 20215 yr 10 minutes ago, ri0t said: I found the glass to be an object attached in plane maker, removed it, still can't interact with the GTN. X-Plane splits the 3D objects and the 3D clickspots (I know...). You can try opening the aircraft obj file located in "objects" folder. For example with the Aerobask Legacy (I'm taking this one as example only): 1. In the aircraft folder, the aircraft file is: Legacy_RG.acf 2. In the aircraft\objects folder, the main file is Legacy_RG.obj 3. Open the .obj in notepad 4. Try searching for "popup" (most of the time, it is named like this). 5. With the Legacy RG you'd find for example: ATTR_manip_command button aerobask/dfc90/popup Autopilot popupTRIS 19473 6 The 1st line is defining: - a command action (ATTR_manip_command) - working with LMB (button) - which command is (aerobask/dfc90/popup) - and tooltip text is (Autopilot popup). This 2nd line is telling which triangles to bind this manipulator to. I believe if you remove these 2 lines you're effectively removing the hard-coded 3D clickspot.
March 16, 20215 yr Author 3 hours ago, RXP said: X-Plane splits the 3D objects and the 3D clickspots (I know...). You can try opening the aircraft obj file located in "objects" folder. For example with the Aerobask Legacy (I'm taking this one as example only): 1. In the aircraft folder, the aircraft file is: Legacy_RG.acf 2. In the aircraft\objects folder, the main file is Legacy_RG.obj 3. Open the .obj in notepad 4. Try searching for "popup" (most of the time, it is named like this). 5. With the Legacy RG you'd find for example: ATTR_manip_command button aerobask/dfc90/popup Autopilot popupTRIS 19473 6 The 1st line is defining: - a command action (ATTR_manip_command) - working with LMB (button) - which command is (aerobask/dfc90/popup) - and tooltip text is (Autopilot popup). This 2nd line is telling which triangles to bind this manipulator to. I believe if you remove these 2 lines you're effectively removing the hard-coded 3D clickspot. Aaah this put me on the right track, I went into the cockpit object and removed all attr_manip_* except for the battery on switches, now I can interact with the GTN. I suppose now I just need to find out which manipulator is blocking the GTN. This could be difficult since clicking the area does nothing. I'll make sure to post it here if/when I figure it out.
March 16, 20215 yr Author It worked! If anyone is here trying to get the GTN in the challenger with the config in my first post, you need to remove line 10511 then line 10493 in Bombardier_Cl_300_cockpit_INN.obj. Line 10511 ATTR_manip_toggle button 1.000000 0.000000 cl300/chkl_panel_s Line 10493 ATTR_manip_none @RXP the ATTR_manip_none is the one that was both blocking the interaction with the GTN, but I was confused because clicking the area had no effect and did not change my pointer. It is documented here.
March 16, 20215 yr It don't remember whether it was a bug or a design decision but now that you're mentioning it, ATTR_manip_none might be "swallowing" mouse events directed to windows displaying over geometry. I'm not sure about this one.
March 17, 20215 yr 23 hours ago, ri0t said: It worked! If anyone is here trying to get the GTN in the challenger with the config in my first post, you need to remove line 10511 then line 10493 in Bombardier_Cl_300_cockpit_INN.obj. Line 10511 ATTR_manip_toggle button 1.000000 0.000000 cl300/chkl_panel_s Line 10493 ATTR_manip_none @RXP the ATTR_manip_none is the one that was both blocking the interaction with the GTN, but I was confused because clicking the area had no effect and did not change my pointer. It is documented here. Well done 🙂
Archived
This topic is now archived and is closed to further replies.