evanet

Thanks for the quick response Pete! I appreciate it. If you change your mind at all, please don't hesitate to reach out. As it was last year, I have no doubt that FSUIPC will factor heavily into breakout rooms and discussions at the conference.

Hi Pete, Apologies for the public post but I wasn't sure how else to contact you and thought this forum might be the best place. I'm working with the team at FlightSimCon to secure speakers and exhibitors for a 2015 flight simulation and aviation conference in Hartford, Connecticut, USA. FlightSimCon is an annual event that seeks to expand the use of desktop flight simulation on platforms like Microsoft Flight Simulator in the United States. There are several conferences and conventions that happen across Europe but to our knowledge FlightSimCon is the only one in the United States. Last year's event was hosted at the New England Air Museum and drew attendees from across North America. The conference hopes to dramatically scale up attendance to number in the hundreds this year. FlightSimCon is a mix of conference and activity. The centrepiece of the conference was an interactive display of flight simulator. Exhibitors were setup alongside the main demonstration area, and breakout rooms were used for the many speakers at the event. This is the conference's third year. Past events have featured "home cockpit builds" (which naturally make heavy use of FSUIPC). In fact, during last year's event, one of the attendees actually brought his entire home cockpit setup -- inside a full-size C172 fuselage -- to the event: I'm writing to ask whether you would consider participating in the conference this year. As one of the most respected names in the flight simulation world, the conference would absolutely love to feature you as a speaker. I could imagine engaging discussions on any of several possible topcs including an overview of FSUIPC, recent developments with the software, some interesting uses of FSUIPC you've seen, your thoughts on the future of the FS franchise (e.g., P3D vs. Dovetail's new release), etc. We have, in the past, had speakers participate remotely, hosting the session via Skype, with great success. I imagine given your location a similar setup would make the most sense. Please let me know the best way we can discuss this possibility. I'm readily available by email at either contact@flightsimcon.com or evanr@bostonvirtualatc.com. I'm also happy to continue the discussion here. For more information on FlightSimCon 2015, please visit the conference website at www.flightsimcon.com. Thank you, Evan

While Pete was busy with his pint, I was able to get a few flights done today -- first time in a while. Better yet, no issues with the ActiveSky weather anymore so I understand that's been resolved as well. Thanks a ton for the help! I'll keep you posted...

I have plenty of Windows event logs :P Here's an example. Forgive my ignorance -- is there a way to find out the location of the crash (I presume that's memory location) from these event logs? Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: g3d.dll, version: 10.0.61637.0, time stamp: 0x46fadb58 Exception code: 0xc0000005 Fault offset: 0x000ba79f Faulting process id: 0x11ac Faulting application start time: 0x01cd8883ef6a5961 Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\g3d.dll Report Id: 353fd910-f477-11e1-b40d-14dae9f4de75[/CODE]

