Vox-tm

Same... the March release of DX9c does nothing here either.Vox

>Well even though I've defeated the issue on my system I'm>just trying to help find solutions for those who do still have>to deal with it. Due to the lack of interest by both Microsoft and Nvidia to rectify this issue, I've given up with MS Flight Simulator completely and moved on. More time is wasted trying to tweak and keep the game stable than actually flying.However, I for one appreciate folks like yourself who keep coming back to these issues to help others, even though you're happy with the operation of your own setup. I sincerely hope you, or someone as equally benevolent as yourself finds the answer to this problem eventually.Good luck,Vox

Yep, tried the beta 169.28 drivers... still the same old crashes. Yada, yada, yada. Unistall 'Acceleration' and use it as a doorstop is my suggestion.Vox

>>1) Only nVidia 8800 users are affected2) Not all nVidia 8800 users are affected<

Dear Phil,Please, please, explain to the flight simulation community in simple, straight-forward, no beating about the bush or 'avoiding the question' terms how the SP2 menu CTD issue can possibly be Nvidia's fault, when using the very same driver with SP1 works flawlessly and with SP2 it doesn't.And then extend us the courtesy of explaining in equally simplistic terms why if MS, ACES or you personally are not going to issue a further SP fix, that you can't at least help Nvidia to rectify the problem in a new driver release so that we can all get off your case and you can go back to planning FSXI in peace.Would the above really be that difficult for the corporate behemoth that is Microsoft to achieve?Vox

Worth a try, didn't work. Sorry, but this isn't a confirmed fix I'm afraid.Vox

>I have been told that this problem is a Nvidia driver problem.This is the general belief, yes. However, what I fail to see is how SP1 doesn't cause the same CTD that SP2/Acceleration does, with the same NVidia driver? MS changed something in SP2, but because they refuse to provide any further patches, they're happy to blame NVidia.It's all quite sad really.Vox

Mmm... none of those settings appear in my BIOS. I'm using a dual core AMD CPU, so this might only be a fix for you Intel boys. Glad it works for you though - the battle is gradually being won!EDIT: Tried disabling the AMD equivalent - "Cool'n'Quiet" - in the BIOS and it made no difference. SP2/Acceleration is still the same crock of crap that it was before. Oh well, worth a try I guess.Vox

In the end, the only solutions that have improved, but not eliminated this issue are:a) Install SP2. However, this causes a different CTD error (d3d9.dll) and has resulted in me uninstalling the worthless crock of s**t.:( Convert all FS9/FSX 'compatible' textures to 32bit. This elimiates most cases of the 'mvcr80.dll' CTD which I only seem to get on non-pure FSX aircraft (i.e. other than the defaults and RealAir aircraft). Unfortunately some transparent textures stop working when converted to 32bit.So it's swings and roundabouts... neither is a complete solution. Ho hum.Vox

Well yes, something should be done - even if it is just Microsoft working with Nvidia to produce a version of their drivers that are compatible. 'Acceleration' *IS* a paid product and Microsoft have a responsibility and obligation to their consumers to fix any incompatibilities that it has. But of late, all we've seen is an attitude akin to "We're moving onto FSXI, so live with it." Very poor show.Vox

Well what'ya know... uninstall 'Acceleration' and the problem goes away. Nice one Microsoft, another sure-fire winner there... not.Vox

Well, I can sympathise with you here. Whereas I used to get the 'msvcr80.dll' CTD problem, it has now been replaced with the 'd3d9.dll' CTD problem. It amazes me that Microsoft can't even seem to get their own products working with their own operating system correctly.Oh well... I'm off to find a hobby that gives me my life back.Vox

I've tried the display.cfg edit and so far things are looking good! Generally an fps increase, smoother play and best of all no apparent crashes as yet. I'll monitor the situation of course.Great suggestion, seems like a winner - thanks!Vox

Hehe, yes I realise :) All I meant was that I had found out what was causing the slowdown. I intend to keep the line in there.Vox

Thanks Phil, and I appreciate that you can't speak on behalf of their product, that's fine. It would be a question of detail loss then, that's all I wanted to know really and thanks for taking the time to reply in this thread.Cheers,Vox

Phil, I know this has been covered before and you are probably blue in the face already from explaining it... but why is there a 4.5 tile setting? Can the engine not be tweaked to set this lower? And what affect would it have on Horizon's scenery if they authored it at a different QMID. They must have done it the way they did for a reason surely?Vox

Sorry Phil if I implied that it was a 'general case' occurrence, it was my understanding that it was. My experience of the problem is limited to using Horizon Sim's Gen-X scenery where loading a flight thousands of miles away from the UK (i.e. Tokyo) seems to still lead to the unnecessary loading of Gen-X photoscenery data. As far as I am aware, the same problem exists with Just Flight's VFR data but it has had a smaller impact as they do not yet supply all volumes of their UK coverage.Vox

JimIt's a known FSX phenomena that large photoscenery add-ons like the one you're referring to will slow down the load time from the 'Free Flight' screen to actually sitting on the tarmac. Just disable the entries in the 'Scenery' section and you can confirm this for yourself.It's also a known 'bug' that FSX loads textures from areas of the world even when you're not flying in that area. Hopefully, SP2 will do something about this problem.Vox

Actually, I think I may have found my culprit... a single SimObjects line-entry in the FSX.CFG that was added by MyTrafficX when I installed it a couple of weeks ago. If I remove it, then initial load times are back to normal.Vox

Agreed, it should.So, fluffy, slow falling snow and cockpit rain effect ftw!Vox

I've had a similar thing happen. FSX used to load in around 30 secs from double-clicking the icon, but now for no reason it takes 2-3 mins. DisablePreload setting doesn't seem to make a difference. It's like an MS update caused FSX to load slowly... Big Brother tactics?Vox

My prediction is that Phil will *personally* turn the cockpit rain effect back on in the Sim because it should never have been switched off :)Vox

I don't think this has been mentioned...Why can we not have the cockpit rain effect switched back on? That must be an easy one. For that matter, why the heck did ACES take it out in the first place anyway?Vox

>frontal textures with grey cloud bottoms and defined puffy>tops, storm themes with very grey moisture laden cloudsSounds good, and definitely in-keeping with this pseudo-October weather we seem to be having in the UK at the moment :( Can't wait to play with some really moody sky colours.Vox

Wow, just stumbled across this... the new website is up:http://www.flightenvironment.comFEX certainly looks stunning!Vox