I have arrived at WSSS in my PMDG Megatop SQ747-400 and the textures go to night crashes my system. It has happened the next time I ran that flight, and I could tell it was changing from day to night textures. (Edit: Sunset)Any help?I have a very stable system of XP 32 bit, and I am just wondering if this has been an issue for others?BTW I love the Imaginesim WSSS for FS9. Very nice scenery. It does shimmer in full daylight though, and the FSX version which I bought does shimmer and has jetways disappearing at a hundred metres or so....Daniel

Edited January 29, 201214 yr by IAF747

Flew into WSSS default scenery night with the PMDG737NGX, had no CTD. DO not have the ImagineSim scenery.

I tried it at KSEA and KJFK, KJFK is FSDreamteam. I didn't use the PMDG 747-400, but I will in my next tests.Daniel

Didn't crash with PMDG at KJFK from sunset to night, but it did it at WSSS from sunrise to day. When the lights go off.......I think it seems isolated to Imaginesim at this stage.Daniel

This could be due to AI aircrafts texture. I did had this trouble few times and it all related to AI texture.

But it is only happening at Singapore, no where else.... I am using PAIDaniel

But it is only happening at Singapore, no where else.... I am using PAI

Why not take the bull by the horns?http://www.imaginesim.com/contact01.htmJohn

But it is only happening at Singapore, no where else.... I am using PAIDaniel

Maybe that AI only fly in/out Singapore and some other airports that you don't often fly in and out.I could be wrong,but worth a try.

Why not take the bull by the horns?http://www.imaginesi...m/contact01.htmJohn

I will give it a go.ThanksDaniel

Why not take the bull by the horns?http://www.imaginesi...m/contact01.htmJohn

They replied to me. Update video drivers and software.Here is a photo that shows the gates in Denver 'disappear. http://www.imaginesim.com/images/kden2/kden_04.jpgSounds like they are not interested in (or don't have the time for) working their scenery over by recompiling it with jetways showing at a greater distance, like 1000 or 1200 metres.Daniel

DanielI assume you have already tested your problem after changing your addon B-747 plane to e.g. a default Cessna.I've had the ImagineSim WSSS Changi FS9 airport scenery for quite some time and never had any problems with it. No shimmering either, in fact it looks and works great.So it sounds as though your problem is something very specific to your own WSSS setup.You say that your system "crashes" but you are not very specific about this. Is it a real CTD ("Crash To Desktop" = FS9 suddenly closes down and then your desktop re-appears) ? Or does your screen suddenly go black ? The latter normally points to a graphics card problem, usually in the related driver software and the former normally points to some kind of a texture problem, possibly related to an addon AI plane's corrupt texture or in the WSSS scenery itself.Are you sure that you have no duplicate Afcad-type files for WSSS or for any other airport within about 40 N-miles from it ?Do you have any other scenery installed in the WSSS area ? E.g. Mesh, LC or Singapore City-type scenery ? If so then you could try to de-actvate those in your FS9 scenery library while leaving only your WSSS scenery active.To test if it's any AI plane's corrupt texture you could rename the BGL extension of your Scenery/World/traffic030528.bgl file to "traffic030528.XXXX" which should kill all AI activities except those initiated by any traffic files possibly included in other addon sceneries. The only way to test this is to search for BGL files begining with "traffic" and if found you should rename their BGL extensions to "XXXX" also. You can always rename them back to BGL afterwards.If none of this helps then you can be sure that it's a problem in your WSSS scenery itself and the only advice I can then give you is the tedious process of deleting/restoring blocks of WSSS textures to/from your (previously emptied) recycle bin and testing your WSSS problem inbetween. The airport scenery will obviously have many untextured scenery objects during each such action but don't look at those and only test if your specific problem persists. Go on with this process until your problem disappears, afterwhich you can restore smaller texture blocks until you find the offending texture(s).I hope you can resolve your problem because WSSS is a wonderful airport scenery.Good luck.Hans

