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.

Attitude Indicator (AI) acting wrong

Featured Replies

I searched the forum for results before posting this but didn't find a solution.

After uninstalling, deleting the folder, and re-installing; my AI for the Falcon still has this weird behavior. It's shaking. The co-pilot's AI also shakes. Why?  I have my anti-virus off and the only add-on installed in the sim are the latest versions of  OpusFSI, Milviz weather radar and the RXP gauges (all inactive in this plane at the moment).

Has anyone else had a similar problem and was able to resolve it?
 

Addendum: video replaced. See video below.


 

Edited by oneleg
Added more details.

Hardware: i7-8700k, GTX 1070-ti, 32GB ram, NVMe/SSD drives with lots of free space.
Software: latest Windows 10 Pro, P3Dv4.5+, FSX Steam, and lots of addons (100+ mostly Orbx stuff).

 Pilotfly.gif?raw=1

1 hour ago, oneleg said:

Has anyone else had a similar problem and was able to resolve it?

The first thing I'd try is clicking Ready to Start in the Hanger and turn on the Avionics Master to make sure the AI is correctly powered up, and then see what happens.

Are you using the APU or ground power when this problem happens?

Al

Edited by ark

I have not been able to reproduce the AI problem you are having, and have not seen any similar reports about the AI. BTW, when you uninstall the Falcon, it is important to delete any files that remain in the install location before reinstalling.

And I will repeat the mantra to make sure you have deleted all saved flights, and to use the default F35 as your initial load (default saved flight) into the spinning aircraft selection window. I have found using the F35 for this often is more effective than using other default aircraft, and this has solved a number of problems for users. The F35 seems to be particularly effective in initializing the sim variables before a complex aircraft is loaded.

Al

Edited by ark

  • Author

Will do and report back. Thank you.

Hardware: i7-8700k, GTX 1070-ti, 32GB ram, NVMe/SSD drives with lots of free space.
Software: latest Windows 10 Pro, P3Dv4.5+, FSX Steam, and lots of addons (100+ mostly Orbx stuff).

 Pilotfly.gif?raw=1

  • Author

New video and longer video posted in YouTube below. I loaded the default F35 first before selecting the F50.

Below is my panel.cfg also.

I forgot to turn on the Avionics Swtich Master in the video, but I have since turned it on and off  several times before and after the video and that didn't seem to make a difference. The AI kept shaking. I don't think it's in the video but these instruments would also shake intermittently: Angle of Attack gauge, the HSI, and the lights on the Hydraulic Panel would flash on and off too.
 

//--------------------------Designed by FLYSIMWARE! 2018 FLYSIM530------------------------------

[Window Titles]
Window00 = CONTROL_PANEL
Window01 = AIRCRAFT_OPTIONS
Window02 = PAYLOAD_MANAGER
Window03 = START_INSTRUCTIONS
Window04 = HCP_PANEL
Window05 = WX Advantage Radar
Window06 = FLYSIM_GPS_PANEL

[Window00]
file_1024=HANGAR.bmp
size_mm=1024,1876
window_pos=0.10,0.05
window_size=0.30,0.90
BACKGROUND_COLOR=0,0,0
visible=1
ident=CONTROL_PANEL

gauge00=CONTROL_PANEL!clipboard fuel repair,    50,320,340,320
gauge01=CONTROL_PANEL!clipboard map,            50,650,340,300
gauge02=CONTROL_PANEL!clipboard atc,            50,965,340,280
gauge03=CONTROL_PANEL!clipboard GPS,            50,1250,340,220
gauge04=CONTROL_PANEL!clipboard CABIN LIGHTS,   516,454,37,37
gauge05=CONTROL_PANEL!clipboard DOME LIGHTS,    516,524,37,37
gauge06=CONTROL_PANEL!clipboard RECOG LIGHTS,   516,594,37,37
gauge07=CONTROL_PANEL!clipboard PANEL LIGHTS,   516,664,37,37
gauge08=CONTROL_PANEL!clipboard kneeboard,      445,1005,530,400
gauge09=CONTROL_PANEL!clipboard OPTIONS,        485,1760,520,110
gauge10=CONTROL_PANEL!clipboard COLDSTART,      550,800,300,70
gauge11=CONTROL_PANEL!clipboard HOTSTART,       550,870,300,70


