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.

Fokker 100 for FS2004...Great!

Featured Replies

  • Author
  • Moderator

>Hi Bill,>>>and don't see any way to assign them to #8 WING lights bus.<>>First let me say I know very little about the aircraft.cfg>file structure but the reason you cannot assign Wing lights to>#8 may be because there is no #8 bus in the Electrical>section. If you look there (at least in the Tay 650) the bus>types only go up to #7.The electrical system for FS9 is set by the sim engine itself, not the aircraft.cfg or .air file. There are a total of 10 electical light busses available for use, whether explicitly defined in the aircraft.cfg file or not... :)>Ooops :-erks, just realised, there's no bus type #9 so the>logo light shouldn't work. Sorry about that.The reason #9 LOGO works is as stated above. The reason #9 WING lights doesn't is because there is no .fx "light" used for the wing lights point source. The only conclusion possible is that the "wing lights" are built into the model and are incorrectly tagged in the Material Editor as LIGHT_NAV (since they respond only to the NAV switch).>Interestingly the Tay 620 aircraft.cfg file contains a much>simpler electrical section with no bus types stated.Sure it does! The only change I made to the following was adding the "missing descriptions" from the //comment line, and changing the bus assignments for the LOGO lights (.5 through .8).[LIGHTS] //Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing 6=taxi, 7=recognition, 8=wing, 9=logo 10=cabinlight.0=1, -6.811, -45.452, -1.505, Fokker_navred ,light.1=1, -6.811, 45.452, -1.505, Fokker_navgre ,light.2=2, -7.092, -45.49, -1.505, Fokker_strobeh ,light.3=2, -7.092, 45.49, -1.505, Fokker_strobeh ,light.4=4, 43.139, 0.00, 0.8, Fokker_vclight ,light.5=9, -22.5, 14.00, 1.0, Fokker_ll,light.6=9, -39.0, 6.00, 5.0, Fokker_ll,light.7=9, -22.5, -14.00, 1.0, Fokker_ll,light.8=9, -39.0, -6.00, 5.0, Fokker_ll,Note carefully that there are NO entries for the WING or NAV lights, hence no .fx "lights" were used on this model. Since they do light up though, they must be defined in the .mdl file using a small poly object and a Material Name light assignment.Isn't deductive reasoning based on extensive knowledge of FS9, GMax and gauge programming wonderful? :)

Fr. Bill    

AOPA Member: 07141481 AARP Member: 3209010556


     Avsim Board of Directors | Avsim Forums Moderator
  • Replies 30
  • Views 4.4k
  • Created
  • Last Reply

Top Posters In This Topic

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.