Kwakadilly

You cup cake pilots never want to have any fun!

ahh, didn't even think of this. When I landed and pulled into the gate everything was magically ok. Thanks!

I'm sure this is an FSX:SE/ SimConnect issue, just unsure as to how to avoid/ fix it. I was taking off and clicked the middle of the nav display to better see my SID as I flew it. Once I got to a good point I turned on the AP and clicked the nav display again to put it back into the VC screen. After that I lost my ability to bring up 2D popups by clicking, no ability to turn knobs, click the warning lights, etc. I have to switch to the 2D cockpit and panels to change anything. I had this issue when I first installed and I noticed a readme that came with the T7 installer saying to go and install all those other SimConnect versions. I did that and it seemed to fix it for both planes. I have done several flights so far without issue. This flight though, it seems like something broke while I was flying. Is there any way to fix this or prevent it from happening? Kinda of annoying that I have to go to the 2D to do anything for the next 3 hours... Thanks! EDIT: Windows 10 and FSX:SE are in use here, FSX:SE and PMDG products are a fresh install. No old panel states are being used either.

This is the solution, why is the thread still going?

whoa, great site. Looks like a promising VA. top 10 gotta be

Yeah, now I am unsure. I walked away and just came back, everything is 30 FPS. I may have been over an in development scenery from a friend that was being rendered and causing the problem. False alarm? I'll just have to do some testing with it

It seems like the contrails are causing an FPS issue. I've been using the product with no issue (granted I have not seen the rain or snow effects), and have seen the contrails in a more faint rendition (like the contrails were not as prominent because the air was warmer, maybe?), however as I cross over the northern United States where the air temperature is much colder the contrails are a lot more visible and as such are causing my sim to lose a significant amount of FPS (runs at 13fps when viewing the contrail, 30 fps when not). I noticed that when I was inside of the aircraft in the VC I would have better FPS than when I was outside and the contrail effect could be seen, which is the exact opposite of what normally tends to happen. I went and checked my FSX.cfg to make sure no other addon changed any settings, and it was fine. I am left to believe it is the effect since this was never an issue prior to using them.

In other words, the 200ER will be here as soon as the NGX SP2 will be here. That is disappointing, especially with such a large demand for it. Maybe I am missing some background piece of the PMDG development puzzle, but in my opinion it would make good business sense to plan, and build, all the variants (to a reasonable extent) of the aircraft you're making. Ex T7 = 200ER/200LR/300ER, B737NG = 700/800/900/900ER/BBJ Variant(s) etc. Just my opinion though. Robert, have you guys ever thought about doing some sort of research poll or questionnaire to find out what aircraft people want to see in the future (where the demand is, basically), what of the projects you're working on are most important to your customers, etc?

Well, I'd say that if they're waiting to fix stuff in the T7 SP before moving to the 200ER, maybe they want to get the NGX SP out before they move on to other things with it. Just a guess. Thanks for the replies, I guess I missed it in the manual.

So, unless I missed it, does anybody know what the current plans are for the 200ER? I know there was a poll a while ago asking what people were interested, and the 200ER was the overwhelming winner. So is it being worked on now or are we going to have to go without one of the most popular versions of the T7? Just curious, couldn't find anything recent on it.

I have to admit, they did well. I stopped flying the 200LR because my VAS would be at 3.0+ upon loading the aircraft and would OOM if I flew into a payware scenery such as LAX. Now with SP1 and the 300ER my VAS is sitting at anywhere from 2.4 to 2.7, and it only goes up to 3.1 if I arrive at a demanding payware scenery. In my book, they fixed it and I am happy!

I wanted to come back and update this, I have figured out what caused the issue. It was a Windows update. After this I decided I might as well install and try out my Windows 8.1, I didn't really like it for my gaming PC so I decided to go back to Windows 7 last night. This morning I made sure I had all the Windows updates installed before trying FSX. I installed FSX and it just closed at the splash screen and never actually opened up FSX. After trying all I could think of and reinstalling over and over I decided I might as well try to install SP1 (I know, bad since I haven't loaded up FSX at all yet) and see. After I did that FSX would crash and give the FSUI.dll error so I started wondering if it was a Windows update. I did a system restore back to the stock Windows 7 with SP1 and none of the updates (well I uninstalled three .NET Frame work updates that I still had installed), reconfigured Windows with all my settings and installed FSX. It worked like a charm. The fact that updating Windows seemed to have caused my sim to die before, and seems to have caused it this time tells me there is an update that screws everything up. I suspect this is a popular CTD because a lot of people have Windows update set to automatic, or they installed it unknowingly. I wish I could say which one exactly, but I'm not sure there were so many. If I can figure it out I will post it.

Thank you for the response, I did not install SP2. I've been running FSX since June without issue, and I had it open running that day. I then realized I had a lot of Windows Updates so I did that and that is when FSX stopped working. I did try what you suggested and more and nothing worked, so I guess a reinstall is in order. Thank you!

I have FSX Acceleration installed. Today I did some Windows updates (112 of them, only the required ones) and following that my FSX stopped working. Every time I launch it I get a fatal error and event viewer says the error is fsui.dll. I've tried everything I could possibly find around the internet, and I've seen a lot of people who have had this issue but none of the thread state how or what fixed it. When I use the suggested AppCrashView tool it does not show these crashes in there for some reason. Here is what Event Viewer shows...any idea on how to fix it? Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: fsui.dll, version: 10.0.61637.0, time stamp: 0x46fadb59 Exception code: 0xc0000005 Fault offset: 0x00073ea4 Faulting process id: 0x1640 Faulting application start time: 0x01cf31c5fe638aea Faulting application path: C:\FSX\fsx.exe Faulting module path: C:\FSX\fsui.dll Report Id: 5181f656-9db9-11e3-8eb6-000000000003

But it was fine for Tabs to imply that I am stupid, uneducated, and have no clue what I am doing without knowing anything about me (mistake on his part). Right. Insult for an insult. I never did or said anything about him or PMDG, I am simply (and politely) putting my problem out there and trying to figure it all out. He was the one who asked, prior to that I kept it to myself and said nothing more than I was anxious for SP1. PMDG CAN fix this, but they refuse to look into the issue and offer up a solution like allowing us the ability to lower the resolution of the screens etc like the NGX does (I think I heard that was coming tbh), allow us to lower the res of the terrain display, give us the ability to remove the electronic checklist or remove RAAS (removed manually) etc. PMDG knew full well the limitations of FSX and they knew that the plane was complex and would use a lot of VAS yet they decided to release it this way anyway rather than look into alternative methods such as having a lot of the systems run external from FSX as Majestics Dash does and FSLabs A320 will. They released the plane without the ability to remove VAS hogging features that we can do without if we have to. It is on them, like it or not. This is obviously going no where, so I'll just go back to patiently waiting for SP1 and testing different theory's and fixes.