[Window01]
file_1024=AIRCRAFT_OPTION.bmp
size_mm=1050,1050
window_pos=0.55,0.20
window_size=0.40,0.75
BACKGROUND_COLOR=0,0,0
visible=0
ident=AIRCRAFT_OPTIONS

gauge00 = CONTROL_PANEL!clipboard DOOR,           213,125,53,99
gauge01 = CONTROL_PANEL!clipboard DOORLOCK,       271,187,37,37
gauge02 = CONTROL_PANEL!clipboard pilot,          928,471,72,57
gauge03 = CONTROL_PANEL!clipboard pilot2,         757,471,72,57
gauge04 = CONTROL_PANEL!clipboard headset,        846,497,64,49
gauge05 = CONTROL_PANEL!clipboard sunglasses,     846,471,64,21
gauge06 = CONTROL_PANEL!clipboard wheel chocks,   163,259,35,24
gauge07 = CONTROL_PANEL!clipboard PLUGS,          594,46,404,143
gauge08 = CONTROL_PANEL!clipboard pilot image,    881,317,155,145
gauge09 = CONTROL_PANEL!clipboard pilot2 image,   718,317,155,145
gauge10 = CONTROL_PANEL!clipboard OPTIONS,        13,12,427,72
gauge11 = CONTROL_PANEL!clipboard START INST,     17,524,161,75
gauge12 = CONTROL_PANEL!clipboard GPU,            872,196,164,86
gauge13 = CONTROL_PANEL!clipboard PAYLOAD,        17,438,161,75
gauge14 = CONTROL_PANEL!clipboard Shades,         468,378,109,108
gauge15 = FUEL_ROUTES!FUEL_QUANTITY,              0,0,1050,1050
gauge16 = FUEL_ROUTES!FUEL_ROUTES,                0,0,1050,1050
gauge17 = CONTROL_PANEL!clipboard GPU IMAGE,      873,200,164,86
gauge18 = CONTROL_PANEL!clipboard SHADES IMAGE,   503,413,30,30
gauge19 = CONTROL_PANEL!clipboard WHEEL CHOCKS IMAGE,   161,252,30,30
gauge20 = CONTROL_PANEL!clipboard PLUGS IMAGE,    777,103,30,30
gauge21 = CONTROL_PANEL!clipboard DOOR IMAGE,     220,154,30,30
gauge22 = CONTROL_PANEL!clipboard DOORLOCK IMAGE, 269,185,30,30
gauge23 = CONTROL_PANEL!clipboard TRIM VOLUME,    258,532,146,58
gauge24 = CONTROL_PANEL!clipboard CABIN SHADES,   470,583,105,143


[Window02]
size_mm = 800,800
window_pos=0.05,0.20
window_size=0.40,0.75
BACKGROUND_COLOR = 0,0,0
VISIBLE = 0
ident = 801
gauge00 = PAYLOAD_MANAGER!PAYLOAD,        0,0,800,800
gauge01 = PAYLOAD_MANAGER!FUEL_TRUCK,    530,691,254,96


[Window03]
file_1024 = START_INSTRUCTIONS.bmp
size_mm = 800,1000
window_pos=0.05,0.20
window_size=0.40,0.75
BACKGROUND_COLOR = 0,0,0
VISIBLE = 0
ident = 802

[Window04]
file_1024=FLYSIMWARE_HSI_85/HCP_PANEL.bmp
size_mm=2690,275
window_pos=0.17,0.02
window_size=0.7
BACKGROUND_COLOR=0,0,0
VISIBLE=0
ident = 803

gauge00=FLYSIMWARE_HSI_85!HCP_PANEL,              0,0,2690,275


[Window05]
ident = 71
visible = 0
sizeable = 1
size_mm = 419,381
position = 0
window_size = 0.343511450381679,0.556719107690809
window_pos = 0,0
gauge00 = MV_WX!WX2D,0,0,419,381,1
gauge01 = MV_WX!WX,64,121,291,205,1
gauge02 = CONTROL_PANEL!clipboard RADAR,  9,81,400,300

[Window06]
file_1024 = GPS530_PANEL_background.bmp
file_1024_night = GPS530_PANEL_background_night.bmp
Background_color=0,0,0
size_mm = 900,900
VISIBLE=0
ident=800
window_size=0.5
position=3
zorder=99

