Luke Kolin

DNS resolution is failing, and your router isn't implementing DNS properly. It's being "helpful" by returning an address that redirects to TalkTalk's error page: http://error.talktalk.co.uk/main?ParticipantID=nmum6rqpq5q6gkm3933n3nf9s76onu6r&FailedURI=http%3A%2F%2F92.242.132.16%2F&FailureMode=1&Implementation=&AddInType=4&Version=pywr1.0&ClientLocation=uk You probably need an entry in your hosts file, or use IP addresses to connect instead of host names. I run my own DNS for my 192.168.0.x addresses, but that's probably overkill for 99% of the population. Cheers! Luke

Looking at the RUN4 line, it looks like he's using a version dllhost.exe to execute the DLL, which does look valid. With that said, I can't speak any more to IVAP - it may be worth asking on the IVAO forums. It's their software. Cheers!

There's no big rush on this - it would be helpful for me (and perhaps others) when debugging issues with PMDG aircraft. Right now I can check whether FSUIPC is providing the data to end clients, but if the offsets I check for don't have data I don't have good tools to help narrow down the cause. I've had reports from both the 737 and 747, and perhaps the 777 - it's relatively rare but also difficult to track down. As best I can tell, the CDU data isn't being read. I wonder if that might make a difference. Cheers! Luke

Ah, so it requests data for all 3, and since you can never have more than one running nothing gets stepped on. I wonder if the data is actually being sent. Pete, how difficult would it be for you to log a message when the data actually comes in for the first time? I assume you could track the aircraft loaded counter to reset the flag so that each time the aircraft is reloaded we can get another message. Cheers! Luke

Pete, I appreciate the integration work you've done with the PMDG 737, 747 and 777 aircraft. We can extract a lot of useful data from them via the custom offsets. I'm running into a few cases where the SDK integration is turned on in the Options.ini file but I'm not getting data from the PMDG SDK. I check the "aircraft model" offset that comes from PMDG since that should never be zero if the SDK is passing data correctly to FSUIPC, but it appears to be. I'm curious how the integration works on your end. Do you make the SimConnect calls no matter what and just copy over any data that comes over, or are you searching for specific AIR files or other triggers to pull the data? Cheers! Luke

I don't understand what "fails the download" means. It downloads fine here. Feel free to email me at luke@kolin.org so we don't take over Pete's forum, or reach out to me on AVSIM. simFDR has a forum there. Cheers!

(blatant plug) You can always give simFDR a whirl - it's in an open beta and can record and save all of your flights for you. Cheers! Luke

It does beg the question of why we need the feature in the first place. ;) Cheers! Luke

Do you have the link? Cheers!

I'll definitely take an early build and base offset. Cheers!

I'm happy to test. I have what I need on my end, let me know if and when you are ready. Cheers!

I'm not sure - I'm actually relaying the request on behalf of some of my users. I'll circle back and see what's installed. I haven't purchased it myself. Cheers!

Pete, do you know if PMDG has released the SDK for the new 744? If so, it would be really helpful to have the same integrations as FSUIPC currently offers for the 737NGX and the 777. Cheers!

********* 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

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

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

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

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!

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

Of course - you're reading from a stream of data, so when you do the read you may not get a complete message. It's up to you to define what a "message end" delimiter is, and buffer until you receive it. Cheers! Luke

>> Installer for FSUIPC4.DLL version 4.853 That's an old version. You should download the latest installer. Luke

That's a feature, not a bug :) XML is designed for data interchange, and in most circumstances you want to discard in the case of syntactical invalidity. It's not a bad format for structured data that needs validation with a schema document. The verbosity is a challenge, but at least it compresses nicely. It also is human-readable. In all seriousness, if you're going to emit XML you really should let a library handle all of the encoding for you. You can read about JSON here: http://www.json.org/ It's essentially a way of serializing Javascript objects. Cheers! Luke

Are you generating the XML yourself or using a library? Generally speaking, encoding of special/reserved characters is why I never generate XML or JSON myself. Cheers! Luke

What's the faulting module in FSX? Look in the Windows Event Viewer to find the crash report. Cheers! Luke

Since FSUIPC isn't a flight recorder or logger, it's like not the cause of your problem. What are you using to record your flights? Let's focus on the symptoms rather than assigning blame. Cheers! Luke