danander11

OK.. Back home and off of my phone so these should make a bit more sense... I'm 99% certain that it's a conflict with FSUIPC and weather calls... Pete Dowson has made reference to such in a couple of places.. I found http://forum.simflight.com/topic/81933-p3d-v33-ctd-when-fsuipc-4955c-is-enabled/ to be most useful in ferreting out some things and tweaking the .INI Most notably that there is a newer version of FSUIPC (downloadable from that same forum) that ups it from v4.955c, (on Schirattis site), to v4.955g Using that newer version and following the other suggestion Pete had seems to have done the trick. (though I could never find the .wx files he referenced.. and I found a couple of the .bin files in different locations instead of just one). One odd thing however is that in viewing the FSUIPC log from the last unsuccessful attempt to start P3D.. it made reference to the PMDG 739 that I had flown and closed out of the last time it worked properly. I'm wondering if perhaps something in P3D called for it to load the last flight and not the default??? Who knows. I'll try some things tonight and see how it goes.. but I sure feel a lot better about this.. Thanks again Kyle and Dan!

Thanks for that! I'd rather not use 'bolt-ins' for functionality but FSUIPC has always worked a treat for me... And is like to hang on if possible. As for the miscommunication, probably more so from my end Communicating with others can sometimes be a dicey affair for me because I think a bit sideways sometimes.

Not sure what there is to be confused about... I try to start P3D and right after the splash screen it goes back to the desktop with p3d nowhere to be found. Starting task manger shows p3d to be running.. But I can't find or access it. The only way to start the startup process over is to select p3d and choose End Task. However, before leaving the house this morning I found that by manually going into the Modules directory and removing the references to FSUIPC, it starts normally every time. Looking at the FSUIPC website the heading shows it is OK for p3dv3.3... But the notes say only to 3.2.4 with no further support. I guess I'll have to find a different way to map buttons and switches. I'll test it more tonight.

Done this.. And it's not that it keeps running once shut down.., it's that it never starts up. Just a splash screen then something happening somewhere that only task manager can see. I'm not sure of what's happening but I cannot change any parameters or see what may be going on, etc...

I don't know... I've posted over at P3D to try and get some help there.. Even uninstalling PMDG hasn't helped. To say that I'm frustrated would be a whopper of an understatement..

That's probably it.. I tried to start a new session tonight to check but it's now gone back to the same behavior. Only this time even removing simconnect made no difference. I click on the icon, the splash screen pops up and sets for a bit then two smaller window open and then close almost immediately and I'm back at the desktop.. yet taskmanager shows it to be running. I. now, can't get past this point. I'll try disabling crossfire and start working at it from a graphics issue of some sort. Any other suggestions?

One last niggle for this thread... Can anyone explain to me please, why my FMC is showing "Nav Data out of date" when it shows 'AIRAC-1608 JUL21AUG17/16'?

Well, It seems to work alright if I do not change planes... So I guess we can say RESOLVED for this one. Thanks again Kyle. (and everyone)

OK.. It worked for a bit then the same thing happened. I've tried restart, power-down and restart, and to repair each of the simconnect.msi installations.. with no effect. It starts p3d normally then goes back to desktop with taskmanager saying that p3d is running.. It must be in stealth mode.. ;-) Uninstall all three simconnect's and restart p3d.. check.., re-install all three simconnect's and bob's your uncle... working as it should. The one thing that I noticed this time was that I wanted to change from a 737-600 to a 737-900 via the f22, (allowing time between each for data loading).. as it went to load the 900 it ctd'ed. that's when this behavior started again. I may have to just shut down p3d completely and start from scratch when I want to use a different pmdg aircraft.. Not sure of how to proceed from here.

So far, so good! (YAY! again).. About the only niggle I've come across so far is getting my weather display to work.. When I test I get the red lettering for WINDSHEAR on the display, but no indication of weather.. I've stepped my way through the FMC to make sure that things are turned on and it all seems to be set.. but no joy on the display. I'm reading through different articles from google about getting it to work but so far nothing. I'll keep after it and thanks again Kyle!

