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.

GraMcN

Members
  • Joined

  • Last visited

  1. This issue may be due to the missing third line in the "texture.cfg" file for EHAM. The following is from a content creator on another platform pertaining to Cairo but may also be the case for your EHAM: Viktoren69 The issue is caused by Asobo/MS. Easy solution taken from the forum https://forums.flightsimulator.com/t/pink-textures-so-far-eham-only-default-asobo-scenery/729894/26 The problem is caused by a missing line in the “texture.cfg” file located in the airport folders (EHAM and HECA). path example: LocalCache\Packages\Official\OneStore\Asobo-airport-heca-cairo\scenery\cairo The file has only two lines, but it should have three, just like other Asobo airports. All you need to do is add the missing line: fallback.3=Scenery\modellib-texture\ModelLib The whole file should look like this: [fltsim] fallback.1=scenery\cairo\texture fallback.2=Asobo_Buildings\Texture fallback.3=Scenery\modellib-texture\ModelLib
  2. Hello Scot, Yes, I am pretty certain SPAD is not running. As I understand it, SPAD is started either manually or when the OS starts by checking off the option in SPAD. I use neither for this aircraft. While preparing to run the _log as per your suggestion, I thought I would setup the "MJCD8_CheckGearPos" function on an empty momentary switch “on repeat” since it had worked with the gear lever as per post #4. On a check flight, I discovered that after the "MJCD8_CheckGearPos" function was invoked once by this switch, subsequent cycling of the gear resulted in the gear lights working as advertised without further use of this switch. Reassigning the "MJCD8_CheckGearPos" to the rotary switch, which I use for engine start-up (on repeat while engine 2 starts, then released), now achieves the same thing. Here are the rotary switch assignments in my config-hid.lua file: JSTK["06A30D670"][14]="Engine_Eng2_Off" JSTK["06A30D670"][15]="Engine_Eng2_Norm" JSTKrl["06A30D670"][15]="Engine_Eng1_Off" JSTK["06A30D670"][16]="Select_Eng2_and_start" JSTKrp["06A30D670"][16]="MJCD8_CheckGearPos" JSTKrl["06A30D670"][16]="Engine_Select_Neutral" JSTK["06A30D670"][17]="Engine_Eng1_Norm" JSTK["06A30D670"][18]="Select_Eng1_and_start" So for now I believe this should work for me. I think I should be able to get back to flying. :smile: Thank you for your patience and great guidance. Graham McNicol
  3. Hi Scot, Thank you for your explanation. Since I can get the green/red’s to function manually, does this suggest there is something amiss with the function Timer () not referencing the "MJCD8_CheckGearPos" function properly? This is what I see immediately below the "function MJCD8_CheckGearPos ()” section in the action.lua file: function Timer () Tcount = Tcount + 1 --_log('[awg] Tcount = ' .. Tcount) -- FD MJC_APstate = MJCD8_Read(31281) if MJC_APstate ~= 0 then DspFD(1) else DspFD(0) end -------------- MJCD8_VS_Show () MJCD8_ALT_Show () MJCD8_HDG_Show () MJCD8_SPD_Show () MJC_FlightInfo () MJCD8_CheckGearPos() end Does this look correct? Graham McNicol
  4. Well after much trial and successive errors, I stumbled on a fix that is working for me. I added "MJCD8_CheckGearPos" on the switch repeat in my config-hid.lua file. The last 4 lines now look like this: D:\1MS FSX\Modules\linda-cfg\aircrafts\Majestic Dash 8 Q-400\config-hid.lua . . . JSTK["06A30D670"][19]="Other_GearHandle_up" JSTKrp["06A30D670"][19]="MJCD8_CheckGearPos" JSTK["06A30D670"][20]="Other_GearHandle_down" JSTKrp["06A30D670"][20]="MJCD8_CheckGearPos" Is this the proper and required setup? Graham McNicol
  5. Hi Scotflieger, Thank you for your welcome and quick reply. Yes, the switches on the Saitek Switch Panel are all working. I checked the default Beechcraft Baron 58 and the more complex PMDG 777 and both work with LINDA and the Switch Panel with the gear lights showing 3 greens/3 reds. I am not sure what siapanel.exe is but I ran process explorer throughout today’s test with LINDA alone then together with SPAD-on and it did not appear. I have never installed any Saitek software. Would it be useful to provide the contents from the LINDA Console log? (It did not show any errors in red.) Regarding LINDA not reading the switch status until one switch is operated, I wonder if this is common with these kind of devices? I have to move a switch on my CH Throttle Quadrant, press the brake axis on the CH Rudder pedals, and twist the joystick (z-axis) used for ground steering to “wake” them up. But I look at it as part of the pre-flight routine. Best regards, Graham McNicol
  6. I have been using and am enjoying learning about LINDA since last fall primarily for Aerosoft DHC-6 Twin Otter Extended and PMDG 777. Setups were done through a combination of FSX, FSUIPC, SPAD, and LINDA. I recently purchased the MJC8Q400 and things are set up mostly through LINDA and without using SPAD. My problem is that I only get solid green lights on the Saitek Switch Panel landing gear indicator LED’s. My hardware consists of MS FFB2 Sidewinder, CH Pro Pedals, CH Throttle Quadrant, TrackIr and Saitek Switch Panel with all USB’s connected directly into my computer. Software summary: Windows 7-64 FSX SP2 MJC8Q400 Pro 1.018 FSUIPC V4.948 registered SPAD V0.5.1 (not loaded for this aircraft) LINDA 2.6.7 LINDA module Majestic Dash 8 Q-400 version 2.3 I did see a few others with this issue on the forum but do not recall seeing how it was resolved. I would be grateful for any assistance in getting the LED’s working properly with the MJC8Q400. Best regards, Graham McNicol (near CYKZ, Canada)

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.