jordanal

I now believe both the v3.707 and still in the 3.708 have issus wit the PMDG FMC and the radios. While using these betas, the PMDG FMC will not tansition from LNAV to ILS guidance much as it did perfectly well up and through FSUPC v3.7 final. I have posted this issue in a new thread here on Pete's forum as well as in the PMDG forum.

Pete, I've posted the following over in PMDG's forum as well. I believe the last couple of FSUIPC Betas have issues with the PMDG FMC probably due to some unique coding they did under the hood. FSUIPC 3.3707 Broke VOR2 DME (~3200nm) seems fixed with 3.708 FSUIPC 3.708 Broke FMC transistion from LNAV to ILS guidance on final I have yet to roll back to v3.7 final due to the fact that I have a lot of aircraft-specific maps that from what I understand are not backward compatible after using 3.70x beta. I recomend that you and PMDG chat about the latest beta before they go final. I believe there are underlying issues involved the may create a headache for us users, PMDG and yourself. Posted in the PMDG forum on AVSIM: I'm pretty sure the latest beta versions of Pete's wonderful FSUIPC utility is breaking the PMDG 747 (and maybe the 737) FMC. In version 3.707 Beta, we noted that the VOR2 DME distance was permenently set ~3200nm. Pete didn't understand why that was but managed to fix it with v3.708 Beta. Now, when transitioning from LNAV to ILS approach guidance, the FMC vector gets all messed up. I have to swich to HDG until I'm right on top of the ILS approach path. I suspect that due to some unique PMDG coding under the hood, Pete is making changes that may adversely affect the PMDG FMC in the coming release. I would like to recommend that PMDG formally get in touch with Pete before he formally releases this version. FWIW, I have not tried to roll back to v3.7 (Final) because his new betas fixed some issues with the aircraft-specific maps that are rummored to not be backward compatible. AL | KCHS - Charleston AFB/Intl | USAF 437AW (~53 C-17's) FS9/Game Rig: AMD64-4000+ SanDiego OC=210/420/2520 | Asus A8N-SLI Deluxe | Corsair TwinX2048-3200C2PT (2x1GB) 2.5-3-3-8/1T@2.8v | Evga NV 7900GT v91.47 (1280x1024x32/4xAA/16xAF/High-Quality) | Enermax 550W PSU | Thermalright XP-120(mm) HSF | NV 1GB LAN | NV SATA-I Raid-0 223GB (3x80GB Samsung) (WinXPx64/Games) | NV SATA-II WD 320GB (Backups) | IDE-0 80GB Samsung (Archive) | Realtek AC'97 5.1 Surround | CH Yoke, TQ, & Pedals | FS9.1 (Settings max'd/60-50Vis/No-Shadows/20FPS) | WideFS v6.7 | FSUIPC v3.7 | FSGenesis Mesh (All) | PMDG (All) | PAI (All) | FSPassengers | FSBuild2 | Etc FS9 Support Rig: AMD3200+ | Gigabyte GA-7NNXP | Leadtek NV 5900 | Corsair TwinX1024-3200 (2x512MB) | Intel 1GB LAN | SiI3112 SATA-I 80GB Samsung | IDE-0 80GB IBM | JustCom 4port KVM | WideClient | GE-Pro v2 | ActiveSky v6 (512x32bit/Wx Influanced)| Radar Contact v4.2 | FS Real Time | FS Flight Keeper | FS Commander | AI Smooth

Well, I think I've solved my checksum errors. The problem was a newly installed McAfee Personal Firewall Plus application on the 32bit WideClient PC only. Comcast, a major U.S. broadband cable provider here on the East coast of the US recently started offering free subscriptions to McAfee antivirus, personal security, and personal firewall. After swapping LAN cables, reseting My Netgear Router/switch, uninstalling and reinstalling my NForce2 MB chipset/Ethernet drivers, I discovered that when I reinstalled all three of the McAfee products mentioned above, my ASv6 station writing slows down and I start getting the checksum errors as noted in the WideFS server log again. I then uninstalled only the Personal Firewall Plus product and my problems and log events disappeared. Comcast is a major provider and it won't surprise me if others start seeing similar problems using this firewall product. I hope my findings here benefit anyone else who start having these checksum errors. v/r, AL

Nope, WinXP x64 went final in March of '05 and has been running great for almost a year now on my rig. Checkout the Hardware forums on Avism under the FS general discussion. This is not new, or beta, but quickly becomeing routine for the AMD64 product line. You are correct that WinXP 64 does require specific driviers but that's it. This OS includes a Windows-on-Windows32 subsystem (WoW32) which allows most 32 bit applications to run fine on the 64bit OS. Anyway, all my drivers inlcuding the Nvidia NForce and Geforce drivers have been final for a while now and have already gone through several itteraions. FS actually runs a bit smoother on the Win64 OS as noted by several others on the AVSIM hadware forum. 1GB RAM is fine even for AMD64. No difference noted. Just as with the 32bit version more RAM is always better. Anyway, my AMD64 system, which is quite standard now, is not the issue here. I'll try changing the LAN cable tonight. I appreciate you taking the time to look through my logs. Al

Thanks Pete; I'm at work right now so I can't provide answers. To everything right now. Sorry about not posting the WideClient Log. You were correct that was my intention, but a couple of beers and sleepy-eyes messed-up my copy-&-past abilities. When you mentioned network issues, it did jar my memory a bit. A couple of weeks ago, I physically relocated my WideFS PC which ment undoing all the cables. One thing I do explicitly remember was changing the LAN cable from the switch to the WideFS PC. I hoping that cable I used might be slightly faulty. Now I have to wait all-day before I can get home and test my theory. I remoted home and gathered all the log files and ini files for you and ziped them up for you as an attachment below. WideFS PC: WinXP x64-bit Pro | AMD-64 3500+ | Corsair XMS 1GB RAM (2x512) | Asus A8N-SLI Deluxe MB | Nvidia NF4 SATA Raid-0 x3 80GB) | EVGA Nvidia 6800GT PCI-x | NF4 Chipset LAN 100MB | FS9.1 FR 25 FPS | FS9.1 Joysitcks disabled | FSUIPC v3.537 AXIS & Buttons Enable w/Aircraft specfic settings. WideClient PC: WinXP Pro (32bit) | AMD 3200+ | Corsair XMS 1GB RAM (2x512) | Gigabyte A7NNXP MB | 2 x 80GB IDE | EVGA Nvidia 5900 | NF2 100MB LAN jordanal - WideFS Checksum Error logs.zip

Hi Pete, I've been using your latest beta of FSUIPC v3.536/7 and recently noticed how slow my ASv6 sessions have been updating FS9 weather. ASv6 is on my Wideclient PC and I've retried the last two versions of the ASv6 updates. I do know for a fact that my network is solid and have no problems. All Windows shares work fine and no network event-log entries noted. I've been running this same 100MB LAN for several years with WideFS and nothing has recently changed as far as the network itself is concerned. I should also mention that a few times, Flightsim Flightkeeper, also in the WideClient PC, has also thrown an error saying that FS9 was not properly initialized when in fact, FS9 was up and running fine on the WideFS server. Anyway, I've tried reinstaling ASv6 several times and I've tried different FS9 startup situations. Can you point me in a good direction as to what to troubleshoot next? I'm starting to think that there's something going on here between the FSUIPC beta 3.536 and WideFS. I've put a lot of work into configuring my new AXIS facilites in the FSUIPC.ini file so dropping back to v3.53 or earlier really isn't an option if I can avoid it, even for troubleshooting. Thanks for your help. Al BTW, I removed many of the duplicate line errors to save space in this post. ********* WideServer.DLL Log [version 6.51] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 27/02/06, Time 21:04:42.549: Server name is XPGAMER 98937 Initialising TCP/IP server 98953 Initialising IPX/SPX server 98953 IPX/SPX socket() failed [Error=10044] Socket type not supported 98953 Failed to start IPX/SPX Server 99031 Incoming connection Accepted ok (skt=7928) 99109 Connected to computer "XPSERVER" running WideClient version 6.510 (skt=7928) 99109 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=1246 (time=0) 99266 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=384 (time=533406) 99797 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=1491 (time=533906) 99906 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=162 (time=534015) 100031 Broadcasting service every 1 mSecs 100391 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=189 (time=534500) 101969 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=371 (time=536062) 103047 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=175 (time=537140) 103172 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=1306 (time=537250) 103734 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=298 (time=537828) 105094 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=973 (time=539219) 105172 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=259 (time=539281) 106219 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=259 (time=540312) 268750 Closing down now ... Memory managed: Offset records: 39 alloc, 39 free Total number of received blocks having sumcheck errors = 248 Throughput maximum achieved: 26 frames/sec, 1802 bytes/sec Throughput average achieved for complete session: 7 frames/sec, 315 bytes/sec Average receive rate from "XPSERVER": 2 frames/sec, 3153 bytes/sec ********* Log file closed ********* FSUIPC v3.537 LOG: ********* FSUIPC, Version 3.537 by Pete Dowson ********* Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL) User Name="Removed For POST" User Addr="Removed For POST" FSUIPC Key is provided WideFS Key is provided Module base=61000000 ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E WeatherOptions(Orig)=4000B7AF[4000B7AF] InitDelay: 0 seconds WeatherReadInterval=4 LogOptions=00000001 DebugStatus=255 3859 System time = 21:04:42 3859 \\XPGAMER\E\Flight Simulator 9\ 3875 C:\Program Files (x86)\ScreenGrab\ScreenGrab.exe 3922 System time = 21:04:42, FS2004 time = 12:00:00 (00:00Z) 13765 C:\Documents and Settings\jordana\My Documents\Flight Simulator Files\KIPT - Default.flt 13765 AIRCRAFT\beech_baron_58\FSD_B58TC.air 13968 Aircraft="Beech Baron 58" 19015 Module [M1] identified = "sb3gaugebridge.dll" 19015 Module [M1] "sb3gaugebridge.dll" access registration is okay 19015 Module [M2] identified = "ActiveRadar.dll" 19015 Module [M2] "ActiveRadar.dll" access registration is okay 67765 C:\Documents and Settings\jordana\My Documents\Flight Simulator Files\UI generated flight.flt 67968 Clear All Weather requested: external weather discarded 69625 Advanced Weather Interface Enabled 98172 Traffic File #18 = "projectai flightplans\scenery\traffic_mrai_wi04-05_federalexpress" 98172 Traffic File #17 = "scenery\world\scenery\traffic-ga" 98781 Traffic File #224 = "projectai flightplans\scenery\traffic_pai_vir" 98875 Traffic File #22 = "projectai flightplans\scenery\traffic_pai_aal" 98875 Traffic File #74 = "projectai flightplans\scenery\traffic_pai_dal" 99000 Traffic File #159 = "projectai flightplans\scenery\traffic_pai_nwa" 99047 Traffic File #210 = "projectai flightplans\scenery\traffic_pai_usa" 99640 Traffic File #25 = "projectai flightplans\scenery\traffic_pai_aca" 99750 Traffic File #48 = "projectai flightplans\scenery\traffic_pai_aza" 99875 Traffic File #67 = "projectai flightplans\scenery\traffic_pai_coa" 100000 Traffic File #192 = "projectai flightplans\scenery\traffic_pai_swa" 100234 Traffic File #209 = "projectai flightplans\scenery\traffic_pai_ups" 100484 Traffic File #75 = "projectai flightplans\scenery\traffic_pai_dals" 100609 Traffic File #79 = "projectai flightplans\scenery\traffic_pai_dlh" 100718 Traffic File #86 = "projectai flightplans\scenery\traffic_pai_egf" 101000 Traffic File #193 = "projectai flightplans\scenery\traffic_pai_swr" 101047 Traffic File #208 = "projectai flightplans\scenery\traffic_pai_ual" 107843 NWI weather clear actioned 107843 External weather discarded 271609 System time = 21:09:06, FS2004 time = 14:29:21 (19:29Z) 271609 *** FSUIPC log file being closed Memory managed: 1257 Allocs, 1834 Freed ********* FSUIPC Log file closed **** WideClient LOG: ********* FSUIPC, Version 3.537 by Pete Dowson ********* Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL) User Name="Removed For POST" User Addr="Removed For POST" FSUIPC Key is provided WideFS Key is provided Module base=61000000 ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E WeatherOptions(Orig)=4000B7AF[4000B7AF] InitDelay: 0 seconds WeatherReadInterval=4 LogOptions=00000001 DebugStatus=255 3859 System time = 21:04:42 3859 \\XPGAMER\E\Flight Simulator 9\ 3875 C:\Program Files (x86)\ScreenGrab\ScreenGrab.exe 3922 System time = 21:04:42, FS2004 time = 12:00:00 (00:00Z) 13765 C:\Documents and Settings\jordana\My Documents\Flight Simulator Files\KIPT - Default.flt 13765 AIRCRAFT\beech_baron_58\FSD_B58TC.air 13968 Aircraft="Beech Baron 58" 19015 Module [M1] identified = "sb3gaugebridge.dll" 19015 Module [M1] "sb3gaugebridge.dll" access registration is okay 19015 Module [M2] identified = "ActiveRadar.dll" 19015 Module [M2] "ActiveRadar.dll" access registration is okay 67765 C:\Documents and Settings\jordana\My Documents\Flight Simulator Files\UI generated flight.flt 67968 Clear All Weather requested: external weather discarded 69625 Advanced Weather Interface Enabled 98172 Traffic File #18 = "projectai flightplans\scenery\traffic_mrai_wi04-05_federalexpress" 98172 Traffic File #17 = "scenery\world\scenery\traffic-ga" 98781 Traffic File #224 = "projectai flightplans\scenery\traffic_pai_vir" 98875 Traffic File #22 = "projectai flightplans\scenery\traffic_pai_aal" 98875 Traffic File #74 = "projectai flightplans\scenery\traffic_pai_dal" 99000 Traffic File #159 = "projectai flightplans\scenery\traffic_pai_nwa" 99047 Traffic File #210 = "projectai flightplans\scenery\traffic_pai_usa" 99640 Traffic File #25 = "projectai flightplans\scenery\traffic_pai_aca" 99750 Traffic File #48 = "projectai flightplans\scenery\traffic_pai_aza" 99875 Traffic File #67 = "projectai flightplans\scenery\traffic_pai_coa" 100000 Traffic File #192 = "projectai flightplans\scenery\traffic_pai_swa" 100234 Traffic File #209 = "projectai flightplans\scenery\traffic_pai_ups" 100484 Traffic File #75 = "projectai flightplans\scenery\traffic_pai_dals" 100609 Traffic File #79 = "projectai flightplans\scenery\traffic_pai_dlh" 100718 Traffic File #86 = "projectai flightplans\scenery\traffic_pai_egf" 101000 Traffic File #193 = "projectai flightplans\scenery\traffic_pai_swr" 101047 Traffic File #208 = "projectai flightplans\scenery\traffic_pai_ual" 107843 NWI weather clear actioned 107843 External weather discarded 271609 System time = 21:09:06, FS2004 time = 14:29:21 (19:29Z) 271609 *** FSUIPC log file being closed Memory managed: 1257 Allocs, 1834 Freed ********* FSUIPC Log file closed ****

Well this time I did as you suggested, unassigned axis, disabled joystick and then removed the joysticks from the fs9.cfg file. So far the devices have stayed gone. As for the numerous times I have to hit the "ignore axis" button, this hasn't improved much. No, I'm not using raw mode. In the CH-Products calibartion utility, the raw numbers 0-255 look solid so I think it might be too sensitive in FSUIPC. Maybe something we can adjust ourselvs with an added option to the axis assignemtns tab? BTW, so far it appears that you can't add comments to the end of axis assignment. I tried to use the same commenting method used in the buttons and keys sections but FSUIPC wipes the axis comments clean after every save. Will this be added? v/r, AL

Pete, So far the axis configuration facility in the FSUIPC 3.536 seems to work well. The axis seem more precise and I'm grateful to finally have an axis assigned as a gear lever on my CH Yoke. GOOD JOB! I am surprised how many times I have to hit "Ignore Axis" to start calibratinig another device but it does seem to work. Question about the removal of existing axis in the fs9.cfg file; I have the CH Products USB Yoke, ThrottleQuad, & Pedals along with a Logitech gamepad. As recommended, I deleted the devices.cfg file, removed the existing axis in my fs9.cfg file, and turned off (unchecked) "Enable Joystick." After configuring all three CH devices using "submit to FS," as I was shutting down for the evening last night when I noticed that there were a bunch of axis assignemnts in my fs9.cfg file again. Were these put back by FSUIPC because I was "submitting to FS" or did FS incorreclty pickup the devices again on its own accord? I quickly read the "updated doc" last night so if I missed an important point again as in my previous thread (LOL), just tell me to go back RTFM, LOL :) BTW, to fix the issue with the devices.cfg file whereby new axis are still picked up by FS, would having only a "GENERIC" section in the file with some eroneous assignments solve the problem? v/r, AL

Yup, sure enough, the module I pulled down was from 12:07am. Re-downloading the zip again now. Thanks for the heads-up... v/r, AL

LOL, OK Pete, fair enough and thanks for a timely reply. As soon as you mentioned the "combining" of sections for buttons and keys I realized where I went wrong in my logic and that I did read that info in the Advanced users doc (yes, I actually read the manual, LOL) I understand about the starting with one being too big of change, it just seemed odd at first when my buttons weren't matching my ini file settings. LOL, OK about axis-0, I'm gonna create labels for them starting with zero, LOL... :D

Hi Pete, Thanks again for supporting FSim all these years. I just started setting up "Aircraft Specific" settings (w/shortaircraftnameOK enabled) in the ini file using FSUIPC 3.53 registered. As you can see ,I did one section for the PMDG 747 and 737 each using the joystickcalibration and buttons sections. The problem is, when I come back into the FSUIPC GUI, the joysticks tab properly indicates "aircraft specific" as being checked but the Buttons tab does not. Now, if I then check the "aircraft specific" box on the Buttons tab, the shortname does appear on the FSUIPC GUI title bar and buttons seem to be assigned, but for some reason "aircraft specific" settings are not on by default even though the section in the ini file seems to be properly recongnized. I hope I've explained this well enough, but if I haven't, let me know and I'll try to rephrase. Oh, one other thing; it would also be easier if the buttons assignments in the ini file started with one instead of zero. It took me a few minutes to realize that in order to identify my actual, physical buttons on the devices it was necessary to add 1 to the button assignemnts as listed in the ini. No joystick I've ever used has a button zero, :wink: Is it possible to change this sometime in the future? BTW, I can't wait 'till you have the aircraft specific axis assignemnts facitlity in FSUIPC, that'll be absolutly fabulous :) Pertinent ini sections as follows: ShortAircraftNameOk=Yes [JoystickCalibration.B737-] ExclThrottleSet=No SepRevsJetsOnly=No FlapsSetControl=0 ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 Aileron=-16193,-582,444,16065 SlopeAileron=5 Elevator=-16193,-453,444,16065 SlopeElevator=5 Rudder=-16066,0,0,16192 SlopeRudder=5 LeftBrake=-16066,16192 SlopeLeftBrake=5 RightBrake=-16066,16192 SlopeRightBrake=5 Throttle1=-16256,-14321,-13418,16256 Throttle2=-16193,-14774,-14000,16192 Spoilers=-16193,16192 Flaps=-16129,16129 [buttons.B737-] 1=P4,1,K65,12 ;TAB+A, Yoke, B 2 2=P4,4,C66079,0 ;GEAR_UP, Yoke, B 5 3=P4,5,C66080,0 ;GEAR_DOWN, Yoke, B 6 4=P4,12,K82,9 ;Shft+R, Yoke, B 13 5=P4,15,C65789,0 ;SIM_RATE_INC, Yoke, B 16 6=P4,16,C65790,0 ;SIM_RATE_DECR, Yoke, B 17 7=P4,19,C65656,0 ;ZOOM_OUT, Yoke, B 20 8=P4,20,C65655,0 ;ZOOM_IN, Yoke, B 21 9=R1,0,K80,11 ;Ctrl+Shft+P, THQ, B 1 10=R1,1,K80,14 ;Ctrl+TAB+P, THQ, B 2 11=R1,2,K83,11 ;Ctrl+Shft+S, THQ, B 3 12=R1,3,K83,14 ;Ctrl+TAB+S, THQ, B 4 13=R1,4,K65,11 ;Ctrl+Shft+A, THQ, B 5 14=R1,5,K65,14 ;Ctrl+TAB+A, THQ, B 6 15=R1,6,K66,11 ;Ctrl+Shft+B, THQ, B 7 16=R1,7,K66,14 ;Ctrl+TAB+B, THQ, B 8 17=P1,8,K72,10 ;Ctrl+H, THQ, B 9 18=P1,9,K78,10 ;Ctrl+N, THQ, B 10 19=P1,10,C65751,0 ;LANDING_LIGHTS_TOGGLE, THQ, B 11 20=P1,11,C66240,0 ;TOGGLE_TAXI_LIGHTS, THQ, B 12 21=R1,12,K90,11 ;Ctrl+Shft+Z, THQ, B 13 22=R1,13,K90,14 ;Ctrl+TAB+Z, THQ, B 14 23=R1,14,K72,11 ;Ctrl+Shft+H, THQ, B 15 24=R1,15,K72,14 ;Ctrl+TAB+H, THQ, B 16 25=R1,16,K86,11 ;Ctrl+Shft+V, THQ, B 17 26=R1,17,K86,14 ;Ctrl+TAB+V, THQ, B 18 27=P1,18,K65,10 ;Ctrl+A, THQ, B 18 28=P1,19,K80,10 ;Ctrl+P, THQ, B 20 29=P1,20,K86,9 ;Shft+V, THQ, B 21 30=P1,21,K86,10 ;Ctrl+V, THQ, B 22 31=P1,22,C65560,0 ;STROBES_TOGGLE, THQ, B 23 [JoystickCalibration.747-400] ExclThrottleSet=No SepRevsJetsOnly=No FlapsSetControl=0 ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 Aileron=-16193,-582,444,16065 SlopeAileron=5 Elevator=-16193,-453,444,16065 SlopeElevator=5 Rudder=-16066,0,0,16192 SlopeRudder=5 LeftBrake=-16066,16192 SlopeLeftBrake=5 RightBrake=-16066,16192 SlopeRightBrake=5 Throttle1=-16256,-14321,-13418,16256 Throttle2=-16193,-14774,-14000,16192 Throttle3=-16193,-14645,-13871,16192 Throttle4=-16256,-14708,-13934,16256 Spoilers=-16193,16192 Flaps=-16129,16129 [buttons.747-400] 1=P4,1,K65,12 ;TAB+A, Yoke, B 2 2=P4,4,C66079,0 ;GEAR_UP, Yoke, B 5 3=P4,5,C66080,0 ;GEAR_DOWN, Yoke, B 6 4=P4,12,K82,9 ;Shft+R, Yoke, B 13 5=P4,15,C65789,0 ;SIM_RATE_INC, Yoke, B 16 6=P4,16,C65790,0 ;SIM_RATE_DECR, Yoke, B 17 7=P4,19,C65656,0 ;ZOOM_OUT, Yoke, B 20 8=P4,20,C65655,0 ;ZOOM_IN, Yoke, B 21 9=R1,0,K80,11 ;Ctrl+Shft+P, THQ, B 1 10=R1,1,K80,14 ;Ctrl+TAB+P, THQ, B 2 11=R1,2,K83,11 ;Ctrl+Shft+S, THQ, B 3 12=R1,3,K83,14 ;Ctrl+TAB+S, THQ, B 4 13=R1,4,K65,11 ;Ctrl+Shft+A, THQ, B 5 14=R1,5,K65,14 ;Ctrl+TAB+A, THQ, B 6 15=R1,6,K66,11 ;Ctrl+Shft+B, THQ, B 7 16=R1,7,K66,14 ;Ctrl+TAB+B, THQ, B 8 17=P1,8,K72,10 ;Ctrl+H, THQ, B 9 18=P1,9,K78,10 ;Ctrl+N, THQ, B 10 19=P1,10,C65751,0 ;LANDING_LIGHTS_TOGGLE, THQ, B 11 20=P1,11,C66240,0 ;TOGGLE_TAXI_LIGHTS, THQ, B 12 21=R1,12,K90,11 ;Ctrl+Shft+Z, THQ, B 13 22=R1,13,K90,14 ;Ctrl+TAB+Z, THQ, B 14 23=R1,14,K72,11 ;Ctrl+Shft+H, THQ, B 15 24=R1,15,K72,14 ;Ctrl+TAB+H, THQ, B 16 25=R1,16,K86,11 ;Ctrl+Shft+V, THQ, B 17 26=R1,17,K86,14 ;Ctrl+TAB+V, THQ, B 18 27=P1,18,K65,10 ;Ctrl+A, THQ, B 18 28=P1,19,K80,10 ;Ctrl+P, THQ, B 20 29=P1,20,K86,9 ;Shft+V, THQ, B 21 30=P1,21,K86,10 ;Ctrl+V, THQ, B 22 31=P1,22,C65560,0 ;STROBES_TOGGLE, THQ, B 23

I have been seeing the same problem, Landing-light on, RCv3 text off and vice-versa but I think I may have found a workaround for this problem. I re-displayed the Advdisp window ontop of the 738 2D-panel last night just before I took off from EGLL, (usually have the window "always hidden" as I use Text-Display across a WideFS connection). I then right clicked on the Advdisp window and selected "show multiple lines" and then re-hid the Advdisp window. Low-and-behold I got my RCv3 text back even with the landing-lights on. The only drawback seems to be the green-text window (usually used for AS2004 metar text updates) is now taller (5 or 6 empty lines) than it would normally be. This seemed to work flawlessly on a 8 hour flight from EGLL to OMDB last night. See if it works for you. FS9.1 PMDG 736/7/8/9 FSUIPC 3.44 WideFS 6.44 AdvDisp 2.131 AS2004.5 163 v/r, Al