December 13, 201015 yr Hello, For those of you who applied the new V2 KIAD update to find that it did not fix the lighting and horrible performance issues, go into your KIAD\scenery folder and delete the "runways_01.bgl" file (the underscore may not be there. There is only one file that has remotely the same looking name.) DO NOT I repeat DO NOT delete the runway_light_01.bgl file. That is new and it needs to stay.IF the installer put some exclude files along with other files into the root KIAD folder, just copy or move those files into the KIAD\scenery folder and overwrite. Leave the AF2 file alone and don't move or copy that file. Lastly, make sure you only have the new ADE files in the scenery folder and not the old AF2 files. Apparently this caused some elevation issues with some other users.The only draw back I found to my fix is that the TDZ lights don't go all the way back to the threshold. (You'll see what I mean) If this is the way they really are at KIAD then the performance problem is truly fixed after you apply this little fix I found.Feel free to comment on this and offer your support. FAA: ATP-ME, 737 CA, enough time in the 757/767 to be dangerous 🤠 Matt Kubanda, 7950X3D, 64GB RAM, RTX 5090@4k, MSFS 2024
December 13, 201015 yr Hello, For those of you who applied the new V2 KIAD update to find that it did not fix the lighting and horrible performance issues, go into your KIAD\scenery folder and delete the "runways_01.bgl" file (the underscore may not be there. There is only one file that has remotely the same looking name.) DO NOT I repeat DO NOT delete the runway_light_01.bgl file. That is new and it needs to stay.IF the installer put some exclude files along with other files into the root KIAD folder, just copy or move those files into the KIAD\scenery folder and overwrite. Leave the AF2 file alone and don't move or copy that file. Lastly, make sure you only have the new ADE files in the scenery folder and not the old AF2 files. Apparently this caused some elevation issues with some other users.The only draw back I found to my fix is that the TDZ lights don't go all the way back to the threshold. (You'll see what I mean) If this is the way they really are at KIAD then the performance problem is truly fixed after you apply this little fix I found.Feel free to comment on this and offer your support.Thanks...DJ
December 13, 201015 yr Can I ask where you got the runway_01.bgl file info from? I ask becuase the v2 versions of Nassau and Atlanta have that same file. Is this a possible workaround for those airports as well? Regards, Al Jordan | KCAE
December 13, 201015 yr Author Can I ask where you got the runway_01.bgl file info from? I ask becuase the v2 versions of Nassau and Atlanta have that same file. Is this a possible workaround for those airports as well?I was about to try an old fix where one would have to edit the .bgl file. then I noticed that on the updated scenery there where actually two sets of runway lights. One was the default lights and the other were the Imaginesim style lights. I knew that in the first version of the scenery, if one took out the runway_01.bgl file, then all the runway lights would disappear. That being said, I tried taking out the old file and wanted to see if the new runway_lights.bgl would keep the new lights and it did. long story short, the installer never deleted the old runway lights data. Once we manually do that, we also take away those ugly weird looking lights. We also bring back some great performance as well.I am going to try it on KCLT. I am not to optimistic though.Did this work for you?I haven't heard back from Imagine Sim since I emailed them last. If they see this thread maybe they will update their installers. FAA: ATP-ME, 737 CA, enough time in the 757/767 to be dangerous 🤠 Matt Kubanda, 7950X3D, 64GB RAM, RTX 5090@4k, MSFS 2024
Create an account or sign in to comment