Jonahbird Posted August 13, 2012 Report Share Posted August 13, 2012 Hi Pete I have used the full FSUIPC and PFC software for over 10 years. Both have always been indispensable and reliable. My PFC equipment is - Single Professional Console (non USB); Avionics; and rudder pedals. My current software versions are FSUIPC4 4.84 and PFCFSX.dll 4.40 A recent change of unit positions, involving no new hardware and no software changes, has thrown up a strange problem. PFC has disappeared from the FSX Add-ons dropdown menu. The latest PFCFSX.dll remained in the Modules folder. I have tried changing that, but the fault remains. Initially I suspected a faulty cable, but X-Plane "sees" these units and continues to work properly. I think this eliminates any hardware fault. I now suspect a file corruption somewhere, but where? Do you have any ideas? I haven't tried a re-install of FSUIPC yet. Best regards Frank Link to comment Share on other sites More sharing options...
Pete Dowson Posted August 13, 2012 Report Share Posted August 13, 2012 My current software versions are FSUIPC4 4.84 and PFCFSX.dll 4.40 Current FSUIPC is 4.85. PFCFSX.DLL is up to 4.404 but the changes from 4.40 are insignificant. A recent change of unit positions, involving no new hardware and no software changes, has thrown up a strange problem.PFC has disappeared from the FSX Add-ons dropdown menu. The latest PFCFSX.dll remained in the Modules folder. I have tried changing that, but the fault remains. Initially I suspected a faulty cable, but X-Plane "sees" these units and continues to work properly. I think this eliminates any hardware fault. Hardware isn't involved. The PFC DLL does not need to detect the hardware to produce the menu. After all, inititially it allows you to specify the serial port actually in the dalogue so it obviously cannot be dependent on the hardware. I now suspect a file corruption somewhere, but where? That would be very unlikely. Check the signatures (right click, then properties-digital signatures) on the DLLs. If the FSUIPC one was corrupt it wouldn't work at all and you'd get a message. Have you checked the FSUIPC4.LOG file? That's the first step. Show it to me (paste t here). Note that I am on holiday from this evening (Monday) until Friday 24th August. Regards Pete Link to comment Share on other sites More sharing options...
Jonahbird Posted August 13, 2012 Author Report Share Posted August 13, 2012 Thanks for that rapid reponse, Pete. The digital signatories are there, and show as simFlightGmbH timestamped 11/2/2012. FSUIPC4 shows the same name and a date of 17/7/2012. The FSUIPC4.LOG file states:- ********* FSUIPC4, Version 4.84 by Pete Dowson ********* User Name="Frank Jones" User Addr="jonesfrn8@aol.com" FSUIPC4 Key is provided WideFS7 Key is provided Running inside FSX on Windows 7 Module base=61000000 47 System time = 12/08/2012 10:45:32 63 FLT UNC path = "\\RODNEY\Flight Simulator X Files\" 94 Trying to connect to SimConnect Acc/SP2 Oct07 ... 94 FS UNC path = "\\RODNEY\FSX\" 312 LogOptions=00000000 00000001 312 Wind smoothing fix is fully installed 312 G3D.DLL fix attempt installed ok 312 SimConnect_Open succeeded: waiting to check version okay 312 Trying to use SimConnect Acc/SP2 Oct07 14134 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 14134 Initialising SimConnect data requests now 14134 FSUIPC Menu entry added 14165 \\RODNEY\Flight Simulator X Files\BA737 @ gate 102 Gatwick.FLT 14165 \\RODNEY\FSX\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.AIR 71527 Weather Mode now = Theme 71527 \\RODNEY\Users\Frank\AppData\Roaming\Microsoft\FSX\Previous flight.FLT 232254 Sim stopped: average frame rate for last 97 secs = 5.8 fps 305013 System time = 12/08/2012 10:50:37 305013 *** FSUIPC log file being closed Average frame rate for running time of 97 secs = 5.8 fps G3D fix: Passes 20436, Null pointers 0, Bad pointers 0, Separate instances 0 Memory managed: 4 Allocs, 4 Freed ********* FSUIPC Log file closed *********** Does this reveal anything? Regards Frank Link to comment Share on other sites More sharing options...
Pete Dowson Posted August 13, 2012 Report Share Posted August 13, 2012 The FSUIPC4.LOG file states:- ... Does this reveal anything? Yes. the exhange of data with SimConnect is not starting. After the line 14165 \\RODNEY\FSX\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.AIR there should be several standard lines like this, occurring as soon as SimConnect starts providing all the needed data: (This is from my own log). 5906 \\LEFT\FSX\SimObjects\Airplanes\B737_800\Boeing737-800.AIR 91844 System time = 13/08/2012 10:21:31, Simulator time = 10:19:59 (09:19Z) 93469 Starting everything now ... 182562 PFC Menu entry added In your case FSUIPC is not getting off the starting line. It won't be servicing any of the offsets let alone loading other DLLs. Are you starting with FS in Paused or Slew modes perhaps? Could you add these lines to the INI file (in the [General] section), please, and try again. Show me the resulting log: Debug=Please TestOptions=x800 This should give me a bit more information on why it isn't starting. Oh, and please update to 4.85. Regards Pete Link to comment Share on other sites More sharing options...
Jonahbird Posted August 13, 2012 Author Report Share Posted August 13, 2012 Hi Pete First re 4.85. It isn't showing in Schiratti.com. Where can I get it? Regards Frank Link to comment Share on other sites More sharing options...
Ian P Posted August 13, 2012 Report Share Posted August 13, 2012 Hi Frank, The latest versions of Pete's modules can always be found under the "Updated Modules" thread, under "Download Links" at the top of this forum. Here's a direct link: http://forum.simflight.com/topic/66139-updated-modules/ Cheers, Ian P. Link to comment Share on other sites More sharing options...
Pete Dowson Posted August 13, 2012 Report Share Posted August 13, 2012 First re 4.85. It isn't showing in Schiratti.com. Where can I get it? As well as checking in the Download Links subforum (where interrim updates are available too), the version provided by Schiratti is actually 4.85, it is just the wording on that page hasn't been updated. I don't have control over the page, I depend on Enrico updating it. Regards Pete Link to comment Share on other sites More sharing options...
Jonahbird Posted August 13, 2012 Author Report Share Posted August 13, 2012 Hi Pete I have now installed version 4.85 and have made the INI amendments and tried another FSX start. I normally start in Full Screen mode. The new FSUIPC4.LOG reads:- ********* FSUIPC4, Version 4.85 by Pete Dowson ********* Running inside FSX on Windows 7 Module base=6C680000 User Name="Frank Jones" User Addr="jonesfrn8@aol.com" FSUIPC4 Key is provided WideFS7 Key is provided 47 System time = 13/08/2012 12:10:12 47 FLT UNC path = "\\RODNEY\Flight Simulator X Files\" 78 Trying to connect to SimConnect Acc/SP2 Oct07 ... 78 FS UNC path = "\\RODNEY\FSX\" 297 LogOptions=00000800 00000001 297 Wind smoothing fix is fully installed 297 G3D.DLL fix attempt installed ok 297 SimConnect_Open succeeded: waiting to check version okay 297 Trying to use SimConnect Acc/SP2 Oct07 14165 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 14165 Initialising SimConnect data requests now 14165 FSUIPC Menu entry added 14181 ## EV_SIM=stop 14181 \\RODNEY\Flight Simulator X Files\BA737 @ gate 102 Gatwick.FLT 14181 \\RODNEY\FSX\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.AIR 14181 ##: ST_SIM=stop 44242 ##: ST_SIM=stop 49109 ##: ST_SIM=stop 51605 ##: ST_SIM=stop 54164 ##: ST_SIM=stop 56722 ##: ST_SIM=stop 59281 ##: ST_SIM=stop 61808 ##: ST_SIM=stop 64366 ##: ST_SIM=stop 66893 ##: ST_SIM=stop 70123 ##: ST_SIM=stop 72650 ##: ST_SIM=stop 75302 ##: ST_SIM=stop 78110 ##: ST_SIM=stop 80700 ##: ST_SIM=stop 83289 ##: ST_SIM=stop 85801 ##: ST_SIM=stop 88312 ##: ST_SIM=stop 90855 ##: ST_SIM=stop 93804 ##: ST_SIM=stop 95722 ## EV_START 95722 ## EV_SIM=start 97142 ##: ST_SIM=start 99747 ##: ST_SIM=start 102352 ##: ST_SIM=start 104895 ##: ST_SIM=start 107422 ##: ST_SIM=start 109950 ##: ST_SIM=start 112508 ##: ST_SIM=start 115035 ##: ST_SIM=start 117641 ##: ST_SIM=start 120293 ##: ST_SIM=start 122820 ##: ST_SIM=start 124895 ## EV_STOP 124895 Sim stopped: average frame rate for last 29 secs = 6.3 fps 124895 ## EV_SIM=stop 133490 ##: ST_SIM=stop 134379 ## EV_START 134379 ## EV_SIM=start 136064 ##: ST_SIM=start 138654 ##: ST_SIM=start 141758 ## EV_STOP 141758 ## EV_SIM=stop 141946 ##: ST_SIM=stop 150214 System time = 13/08/2012 12:12:42 150214 *** FSUIPC log file being closed Average frame rate for running time of 35 secs = 6.3 fps G3D fix: Passes 18646, Null pointers 0, Bad pointers 0, Separate instances 0 Memory managed: 4 Allocs, 4 Freed ********* FSUIPC Log file closed *** ******* Incidentally, for some time I have been unable to close FSX by its normal exit route. I get a Windows tablet saying "MFS has stopped working" and I have to close with the close option it offers. Could that be part of the same problem? Regards Frank Link to comment Share on other sites More sharing options...
Pete Dowson Posted August 13, 2012 Report Share Posted August 13, 2012 Meanwhile, I have made the INI amendments and tried another FSX start. I normally start in Full Screen mode. The new FSUIPC4.LOG reads: That looks exactly like it would if you'd never gone to "fly now" mode, as if it was still in the FS initial selection screen when you terminated it! FSUIPC can't do anything until in Flight Mode. Look: Average frame rate for running time of 38 secs = 6.1 fps my FSX installation, using Vertex 3 SSDs on SaTA 6Gb/s ports and on an i5-2500K clocked at 4.8GHz takes at least 60 seconds to get to flight mode, and then has frame rates in the 30's or more. How you can fly at 6 fps I don't know, but it certainly looks like it never got to Flight Mode. Here are examples of what the log looks like once things start happening: 57172 ## WHYSTART: SOON: (0366=N || (0264=Y && 3365=Y)) && (3D00=Y || (0580=N && 0264=N)) 57172 ## ... and no class #32770 window! 57172 ## WHYSTART: NOTYET: (No#32770=Y && time=Y && 3365=Y && seeStart=Y && startime=N) 58000 ##: ST_SIM=start 58703 ## WHYSTART: NOTYET: (No#32770=Y && time=N && 3365=Y && seeStart=Y && startime=N) 59047 ## WHYSTART: NOTYET: (No#32770=Y && time=N && 3365=Y && seeStart=Y && startime=Y) 60531 ##: ST_SIM=start 60531 ## WHYSTART: NOTYET: (No#32770=Y && time=N && 3365=Y && seeStart=Y && startime=N) 61547 ## WHYSTART: NOTYET: (No#32770=Y && time=N && 3365=Y && seeStart=Y && startime=Y) 61734 ## Starting everything now ... Can you confirm that you did actually get to Flight Mode, with the Add-Ons menu, and the frame rate got up to flyable levels? If you did I don't understand what is going wrong. It isn't getting many if any needed signals from SimConnect -- not even the clock updates. This is why I thought it might be in Paused mode. Did you check that? You didn't say before. If you think everything is correct and 'ready to fly', I think I'll need to see a SimConnect log -- see the FAQ subforum for how to get one of those. It may get quite big, so ZIP it up and send t to petedowson@btconnect.com. I'm running out of time today. Then it will be 24th or later! Incidentally, for some time I have been unable to close FSX by its normal exit route. I get a Windows tablet saying "MFS has stopped working" and I have to close with the close option it offers. Could that be part of the same problem? Maybe. There are quite a few different problems which cause threads to hang, especially with complex addons like PMDG aircraft. One thing to try. Change the aircraft to a default one and save a new default flight. Try then resloading with default, into Flight mode, before changing back to the PMDG. I have read a lot of reports that say starting with an advanced aircraft can often cause problems. Oh, and do try with 4.85 of course. Regards Pete Link to comment Share on other sites More sharing options...
Jonahbird Posted August 13, 2012 Author Report Share Posted August 13, 2012 Hi Pete I have installed 4.85. Thank you for the pointer (Ian -Thanks to you too). The complex PMDG does seem to be the problem. I did as you suggested and restored the Ultralight at Friday Harbour as the default. All the PFC units work in that start up. Also I was able to close without having two bites at the cherry. The 737NGX seems to have been the cause. Now I know a bit more about these drivers, I may be able to discover how best to run the 737. I rarely look at fps (since the advent of FSX). I have had no difficulty in flying the 737, but will be watching fps closer in future. Out of interest here is the latest FSUIPC.LOG:- ********* FSUIPC4, Version 4.85 by Pete Dowson ********* Running inside FSX on Windows 7 Module base=6EB50000 User Name="Frank Jones" User Addr="jonesfrn8@aol.com" FSUIPC4 Key is provided WideFS7 Key is provided 47 System time = 13/08/2012 13:03:05 47 FLT UNC path = "\\RODNEY\Flight Simulator X Files\" 390 Trying to connect to SimConnect Acc/SP2 Oct07 ... 390 FS UNC path = "\\RODNEY\FSX\" 609 LogOptions=00000800 00000001 609 Wind smoothing fix is fully installed 609 G3D.DLL fix attempt installed ok 609 SimConnect_Open succeeded: waiting to check version okay 609 Trying to use SimConnect Acc/SP2 Oct07 3027 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 3027 Initialising SimConnect data requests now 3027 FSUIPC Menu entry added 3042 ## EV_SIM=stop 3042 \\RODNEY\Flight Simulator X Files\Ultralight.FLT 3042 \\RODNEY\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR 3042 ##: ST_SIM=stop 33135 ##: ST_SIM=stop 35678 ##: ST_SIM=stop 38314 ##: ST_SIM=stop 40935 ##: ST_SIM=stop 43540 ##: ST_SIM=stop 46114 ##: ST_SIM=stop 48719 ##: ST_SIM=stop 51262 ##: ST_SIM=stop 53914 ##: ST_SIM=stop 55006 ## EV_START 55006 ## EV_SIM=start 55053 ## WHYSTART: SOON: (0366=Y || (0264=N && 3365=Y)) && (3D00=N || (0580=Y && 0264=Y)) 55053 ## ... and no class #32770 window! 55053 ## WHYSTART: NOTYET: (No#32770=Y && time=Y && 3365=Y && seeStart=Y && startime=N) 55505 System time = 13/08/2012 13:04:00, Simulator time = 13:03:09 (20:03Z) 56036 ## Starting everything now ... 56067 AES Link established 57175 Advanced Weather Interface Enabled 62354 PFC Menu entry added 133974 Sim stopped: average frame rate for last 78 secs = 19.6 fps 230180 Sim stopped: average frame rate for last 55 secs = 19.8 fps 267386 \\RODNEY\FSX\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.AIR 269086 Aircraft="Boeing 737-836NGX British Airways Virtual Winglets" 328835 Sim stopped: average frame rate for last 58 secs = 16.0 fps 544647 Sim stopped: average frame rate for last 109 secs = 6.9 fps 609465 Sim stopped: average frame rate for last 24 secs = 7.9 fps 624613 System time = 13/08/2012 13:13:29, Simulator time = 21:08:56 (20:08Z) 624613 *** FSUIPC log file being closed Average frame rate for running time of 347 secs = 13.6 fps G3D fix: Passes 34730, Null pointers 0, Bad pointers 0, Separate instances 0 Memory managed: 162 Allocs, 162 Freed ********* FSUIPC Log file closed *********** It still looks like an interrupted process to me. Is that extra info the result of the lines you told me to add to the INI? Pete, thank you for the interest you have taken and the help you have given, especially as there is packing to do :). Have a great holiday. Regards Frank Link to comment Share on other sites More sharing options...
Pete Dowson Posted August 13, 2012 Report Share Posted August 13, 2012 The complex PMDG does seem to be the problem. I did as you suggested and restored the Ultralight at Friday Harbour as the default. All the PFC units work in that start up. Also I was able to close without having two bites at the cherry. Okay. Once FSX is up and running okay you should be able to load the PMDG (or a flight which loads it) without problems. Not sure about the closing though. The 737NGX seems to have been the cause. Now I know a bit more about these drivers, I may be able to discover how best to run the 737. I rarely look at fps (since the advent of FSX). I have had no difficulty in flying the 737, but will be watching fps closer in future. In FSX, unlike FS9 and before, FPS isn't be most important factor, unless it is less than about 15 when it can start to make landings difficult because of the responsiveness, or lack thereof. Smoothness is more important, and FSX is capable of beeing smoother at lower frame rates than FS9. Out of interest here is the latest FSUIPC.LOG:- Looks fine. You can remove those extra INI lines now. I note that the time to "everything read to fly" is greater than before, by some margin. Maybe some of this is memory caching? 56036 ## Starting everything now ... Regards Pete Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now