Kyle, If I have the wrong impression, then I apologize.. but even after reading the comments here and going back to re-read the post on FB as well as the comments, whilst not explicitly stated, the impression I have still leads me to the same conclusion. I hope, for everyone's sake, that 64bit does come along and the transition will be relatively easy. After reading your comments here, my hope grows. As for the last bit.. for that I humbly apologize... It was a LONG day yesterday and after a fresh install of PMDG on top of a fresh install of P3D I was pretty churlish when my expectations weren't met.. It, however, seems to be resolved this morning and I am looking forward to spending some time 'flying' today. If I have come off as stroppy and troublesome, that was not my intent. I've lurked around the forums for a bit and see that you have and are doing good things for people and the LAST thing I want to do is get on your bad side. As for PMDG, I love the products themselves and have been a customer since 2010 (747!!!!!).

Kyle, Thanks for your help... First thing this morning I uninstalled all of the simconnect.mis's that I installed last night so that I could get back to the main menu.., which worked.. but the panels, switches, etc still did not. This morning first thing I reinstalled each of the three .msi files and tried to open P3D. This time it opened normally asked me for the license for 737! Starting a scenario has me sitting on a ramp with a fully configurable aircraft!!! (YAY!) So, I think that this is solved.. but I'll run a flight and check some things to be sure. As to your points in the above post, I 'did' set the 739 as a default aircraft but I'll change this back. I had previously checked the "Show this screen at startup" box. As to the EMT... I'm not even sure of what that is.. the little bit of searching I have done on this leads me to believe it is some sort of migration tool(?).. I haven't used anything of the sort.. This was a brand new install of P3D and PMDG. Lastly, thank you once again for your help!

Hello everyone, 737 8-900 base and 6-700 expansion installed into Win 10 (64bit) P3D v3.3.5.17625 is not working for me. I load just fine but nothing is clickable, the screens are all black, and I was not asked for my license when I installed.. (although I had it installed before so I'm not sure that's an issue). After installing I loaded a session and the plane sits in a non-functioning state, Nothing is click-able or drag-able, screens are blank and nothing functions. I've gone through the README for P3D and followed the advice there by creating a scenario with the 739 and starting from that each time. Still nothing.. so I follow it a bit more and go through the simconnect installs as noted. Now, when I start P3D, the load screen sits there for a minute or so then it goes back to the desktop and never enters the aircraft. At first I thought the program might have just CTD'ed but a clicking on the P3D icon would not restart the sim. A check of task manager showed that P3D is running, with nothing visible. After uninstalling the three simcconect programs, it's back to a non-functioning aircraft.. (well, the keyboard commands work, but mouse nor controllers do). Suggestions?

Kyle, I'm not sure if that was directed at me or not but I did point to the exchange, not just my portion of it, regarding the pricing decision for P3D. I believe it to be a fair-go to alert someone that is already concerned about the cost of migrating to P3D.. just as I feel that the prices charged for the migration were high. I cannot say that I recall a single instance of where a developer did not offer a cross-grade license or pricing for existing customers... and I buy a lot of software. I did not mean for it to be inflammatory or derisive.. just fair warning. I'm still not sure that I will buy the 777 licenses that I had for FSX.. I can't seem to get the 737 working. and following the P3D install advice, (re:simconnect), just made things worse. For what it cost, it should have worked right out of the box, but that's a topic for another thread. Danny

From their facebook page... (https://www.facebook.com/pmdgsimulations/posts/878150648891387 my exchange is the last on this post.) You will get the 64 bit update ONLY if it happens in v3.xxx. If for any reason P3D goes to v4.xxx for 64 bit, (which seems reasonable based on what everyone else has done), you will pay again. They've said that they 'expect' it to happen in v3.xxx, but there are no guarantees. (I'm keeping my fingers crossed though.. I love the 739) I've gone ahead and re-purchased 737 base and expansion for P3D but I'm having an registry error for P3D that I'm trying to sort out.. I've installed 737 only to find that none of the gauges, switches, screens, etc... worked. However, I'm not entirely certain it's a PMDG issue. Until I can get P3D to install with no errors I'm not flying. That being said.. the bit of flying that I DID do in P3D was awesome.. graphics are MUCH better, more features and just seems a lot smoother all around. Now to get my scenery issues sorted.