Hi Pete, Apologies if this has been posted already. A search for "g3d.dll" came up with nothing. Do you have any information you could share with us on the causes of the g3d.dll FSX fatal errors? From what I've read, the latest version of FSUIPC is supposed to prevent/fix FSX crashes due to g3d.dll. I'm hoping if you could prevent/fix them, you might be able to tell us more about the cause, if it's not too technical. Here's my story... In December I bought a new i7 2600 3.4 with 8GB of RAM and installed FSX with all of my add-ons (REX, UTX, GEX, ASE, the list goes on...). Machine had been running great. Normally about once a year I do an FSX re-install even if I don't have any issues and I decided to do that a few weeks ago. At the time, FSX was running perfectly; no issues with fatal errors, 100% completion rate on all of my flights. I wiped the entire machine and installed FSX with Service Pack 2, loading the default flight in FSX between the service packs and re-starting between each add-on installation. This is how I usually do things and I haven't previously had any issues. As I was installing add-ons I began to get FSX crahses before the program would load. As the splash screen was open, FSX would crash, citing g3d.dll as the error. I traced this to an interesting situation: if the "Free Flight" tab on the main FSX menu was being loaded, the program would sometimes crash on start-up while the splash screen was visible. But if I was on another tab like Multiplayer or Settings it never would. In other words, if I closed FSX with Free Flight as the last thing I saw, it'd crash sometimes when I tried to re-open it. Whenever it crashed it would re-write/re-create a bunch of files in the "AppData/FSX" directory including scenery.cfg. Normally if I delete scenery.cfg I can open FSX a few more times...until scenery.cfg gets re-created and then FSX crashes. But again, if I'm trying to load the "Multiplayer" tab I never get the errors. The same is true if I do get FSX to load and I'm switching between these tabs on the main screen. From Free Flight to Multiplayer, no problem. The other way, often FSX will crash with g3d.dll listed as the faulting module. Trying to fix the issue, I wiped the entire computer twice and re-installed FSX twice. With both Acceleration and SP2 I had the same issue. I figured this wouldn't really be an issue since I rarely use Free Flight anyway. However, I've started to get g3d.dll fatal errors in-flight now, something that has never happened to me before. It's gotten so bad that I pretty much can't complete an airliner flight these days. I don't currently run FSUIPC, though I'm aware it's a possible fix to the errors. I'm thinking that's my next step. First question: do you think FSUIPC will fix the g3d.dll fatal errors that happen during the loading or switching to the "Free Flight" tab, or just the in-game errors? I used to run FSUIPC but stopped because I found it interfered with ActiveSky's weather. Pete, you may remember that we had a conversation about this a few years ago and that we never could figure out whether FSUIPC was the cause. At the time, I found that when FSUIPC was not running, ASE weather worked fine but when it was, I ended up getting weather from the default weather engine during multiplayer flights. For that reason I've been hesitant to run FSUIPC now and have been hoping that I can find and fix the issue with g3d.dll separately. I also have sort of thought that since plenty of the crashes happened while the FSX program was loading, FSUIPC might not make a difference. Second question: do you have any idea what could be causing the g3d.dll fatal errors? Do you have any suggestions, beyond running FSUIPC during my flights, that you think might help resolve the issue? Turns out I'm one of at least 3 people getting this error on a regular basis within the FSX community I'm a part of. I am not a registered user of FSUIPC but I've always been impressed with the work that you have been able to accomplish for FSX, parts of which you have provided to the FS community for free. I'm hoping someone as kind and knowledgeable as you will be able to point me in a new direction for resolving the g3d.dll errors that have more or less precluded my ability to enjoy FSX the way I used to. If it would help to give you a full list of my add-ons or specifications let me know, I'd be happy to do that.

Ok, Pete, thanks for your help. I'll continue doing what I'm doing -- installing and de-installing FSUIPC each time I want to fly. Evan

Gave it a try -- same result.

That's what I thought as well. Beyond those three references, there are no other "Weather Mode now" references/changes. Will do... but that may take a few more minutes!

Ok, here's the rest of the beginning of the log file (not edited, except I shortened a few of the paths): ********* FSUIPC4, Version 4.53 by Pete Dowson ********* Reading options from "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini" User Name="" User Addr="" FSUIPC4 not user registered WIDEFS7 not user registered, or expired Running inside FSX on Windows Vista (using SimConnect Acc/SP2 Oct07) Module base=61000000 Wind smoothing fix is fully installed DebugStatus=0 31 System time = 13/12/2009 09:51:23 78 FLT UNC path = \Documents\Flight Simulator X Files\" 78 FS UNC path = "\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\" 453 LogOptions=00000000 00000001 453 SimConnect_Open succeeded: waiting to check version okay 1357 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 1357 Initialising SimConnect data requests now 1357 FSUIPC Menu entry added 1373 \Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FLIGHTS\OTHER\FLTSIM.FLT 1373 \Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR 1888 Weather Mode now = Global 50825 Weather Mode now = Real World 114380 \Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_B757-200\cs757-200.AIR 190150 System time = 13/12/2009 09:54:33, Simulator time = 06:52:34 (11:52Z) 259929 Weather Mode now = Global 260506 Advanced Weather Interface Enabled 289881 **** No SimConnect events or states being received! Re-connecting now**** 289881 SimConnect_Open succeeded: waiting to check version okay 289881 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0) 289881 Initialising SimConnect data requests now 289881 FSUIPC Menu entry added I didn't know there was a difference, and/or how you can make that change. Is it somewhere in ASA's options? Good idea, I'll try this same flight but will wait until everything is up and running to start ASA. Evan

