Products Support > Honolulu FSX/P3D
Scenery causing FSX to act strange
virtuali:
--- Quote from: philipvjensen on August 07, 2010, 05:28:48 pm ---I'm sorry that is arrogance you speak, I have NO issues with any of the addons I have including all of FTX sceneries, 24 aerosoft sceneries and your saying its my drivers? and not your scenery?
--- End quote ---
What's "arrogance" ?
That a scenery can't cause the problem you are showing in the video, it's a plain an simple fact, you just can't dismiss a fact as "arrogance", just because you don't accept it.
I think to have clearly explained that, if you don't see it at other places, it doesn't mean it's CAUSED by the scenery.
Let's do an example (I'm not using real numbers, it's just an example), suppose FSX + all your other installed addons are taking, let's say 70% of your available video memory and, suppose there's problem in your video driver that happens ONLY when memory is used more than 90%. If, by adding PHNL, you reach 95% of vram, this might trigger that problem, without obviously being a problem of the scenery ITSELF, but just the thing that triggered it so, if you never had all that memory taken to begin with, and installed PHNL only, you wouldn't probably had any issue, because it might been caused by everything combined.
This is just ONE explanation, but it's cleary sound one.
Besides, nobody has every reported this specific issue before so, it's clearly something that is happening on your system only.
philipvjensen:
ok so I updated my driver to a slightly newer one, now no more weird screens but after flying out and back into sceneries and taxiing around for a bit I get a CTD I uninstalled QW757 but that doesn't help.
Description
Faulting Application Path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Problem signature
Problem Event Name: APPCRASH
Application Name: fsx.exe
Application Version: 10.0.61637.0
Application Timestamp: 46fadb14
Fault Module Name: nvd3dum.dll
Fault Module Version: 8.17.12.5896
Fault Module Timestamp: 4c378e88
Exception Code: c0000005
Exception Offset: 003514c3
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 3081
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Extra information about the problem
Bucket ID: 1955490610
I know your going to say graphics card but I had it tested at the comp shop and it passed all graphic software tests no problems. The GTX480 is nvidias flagship model at the moment so I don't know why this is happenign when I load your sceneries
virtuali:
--- Quote from: philipvjensen on August 08, 2010, 02:55:38 pm ---Fault Module Name: nvd3dum.dll
--- End quote ---
--- Quote ---I know your going to say graphics card
--- End quote ---
I'm not telling you it's graphic card. It's Windows ITSELF that told you it's the graphic card. The above report clearly indicates, the graphic driver has crashed.
--- Quote --- but I had it tested at the comp shop and it passed all graphic software tests no problems.
--- End quote ---
That's not really relevant, it might just tell you the card is not broken. However, it doesn't tell anything about the video driver/card combination ability to perform without errors in FSX.
If FSX, for any reasons, triggers an BUG in the video driver, which can't be disclosed by the standard test, because might be also related to an *FSX* bug or an FSX setting, you will have problems in FSX only, with the card happily passing all tests.
--- Quote ---The GTX480 is nvidias flagship model at the moment so I don't know why this is happenign when I load your sceneries
--- End quote ---
You are really too quick to jump to conclusions. Let's search Google for the "nvd3dum.dll" which IS what's happening to you:
Lots of reports of it ( more than 30 thousands, to be precise...), from all kind of sources, like this one:
http://forums.nvidia.com/index.php?showtopic=91437
Interesting comment here:
http://forums.nvidia.com/index.php?showtopic=102842
The user started having the nvd3dum.dll crash when he broke the fan. Could be that (not strange, for this seaons) your card is overheating when put under heavy load ?
or this one:
http://www.left4deadforums.com/19784-nvd3dum-dll.html
This one, also related to FSX:
http://www.flightsimworld.com/forums/index.php?showtopic=155912
Interesting comment here:
"Ok, I have worked something out. If I fly at TNCM with lovely weather during the day It works fine. But if I load up TNCM in rain and night then it crashes almost immediately."
Which is exactly what I've said initially: when the system is stressed by ANY complex scenery, FlyTampa in this case, (which of course is not the only thing running, all the addons contribute to the overall stress), something happens, which might be specific to your setup. Heat *could* be a factor here.
I think this gives plenty of evidence it's NOT a problem of our sceneries. It can happen with every software, and it can happen also with other FSX sceneries.
philipvjensen:
ok so I nailed it down to KLAS was causing my FSX to crash but only after taking off and landing again and taxiing for a good amount of time.
Then I installed the trial of KDFW tested that out, and went back to KLAS and put MAX settings on everything and a 767 Level-D taxied flew out came back in and taxiied around for a while and no crashes and i spent 3 hours testing. So it seems after installing KDFW something changed because I had 5 KLAS fsx crashes after KDFW no crashes at KLAS.
I will hopefully buy KDFW and experience no more crashes as I am believe it or a not a big fan of your sceneries
virtuali:
--- Quote from: philipvjensen on August 09, 2010, 12:41:36 pm ---ok so I nailed it down to KLAS was causing my FSX to crash but only after taking off and landing again and taxiing for a good amount of time.
--- End quote ---
It's not KLAS that is making crashing your computer. It's your video driver.
Fact that happens at KLAS, it's just becasue it's a very complex scenery, it might crash in any other location that is this complex. And of course, it's just not KLAS, but all the other stuff you have loaded in that area, airplane, ai, terrain, mesh, default city scenery (which is quite demanding at KLAS). It's the overall combination that might have trigger the problem in your system, not just KLAS by itself.
--- Quote ---Then I installed the trial of KDFW tested that out, and went back to KLAS and put MAX settings on everything and a 767 Level-D taxied flew out came back in and taxiied around for a while and no crashes and i spent 3 hours testing
--- End quote ---
Believe it or not, KDFW in FSX is less demanding than KLAS, also because the default scenery there is way less complex so, it might not reach the total resource comsumption that triggers your system problem, that's why it happens at KLAS and not at KDFW, without this having anything to do with KLAS having a specific problem on its own.
If it was something specific at KLAS, we should have heard it by now but, if you look at the KLAS forum, nobody ever experienced a video driver crash at KLAS. Not even in any of our sceneries, BTW, but surely not at KLAS.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version