Products Support > Honolulu FSX/P3D

Scenery causing FSX to act strange

<< < (3/3)

philipvjensen:
hi I respect your comments, but im telling you as I see it, i tested KLAS for 3 hours 5 crashes, after I instaleld the KDFW scenery and tested other FSDREAMTEAM sceneries for 1 hour no issues then back to KLAS 2 hours of testing no crashes

philipvjensen:
also as a result I have purchased KDFW, hopefully no future fsx crash issues

virtuali:

--- Quote from: philipvjensen on August 09, 2010, 03:00:07 pm ---hi I respect your comments, but im telling you as I see it, i tested KLAS for 3 hours 5 crashes, after I instaleld the KDFW scenery and tested other FSDREAMTEAM sceneries for 1 hour no issues then back to KLAS 2 hours of testing no crashes
--- End quote ---

I've already explained why, fact that you are getting crashes at KLAS and not KDFW, doesn't mean KLAS has a problem, but only that your PC has a problem running *everything* that is installed, when you are located at KLAS.

As I've said, NOBODY else reported a video driver crash at KLAS before, if the problem was the scenery, we would have heard at least other reports.

Keep ignoring this, and being convinced KLAS has a problem and KDFW doesn't, will only result in you never discover what the *real* cause was so, the problem will eventually surface again, either with another scenery, or even with another application besides FSX.

philipvjensen:
firstly, my computer has been setup to purely run FSX, so you do not know my configuration, it has been expertly configured and optimized far behind what you may know, secondly none of my sceneries never had a problem or crashed under full load. My computer has never crashed nor have I seen any strange behaviours with my FSX or computer operations until I installed your scenerys. I will except your sceneries are demanding but so is FTX YMML from orbx with full traffic and a PMDG aircraft, in fact it is more demanding than KLAS and I never experienced any issues over the 40+ landings and take offs I have done there.

virtuali:

--- Quote from: philipvjensen on August 09, 2010, 03:39:55 pm ---firstly, my computer has been setup to purely run FSX, so you do not know my configuration, it has been expertly configured and optimized far behind what you may know
--- End quote ---

That's entirely irrelevant: if FSX has a bug or your video driver has a bug, or the COMBINATION of FSX and the video driver has a bug, which manifests ONLY under a certain conditions, and made the video driver crashing, even the best built system in the world, will crash it as well.

Besides, it was you that initially said the all our sceneries behave strangely with video problems, and this went away when you UPDATED your drivers, and it's changing now into a video driver crash, at KLAS only. Which means, it's clear it has always been a video driver issue to begin with, that has improved with a new video driver, but it hasn't entirely fixed.


--- Quote ---secondly none of my sceneries never had a problem or crashed under full load.
--- End quote ---

Not even KLAS has crashed. It's your VIDEO DRIVER that has crashed.

A scenery can't crash a video driver, because they can't simply communicate with each other. When the scenery has a problem, it's the FSX G3D.DLL module that crashes, which is the module that takes the job of translating scenery commands into DirectX commands so, whenever the scenery has a problem, it will alwyas crash the FSX module it can communicate with. Sometimes, if the problem is a texture, G2D.DLL crashes but again, a scenery can only cause FSX modules to crash, it simply can't "reach" a video driver.


--- Quote ---I will except your sceneries are demanding but so is FTX YMML from orbx with full traffic and a PMDG aircraft, in fact it is more demanding than KLAS and I never experienced any issues over the 40+ landings and take offs I have done there.
--- End quote ---

Again, you are oversimplyfing things: "demanding" doens't mean much, if one doesn't analyze exactly WHAT is being drawn on screen, which kind of materials, texture formats, effects, which in turns convert in which shaders are called. If your video driver has a bug that manifests itself ONLY with specifc video card function that deals with a specific kind of material/effects/texture formats, it might crash even if you have MORE demanding sceneries, that maybe use different combinations of materials, texture formats, shaders, etc.

Navigation

[0] Message Index

[*] Previous page