No, just the standard multiplayer interface in FSX. I took a look through the user guide and located the log. I get a few interesting lines: Wind smoothing fix is fully installed 1888 Weather Mode now = Global 50825 Weather Mode now = Real World 260506 Advanced Weather Interface Enabled And then a whole lot of this: 7459438 WRITE0 0924, 2 bytes: A8 2D .- 7459438 WRITE0 0BB6, 2 bytes: 59 14 Y. 7459500 WRITE0 088C, 2 bytes: A8 2D .- 7459500 WRITE0 0924, 2 bytes: A8 2D .- 7459500 WRITE0 0BB6, 2 bytes: 59 14 Y. 7459562 WRITE0 088C, 2 bytes: A8 2D .- 7459562 WRITE0 0924, 2 bytes: A8 2D .- 7459562 WRITE0 0BB6, 2 bytes: 59 14 Y. 7459625 WRITE0 088C, 2 bytes: A8 2D .- 7459625 WRITE0 0924, 2 bytes: A8 2D .- 7459625 WRITE0 0BB6, 2 bytes: 59 14 Y. ... and a few of these: 8110492 WRITE0 0BC0, 2 bytes: AF 12 .. 8110523 WRITE0 0BB6, 2 bytes: ED 10 .. 8110523 WRITE0 0BC0, 2 bytes: A4 12 .. 8110617 Weather Read request (Global set) to area 1: ICAO="GLOB", Req=0 8110617 Weather Read request (Nr Station) to area 8: Lat=37.25, Lon=-80.02, Alt=0.0, Req=1 8110617 Weather Received (type 1 request, AtStation): "GLOB&A0 131615Z 252118KT&D457LG 252118KT&A914NM 252118KT&A1829MG 252118KT&A2743SG 252118KT&A3658NG 252118KT&A5486NG 252118KT&A7315LG 252118KT&A9144NG 252118KT&A10363NG 252118KT&A11887NG 252118KT&A13411NG 252118KT&A14935NG 100KM&B-1500&D29500 0ST000&ST001FLMN000N 15/12 Q1013 @@@ 30 15 252 118 | 60 15 252 118 | 90 15 252 118 | 120 15 252 118 | 180 15 252 118 | 240 15 252 118 | 300 15 252 118 | 340 15 252 118 | 390 15 252 118 | 440 15 252 118 | 490 15 252 118 | " 8110617 WX Received in 0 mSecs, WX request type 1, ICAO=GLOB 8110617 Weather Received (type 5 request, Nearest): "KROA&A355 131654Z 256134KT&D457NM 256134KT&A552NM 256134KT&A554NM 256134KT&A559LM 256134KT&A1467LG 256134KT&A1469LG 256134KT&A1474MG 256134KT&A2381NG 256134KT&A2383NG 256134KT&A2388NG 256134KT&A3296NG 256134KT&A3298NG 256134KT&A3303LG 256134KT&A5124LG 256134KT&A5126LG 256134KT&A5131MG 256134KT&A6953NG 256134KT&A6955NG 256134KT&A6960NG 256134KT&A8782NG 256134KT&A8784NG 256134KT&A8789LG 256134KT&A10001NG 256134KT&A10003NG 256134KT&A10008NG 256134KT&A11525NG 256134KT&A11527NG 256134KT&A11532NG 256134KT&A13049NG 256134KT&A13051NG 256134KT&A13056NG 256134KT&A14573NG 256134KT&A14575NG 256134KT&A14580NG 100KM&B-1855&D29500 0CU000&CU001FMMN000N 15/12 09/06&A554 09/06&A559 03/00&A1469 03/00&A1474 -2/-5&A2383 -2/-5&A2388 -8/-11&A3298 -8/-11&A3303 -20/-23&A5126 -20/-23&A5131 -32/-35&A6955 -32/-35&A6960 -44/-47&A8784 -44/-47&A8789 -52/-55&A10003 -52/-55&A10008 -56/-59&A11527 -56/-59&A11532 -56/-59&A13051 -56/-59&A13056 -56/-59&A14575 -56/-59&A14580 Q1013 @@@ 30 9 256 134 | 30 9 256 134 | 30 9 256 134 | 60 3 256 134 | 60 3 256 134 | 60 3 256 134 | 90 -2 256 134 | 90 -2 256 134 | 90 -2 256 134 | 120 -8 256 134 | 120 -8 256 134 | 120 -8 256 134 | 180 -20 256 134 | 180 -20 256 134 | 180 -20 256 134 | 240 -32 256 134 | 240 -32 256 134 | 240 -32 256 134 | 300 -44 256 134 | 300 -44 256 134 | 300 -44 256 134 | 340 -52 256 134 | 340 -52 256 134 | 340 -52 256 134 | 390 -56 256 134 | 390 -56 256 134 | 390 -56 256 134 | 440 -56 256 134 | 440 -56 256 134 | 440 -56 256 134 | 490 -56 256 134 | 490 -56 256 134 | 490 -56 256 134 | " 8110617 WX Received in 0 mSecs, WX request type 8, Lat=37.2493, Lon=-80.0239, Alt=0.0m 8110617 **** METAR errors: length=1528, spurious layers removed: Wind 22, Temp 11 8110617 WRITE0 0BB6, 2 bytes: 97 13 .. 8110617 WRITE0 0BC0, 2 bytes: 98 12 .. 8110648 WRITE0 0BB6, 2 bytes: 65 16 e. 8110648 WRITE0 0BC0, 2 bytes: 8B 12 .. The second part really doesn't mean a whole lot to me, but the first part seems a little less cryptic. What is the wind smoothing fix and advanced weather interface? Since you said FSUIPC doesn't do anything with weather, I assume that's something to do with ASA or the default weather? I know you don't need to help here, but I really do appreciate the effort. Thanks Pete! Evan