DanielI assume you have already tested your problem after changing your addon B-747 plane to e.g. a default Cessna.I've had the ImagineSim WSSS Changi FS9 airport scenery for quite some time and never had any problems with it. No shimmering either, in fact it looks and works great.So it sounds as though your problem is something very specific to your own WSSS setup.You say that your system "crashes" but you are not very specific about this. Is it a real CTD ("Crash To Desktop" = FS9 suddenly closes down and then your desktop re-appears) ? Or does your screen suddenly go black ? The latter normally points to a graphics card problem, usually in the related driver software and the former normally points to some kind of a texture problem, possibly related to an addon AI plane's corrupt texture or in the WSSS scenery itself.Are you sure that you have no duplicate Afcad-type files for WSSS or for any other airport within about 40 N-miles from it ?Do you have any other scenery installed in the WSSS area ? E.g. Mesh, LC or Singapore City-type scenery ? If so then you could try to de-actvate those in your FS9 scenery library while leaving only your WSSS scenery active.To test if it's any AI plane's corrupt texture you could rename the BGL extension of your Scenery/World/traffic030528.bgl file to "traffic030528.XXXX" which should kill all AI activities except those initiated by any traffic files possibly included in other addon sceneries. The only way to test this is to search for BGL files begining with "traffic" and if found you should rename their BGL extensions to "XXXX" also. You can always rename them back to BGL afterwards.If none of this helps then you can be sure that it's a problem in your WSSS scenery itself and the only advice I can then give you is the tedious process of deleting/restoring blocks of WSSS textures to/from your (previously emptied) recycle bin and testing your WSSS problem inbetween. The airport scenery will obviously have many untextured scenery objects during each such action but don't look at those and only test if your specific problem persists. Go on with this process until your problem disappears, afterwhich you can restore smaller texture blocks until you find the offending texture(s).I hope you can resolve your problem because WSSS is a wonderful airport scenery.Good luck.Hans

That is the best answer I have ever had! Thanks Hans! I also love the WSSS Imaginesim scenery, it is awesome! I only started having problems when I did a VHHH-WSSS flight SIA 744 and when I was taxiing I saw that the thing crashed.I have The Very Singapore installed, but I found the way to install it. I don't remember how I did that now.OK, I will re-read what you wrote and investigate the problem.I had some beer just now but I suspect it is the former, the screen turns black for a while.I am running PAI, never had a problem with traffic before.Daniel

Edited February 8, 201214 yr by IAF747

To test if it's any AI plane's corrupt texture you could rename the BGL extension of your Scenery/World/traffic030528.bgl file to "traffic030528.XXXX" which should kill all AI activities except those initiated by any traffic files possibly included in other addon sceneries. The only way to test this is to search for BGL files begining with "traffic" and if found you should rename their BGL extensions to "XXXX" also. You can always rename them back to BGL afterwards.

Just a tiny note on this. A much "safer" and also simpler way to prove whether AI traffic is the issue is to turn traffic off within the Flight Simulator settings.But I don't think this is the issue as the problem is now identified as a black screen issue. That sounds very much like a hardware issue and I suspect the advice on drivers etc is indeed the right one. It may also be worth running FS at a different screen resolution and also windowed instead of full screen etc to see if that makes a difference.Presume no error messages then?John

John,Of cause you're dead right with your "safer" method and that should also have been tried but in Daniel's not very well described case I intially prefer the more "drastic and failsafe" approach to such problems. However, like you, I now tend to think that his problem COULD be hardware and/or driver related, especially with the more "heavy" sceneries like WSSS but, if that was actually the case then it's my humble opinion that his problem would not only occur at WSSS.Could also be a graphics card overheating problem because of his black screen. Daniel, please remove your graphics card and blow out any dust which may have accumulated on the fan blades and/or on the cooling fins below it.Lets just wait and see what Daniel comes up with.Hans

Hi Daniel,Your problem is caused by a remaining file of your previous scenery Very Singapore. I had exactly the same problem until I removed one by one the faulty part of it to preserve the others. Unfortunately as it was some time ago after I installed Imaginesim WSSS, I can't remember which one was causing the crash, but now I can fly in and out of WSSS without CTD thanks to this housekeeping exercise. Go to your scenery folder and remove the old Very Singapore files by small batches, once you don't get the crash, add back what you removed without the last. Good luck.

Edited February 9, 201214 yr by Jean-Claude