Jump to content
The simFlight Network Forums
johnk515

PMDG 737 taxi light problem in P3D V4.5

Recommended Posts

I've been flying my PMDG 737 for sometime in P3D v4.5 with the latest FSUIPC 5.  Haven't done any night flights until lately.  I discovered that when I turned on the taxi lights, they weren't showing on the ground.  From the external view, when I turned on the taxi lights, they came on for about a second then went off.  My other lights work fine.  My PMDG 777 all exterior lights work.  I use the control number 69749 from the pmdg pdf file for the 737.  I've also, turned off that switch and just clicked on the switch in the ovh in vc, but still goes off after a second.  Over at the PMDG forum they said I should move the FSUIPC temp to see it works then.  The thing is that I use FSUIPC for all my commands.  So would I need to activate the controlers in p3d v4 and would all I have to move temporally the ini file?  Or would I need to move any others to test it without FSUIPC.  I just thought that having the taxi lights unassigned to FSUIPC would be enough without basically removing.  Or do you have anything I could check that could fix the problem. 

Share this post


Link to post
Share on other sites

Hi,

the control you use is correct.

Would be as well good to have have some more information, please attach or copy and paste the content, after a closed session, of your FSUIPC5.log and FSUIPC5.ini files.

To disable you can just rename it to i.e. FSUIPC5OFF.dll (or what ever you like) then it will not be loaded. In case the LDG Light switches also back to OFF when using the VC then something else is switching it OFF, maybe some Lua plugin running that is doing it? That would be then as well disabled whem FSUIPC is not running.

You cal also activate event logging in FSUIPC but only for a short session and switch LDG Light. Then close the session before the FSUIPC5.log file gets too long.

Thomas

Share this post


Link to post
Share on other sites

The PMDG support team had me start the 737 in the default mode with engines running.  I have been using a start that had just the ground power running.  When I did, it still does the same thing, comes on 1 second later turns off. Here's the log:

