Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

KLGB version 5 uploaded

Featured Replies

I copied the two C-17 files into my KLBG Scenery folder as directed and I get the C-17 too far forward. The engines are into the building and the wings hit objects too. Bob.

 

  • Replies 40
  • Views 7.3k
  • Created
  • Last Reply

Top Posters In This Topic

I copied the two C-17 files into my KLBG Scenery folder as directed and I get the C-17 too far forward. The engines are into the building and the wings hit objects too. Bob.

Agreed. Still having pause issue also.

Angelo Cosma
PPL ASEL / IFR
Federal Aviation Administration (FAA) 

Field Service Representative (SEA) ZSE ARTCC

Intel i7 6700K 4.8Ghz / ASUS ROG Maximus Hero VIII / 16GB DDR4 3200Mhz Ram / EVGA 1080Ti FTW3/ Corsair H110i GTX EVGA 850 Watt Gold / Samsung 850 500gb SSD

I have v5 KLGB installed and default KLAX. I flew the PMDG NGX into KLGB ILS R30 so no overfly of the airport first. And had no pause. I did not install the C17. I'll try it a few more times to test.

 

Dave

Dave Paige

In addition to the fact that the C-17 is too far forward the readme says there are two C-17's parked somewhere. There is only one. The bgl placement file has two at the exact same location"

 

<!-- Created by Scenery Design Engine (SDE) on 6/27/2014 -->
<FSData
   version="9.0"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xsi:noNamespaceSchemaLocation="bglcomp.xsd">
   <SceneryObject
      lat="33.8118728622794"
      lon="-118.151141703129"
      alt="0.0M"
      altitudeIsAgl="TRUE"
      pitch="0"
      bank="0"
      heading="0"
      imageComplexity="NORMAL">
      <LibraryObject
         name="{24e08c21-7470-491d-9d80-481908e101df}"
         scale="1.00"
         />
   </SceneryObject>
   <SceneryObject
      lat="33.8118728622794"
      lon="-118.151141703129"
      alt="0.0M"
      altitudeIsAgl="TRUE"
      pitch="0"
      bank="0"
      heading="0"
      imageComplexity="NORMAL">
      <LibraryObject
         name="{24e08c21-7470-491d-9d80-481908e101df}"
         scale="1.00"
         />
   </SceneryObject>
   <ModelData
      sourceFile="24e08c21-7470-491d-9d80-481908e101df"
      fileOffset="0"/>
</FSData>

 

Bob.

  • Author

This is slightly off-topic, but your fix pointed to the sunsky jet page? Are you a developer with that team? 

Yes.

 

Shez

Shez Ansari

Windows 11; CPU: Intel Core i7-8700K; GPU: EVGA GEFORCE GTX 1080Ti 11GB; MB: Gigabyte Z370 AORUS Gaming 5; RAM: 16GB; HD: Samsung 960 Pro 512GB SSD, Samsung 850 Pro 256GB SSD; Display: ASUS 4K 28", Asus UHD 26"

  • Author

I copied the two C-17 files into my KLBG Scenery folder as directed and I get the C-17 too far forward. The engines are into the building and the wings hit objects too. Bob.

Bob,

 

Please check there is only one file called C17s.bgl in the scenery folder. This should be from LGBfix1. No other files referencing C17s should be there.

 

Shez

Shez Ansari

Windows 11; CPU: Intel Core i7-8700K; GPU: EVGA GEFORCE GTX 1080Ti 11GB; MB: Gigabyte Z370 AORUS Gaming 5; RAM: 16GB; HD: Samsung 960 Pro 512GB SSD, Samsung 850 Pro 256GB SSD; Display: ASUS 4K 28", Asus UHD 26"

Bob,

 

Please check there is only one file called C17s.bgl in the scenery folder. This should be from LGBfix1. No other files referencing C17s should be there.

 

Shez

Hi Shez. My mistake. I did not apply the fix. There are two files (c17 US Library.bgl and C17s.bgl). Without the fix there were two C-17's at the same place. With the fix they are correct. I could swear that I applied the fix but I must not have overwritten the C17s.bgl. Regards, Bob.

Who else still experiences the pause? With or without FSDT KLAX?

Angelo Cosma
PPL ASEL / IFR
Federal Aviation Administration (FAA) 

Field Service Representative (SEA) ZSE ARTCC

Intel i7 6700K 4.8Ghz / ASUS ROG Maximus Hero VIII / 16GB DDR4 3200Mhz Ram / EVGA 1080Ti FTW3/ Corsair H110i GTX EVGA 850 Watt Gold / Samsung 850 500gb SSD

Okay with FSDT KLAX unchecked in scenery library the pause did NOT occur. Is there a way to force KLAX to load earlier? Is there a way to keep KLAX active and avoid the freeze problem? Maybe with the Altitude Cull slider or anti pop up slider for FSDT? What have you guys tried?

Angelo Cosma
PPL ASEL / IFR
Federal Aviation Administration (FAA) 

Field Service Representative (SEA) ZSE ARTCC

Intel i7 6700K 4.8Ghz / ASUS ROG Maximus Hero VIII / 16GB DDR4 3200Mhz Ram / EVGA 1080Ti FTW3/ Corsair H110i GTX EVGA 850 Watt Gold / Samsung 850 500gb SSD

After testing this, I still observed the pause with all of my LA/OC area addons disabled. The default airport, with all area addons still disabled, had a slight stutter, but not the 1 or 2 second pause I had with KLGBv2. Not sure what the issue is, but it's small enough for me not to fret over it, I am re-enabling all the airports in the LA Basin again and going flying.

Ethan Edelson

Do the approach lights to RWY 30 ever illuminate? I have flown at night with less than 3 miles viz and I have the runway edge lights visible but no centerline or approach strobes.

 

Angelo

Angelo Cosma
PPL ASEL / IFR
Federal Aviation Administration (FAA) 

Field Service Representative (SEA) ZSE ARTCC

Intel i7 6700K 4.8Ghz / ASUS ROG Maximus Hero VIII / 16GB DDR4 3200Mhz Ram / EVGA 1080Ti FTW3/ Corsair H110i GTX EVGA 850 Watt Gold / Samsung 850 500gb SSD

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.