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.

ztimbre

Members
  • Joined

  • Last visited

  1. Sorry to come late to the party.... can someone point me to where Carenado said they'll add GTN integration? Did they make any mention of the RealityXP units? Thanks. Z.
  2. That's fixed it for me! Thanks for the speedy update! Z.
  3. Hi Shez, Thanks very much for the new version. Ground flickering is solved! I am still having frame rate drops. I took some time this afternoon and isolated the problem to the file "LGBrunwaylights.bgl" It looks like you are using SCASM lights, and considering the runway headings at LGB, I think you are encountering the problem described in this thread: http://www.fsdeveloper.com/forum/threads/scasm-lights-kill-my-fps.21793/#post-194616 This problem will not appear for people using FSX+SP2, only those using acceleration (which I am). I've checked the scenery at night, and it appears that the problem sections are the runway overruns. I am a scenery designer, and would be happy to test/tweak, if you like. Thanks again for a great scenery! Z.
  4. Well, I am always open to learning something new. I'm no expert, but I can think of many factors that would have a big influence on the sink rate at touchdown in different aircraft/situations, such as different autopilot software, inaccurate payload data in the FMS, errors in the air data system, pilot carrying extra speed, etc.I respect PMDG and LVD's work, and their dedication to accuracy. Personally though, I am not really interested in comparing the CS behavior to other sim aircraft. I am only really interested in comparing with what the real world aircraft does. So, My comment comes from numerous discussions on aviation forums, for example this thread at, ironcially, the CS forums.http://www.captainsi...?num=1300307356Now whether you believe the user "LOU" is a real commercial pilot is up to you. But google will turn up a bunch of the similar discussions I'm sure.This document is the one that was sticking in my memory.http://www.smartcock...ted_Runways.pdfwhich gives the rationale, and says that average touchdown rates are 3 ft./sec. (180 fpm), with as low as 2 ft/sec. (120 fpm) and up to 5 ft/sec. (300 fpm) being very common, and up to 10 ft./sec. (600 fpm) permitted. (yes, the doc is about airbus, but I've seen the same for boeing.)So the 400 fpm of the CS 757 maybe a bit on the high side, but none of these sources say that typical autoland systems are striving for sub 100 fpm touchdowns.Anyway, I've just emailed a friend of mine who, until recently, flew 737s and (I believe) 767s. He says he will check the AFM to see what it says.p.s. -hell just froze over. Never thought I would find myself 'defending' anything CS does....
  5. 400 FPM is not really excessive for an autoland, according to everyting I have seen. The computer is not trying to 'grease it on'. The goal is to make a firm landing so that there is no delay in getting the autobrakes engaged and the spoilers up to provide maximum stopping distance.My only question is: will the CS 4.6 meet descent crossing restrictions when in VNAV mode? Previous versions were absolutely terrible in that area. (For example, the KEPEC2 arrival into KLAS which is pretty demanding and was absolutely mangled by previous versions of the CS 757.)
  6. very nice shots BrzI! Would you mind another request for you config files.? I'd be grateful if you would send them to me at madroad41 [at] hotmail [dot] comCheers!
  7. Hi Dick,Sorry to intrude, but can you recommend a good screenshot program? What do you use? I have had trouble finding a good program that will capture images larger than my screen resolution (currently 1600 x 1086).cheers,ZI have
  8. Thank you Carenado, fantastic aircraft! I've been flying the wings off all models (and no bouncing issues at all). :)Thanks for remembering your FS9 users. I bought the standard FSX version as well, specifically to thank you for continuing to build for FS9.
  9. ztimbre replied to a post in a topic in Carenado General Forum
    Great news, thanks Carenado!!
  10. ztimbre replied to a post in a topic in Carenado General Forum
    I've purchased the FSX version and it is great. However, I still prefer to fly FS9 and can't wait to get the C185 in that sim!Eagerly awaiting news from Carenado :D
  11. Just a thought... but are you guys using that utility that resets the tower view to the nearest airfield as you fly along? (I believe it is called "autower")
  12. Hi Jim,Thanks for the continued suggestions. Altimeter is still set to the 'B' key, and does work some of the time, as described above. The weather theme in FS when ASE is running does show as User Defined.Over the past couple days, I have continued to test various configurations of FS and ASE in an attempt to isolate the conditions that cause the problem. At this point, it appears to be caused by DWC. Every flight I have done with DWC on has suffered some problem (including, in one flight, the 'reversed winds' described in another thread here). SO FAR, every flight that I have done with DWC OFF has been error free. Altimeter, winds, visibility all render correctly at all stages of flight. I have only done three or four flights with DWC off, so I want to test further before definitely saying it is the faulty element.
  13. Hi,Afraid not. No other FS software running.Is there any significance in the fact that, on last night's flight ASE said the altimeter at KECS should be 29.80, but according to the ASE_log file it is sending 29.74?12:49:52 AM:0593 - Sent String: KECS 270159Z AUTO 34011KT 10SM CLR 03/01 A2974 RMK

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.