Hello, For those that were having major issues with Imagine Sims Scenery in FSX, did the patches solve the problem?I am particularly referring to the situation at KLGA with FSX+Acceleration where the airport was unflyable at night.

Hello, For those that were having major issues with Imagine Sims Scenery in FSX, did the patches solve the problem?I am particularly referring to the situation at KLGA with FSX+Acceleration where the airport was unflyable at night.

Jeff; It does solve the performance hit. Can't say I'm in love with the looks of the new lights, though.CheersBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

I second the Colonel.Thanks

I lost the Jetways when I updated KLGA!

I had issues with KIAD, being completely unflyable at night because the Runway 12/30 runway lights were "messed up". I'm not sure if that's the same issue that anyone else is seeing, but I was able to fix it.I used SCASM to re-orient runway 12/30 to it's reciprocal heading, and adjusted the lighting/markings to reflect the change. Recompiling to .bgl and replacing the runways_01.bgl fixed the issue.I would offer the replacement files, but I'm not sure that would be legit...Unfortunately, the fact that the scenery uses SCASM runways means that there can be problems with invisibile AI, and my tweaks don't correct that issue.If anyone is really dedicated to fixing the lights, and doesn't mind downloading a small program (SCASM) and editing a few lines in a .txt file, I can post the steps to fix it here.

That is good new that it is fixed now. I'll install tonight. The IAD problem is the same as the one at LGA so I would bet they will take care of the IAD problem eventually. Are the new installers the complete package or do I need to install the old version first?

That is good new that it is fixed now. I'll install tonight. The IAD problem is the same as the one at LGA so I would bet they will take care of the IAD problem eventually. Are the new installers the complete package or do I need to install the old version first?

Jeff--They're updates, not complete installs. You'll need to install a complete earlier version first.Nick--I'd really appreciate seeing that how-to on fixing this problem.CheersBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Nick--I'd really appreciate seeing that how-to on fixing this problem.

Bob,No problem. A few notes first:The problem I had with KIAD was extremely low fps whenever the runway/approach lighting for runway 12/30 was in view. Additionally, the lights for that runway appeared oversized, and very different than the other runways. I'm not sure if that's the same issue that others are seeing or not. Nonetheless, the problem can be fixed by swapping the heading of the SCASM runway that Imaginesim used to create the default lighting effects.This "fix" could conceivably be used for other problem airports, but you would need to substitute the proper data for the runway in question.I wrote Imaginesim and provided my modified files for their reference, and was informed that they were working on an update that would remove any traces of legacy SCASM-based scenery, and would cure performance issues. That update should be forthcoming. I don't know what alternative method they chose, or when the update will be made available.In the mean time, you can try the following manual fix. Insert all the small print stuff here, like BACKUP YOUR ORIGINAL FILES!!!!, and I'm not responsible if your computer blows up, and Imaginesim might not take kindly to your modification of their files and will certainly will not provide support for them. So, do this at your own risk, mmmkay?Here goes...1) Download a program called BGL Analyze from the AVSIM library here: BGLAnalyze v3.12) Download a program called SCASM here: SCASM v2.963) Unzip both to a convenient temporary directory.4) Run BGLAnalyze and open the "runways_01.bgl" file found in the "/Imaginesim/KIAD Washington/Scenery" directory.5) Choose "Disassemble" from the menu bar, and then choose "BGL". Choose the folder where you unzipped SCASM, and save the resulting .sca file. You can now close BGLAnalyze.6) Navigate to the location of the .sca file you just saved, and open it with any text editor. Word Pad or Note Pad work fine.7) Look for an entry that begins with:"Runway( N38:56:19.26 W077:28:23.50Alt 95.4Heading 290.8blahblahblah..."And replace that entire entry with the following:Runway( N38:56:19.26 W077:28:23.50Alt 95.4Heading 110.8Length 10501 ; in feetWidth 150 ; in feetMarkers 00Id 30 Lights 19Surface FFThreshold 0ThrOffN 0ThrOffF 0ExtN 0ExtF 0ThrLightsN 69AprLN 3StrobesN 5VasiBarsN 8VasiSpaceN 700VasiDistN 4280VasiSideN 139VasiSlopeN 3.0ThrLightsF 5VasiBarsF 8VasiSpaceF 700VasiDistF 3700VasiSideF 137VasiSlopeF 3.0)I'm not sure that it matters, but feel free to excercise the TAB key and format the replacement entry to match the surrounding entries.8) Save the file and exit.9) Drag the "runways_01.sca" file over the SCASM program icon, and a new .bgl should be generated.10) Place this new .bgl into the "/Imaginesim/KIAD Washington/Scenery" directory.That's it. For me, the result was MASSIVELY improved fps, and the appearance of the lights are now "normal".

