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.

Mr.Ed

Members
  • Joined

  • Last visited

  1. I replaced my Saitek Throttle Quadrant last week. When I plugged it in for the first time, it reset a lot of my previously custom set key assignments and axis controls...so I had to redo all those assignments and re-calibrate. Everything seemed okay, EXCEPT one annoying issue: every time I come out of Slew mode, throttle goes to 70% and flaps go to 10 degrees...(I have throttle and flaps set to 2 of the quadrant axes). It is as if the controller's axes are being reset to middle position when I come out of slew. I dont know what is causing this and it is very annoying. (Example, when I slew to new position on a taxi way, my throttle revs up to 70%, even though my controller's knob is at 0% (idle). Any ideas what I might be missing? In the meantime, when I come out of slew mode, I just have to quickly move the controller's knobs slightly to get them to respond back to their actual position.
  2. I have a Saitek Switch Panel - all switches and gear work, but the engine knob does nothing... However, the problem is occurring only with my FS9 based aircraft. Is there a modification that I need to make in the "aircraft.cfg", or ".air" file, or is there a particular gauge I need to bridge this apparent disconnect between my aircraft and engine start knob?.. something the FSX default aircraft have that my old FS9 aircraft do not? I know my best solution is to get rid of the old aircraft, and that is my next move if there's no easy fix. Thanks.
  3. The alerts sounds for "Terrain, Pull up" and "Sinkrate" are way too loud, and scare me half to death. I would like not to hear them at all. How do I disable them? I know these sound files are not in my FS9 main sound folder, and not in any of my aircraft sound folders...so I suspect they are gauge controled.I hear these warnings only in my B717 and MD80 panels (freeware)... but I know nothing about gauges and MXL files.Thanks for you help in advance.Eric
  4. These are not standard sound files... I work with FS9 sounds everyday. The sound files in question are not in the main FS9 Sound folder or in any aircraft sound folder, as I have ALL custom sounds in those locations.I appreciate your inputThanks anyway.- Eric
  5. The alerts sounds for "Terrain, Pull up" and "Sinkrate" are way too loud, and scare me half to death. I would like not to hear them at all. How do I disable them? I have not found any sound files, so I suspect they are tied to gauges.Thanks for you help in advance.Eric
  6. >Hi,>>10SM is unlimited for FS04. Are you saying that 10SM gives you>forever clear or 40 with your settings?>>Hope this helps,>JimYes. 100% clarity, but only in the lowest level. If I go into SLEW mode, and rise... I return to limited vis. I took Damian's suggestions... about resetting FSUIPC settings...etc. Didn't help.It must be something that changed when I installed the first ASv6 update. This was not happening before.I will continue to mess around with it, and let you know if I find gold.- Eric
  7. True, 10SM is unlimited for most reporting stations, but I've had the problem with 6 miles visibility at KDCA... and regardless, 10SM should not appear as unlimited with my settings.Have a good weekend...(rest of..)Eric
  8. Wind Direction: Updating FSUIPC appears to have fixed the wind direction problem. I am too embaressed to say what version I had running before. :-)Visibility: Still goes unlimited (after updating FSUIPC). I just did a test flight to KDCA and it happened (METAR report was 10sm), Closing and reopening AS6 while I pause my approach corrects the problem with a reload of the weather. The only other info I can add.. is that this problem is intermittent... >>> It happened today before I landed at KLAS, and just now on approach to KDCA. Last night on approach to KSWF, the problem did NOT occur, visibility stayed true to the METAR report which was about 1 mile.- Eric
  9. Certainly!! The drops bounce off quicker than the eye can see.Nice picture.Thank Goodness for FS9.cfg to get rid of the droplet effect:>> WindshieldPrecipitationEffects=0 <<- Eric
  10. Is it just me, or does FS9 produce very poor precipitation effects? Rain and snow both fall way to too slowly!and more importantly, at slow ground speeds, the precipitation still falls straight down until I reach speeds over 40 kts. In reality, the apparent angle of falling precipitation should immediately begin to tilt diagonally when I start moving. The faster I go, the more tilt there should be! Same thing should happen if there is any wind! Instead, I have rain or snow falling with me until I'm half way down the runway at 50 kts, then it suddenly falls nearly horizontal.Are there any settings or files that can me modified to help?If I remember correctly, precipitation angles and falling speeds were much more realistic in FS2000 / FS2002. This is not a big deal for me, but I was curious to know if anyone else noticed this.Thanks,- Eric
  11. Thanks for the fast reply...I tried both of your suggestions (Jim / Damian), modifying the sight distance in FS does not affect the VIS problem... and although unselecting the Depict Haze Layer helps with transittions, it does not eliminate the "Unlimited Vis".I've had some luck however,It appears this issue may have more to do with weather settings on saved flights. I normally will start with a saved flight.The problem does not occur when I set the visibility level to 40 miles up to 50,000 feet in FS for a saved flight, as long as I immediately load that flight. Problem returned after I restart FS9 and load that flight again... I go back to FS weather settings, and find visibility back to FS9 default (15,000 feet). So it seems, in order for this to work, I must reset this visibility and save the flight before I load it, each time I restart FS9.On a side note, I am very impressed with this product! I am a Meteorologist so I'm particularly critical with weather simulation!!Thanks,I hope this information helps.- Eric
  12. Hey all,I am brand new to Active Sky, just downloaded the new version 6.I too am having a problem with unlimited visibility at high altitudes. I fly commercial jets at FL300 and higher, and have set the AS Visibility Limits to 40 miles. This appears to work at low levels, but as soon as I climb to above 10,000 to 15,000 feet, visibility goes unlimited...which basically kills the realism. There appears to be no specific level at which this happens, expect that it is under 20,000 feet. Seems to happen as I ascend above clouds levels.I have read over other posts regarding this issue, and tried the suggestions, but so far, nothing is working.Does anyone know what the problem is? or is this a dead end.Prior to Active Sky, I simply applied a 40 mile visibility up to 50,000 ft with FS weather settings...and that was great, but trying this with AS doesn't work.Thanks for your help!Happy Holidays too!- Eric DeRocheDell XPS-4002.80 GHz 2.00 GB RAM

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.