Jump to content

JaimeC

Members
  • Content Count

    9
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

2 Neutral

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. In my system with the left click and drag the brightness of the lamps is adjusted (if you zoom in enough you will see that text DIM and an arrow on the lamp label). With the right click the lamp test is done. With left and right and drag you perform both functions: test and brightness adjustment. Note that I use the "cokcpit interaction system" in "legacy" The amount of detail on this plane is amazing. My congratulations to A2A.
  2. My feedback https://community.justflight.com/topic/4370/version-1-0-3-worse-than-last-version (jaime) In short: Requested refund
  3. Sorry for the confusion. I meant it is a general problem of the Carenado M20R. With all other aircraft the views works with the default settings. Hat switch on T.16000M FCS here.
  4. HI @theskyisthelimit I have the same problem with views. I think it's general and I've also seen it commented on in several videos. About reinstalling, I haven't tested it myself but, do you have the M20R in the menu Official Content, Owned (yes)? If it appears there, it may be the way to re-install it.
  5. I was hoping it would detect it as a different device with different assignments within the simulator. Still, it's a great idea. I am already looking for stores to buy one. But of course I am not going to put your stickers on my main keyboard 😉, maybe on the auxiliary (as long as they are not subject to copiright) 😄
  6. Excellent idea, thank you. A question. Can you separate the keystroke from the normal keyboard? That is, if I press NumLock on the auxiliary numeric keypad, can it be different from the NumLock on my normal keyboard? Apologies for my bad English, I hope you understand me.
  7. This aircraft is a little peculiar. From his own on-screen menu you can select if you want the default gps of xplane, your 650 or your 750 and fix the 3D configuration accordingly. It also allows you to pilot from the left or right side, but it is not a simple change of seat, it changes the instruments position. With what you have told me, in the end I have found the solution: 1- I have eliminated all references to 650 in the .ini. I think this is not necessary, but I will not use it on this plane. 2- This has been the key, I have changed from CopilotSide = false to CopilotSide = true I think that when flying on the right side the dataref are different and that's why it did not work well. Thank you very much for your help.
  8. Hi Jean-Luc Ohhh, sorry, so they have nothing to do with you, I'll have to find an exorcist 😉 Now seriously, I want to clarify that the rapid movements are caused by my moving the course selector so that it is seen that in one mode it acts normally and in another it is frozen. Just to clarify because my English is very bad. I am very new in the GTNs although I have already put them in several planes without any problems, but without HSI, only CDI In this plane I am using the default developer configuration and I do not know if it is ok. I attached the configuration in case you can help me and you see some obvious error. In any case I will also communicate with the developer. Would you be so kind as to tell me what should be the indication of an HSI linked with a GTN in real life? What course and distance should indicate? The one of the VOR tuned, the one of the GPS route? Sorry if the question is stupid and I know it is out of your role as support, but I tried to find information on the internet and I have not been able to find it. Thanks PS: I had to have thought about it before but .... I just tried with the default Baron B58 and now I see how it should work, both in HSI and Bendix. That seems normal and logic to me. Definitely something is wrong with the "connection" of the gtn with the SF260, but I do not know where the problem really is. rxpGTN.xpl.log 19/02/24 18:42:14.491 19576 - ] # win.xpl version 2.5.13.0 19/02/24 18:42:14.491 19576 INFO ] rxpGtnSim.dll.log 19/02/24 18:42:16.687 19576 - ] # rxpGtnSim64.dll version 2.5.13.0 19/02/24 18:42:16.686 19576 INFO ] 19/02/24 18:43:07.636 19576 INFO ] using: C:\X-Plane 11\Aircraft\JRollon\SIAI-Marchetti-SF260\checklist.gtn 19/02/24 18:43:10.131 18216 INFO ] 19/02/24 18:43:10.187 19576 INFO ] using: C:\X-Plane 11\Aircraft\JRollon\SIAI-Marchetti-SF260\checklist.gtn 19/02/24 18:43:10.494 08236 INFO ] 19/02/24 18:46:04.756 19556 INFO ] 19/02/24 18:46:05.841 08060 INFO ] RealityXP.GTN.ini [GTN] ; comma separated list of gauges gauges = GTN_650_1, GTN_750_2 [GTN_650_1] ; comma separated list of render targets. drawto = WINDOW, PANEL3D ; is the master device if true. MasterDevice = false UseFailures = true ; aviation db: 0: nav_db2_grm, 1: nav_db2, 2: nav_heli_db2_grmn, 3: nav_heli_db2 NavDbType = 1 TawsMode = TAWS_A ; TAWS approach air speed (knots), or -1 (auto detect Vref: 99) TawsApprSpeed = -1 ; TAWS maximum flap extension speed (knots) or -1 (auto detect Vfe: 225) TawsFlapSpeed = -1 ; TAWS maximum gear extension speed (knots) or -1 (auto detect Vle: 999) TawsGearSpeed = -1 [GTN_650_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 = -39,885,830,350 ; 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,350,830,350 ; 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 [GTN_650_1.PANEL3D] ; display window if true. visible = true ; show screen only gauge if true. nobezel = true ; display type: WINDOW,PANEL2D,PANEL3D,PANELS frame.type = PANELS ; display position and dimension (left,top,width,height) frame.rect = 1024,1287,1024,539 ; 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 [GTN_750_2] ; comma separated list of render targets. drawto = WINDOW, PANEL3D ; is the master device if true. MasterDevice = true CopilotSide = false RadiosPair = 1 UseFailures = true ; aviation db: 0: nav_db2_grm, 1: nav_db2, 2: nav_heli_db2_grmn, 3: nav_heli_db2 NavDbType = 1 TawsMode = TAWS_A ; TAWS approach air speed (knots), or -1 (auto detect Vref: 99) TawsApprSpeed = -1 ; TAWS maximum flap extension speed (knots) or -1 (auto detect Vfe: 225) TawsFlapSpeed = -1 ; TAWS maximum gear extension speed (knots) or -1 (auto detect Vle: 999) TawsGearSpeed = -1 [GTN_750_2.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 = 633,885,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,790,830,790 ; 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 [GTN_750_2.PANEL3D] ; display window if true. visible = true ; show screen only gauge if true. nobezel = true ; display type: WINDOW,PANEL2D,PANEL3D,PANELS frame.type = PANELS ; display position and dimension (left,top,width,height) frame.rect = 0,1259,1024,1257 ; 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
  9. Hi I don't really know about the behavior of an HSI linked to a 750 in the real world, but it looks odd to me. In the video you can see that I have a route programmed in the gps and a vor tuned. If I choose VLOC mode, everything seems normal. If I move the course selector, the course indication changes and the CDI also. Up to here everything normal. But if I change to GPS, the course and CDI remains frozen at the last value. As I said I have no idea if this is true in real life. Note: I'm sorry for the poor quality of the video. https://www.youtube.com/watch?v=fvqDd6UQHIM&feature=youtu.be
×
×
  • Create New...