Pete, I probably should have mentioned this earlier... I'm using FSX, and the standard multiplayer that comes with it to connect directly to a server (no GameSpy). I'm not using any third-part multiplayer connection software, just the default FSX. I've seen the same issues offline and online with the same settings for weather (that is, real-world weather with 15 minute updates in FSX and running ASA on top of that). Based on what I've read through ASA, I don't believe that the settings you make in FSX's weather options will make a difference to what ASA outputs. I haven't used FSUIPC much... so would I simply go to the "Logging" tab, check the boxes for "Weather", "IPC Reads", "IPC Writes", and then... what? Where does that info go, and what other options should I choose?

Do you know of any way to check whether add-ons (or any) might be interfacing through FSUIPC? The only add-ons I run with FSX are ASA, FSUIPC (sometimes), and then the Level-D B767 and Captain Sim 757. All my flights are on multiplayer, and I do not believe there's a way to turn off or affect any of the online weather settings. By default, ASA appears to override any default FSX weather (even if it's real-world weather with updates) and do its own thing (that is, unless FSUIPC is enabled). Do you know if FSUIPC might be preventing ASA from overriding the default weather? It almost looks like, at times, the game is trying to decide whether to use weather from one source or another.

That's what I thought -- that FSUIPC would have no impact. And yet, whenever FSUIPC is ENABLED, I get the strange behaviour with constant wind variation, and whenever FSUIPC is DISABLED, this behaviour goes away. What do you think could be interfacing to FSUIPC to make this happen (I know that's something of a crazy question given its scope)? I just installed a clean copy today and am seeing the same behaviour (I also notice the same behaviour in different aircraft, including Captain Sim's B757 which seems to require FSUIPC). According to Jim from HiFi Simulations, FSUIPC is not supposed to have any effect on ActiveSky Advanced or the weather, yet it's not just in my own setup that I've seen this issue. By the way, I've tried uninstalling Acceleration and am seeing the same error (without Acceleration and a new plane)... so that's not the problem.

I've been a big fan and almost exclusive pilot of the Level-D B767 for about a year and a half now, and love the plane. I've also had ActiveSky Advanced installed since it came out, and for months enjoyed flying the 767 with ASA's direct wind control. Issues with FSX's default wind, including unrealistic 100+ knot wind shear, rapid changes in speed, and S-Turns were a thing of the past, and I was quite happy with my setup. Recently I joined a virtual airline that was on the VAFS network and for that I needed to install the unreigstered version of FSUIPC which I did without issue. The VA I belong to (Boston Virtual ATC's Cape Air Virtual) flies only twin Cessnas, so for a little while (less than a month) I hadn't flown the 767 with FSUIPC installed. With FSUIPC still installed (but VAFS not running) and running ASA as well, I noticed some major changes with the weather (specifically upper wind) when I did return to the 767. Suddenly it seemed like the default weather was back. While things weren't quite as bad as the pre-ASA days, I noticed dramatically shifting wind speed (the wind indicator would jump very rapidly by 2-3 knots, rarely indicating a consistent wind speed), and unrealistic, excessive turbulence re-appeared, to the point where the 767 would be doing S-Turns for the entire flight. The only configuration change was the installation of FSUIPC. Despite trying various options within FSUIPC's dialog ("Weather Settings Off", etc.), I was unable to get back the pre-FSUIPC days. After speaking with Jim (ASA support), I tried uninstalling FSUIPC (by changing the name of FSUIPC4.dll) and things were back to normal -- no more S-Turns, wind shifts, or strange weather (although neither Jim nor I believed that FSUIPC had any impact on weather). So for the past few weeks I've simply been de-activating FSUIPC when I don't need it by changing the name of the file back and forth as necessary. As an administrator of Boston Virtual ATC, I've spoken with a number of members who also fly the Level-D and have noticed similar issues with FSUIPC, although I have not confirmed in any of these cases that uninstalling FSUIPC would solve the problem. Does FSUIPC (the unregistered version) affect upper winds in the way I've described, and is this intentional? If that's the case, I'll happily continue uninstalling/installing FSUIPC as necessary to fly for my VA and fly my beloved 767. However, if there is an issue, please let me know if there's anything I can do to help troubleshoot. I understand FSUIPC is one of the most widely used pieces of software in conjunction with FSX and a ton of add-on aircraft, and hope that, if other people are experiencing this issue, we can find a resolution. Thanks, Evan