gauge00 = FLYSIMWAREGPS!LEFT 2D,                  12,60,900,1043
gauge01 = FLYSIMWAREGPS!FLYSIMWAREGPS,            104,60,900,1043
gauge02 = FLYSIMWAREGPS!BOOTSCREEN,              157,237,598,514
gauge03 = CONTROL_PANEL!clipboard GPS,            10,562,120,100

[Vcockpit01]
Background_color=0,0,0 
size_mm=900,900
visible=1
pixel_size=900,900
texture=$gps_1

gauge00=Falcon_50!SYSTEM,             0,0,2,2
gauge01=Falcon_50!FUEL_USED,          0,0,2,2
gauge02=Falcon_50!FUEL_SYS,           0,0,2,2
gauge03=Falcon_50!CLICK,              0,0,2,2
gauge04=Falcon_50!SOUNDS,             0,0,2,2
gauge05=Falcon_50!KEYS,               0,0,2,2
gauge06=Falcon_50!AP_MODES,           0,0,2,2
gauge07=Falcon_50!SPD_HOLD,           0,0,2,2
gauge08=Falcon_50!ALT_HOLD,           0,0,2,2
gauge09=Falcon_50!ENGINES,            0,0,2,2
gauge10=Falcon_50!START_SYS,          0,0,2,2
gauge11=Falcon_50!PRESSURIZATION,     0,0,2,2
gauge12=Falcon_50!TEMPERATURE,        0,0,2,2
gauge14=FBGS_XMLSound_x64!FBGS_XMLSound, 0,0,1,1,Sound\FSW#121
gauge15=Flysimware_Fuel_Dump_x64!Fuel_Dump,    0,0,2,2
gauge16=FLYSIMWARE_CONSOLE!Navigation_FLYSIM530, 0,0,2,2
gauge17=FLYSIMWAREGPS!FLYSIMWAREGPS,    10,10,900,1036
gauge18=FLYSIMWAREGPS!BOOTSCREEN,       66,190,596,509
gauge19=dsd_p3d_xml_config_x64!config,  5,5,5,5, ./gauges/dsd_F50_xml_config_x64.ini
gauge20=dsd_p3d_xml_sound_x64!Sound,  5,5,5,5,
gauge21=Falcon_50!ANNUNCIATOR,     0,0,2,2

[Vcockpit02]
Background_color=0,0,0 
size_mm=512,512
visible=1
pixel_size=512,512
texture=$VCRain

gauge00=FLYSIMWAREVCRAIN!VCRAIN,         0,0,512,512


[Vcockpit03]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$DME

gauge00=FLYSIMWARE_SPERRY_DME!SPERRY DME,         0,6,256,74

[Vcockpit04]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$TAT_TAS

gauge00=FLYSIMWARE_TAT_TAS!TAT_TAS,         0,0,256,256


[Vcockpit05]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$HSI_LCD_1

gauge00=FLYSIMWARE_HSI_85!HSI_LCD_1,         0,0,256,256

[Vcockpit06]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$HSI_LCD_2

gauge00=FLYSIMWARE_HSI_85!HSI_LCD_2,         0,0,256,256

[Vcockpit07]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$HSI_NM_1

gauge00=FLYSIMWARE_HSI_85!HSI_NM_1,         0,0,256,256

[Vcockpit08]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$HSI_NM_1A

gauge00=FLYSIMWARE_HSI_85!HSI_NM_1A,         0,0,256,256


[Vcockpit09]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$HSI_NM_2

gauge00=FLYSIMWARE_HSI_85!HSI_NM_2,         0,0,256,256

[Vcockpit10]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$HSI_NM_2A

gauge00=FLYSIMWARE_HSI_85!HSI_NM_2A,         0,0,256,256

[Vcockpit11]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$ADI_1

gauge00=FLYSIMWARE_ADI_85A!ADI_1,         0,0,256,256

[Vcockpit12]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$ADI_2

gauge00=FLYSIMWARE_ADI_85A!ADI_2,         0,0,256,256


[Vcockpit13]
Background_color=0,0,0 
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$TCAS

gauge00=FLYSIMWARE_TCAS!VSI_TCAS_1,        0,0,1024,1024


[Vcockpit15]
Background_color=0,0,0 
size_mm=512,512
visible=1
pixel_size=512,512
texture=$CLOCK_1

