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.

Airplane_21

Members
  • Joined

  • Last visited

  1. Thanks John, I appreciate the insight. I'll give the trial-and-testing a go and see what comes about.
  2. Of course I have, I've referenced AS16 all throughout my post. My aircraft speed drops to 0KTS when ActiveSky 2016 is being used for real world weather at cruise altitude. Apologies if my post was unclear, but yes my whole issue pertains to AS16!
  3. Went through a similar experience 2 months ago and after waiting around for a week, I came to the conclusion that FSXWX has unfortunately said goodbye to us flight simmers. Even their website won't load properly now. It's a massive shame! On the other hand however it forced me to finally give in and purchase ActiveSky 2016 during their winter sale and I can definitely say it's worth the money. If you have the finances, please purchase AS!
  4. I'm really hoping a fellow flight simmer would be able to shed light on what's going on. When ascending to cruise altitude/flying at cruise altitude, if I attempt to momentarily change simulator windows (as in, pressing ALT+ENT to minimize FSX or enter the map view mode by selecting World > Map), on entering back into the sim my aircraft drops out of the sky because my airspeed plunges to 0 KTS. I thought maybe Ultimate Ground X or AISmooth addon(s) were causing issues, so I disabled both of them and only ran AS16. Issue still continued. I thought maybe increasing the simulation speed to 4x is causing issues, so I flew in normal simulation speed to cruise altitude. Issue still continued. Event though I always go through pre-flight checklists before take off, I double checked that my pitot heat/anti-ice systems were on, and sure enough they were. I confirmed this on various aircraft, including the default A321/B737/B747 and even my payware PMDG 777 and 747. Issue continued! I am now quite simply stumped as to what is causing my aircraft to suddenly just stall out of the sky and drop the airspeed to 0KTS out of nowhere. My aircraft just falls out of the sky and crashes! Could anyone please help me figure out what is going on. 😞
  5. Hi, apologies for the late reply. Please try to view the images again in this link: https://ibb.co/pnJnYzb https://ibb.co/ZNC2j7x and https://ibb.co/pnJnYzb https://ibb.co/ZNC2j7x The first image is showing the towbar missing, the second image is showing the airport top-down view while trying to edit the pushback route and the lack of green arrows that would show the pushback route. Yes some of my other default and payware aircraft don't have this issue -- I can see the towbar on the Schopf vehicle. But a majority of my aircraft don't when using any of the pushback vehicles. I can see the ground personnel just fine however.
  6. Apologies for the late reply. Yes I've triple checked the manual, tried to uninstall and install the programme on my FSX again and still no luck. I've found out that the issue is with other aircraft as well! Attached below is an example on a Thomas Ruth A330 add-on... Screenshot01 Please let me know what's going on?
  7. UPDATE -- For anyone who might face similar issues, deleting the add-on and then copying the entire add on back into the /SimObjects folder did the trick. Not sure what caused the strange issue, but a simple "delete/add" again did the trick.
  8. Thank you for the reply. Could you please disclose a bit more about which specific section I should be looking at in the aircraft.cfg? How much more would you recommend raising them to?
  9. I recently installed UGCX V2.6 and on trying to pushback with a specific freeware aircraft (a OpenSky B747-8i) at a default airport (Boeing Field) with no add-on scenery, the towbar is not visible at all. I can see the marshallers however. Also, on trying to create a custom pushback route, I can't see the 'green arrows' that would otherwise appear from the top-down view when in editing mode to show the custom pushback path and where the aircraft would stop -- I do not have EZDOK or any other recording software downloaded. What can I do to fix these issues?
  10. I suddenly have a bizarre issue where my Project Airbus A320 is "jumping" and jolting around on the ground parked at a gate -- engines off, weight and balance completely okay. It jumps around on the spot and eventually slides off of its position and completely off the taxiway centerline. When I switch to another Project Airbus A318 aircraft, that doesn't jolt around at all, yet 2 other PA A320 models suddenly have this strange issue. There has been no change to the aircraft.CFG of any kind. I recently installed ActiveSky 2016 -- I thought maybe some erroneous setting there is over exaggerating surface wind conditions, but when I start FSX without using AS, the problem still persists. I've also disconnected my Logitech joystick, and yet the issue still persists. So that's 2 potential problems that have been ruled out. Can anyone please help me understand how to fix this? I am presuming some sort of Center of Gravity issue exists...here's the weight and balance section: [WEIGHT_AND_BALANCE] //Cebu Pacific A320-214 RP-C3241 config //Pax Zonings station_load.0= "7605.9, 21.24, 0.000, 0.000, CAB OA (60)" station_load.1= "7149.6, -3.33, 0.000, 0.000, CAB OB (60)" station_load.2= "6541.1, -26.34, 0.000, 0.000, CAB OC (59)" -ok //Cargo & Baggage station_load.3= "2921.1, 22.10, 0.000, 0.000, CPT 1" //Compartment 1 (7500lbs) station_load.4= "3086.5, -11.99, 0.000, 0.000, CPT 3" //Compartment 3 (5349lbs) station_load.5= "1190.5, -22.67, 0.000, 0.000, CPT 4" //Compartment 4 (4652lbs) station_load.6= "171.96, -33.11, 0.000, 0.000, CPT 5" //Compartment 5 (3300lbs) //Basic Weight 42637 kgs | 93998 lb //Crew 3/4(1 OBS)= 520 kgs | 1146 lbs //Pantry Wgt Sector- DOM= 570 kgs | 1257 lbs ----------------------------------------------------------- //Dry Operating Weight/Index= 43727 kgs | 96401 lbs 56.5 ----------------------------------------------------------- //"weights in kilos" //ZFWCG/MACZFW= 31.8% / 56.7 reference_datum_position=0.000000,0.000000,0.000000 empty_weight_CG_position=0.000000,0.000000,0.000000 empty_weight=91833.343750 empty_weight_roll_MOI=0.000000 empty_weight_pitch_MOI=0.000000 empty_weight_yaw_MOI=0.000000 empty_weight_coupled_MOI=0.000000 max_gross_weight=180750.005859 [WEIGHT_AND_BALANCE] empty_weight=96401.4 empty_weight_roll_MOI=959904.000000 empty_weight_pitch_MOI=1710000.000000 empty_weight_yaw_MOI=1230000.000000 empty_weight_coupled_MOI=0.000000 max_gross_weight=169756 reference_datum_position=0.0000,0.000000,0.000000 empty_weight_CG_position=0.63,0.000000,0.000000 CG_forward_limit=0.18 CG_aft_limit=0.40 //Weight & Balance prepared by PB. (Version 179 Y)
  11. I have the amazing ATN gauge V1.2 (atngau12_148688.zip) by Etienne Martin added to my FSX on my Windows 10 system, with all installation instructions having been followed, including placing the important MSVCR71.dll file in the Windows>System32 folder that the gauge needs to run properly as well as the gauge file itself in the FSX > Gauges default folder. This gauge is also installed on my Windows 7 PC on FSX, where it works absolutely fine, but since switching to Windows 10, the gauge doesn't show up at all. I've tried to copy paste the exact gauge coordinates in the panel.cfg folder of my FSX aircraft from Windows 7 to Windows 10, and still the gauge refuses to show up. All other default gauges are showing up as normal. I can even see that FSX recognizes my panel entry in the Instruments > Pushback toggle bar, but the gauge itself won't display. I understand that this is a FS2004 file as well, but it was working perfectly fine with FSX too on my Win7 system for 3 years as previously mentioned. This is an example of the panel.cfg entry in my default B737-800 of this gauge under the necessary sections as instructed in the installation file: [Window Titles] window00=Main Panel window01=Radio Stack Window02=GPS Window03=Throttle Panel Window04=Overhead Panel Window05=Autopilot Window06=PFD Window07=MFD Window08=EICAS Window09=Mini Panel Window10=Pushback [Window00] file_1024=737-800_panel_background.bmp file_1024_night=737-800_panel_background_night.bmp size_mm=1024 position=7 visible=1 ident=MAIN_PANEL gauge00=B737_800!pfd_screen, 189,548 gauge01=B737_800!pfd, 210,567,179,179 gauge02=B737_800!mfd_screen, 409,548 gauge03=B737_800!mfd, 430,567,179,179 gauge04=B737_800!eicas_screen, 740,548 gauge05=B737_800!eicas, 760,565,179,179 gauge06=B737_800!compass, 839, 39 gauge07=B737_800!autopilot, 561,330 gauge08=B737_800!knob_1, 329,501 gauge09=B737_800!knob_2, 390,501 gauge10=B737_800!knob_3, 830,480 gauge11=B737_800!clock, 77,570 gauge12=B737_800!attitude_backup, 630,444 gauge13=B737_800!adf_vor_backup, 630,662 gauge14=B737_800!alti_and_asi_backup, 631,555 gauge15=B737_800!gear_lever, 959,524 gauge16=B737_800!annunciator_below_glideslope, 214,517 gauge17=B737_800!annunciator_le_flaps, 854,516 gauge18=B737_800!annunciator_speed_brake_armed, 516,516 gauge19=B737_800!annunciator_auto_brake_disarm, 823,441 gauge20=B737_800!annunciator_anti_skid_inop, 812,517 gauge21=B737_800!efis_control_panel, 416,344 gauge22=B737_800!flap_indicator, 892,452 gauge23=B737_800!annunciator_panel_1, 267,361 gauge24=B737_800!annunciator_panel_gear, 958,454 gauge25=B737_800!Knob_N1_Set, 755,454 gauge26=SimIcons1024!ECU Icon, 433, 448 gauge27=SimIcons1024!Overhead Icon, 455, 448 gauge28=SimIcons1024!Kneeboard Icon, 477, 448 gauge29=SimIcons1024!ATC Icon, 499, 448 gauge30=SimIcons1024!Map Icon, 521, 448 gauge31=SimIcons1024!GPS Icon, 543, 448 gauge32=SimIcons1024!Radio Icon, 565, 448 gauge33=SimIcons1024!Other Controls Icon, 587, 448 gauge34=n_number_plaque!n_number_plaque, 95,731,67,19 gauge35=Atn!Toggle ,0,0,1,1,15123 [Window10] position=3 BACKGROUND_COLOR=0,0,0 size_mm=300,192 window_size=300,192 visible=0 sizeable=1 ident=15123 gauge00=Atn!Pushback,0,0,300,80,15123 gauge01=Atn!Scale,0,80,300,56 gauge02=Atn!Electric,0,136,300,56 I'm confused as to why the gauge won't display on my Windows 10 installation, considering I've installed it exactly as it was previously. Any help whatsoever regarding why this is happening would be greatly appreciated!

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.