• Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by kdfw__

  1. i'd recommend the new rxp gns530 with Roland Ifor's freeware wxr gauge for active sky. ap works perfectly fine, looks perfect. configs, etc. at https://library.avsim.net/search.php?SearchTerm=xtreme&CatID=p3dpan&Go=Search
  2. for a super short trip, dd lows to orbx lowi is a fun jump, esp on the newly released fsl a320.
  3. looks good, bezel can now be darkened (via editing the values in the config file). gps is working again on v4.1, nice! as a side, i did see the gps freeze up (no response to buttons) once but calling up the config window and rebooting (via switching off tcad) got it going again. not sure what happened, just changed system time to check night lighting... didn't happen again.
  4. download https://library.avsim.net/search.php?SearchTerm=xtreme&CatID=p3dpan&Go=Search and check out the panel configs for adding gns530.
  5. optimize parts is fixed with p3dv4.1
  6. FSX-MS

    would be great if we can get the sewer pipe flying on v4.
  7. if they offer a compelling fsx to p3dv4 upgrade path (unlike what i had to do for a certain 744), i'm get the fsx version first.
  8. issue: when using GPS500, not getting the LPV guidance, GNS530 shows the LPV guidance. this one is easy to replicate, go to KTKI rwy17 and tune to ILS, should see the loc/gs needles and activate RNAV17, should also see LPV needles sitting at the end of rwy. using GPS500, no gs when ILS is tuned, regardless of the nav/gps switch if LinkVor = true. if LinkVor=false, then ILS gs needle appears. RNAV needle does not show up regardless of nav/gps switch or LinkVor setting. using the GNS530, if CDI=gps and RNAV is activated, gs shows up. If CDI=vloc and ILS is tuned, gs shows up. this is with CDI button connected to the nav/gps switch setting = true (if false, the CDI and nav/gps switch doesn't sync). It looks like the nav variables are not overwritten by the GPS500 to animate the gs/loc.
  9. Hi Jean-Luc, Great, thanks for the update! Looking forward to it. Not to be a pain, but any idea on the wind vector not showing?
  10. Hi Jean-Luc, thanks for looking into this matter. i think as a first step, would it not be quick and easy to provide a bezel that's black (or an user option to select choice of blackness)? present bezel is something like rgb=59 59 59, a dark gray. since the gns units are really black, going with 14,14,14 (highlighted areas) to 7,6,1 (quite black) would look fine during daylight and at night in the vc. and if you can trick the bezel to load appropriate bezel.bmp based on the crude fs time of day parameter, that would be excellent.
  11. so here's the stock JF_C69 included with p3dv4 with gps added to the AP area: rxp gns530 with vc lights ON, note the bezel, not dark but emissive. next with the vc lights off, bezel lighting is the same, still emissive. next is the stock gps, at night with vc lights on, bezel texture is the "_night.bmp" version, darker than regular: no vc lights, the daylight emissive version is rendered: so it seems bezel texture has to be selected based on the sim time to properly blend with the VC.
  12. Jean-Luc, Bert, reran the 'setup aircraft' from 'addons' pulldown on the tduke and for some reason the tduke is now able to fully function with the gps500. i didn't save off the pre-edit rxp config file so not sure what exactly changed to make it work. so that's good news. now, regarding the bezel at night--is there some thought as to adding a dark bezel .bmp for gauge placed in the vcockpit section? please see https://www.avsim.com/forums/topic/520205-lpv-guidance-not-showing-using-gps500/?do=findComment&comment=3713683
  13. yes, weird. and 530 works just fine...
  14. likewise, i see the gs/loc needles deflect in self test when the gps/nav=gps, no deflection when gps/nav=nav.
  15. panel.cfg change. i guess when you operate the gps500, you'll not have the vloc button so using the gps/nav switch, right?
  16. p3d is log file 17/09/25 04:25:41.864 03704 - ] # rxpGNS2.dll version 17/09/25 04:25:41.869 03704 INFO ]
  17. first of all, it's p3dv4 hf1. i thought other than the lpv mode, gps500 was at least tracking the flt pln but i just tried again and it seems to just point north 360 when nav is engaged (with gps/nav sw=gps). maybe the behavior changed with the recent updates, i can't tell. so here's what i'm seeing on my end with the current version: 1) gps500 isn't able to track plan or lpv 2) gps500 on power up deflects hcdi/vcdi needles on the adi but once out of self test, flag comes down. 3) swap to gns530 on the same aircraft works fine. tried this on both the tduke and xproto glj25. g530sim.exe is on the list of excluded processes from the ms av realtime scan.
  18. gps500 is coupling to the ap, i see the needles deflect at power on if i set 'connect gps to vor indicator.' vcdi/hcdi halfway as it should. gps nav is working, follows track and procedures fine. just no LPV with the 500. gns530 on the other hand is working perfectly fine. i checked the win event log and see two errors each time the gps is turned on and off, always with exception codes 05 and 41d: turn on/off first error Faulting application name: G530SIM.exe, version:, time stamp: 0x4bff0a69 Faulting module name: unknown, version:, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x2370 Faulting application start time: 0x01d335755c43fb69 Faulting application path: C:\Program Files (x86)\Garmin\GNS Trainer\GNS\G530SIM.exe Faulting module path: unknown Report Id: 3de96b48-5c10-4a80-8c35-96cb739c1377 Faulting package full name: Faulting package-relative application ID: turn on/off 2nd error Faulting application name: G530SIM.exe, version:, time stamp: 0x4bff0a69 Faulting module name: unknown, version:, time stamp: 0x00000000 Exception code: 0xc000041d Fault offset: 0x6a17c1ed Faulting process id: 0x2370 Faulting application start time: 0x01d335755c43fb69 Faulting application path: C:\Program Files (x86)\Garmin\GNS Trainer\GNS\G530SIM.exe Faulting module path: unknown Report Id: fe76743c-f351-4244-8a74-1d31912cbc22 Faulting package full name: Faulting package-relative application ID: turn on/off 2nd error
  19. Hi Bert, i tried using the realair tduke v1.2 and i'm not seeing the LPV needle with the gps500. nav1 gs needle works if 'connect to cdi mode to nav/gps=false' but regardless of this and the other settings, no luck on LPV here...
  20. Hi Jean-Luc, just tried v2.3.3 but behavior is the same for gps500. gns530 is working the same as before, properly see gs for lpv and nav. as for the bezel suggestion i made above, hope you can give it some thought. perhaps easiest route is to have a bezel xml gauge which has the day/night .bmp with click spots and display the gns530 as screen only.
  21. Hi Jean-Luc, The VC gauge--if you look at the standard fsx lear jet pfd gauge construction in Lear_45_XML.cab (or p3d's Maule_M7_260C.cab), you'll find bitmaps with "_night.bmp" suffix. this forces the sim to render the "_night.bmp" at night time automatically. So at night, a dark bezel/gauges can be displayed and during day time, the standard bezel/gauges can be displayed. I'm sure your bezel/button .bmps in the rxp.dll contains the daytime .bmp but i think you should be able to add a night version of the bezel/buttons like it's done on the xml gauges here. the sim may not automatically select the day/night texture for a dll gauge but if you can conditionally select the .bmp off the simulator's time (dawn/day/dusk/night variables), this should be doable.
  22. HI Jean-Luc, thanks for looking into the needle issue. regarding the bezel lighting, this is what i'm seeing: at night with panel/guague lights on (not the vc flood lights), the light maps turn on and i get the 1st one with the button brightness=100. the bezel rendered on the vc is bright, 2d popup is not particularly dark (i recall the rxp v1 pop up looked darker at night). the 2nd one here is with brightness=0, maybe button brightness changed but the bezel itself didn't change. the vc gauge is unchanged as well, bright gray bezel.
  23. in addition to the issue above, i'm not able to change the bezel brightness. according to the manual on p6, the bezel brightness can be adjusted independently from screen brightness (screen brightness slider works). right now, the bezel is full bright emmissive at night when the gauge is placed in the vc (not pop up but on the panel surface). ideally, the bezel should be pretty much black with button backlight (used to be green on the original rxp gauge but now white?). thanks.
  24. here are the relevant portions of panel.cfg, you'll want to make sure the 2d pop up windowXX are unique and match up. be sure to use the rxp config menu to enable xfill. Window03=Reality XP GNS Unit 1 (managed) Window04=Reality XP GNS Unit 2 (managed) [Window03] size_mm=100,100 window_pos=0.751661,0.000000 //window_size=0.128339,0.169677 window_size=0.260417,0.333333 visible=1 always_visible=1 zorder=99 background_color=0,0,0 ident=15531 gauge00=rxpGNS2!GNS_530_1, 0, 0,100,100 [Window04] size_mm=100,100 window_pos=0.751661,0.333333 //window_size=0.128339,0.169677 window_size=0.260417,0.333333 visible=1 always_visible=1 zorder=99 background_color=0,0,0 ident=15532 gauge00=rxpGNS2!GNS_530_2, 0, 0,100,100 [Vcockpit01] Background_color=0,0,0 size_mm=1024,1024 visible=0 pixel_size=1024,1024 texture=$Panel_1 gauge00=GAUGEPC12EADI!Gauge_EFIS50_EADIVC, 0, 0,512,480 gauge01=GAUGEPC12EHSI!Gauge_EFIS50_EHSIVC, 0,481,512,480 gauge02=PC12CAR!ToggleEFIS, 0, 0,512,480 gauge03=rxpGNS2!GNS_530_1, 512, 0, 510,372 //gauge04=GPS530_3D_PC12!GPS_5302_3D, 512,373, 510,372 gauge04=rxpGNS2!GNS_530_2, 512,373, 510,372 gauge05=PC12CAR!ToggleCAR530, 512, 0, 510, 32 gauge06=GAUGEPC12!Gauge_UPDATE, 0, 0, 1, 1 gauge07=CarSound_PC12!CarSound, 0,0,5,5 gauge08=PC12_EX500!EX500, 0,0,1,1 gauge09=PC12_Cabin_alt!C340_PRESS, 0,0,1,1 [Vcockpit04] Background_color=0,0,0 size_mm=512,512 visible=0 pixel_size=512,512 texture=$Panel_4 //gauge00=EX500_PC12!EX500_config, 0, 0, 1, 1 //gauge01=EX500_PC12!EX500_3D, 0, 0, 513,409 gauge00=RolASNRadar!ORadGauge, 99, 70, 314, 251, sweep|beam|icing //gauge02=EX500_PC12!EX500_Update, 0, 0, 1, 1 //gauge03=PC12CAR!ToggleCARG500, 0, 0, 513, 32