Thanks Nick...I'm gonna go give this a try.CheersBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

I just stumbled on this topic, and was hoping I could do the same for TJSJ. What exactly should I edit?here is the runways_01 file

; ----------------------------------------; runways_01.bgl disassembled by BGLAnalyze © on Sat May 22 22:58:10 2010; ----------------------------------------Header( 1 N18:53:24.74 N17:59:28.03 W065:31:37.06 W066:28:28.94 )LatRange( N17:59:28.03 N18:53:24.74 ); since SCASM does not support multiple latitude ranges; the range has been set to the minimum/maximum latitude.; LatRange information in the BGL file is given as comment.; If you want to use band separation, you must edit; the source file manually.; Insert the "Set( FSVers 0x800 )" instruction at the beginning; of the file, if you want to use the FS2002 instructions; for the facilities sectionmif( [$Version < 285] ) Error( You need at least SCASM version 2.85 to compile this code )mifend; ----------------------------------------; Procedural scenery; ----------------------------------------; LatRange( N17:59:27.93 N18:53:22.18 ); ----------------------------------------; ----------------------------------------; Object # 1, offset: 0x000A size: 168 bytes (0x00A8) ;; Lat: 0001F4528h Lon: 0D110EA3Ch; ----------------------------------------Area( 5 N18:26:26.35 W066:00:03.00 40 ) Runway( N18:26:00.60 W066:00:07.81 Alt 2.7 Heading 90.1 Length 8016 ; in feet Width 150 ; in feet Markers 00 Id 10 Lights 7 Surface FF Threshold 0 ThrOffN 0 ThrOffF 0 ExtN 0 ExtF 0 ThrLightsN 05 AprLN 2 StrobesN 3 VasiBarsN 3 VasiSpaceN 700 VasiDistN 2861 VasiSideN 119 VasiSlopeN 3.0 ThrLightsF 05 VasiBarsF 4 VasiSpaceF 700 VasiDistF 3451 VasiSideF 122 VasiSlopeF 3.0 ) Runway( N18:26:39.00 W066:00:05.66 Alt 2.7 Heading 66.8 Length 10002 ; in feet Width 200 ; in feet Markers 00 Id 8 Lights 7 Surface FF Threshold 0 ThrOffN 0 ThrOffF 0 ExtN 0 ExtF 0 ThrLightsN 05 AprLN 3 StrobesN 3 VasiBarsN 8 VasiSpaceN 700 VasiDistN 3851 VasiSideN 142 VasiSlopeN 3.0 ThrLightsF 05 VasiBarsF 3 VasiSpaceF 700 VasiDistF 3851 VasiSideF 148 VasiSlopeF 3.0 )EndA; sorted list of objects; N18:26:26.35 W066:00:03.00 Object # 1; ----------------------------------------; end of SCASM source

David,Unfortunately, I don't have TJSJ, so I'm not sure if it suffers from the same issue I observed in the KIAD scenery. I'm not even sure if the issue I saw at IAD is the same issue anyone else has...it could just be a graphics card driver issue for all I know.If you're seeing grossly oversized and "stark" hard edged lights for a specific runway, then that issue could potentially be corrected by turning the SCASM runway 180 degrees. From what little experimentation I've done, it appears that SCASM want the "base" end of the runway to be 1-18, and not 19-36. From the looks of the SCASM code you supplied, it already complies with that standard. If you're not seeing the symptoms described above, then switching the code could very well break the rendering of the lights. However, if you're desperate and want to try swapping ends anyway, make a backup of your original .bgl and modify your SCASM code to this:

; ----------------------------------------; runways_01.bgl disassembled by BGLAnalyze

or another idea..... Im just gonna throw it out there.....Why doesnt ImagineSim fix it????????????????

They said they're working on updating their previous releases one at a time, and that IAD was next after LGA. My solution is merely a temporary "community" fix, that I hope can help others in the interim.

That's it. For me, the result was MASSIVELY improved fps, and the appearance of the lights are now "normal".

Thanks Nick! It worked for me too!Best regards,Jim

Thanks Nick! It worked for me too!Best regards,Jim

Awesome, Jim. I'm glad it was useful for you. I was worried that what I was seeing was a system specific issue, and that the "fix" wouldn't be of any benefit to others.