black hole in Gloucestershire

[Motormouse]

Well, not exactly, but all of a sudden my fs9 is getting an app hang followed by a ctd
when approaching Gloucestershire.
I've not made any scenery changes for ages, and all has been running well, Vfr scenery , UK2000
Etc.
Any ideas anyone?

Pete

[NigelC]

App hang can be caused by other sofware outside of FS. What else have you loaded or changed recently??

[DaveB]

Do you fly in that area regularly Pete or is it somewhere you've not visited for a long time? Most of these probs are caused by either conflicting traffic files and bgl's that can't find textures. Is the hungapp detail giving any clues?
You could try starting the sim from a different situation/location. I've binned all my saved flights before now and started a new lot just to get out of a similar situation

Sri I can't offer any definitive suggestions

ATB
DaveB

[emfrat]

Pete - That sounds horribly familiar. I used to get a crash like that in my FS9 VFR. If I took off from Bristol, located on Oldbury power station and turned towards Lyneham, it would happen as I crossed a line roughly between Wotton-under-edge and Stroud, in the vicinity of Nailsworth. From memory the cause was a conflict between two sets of add-on trees for my VF/GM scenery. I will dig through the VF forum and try to find the fix. Could be something about it at Shep's Shed too.

Cheers
MikeW

EDIT: Haven't found the post I was thinking of, as yet, but this thread refers to the same thing.
http://www.visualflight.co.uk/forums/to ... IC_ID=6436

If you could disable the bgl referred to in the first post (just rename it to bgx ) that would be a good test - if the problem goes away, we are on the right track.
In the VFGM Photoscenery there is some overlap of tiles where Vol2 adjoins Vol3. In those days a lot of people were 'planting' agn trees. One was working W to E from Cornwall and another was working E to W from London. Unfortunately a Vol 3 tile which overlapped a Vol 2 one received a different set of trees to its Vol2 twin, causing a hang and crash. It only happened in a very limited area.
MikeW

[Airspeed]

Hung App under FSX on drive D, Hung App under this black hole.....
Am I seeing double? One in FS9, one in FSX....
Definitely sounds like something other than the sim causing the error.

[Motormouse]

Pete - That sounds horribly familiar. I used to get a crash like that in my FS9 VFR. If I took off from Bristol, located on Oldbury power station and turned towards Lyneham, it would happen as I crossed a line roughly between Wotton-under-edge and Stroud, in the vicinity of Nailsworth. From memory the cause was a conflict between two sets of add-on trees for my VF/GM scenery. I will dig through the VF forum and try to find the fix. Could be something about it at Shep's Shed too.

Cheers
MikeW

EDIT: Haven't found the post I was thinking of, as yet, but this thread refers to the same thing.
http://www.visualflight.co.uk/forums/to ... PIC_ID=643

If you could disable the bgl referred to in the first post (just rename it to bgx ) that would be a good test - if the problem goes away, we are on the right track.
In the VFGM Photoscenery there is some overlap of tiles where Vol2 adjoins Vol3. In those days a lot of people were 'planting' agn trees. One was working W to E from Cornwall and another was working E to W from London. Unfortunately a Vol 3 tile which overlapped a Vol 2 one received a different set of trees to its Vol2 twin, causing a hang and crash. It only happened in a very limited area.
MikeW

Thats the one, the VF forum link doesn't work for me, can you post up the appropriate bgl number, ta very much

Pete

[emfrat]

Pete - Sorry about that - there was a 6 missing at the end of the URL (an error known as 'fat fingers')
s/be http://www.visualflight.co.uk/forums/to ... IC_ID=6436
I will fix it in a mo, but the relevant part is:
"I've also ascertained that with the VFR Scenery file EW00150008.bgl (originally from JFVFR2\VFGM_PhotoScenery_Vol2_2) disabled, the problem does not occur."
If that fixes it, you need to remove the agn files that were added to that volume. There will be lots of them, so use the 'divide and conquer' approach. Move about half of the agn files to a folder outside FS, and note the numbers.. Restart FS and check for the problem. If it is gone, bring back half the ones you moved and test again. If it reappears, move half of those out again, and test, and so on... You will quickly home in on the culprits.
ATB
MikeW