[solved] Very disapointed

[Rajah]

I am very disapointed because FSP causes frequently g2d.dll errors witch reslults in a black screen.
I saw the sticky topic "Crash to desktop". It's not my hobby to investigate the 26 topics with possibles causes and
solutions when I never
had problems before! I am flying online on the IVAO network and it is very boring that after ATC clearance and
airborn I have to stop the
flight and startover again. Also after 2:30 hours flying and taxiing to the gate where it happens also 3 minutes
before on the blocs.
I did remove already all the add on airports (so less fun already) .
Is this program not suitable for flying on a network like IVAO?

Frans

[Dutch64]

If you have g2d.dll errors they are almost for sure related to your videocard drivers. Try to reinstall them, it might fix this issue



Post Edited ( 12-30-05 14:58 )

[Alexair]

I used to have CTD on EACH and EVERY flight I used to do on IVAO...

I tried a LOT a stuff: Re-installing Win XP, FS9.1, FsPax, Update the Grapich card's driver, etc... Nothing worked... And I have posted
several post about the problem. I was on same point than yours, just about to quit useing FsPax, until...

This is some of the tricks I did and apparently one or more of them worked out just fine because I have no more CTD on IVAO:

1) I have checked my PC for virus and other creepy stuff like that, but not with my anti-virus but with this:

http://www.bitdefender.com/scan8/ie.html

Totally free and work perfect (just take some time if you have a lot of stuff like I have: about 120Go of files, etc...).

I have seen a big difference with my anti-virus...

2) Then I have re-installed Win XP over the previous (for not losing anything by formating). I think that solve some problems.

3) I have checked and updates all drivers that needed and update (was especially the case for my sound card and believe me that make
a difference for CTD).
Try this:

http://www.touslesdrivers.com/index.php?...pression=0

It's in French but basically it is watching your system and tell you which stuff need to be updated (it give you the proper driver so you don't
need to search all over the web to find it, VERY NICE stuff to use).

4) I remove my previous MESH and install others just in case (that have probably worked also in CTD issue, and I guess some
sceneries could be the issue too).
I have tried the free mesh from Yohann Baptsist that you can find on AVSIM.COM

5) I am using only the version 3.40 of FSUIPC, I have tried more recent version but the result is more chance to have CTD (don't know why
but it is for sure).

Now the result:

No more CTD on IVAO (except some very rare CTD if I am doing something wrong or asking really too much of the system).
But believe me, I am now flying like a charmed on IVAO...

I know that it is a lot of work reading all post about CTD but do it anyway, you might find a solution for your CTD problem...

Hope that might help you, there is no miracle recipe to solve CTD problem. It is caused by different stuff, depending on people PC. So
from my personnal experience I have only one thing to say: You have to try and experiment different solutions but I think that FsPax is
quite stable (not totally I think but I might be wrong but enough to make some nice flight on IVAO).

Alex Kratz
FRANCE

[psolk]

I can actually say quite definiteively that FsP has NO adverse affects on a default Vanilla FS.
I only know because for the past three weeks I have been going through one of the most extensive FS compatability tests I have ever completed. I too
was plagued by CTD and Out of Memory error messages. After months of troubleshooting and grasping at straws I decided to start from scratch.

I formatted my complete machine and set up two partitions. One for XP and FS, one for XP and everything else.
I then proceeded to lay out a game plan for my testing. Typically, most people blame CTD's on an add-on aircraft, LVL-D, PMDG or PSS as you are
always flying the plane when FS crashes. With that being said I decided to test the planes first, global add-ons next, global scenery next and
finally local scenery.
My procedure was as follows:

1. Install FS
2. Install FS 9.1 patch
3. Fly for numerous days without rebooting FS or PC to verify no errors
4. Go through backup procedure
4a. Create system restore point
4b. back up app data /Fs9 directory and entire FS directory
5. Install add-on
6. Test with same exact flights for numerous days without rebooting PC or FS.

This is what I have tested so far and any issues I have found in the order they were added and tested... Issues = ctd not a perfect program
1. FSUIPC V 3.48 through V 3.52 (registered) No issues
2. FSbuild 2.2 (registered) No issues
3. ActiveCamera V 2.1 (registered) No issues
4. LVL-D 767 No issues
5. PMDG 744 and NG No issues
6. PSS T7 No issues
7. ASV-E upgraded to ASV6 No issues
8. Fs-Passengers NO ISSUES
9. FDC (FlightDeck Companion) CTD when destination polling features enabled, buffer overrun with
disabled and PMDG, PSS or LVL-D) This was it, I found my global add-on that was causing the out of memory messages (or did I)

From here I was in a holding pattern for a few days. Do the flight with FDC, crash, uninstall do it again, no crash, install crash, uninstall no
crash. I gathered my logs and sent them to the developer who like Dan has been wonderful in looking at the issue. No I decided to try some global
scenery as I thought I had solved all of my problems.

10. Added UTUSA all features enabled No issues
11 Install QLRP4UT add-on for UT CTD

So now I am in a holding pattern again. I have since done KSEA-KEWR 6 times. 4 times with just UTUSA and no issues, twice with QLRP4UT and two CTD.


The point of all of this is that the ONLY way to know your issue IS to put the time into it to really diagnose it. It is like this, I bought a car
with 260 horsepower. I then added a ton to it and it is now a 370 horsepower car with two stereos HOWEVER I knew I was opening myself up to a lot of
potential problems when I started modifying the default. Fs is the same exact thing. We buy it stock and then we want to add more horsepower but do
not recognize the risks associated with it. If I had a problem with the car I would have to start tearing it down one part at a time to isolate the
problem, same exact thing with FS....

-Paul

[Rajah]

Well, Alex and Paul, thanks for your extend answer. However I don't think I have the patience to do this all.
I did an upgrade of my NVIDIA GeForce 6800GT video card, as DUTCH64 suggested, and hope that this will do the trick.
After 10 flights with FSP I will let you now.

Frans

[Rajah]

Second flight: black screen error msvcr70.dll

Frans

[Dutch64]

Frans, in that case i would strongly recommend to do what Paul and Alex wrote above.... The two files you mentioned so far have nothing to do with fsp
so it must be some combination of things. PLease check your pc thoroughly as described above.

[Rajah]

Well, I uninstall FSP and see what happens than. If no CTD appears than it is over for me.

Thanks

Frans

[Rajah]

Well after uninstall I did not have any crashes anymore. I installed FSP again and till now (6 flights) all goes well.

So far so good and thanks to all of you for your help!


Frans