Luke Kolin Posted January 20, 2017 Report Posted January 20, 2017 Just updated to 959n on FSX SP2, and I'm receiving a crash on launch after I've been prompted to trust the module. FSX is writing the signature to the fsx.cfg, and FSUIPC is starting. Here are the error info and FSUIPC4.LOG: Problem signature: Problem Event Name: APPCRASH Application Name: fsx.exe Application Version: 10.0.61472.0 Application Timestamp: 475e17d3 Fault Module Name: FSUIPC4.dll Fault Module Version: 4.9.5.914 Fault Module Timestamp: 5881f118 Exception Code: c0000005 Exception Offset: 0001fc68 OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1033 Additional information about the problem: LCID: 1033 ********* FSUIPC4, Version 4.959n (20th January 2017) by Pete Dowson ********* Windows 7 Ultimate reported as Build 7601, Release ID: -- (Version 6.1) fsx.exe version = 10.0.61472.0 Reading options from "D:\Program Files\FSX\Modules\FSUIPC4.ini" Running inside FSX on Windows 7 Module base=63380000 User Name="Luke Kolin" User Addr="luke@sce.net" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 15 System time = 20/01/2017 12:06:39 15 FLT path = "C:\Users\luke.POLARIS\Documents\Flight Simulator X Files\" 15 ------ Module Version Check ------ 15 acontain.dll: 10.0.61472.0 15 api.dll: 10.0.61472.0 15 controls.dll: 10.0.61472.0 15 fs-traffic.dll: 10.0.61472.0 15 G3D.dll: 10.0.61472.0 15 language.dll: 10.0.61472.0 15 sim1.dll: 10.0.61472.0 15 visualfx.dll: 10.0.61472.0 15 weather.dll: 10.0.61472.0 15 window.dll: 10.0.61472.0 15 ---------------------------------- 47 Trying to connect to SimConnect Acc/SP2 Oct07 ... 62 FS path = "D:\Program Files\FSX\" 203 ---------------------- Joystick Device Scan ----------------------- 203 Product= CH PRO THROTTLE USB 203 Manufacturer= CH PRODUCTS 203 Vendor=068E, Product=00F1 (Version 0.0) 203 Serial Number= 203 Product= CH PRO PEDALS USB 203 Manufacturer= CH PRODUCTS 203 Vendor=068E, Product=00F2 (Version 0.0) 218 Serial Number= 218 Product= CH FLIGHT SIM YOKE USB 218 Manufacturer= CH PRODUCTS 218 Vendor=068E, Product=00FF (Version 0.0) 218 Serial Number= 218 ------------------------------------------------------------------- 218 LogOptions=80000000 00000001 218 ------------------------------------------------------------------- 218 ------ Setting the hooks and direct calls into the simulator ------ 218 --- CONTROLS timer memory location obtained ok That is as far as the log goes. Pete, hopefully that may give you some clues. FWIW I had the same problems with 4.959e on FSX, but it runs OK in P3D. I'm going to upgrade the P3D version and see what happens. Cheers! Luke
Luke Kolin Posted January 20, 2017 Author Report Posted January 20, 2017 Two more data points for you - works fine on P3D 3.4.18, and when I roll back FSX to 4.959 it also starts up. I didn't clear out anything so I don't believe it's related to data / weather / logbooks files. In the FSX log, it looks like the next log entry after the CONTROLS time memory location is this: 172 --- SIM1 Frictions access gained and basic values patched I assume that init code is all single-threaded and executed sequentially, so perhaps there's a bug in patching the friction values? Cheers!
Pete Dowson Posted January 20, 2017 Report Posted January 20, 2017 1 hour ago, Luke Kolin said: Just updated to 959n on FSX SP2, and I'm receiving a crash on launch What was your previous version, please? The change in n from m was extremely minor, just in a test for P3D on the Traffic Limiter. It runs fine here on FSX-SE. Pete
Pete Dowson Posted January 20, 2017 Report Posted January 20, 2017 1 hour ago, Luke Kolin said: when I roll back FSX to 4.959 it also starts up. I didn't clear out anything so I don't believe it's related to data / weather / logbooks files. In the FSX log, it looks like the next log entry after the CONTROLS time memory location is this: 172 --- SIM1 Frictions access gained and basic values patched I assume that init code is all single-threaded and executed sequentially, so perhaps there's a bug in patching the friction values? There's no change at all for FSX or FSX-SE hooking in any versions since the last FSX-SE update. I'll see where that crash offset places it. Pete
Luke Kolin Posted January 20, 2017 Author Report Posted January 20, 2017 10 minutes ago, Pete Dowson said: What was your previous version, please? The change in n from m was extremely minor, just in a test for P3D on the Traffic Limiter. I went from 4.959 to 4.959n. I tried 4.959e a few days ago and got a similar crash but I didn't record the crash data at the time. I suspect (but can't prove) that whatever is causing this got introduced between 4.959 and 4.959e. Cheers! Luke
Pete Dowson Posted January 20, 2017 Report Posted January 20, 2017 53 minutes ago, Luke Kolin said: I suspect (but can't prove) that whatever is causing this got introduced between 4.959 and 4.959e. Maybe. I've found an error in the routine which does "PatchSIM1friction" when you've added this to the INI file. There's a loop copying friction values across into SIM1 which finishes when the offset value in the source list is set at 0xFFFF.. Unfortunately the table ends with a DWORD 0xFFFFFFFF, so it doesn't match. The loop will continue too long and if it accesses anything not accessible you get the access error. It looks like this silly error has been there every since the built-in frictions patch was added. The difference since the 4.959e version is that some small changes in variable types were made to stop hosts of warnings appearing when we compiled with VS15 (to try to solve the Win10 problems with P3D). You should find that if you remove the "PatchSIM1Friction=Yes" parameter from the INI it will work. Please let me know if it doesn't. Meanwhile I'll fix this error in any case. I have some other things to sort out first, but if I post up a version 4.959p later today, or more likely tomorrow morning, could you try it for me please (with that parameter back in) and let me know? Pete
Luke Kolin Posted January 20, 2017 Author Report Posted January 20, 2017 4 minutes ago, Pete Dowson said: You should find that if you remove the "PatchSIM1Friction=Yes" parameter from the INI it will work. Please let me know if it doesn't. Meanwhile I'll fix this error in any case. I have some other things to sort out first, but if I post up a version 4.959p later today, or more likely tomorrow morning, could you try it for me please (with that parameter back in) and let me know? Changed that FSUIPC4.INI option to No and things started up just fine! I'll let you know tomorrow on the new version when it's released. Thanks! Luke
Pete Dowson Posted January 20, 2017 Report Posted January 20, 2017 Can you download a test version with the change I mentioned and check it please, with that parameter back? FSUIPC4959p_TEST.zip Thanks, Pete
Luke Kolin Posted January 20, 2017 Author Report Posted January 20, 2017 Thanks, Daveo - I'm currently dragging an MD-11 across the pond so I won't be able to test until later tonight. I'll give it a quick whirl when I land before the sun comes up on the other side of the ocean. Thank you Pete for your usual amazing turnaround! Luke
Luke Kolin Posted January 21, 2017 Author Report Posted January 21, 2017 ********* FSUIPC4, Version 4.959p (20th January 2017) by Pete Dowson ********* Windows 7 Ultimate reported as Build 7601, Release ID: -- (Version 6.1) fsx.exe version = 10.0.61472.0 Reading options from "D:\Program Files\FSX\Modules\FSUIPC4.ini" Running inside FSX on Windows 7 Module base=6B0F0000 User Name="Luke Kolin" User Addr="luke@sce.net" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 16 System time = 20/01/2017 21:27:48 16 FLT path = "C:\Users\luke.POLARIS\Documents\Flight Simulator X Files\" 16 ------ Module Version Check ------ 16 acontain.dll: 10.0.61472.0 16 api.dll: 10.0.61472.0 16 controls.dll: 10.0.61472.0 16 fs-traffic.dll: 10.0.61472.0 16 G3D.dll: 10.0.61472.0 16 language.dll: 10.0.61472.0 16 sim1.dll: 10.0.61472.0 16 visualfx.dll: 10.0.61472.0 16 weather.dll: 10.0.61472.0 16 window.dll: 10.0.61472.0 16 ---------------------------------- 47 Trying to connect to SimConnect Acc/SP2 Oct07 ... 47 FS path = "D:\Program Files\FSX\" 141 ---------------------- Joystick Device Scan ----------------------- 141 Product= CH PRO THROTTLE USB 156 Manufacturer= CH PRODUCTS 156 Vendor=068E, Product=00F1 (Version 0.0) 156 Serial Number= 156 Product= CH PRO PEDALS USB 156 Manufacturer= CH PRODUCTS 156 Vendor=068E, Product=00F2 (Version 0.0) 156 Serial Number= 156 Product= CH FLIGHT SIM YOKE USB 156 Manufacturer= CH PRODUCTS 156 Vendor=068E, Product=00FF (Version 0.0) 156 Serial Number= 156 ------------------------------------------------------------------- 172 LogOptions=80000000 00000001 172 ------------------------------------------------------------------- 172 ------ Setting the hooks and direct calls into the simulator ------ 172 --- CONTROLS timer memory location obtained ok 172 --- SIM1 Frictions access gained and basic values patched 172 --- FS Controls Table located ok 172 --- Installed Mouse Macro hooks ok. 172 --- Wind smoothing fix is fully installed 172 --- G3D.DLL fix attempt installed ok 172 --- SimConnect intercept for texts and menus option is off 172 --- All links checked okay 172 ------------------------------------------------------------------- 172 SimConnect_Open succeeded: waiting to check version okay 172 Trying to use SimConnect Acc/SP2 Oct07 172 Opened separate AI Traffic client okay 1186 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 1186 Initialising SimConnect data requests now 1186 FSUIPC Menu entry added 1217 C:\Users\luke.POLARIS\Documents\Flight Simulator X Files\KSEA 34R.FLT 1217 D:\Program Files\FSX\SimObjects\Airplanes\C172\Cessna172SP.AIR It loads. Thanks Pete! Luke
Pete Dowson Posted January 21, 2017 Report Posted January 21, 2017 6 hours ago, Luke Kolin said: It loads. Thanks Pete! Good. I won't release 4.959p generally, as I'm close to releasing a full build 4.960, probably Monday or Tuesday. Please just replace it then. Won't be any difference unless something else crops up over the weekend, but I hope to do the few documentation updates before then. Pete
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