strangly enough, i just restored my OS from back up

 

manually installed,

1 - Microsoft Visual Basic C++ 2005 redistributable

2 - MSXML 4.0 SP2 Parser and SDK

3 - DirectX 9.0 Web setup

4 - Java (for for FPS Limiter to work)

 

 

FSX runs fabulus! under Windows 8 x64! :blush:

 

All Sliders under Scenery tab are to the max

ground detail texture checked

ground shadow unchecked

without UIAtomationCore.dll in FSX root!!!

Windows 8 is runing its own version of UIAtomationCore.dll, untouched in system32/syswow64 locations.

isolating this leaves the only remains from the original post i folowed before all this begun

is the sfx.cfg tweak

[bUFFERPOOLS]
PoolSize=0

:wacko:

 

(so far no crashe with menu clicks)

Anyway upgrading to Win 8 is waste of money if you aren't using touch screen.

 

Not true.. I don't have a touch screen and I think my money was well spent. It is a lot faster and stable than Win7.

 

I did not notice any significant change in perfomance on FSX or FS9. If you use your PC for more than just Flight Simming, you're going to love Win8.

Not true.. I don't have a touch screen and I think my money was well spent. It is a lot faster and stable than Win7.

 

100% agreed

 

 

 

 

 

 

 

 

 

 

 

 

FSX does not "need" UIAutomationcore.dll, but it does try to load it, and if it can load it, it does, and uses it, and this is what can cause issues.

 

Previous work-arounds, have included:

 

(1) Putting a Vista 32 copy of UIAutomationcore.dll in the FSX directory, so it finds that first.

(This greatly improves stability, by having FSX (only) using this Vista32 copy of UIAutomationcore.dll, but is not a 100% solution.)

 

(2) Removing UIAutomationcore.dll completely.

(This restored FSX's stability, but a few W7 programs then fail to work correctly .. it would seem that even more W8 programs are also affected)

 

The IDEAL solution would be to put a "STUB" version of UIAutomationcore.dll in the FSX directory, so FSX could find it (Rather than searching and finding the default version), but the STUB version would not effectively do anything, so would not cause the instability.

 

With the above solution, any other W7 or W8 program than needed UIAutomationcore.dll, would find it in it's default location, and all would be as MS designed the W7 & W8 Operating Systems.

 

Just needs some smart windows programmer to make a stub version if UIAutomationcore.dll.

(This greatly improves stability, by having FSX (only) using this Vista32 copy of UIAutomationcore.dll, but is not a 100% solution.)

 

In what way? Obviously, I'm a sample size of 1, but it's been a 100% solution on my system as far as I can tell. No errors and no obvious drawbacks. Perhaps I shouldn't ask, as ignorance has been pretty blissful for me, but what am I missing?

 

Scott

In what way? Obviously, I'm a sample size of 1, but it's been a 100% solution on my system as far as I can tell. No errors and no obvious drawbacks. Perhaps I shouldn't ask, as ignorance has been pretty blissful for me, but what am I missing?

 

Scott

 

Even with the Vista32 UIAutomationcore.dll, some users have reported lockups, after a large number of View changes, suggesting, that while the old Vista dll might greatly reduce the Change view/lock-up issue, its not a 100% solution.

I do not want to jump in, in that new "Win8 is useless and bad" bashing.

 

 

Just want to point out that I have UIAutomationcore.dll in FSX root folder since several month without any problems ...

You're running FSX in window mode? Of course it isn't going to be as big a performance hit, for starters there is no vsync. And as others have said, what did you expect deleting a windows dll file???

I'm pretty sure that the METRO issues posted are due to NVidia settings and not the UIAutomation fix (which I was never a proponent of.) Just leave your global NVidia settings at default and use NVidia Inspector to tweak your FSX settings. BTW it is NEVER a safe practice to mess with OS DLL's. NEVER!! Cheers and enjoy your flight. jja PS You can always set the FSX compatibility level to XP, Vista or whatever. BUT DON"T MESS WITH SYSTEM DLLS LOL.

I'm pretty sure that the METRO issues posted are due to NVidia settings and not the UIAutomation fix

 

im willing to test braking metro through NVidia settings, you have a clue where to start?

 

btw:

the windowed in play images are showing ram utilization and GPU usage running FSX on win8 (skeptic's compare :-)

game loaded, over full city view, banking, over water and sky and clouds

I got the same results as the post pics by setting nVidia global settings to what I use in nVidia Inspector. Once I set them back to the default METRO was fine.

 

Cheers

jja

Come on Graham....if everyone had that attitude (as much as i agree, dont fix what aint broken) We would still have mobile fones in briefcases.

 

We have to try things to see if its better...its human nature.

 

Fair enough. I have had my fill of tweaking Win 7 etc now at a point where it is working well and I can't bear the thought of starting all over without even using what I already have. I understand people like to constantly tweak and get 1 fps more so good luck

Help me FSX keeps crashing any ideas? Im a windows 8 user as well any suggestion pool size or something?

Please post the error report.

Please post the error report.

How do I show an error report? All it does is CTD without showing anything But if I'm lucky it says Microsoft has reported an unexpected error or what not. Something that would typically show in a crash to desktop.