gauge00=FLYSIMWARE_DAVTRON_CLOCK!DAVTRON_CLOCK,     0,0,512,512

[Vcockpit16]
Background_color=0,0,0 
size_mm=512,512
visible=1
pixel_size=512,512
texture=$CLOCK_2

gauge00=FLYSIMWARE_DAVTRON_CLOCK!DAVTRON_CLOCK_2,     0,0,512,512

[Vcockpit17]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$ADF

gauge00=FLYSIMWARE_COLLINS_RADIO!Radio ADF1,         0,0,256,150

[Vcockpit18]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$ADF_2

gauge00=FLYSIMWARE_COLLINS_RADIO!Radio ADF2,         0,0,256,150


[Vcockpit19]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$NAV_1

gauge00=FLYSIMWARE_COLLINS_RADIO!Radio NAV1,         0,0,256,150

[Vcockpit20]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$NAV_2

gauge00=FLYSIMWARE_COLLINS_RADIO!Radio NAV2,         0,0,256,150


[Vcockpit21]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$COM_1

gauge00=FLYSIMWARE_COLLINS_RADIO!Radio COM1,         0,0,256,150

[Vcockpit22]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$COM_2

gauge00=FLYSIMWARE_COLLINS_RADIO!Radio COM2,         0,0,256,150


[Vcockpit23]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$N1_L_ENG

gauge00=FLYSIMWARE_ENG_GAUGES!N1_LCD1,         0,0,256,256

[Vcockpit24]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$N1_C_ENG

gauge00=FLYSIMWARE_ENG_GAUGES!N1_LCD2,         0,0,256,256

[Vcockpit25]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$N1_R_ENG

gauge00=FLYSIMWARE_ENG_GAUGES!N1_LCD3,         0,0,256,256

[Vcockpit26]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$CELSIUS_L_ENG

gauge00=FLYSIMWARE_ENG_GAUGES!ENG1_CELCIUS,     0,0,256,256

[Vcockpit27]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$CELSIUS_C_ENG

gauge00=FLYSIMWARE_ENG_GAUGES!ENG2_CELCIUS,     0,0,256,256

[Vcockpit28]
Background_color=0,0,0 
size_mm=256,256
visible=1
pixel_size=256,256
texture=$CELSIUS_R_ENG

gauge00=FLYSIMWARE_ENG_GAUGES!ENG3_CELCIUS,     0,0,256,256


[Vcockpit29]
Background_color = 0,0,0
size_mm=512,512
visible=0
pixel_size=512,512
texture=$MV_WXM
gauge00=MV_WX!WX,  0,0,512,361
gauge01 = CONTROL_PANEL!clipboard RADAR,  0,0,512,361

[Vcockpit30]
Background_color = 0,0,0
size_mm=256,256
visible=0
pixel_size=256,256
texture=$ATC

gauge00=FLYSIMWARE_ATC!ATC,     0,0,256,256

[Vcockpit31]
Background_color = 0,0,0
size_mm=256,256
visible=0
pixel_size=256,256
texture=$HF

gauge00=FLYSIMWARE_HF_RADIO!HF,     0,0,256,256

[Default View]
X=0
Y=0
SIZE_X=8192
SIZE_Y=6143


Day=255,255,255
Night=255,255,55
Luminous=201,64,64
 

Edited by oneleg
Added details with regards to the other instruments and the avionics master switch.

Hardware: i7-8700k, GTX 1070-ti, 32GB ram, NVMe/SSD drives with lots of free space.
Software: latest Windows 10 Pro, P3Dv4.5+, FSX Steam, and lots of addons (100+ mostly Orbx stuff).

 Pilotfly.gif?raw=1

  • Author

@ark Got the issue resolved by rebooting, disabling the anti-virus again, and making sure that the default plane is the F35, and only the default F35, before selecting complex planes such as the F50. Great tip about using the F35 only for a trouble-free F50. Thank you.

Edited by oneleg

Hardware: i7-8700k, GTX 1070-ti, 32GB ram, NVMe/SSD drives with lots of free space.
Software: latest Windows 10 Pro, P3Dv4.5+, FSX Steam, and lots of addons (100+ mostly Orbx stuff).

 Pilotfly.gif?raw=1

Archived

This topic is now archived and is closed to further replies.

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.