Page 1 of 2

and then it all goes black!

Posted: 11 Apr 2010, 18:10
by John
Once in a while (increasingly) My FS9 for no reason I can determine just goes to a black screen, with the sound of the last aircraft I was flying still continuing in the background, then after about 45 seconds I get a 'flightsim has quit message'. A bit vague I know, but any ideas?

John

Re: and then it all goes black!

Posted: 11 Apr 2010, 18:35
by Garry Russell
Hi John

I have had FS.9 on Six HD's spread over three computers and I have had that on occasions on all of them.

Most of the occurances seem to be when switching views. *-)

It would be inteseting to know if it is a standard "one of those things" :wall:

Very occasionally when it does that, it will comeback but it usually quits then restarts itself.....annoying. :rant:

Re: and then it all goes black!

Posted: 11 Apr 2010, 18:44
by DaveB
Is it giving an error John?? More often it will give the old cookie 'Flightsim has experienced a problem blah, blah'.. spit out an error, then restart unless you tell it not to. There are a number of things that can cause it and often, the error report isn't helpful (as is the case for most M$ errors) 8)

ATB

DaveB B)smk

Re: and then it all goes black!

Posted: 11 Apr 2010, 19:50
by Garry Russell
HI Dave

When that particular happen to me there is no error...I do get the 'FS has a problem has to quit' in other instances.

As I mentioned it sometimes comes back an I've always had the impression it has run itself out of memory and is trying to empty buffers but usually falls over itself.

Maybe not :dunno:

Because I don;t have a lot of ram I have put it doen to that being the reason I get it but not many others. :worried:

Re: and then it all goes black!

Posted: 11 Apr 2010, 20:25
by DaveB
Hmm.. this is a problem I've not seen *-) Whenever I've had a black screen.. the system has hung due to some FS error or other and it comes up (eventually) with the 'FS has wrapped it's hand in' screen. Without any error report, I'd not know what to suggest :dunno: *-)

ATB

DaveB B)smk

Re: and then it all goes black!

Posted: 11 Apr 2010, 20:55
by John
DaveB wrote:Hmm.. this is a problem I've not seen *-) Whenever I've had a black screen.. the system has hung due to some FS error or other and it comes up (eventually) with the 'FS has wrapped it's hand in' screen. Without any error report, I'd not know what to suggest :dunno: *-)

ATB

DaveB B)smk
That's ok Dave, the more I look into it, the more I think it might be a scenery thing, it crashes over 'Pompey' but having just flown over 'Emma Field' it seems fine!

Kind regards

John

Re: and then it all goes black!

Posted: 11 Apr 2010, 21:20
by DaveB
Hi John :hello:

Are you running with FSNav too or is it just the sim on it's own?

ATB

DaveB B)smk

Re: and then it all goes black!

Posted: 11 Apr 2010, 21:29
by emfrat
John -
I had almost identical symptoms in my VFR installation. It happened between Gloucestershire and Lyneham and was caused by a bgl conflict between two volumes of the VFGM scenery.
There will be something about it in the Visual Flight forum - I will have a look when I get home tonight.

ATB
MikeW

Re: and then it all goes black!

Posted: 12 Apr 2010, 00:43
by John
emfrat wrote:John -
I had almost identical symptoms in my VFR installation. It happened between Gloucestershire and Lyneham and was caused by a bgl conflict between two volumes of the VFGM scenery.
There will be something about it in the Visual Flight forum - I will have a look when I get home tonight.

ATB
MikeW
Thanks for that, I'm sort of thinking it might be something like that.
DaveB wrote:Hi John :hello:

Are you running with FSNav too or is it just the sim on it's own?

ATB

DaveB B)smk
FSNav? No I'm not... I am but a simple soul

KInd regards and thanks for the ideas chaps ;)

Re: and then it all goes black!

Posted: 12 Apr 2010, 12:14
by emfrat
John -
I know I definitely posted on this subject, and it would have been in the VF forum, but I can't find it !
The VFGM photoscenery has some tile overlaps between volumes. In the case I am talking about, some autogen trees had been added to a VFGM P-S bgl for the 'central' area and because this same bgl also existed in the adjoining 'western' volume, a conflict occurred. The 'cause behind the cause' was that I had inadvertently re-introduced the conflict when I changed from the 4-volume setup to an All-in-one.
I know it's there somewhere - please bear with me *-)

ATB
MikeW