********* FSUIPC5, Version 5.151 (21st February 2019) by Pete Dowson *********
Running inside Prepar3D v4
Module base=7FF8978E0000
Windows 10 Pro 64 Bit reported as Build 18362, Release ID: 1903 (OS 10.0)
Prepar3D.exe version = 4.5.11.29713
Reading options from "D:\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.ini"
Checking the Registrations now ...
User Name="John Kramer"
User Addr="snookums.51@gmail.com"
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
       16 System time = 10/09/2019 15:37:57
       16 FLT path = "C:\Users\Dad\Documents\Prepar3D v4 Files\"
       16 Using DialogMode
       31 FS path = "D:\Lockheed Martin\Prepar3D v4\"
      187 ---------------------- Joystick Device Scan -----------------------
      187 Product= Saitek X52 Flight Control System
      187    Manufacturer= Saitek
      187    Vendor=06A3, Product=075C (Version 1.0)
      562    GUIDs returned for product: VID_06A3&PID_075C:
      562       GUID= {6CD7B660-EDE8-11E5-8001-444553540000}
      562       Details: Btns=34, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U255,V255,X2047,Y2047,Z255
      562 Product= Model 2238-CON
      578    Manufacturer= Desktop Aviator
      578    Serial Number= 1TA018E0
      578    Vendor=16D0, Product=0621 (Version 0.1)
      578    GUIDs returned for product: VID_16D0&PID_0621:
      578       GUID= {8B580F80-AF53-11E7-8001-444553540000}
      578       Details: Btns=31, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
      578 Product= Model 2120/2125
      578    Manufacturer= Desktop Aviator
      578    Serial Number= DTpc03d9
      578    Vendor=16D0, Product=0480 (Version 0.1)
      578    GUIDs returned for product: VID_16D0&PID_0480:
      578       GUID= {40B196F0-6FBA-11E7-8002-444553540000}
      578       Details: Btns=20, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
      578 Product= Saitek Pro Flight Rudder Pedals
      594    Manufacturer= Saitek
      594    Vendor=06A3, Product=0763 (Version 1.0)
      594    GUIDs returned for product: VID_06A3&PID_0763:
      594       GUID= {D27F8600-EDE3-11E5-8001-444553540000}
      594       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
      594 Product= DP3T Emulator
      594    Manufacturer= Desktop Aviator
      594    Serial Number= zzA0dxxx
      594    Vendor=16D0, Product=0747 (Version 0.2)
      594    GUIDs returned for product: VID_16D0&PID_0747:
      594       GUID= {40B16FE0-6FBA-11E7-8001-444553540000}
      594       Details: Btns=30, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
      594 -------------------------------------------------------------------
      625 Device acquired for use:
      625    Joystick ID = 0 (Registry okay)
      625    0=X52 H.O.T.A.S.
      625    0.GUID={6CD7B660-EDE8-11E5-8001-444553540000}
      625 Device acquired for use:
      625    Joystick ID = 4 (Registry okay)
      625    4=Model 2238-CON
      625    4.GUID={8B580F80-AF53-11E7-8001-444553540000}
      625 Device acquired for use:
      625    Joystick ID = 3 (Registry okay)
      625    3=Model 2120/2125
      625    3.GUID={40B196F0-6FBA-11E7-8002-444553540000}
      625 Device acquired for use:
      625    Joystick ID = 1 (Registry okay)
      625    1=Mad Catz Pro Flight Rudder Pedals
      625    1.GUID={D27F8600-EDE3-11E5-8001-444553540000}
      625 Device acquired for use:
      625    Joystick ID = 2 (Registry okay)
      625    2=DP3T Emulator
      625    2.GUID={40B16FE0-6FBA-11E7-8001-444553540000}
      625 -------------------------------------------------------------------
     1422 LogOptions=00000000 00000001
     1422 -------------------------------------------------------------------
     1422 SimConnect_Open succeeded: waiting to check version okay
     1422 Opened separate AI Traffic client okay
     1422 ### PDKmodeHelper callback registered
   242922 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.5.11.29713 (SimConnect: 4.5.0.0)
   242937 Initialising SimConnect data requests now
   242937 FSUIPC Menu entry added
   242937 ... Using Prepar3D with Professional License
   242984 C:\Users\Dad\Documents\Prepar3D v4 Files\KAVC.fxml
   242984 D:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Carenado Commander 114\Car_Commander114.air
   329031 ### The user object is 'AC11 Commander 114 - Deep Blue'
   329031 ### Mode is NORMAL
   329578 ### Mode: PAUSE on
   527453 Loading Complete ...
   527516 ### Mode is NORMAL
   530500 Aircraft loaded: running normally now ...
   530547 User Aircraft ID 1 supplied, now being used
   530812 System time = 10/09/2019 15:46:48, Simulator time = 15:43:25 (22:43Z)
   531594 Aircraft="AC11 Commander 114 - Deep Blue"
   536812 -------------------- Starting everything now ----------------------
   536859 ASN active function link set
   536859 Ready for ActiveSky WX radar with additional data
   538000 Advanced Weather Interface Enabled
   700922 D:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.air
   700922 PMDG 737 offsets enabled
   711453 Aircraft="Boeing 737-8K2NGX KLM Royal Dutch Airlines Winglets"
   745687 **** Restarting traffic scanning due to non-reception ****
   751953 Sim stopped: average frame rate for last 40 secs = 22.8 fps
   751953    Max AI traffic was 41 aircraft (Deleted 0)
   751953 -------------------------------------------------------------------
   914516 Sim stopped: average frame rate for last 109 secs = 29.1 fps
   914516    Max AI traffic was 42 aircraft (Deleted 0)
   914516 -------------------------------------------------------------------
   918344 === Closing session: waiting for DLLStop to be called ...
   947031 === DLLStop called ...
   947031 === Closing external processes we started ...
   948031 === About to kill any Lua plug-ins still running ...
   948172 === Closing global Lua thread
   949187 === About to kill my timers ...
   949391 === Restoring window procs ...
   949391 === Unloading libraries ...
   949391 === stopping other threads ...
   949391 === ... Button scanning ...
   949484 === ... Axis scanning ...
   949594 === Releasing joystick devices ...
   949594 === Freeing macro memory
   949594 === Removing any offset overrides
   949594 === Clearing any displays left
   949594 === NOTE: not calling SimConnect_Close ...
   949594 === AI slots deleted!
   949594 === Freeing button memory ...
   949594 === Deleting wxstationlist.bin file ...
   949594 === Closing my Windows ...
   949594 === Freeing FS libraries ...
   950594 === Closing devices ...
   950594 === Closing the Log ... Bye Bye! ...
   950594 System time = 10/09/2019 15:53:47, Simulator time = 15:45:41 (22:45Z)
   950594 *** FSUIPC log file being closed
Minimum frame rate was 9.7 fps, Maximum was 29.9 fps
Average frame rate for running time of 164 secs = 27.6 fps
Maximum AI traffic for session was 42 aircraft
Memory managed: 71 Allocs, 70 Freed
********* FSUIPC Log file closed ***********
By the way the landing lights are working fine now.  So it's just the taxi lights.  Which worked just fine in FSX:SE and my PMDG 777 works fine using it's custom controls.  I'm at a loss.  And if I use the mouse to turn on and off the taxi lights, when I turn it on the lights go on then off, but the switch is still on. I attached my ini file.

FSUIPC5.ini

Share this post


Link to post
Share on other sites

Hi,

presumably, from your ini, your taxi lights are assigned to a button that stays in when pressed (i.e. no release), and then releases when pressed again?

i.e.
112=P4,9,C69749,1     -{Custom control: <69749>}-
113=U4,9,C69749,0     -{Custom control: <69749>}-

You have the same on your 777 but on a different button, which, as you say,  works for you, which is strange. Also, if the same happens when you activate in the sim overhead, then it does sound like a PMDG issue. 

There are no events in your log - did you activate this as advised by Thomas? If not, can you activate logging for 'Button and key operations' and also 'Events (non-axis controls)' (from FSUIPC's Logging tab), and produce another log file that shows the taxi lights being activated.

John

Share this post


Link to post
Share on other sites

I updated to the new FSUIPC5.  I also ran a repair on my P3D v4.5.  Then when I loaded up my PMDG 737, the taxi lights were now working.  I believe that doing the repair was what fixed the lights.  I don't know if the update of FSUIPC did it, all I now is all is working. Oh, and if you still want the log I can send it to you, but by then they were working.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.