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.

woweezowee

Members
  • Joined

  • Last visited

Everything posted by woweezowee

  1. Now I'm really curious to see what developers will (and what they can) do with this finding. If it puts an end to the everlasting roll-debate, that would not only make X-Plane better, but very likely that forum here, too
  2. Maybe I stand corrected. I got valuable information from one developer of aircraft for X-Plane, that a solution for the torque issue would require a plane maker setting of its own - at least. So, ok. Back to FlyII for single engines? Nah… I enjoy my X-Plane fleet. Sorry for confusion.
  3. A "fix" only comes with valuable input based on hard facts. As far as I know that was the latest state of affairs: by Goran: http://forum.avsim.net/topic/410410-trying-to-like-x-plane/page-5#entry2690530 Edit: One last note: Dan is very active in the *.org support forums. The issue should be taken there in order to get some "official" feedback (and discussion): http://forums.x-plane.org/index.php?showforum=106
  4. There's lots of stuff that has to be fixed by Austin and his team, that's right. But he's not the one to fix other peoples bogus flight models. It can be done better, Dan knows and should do better. There's a reason that alternate plane maker mods are discussed and suggested for nearly every Carenado single engine. For the C208 it was even published by Carenado themselves.
  5. You other guys read this, right? ok. So please contact Dan Klaue, the author of the flight model. The C185 isn't affected that much, too (*). So he basically already should know how to make it better. If Austin changes the stuff system-wide, a whole lotta planes that already exist will be affected. Doesn't make sense to me to call for that. That already had happened several times, e.g. when Austin "fixed" the critical altitude. Aircraft authors should adjust to what's there in such a major version run. Because it's possible to make good flight models in X-Plane. (*) Curiously, the first version of the 152 for 64-bit (2.0) wasn't affected that much, too. Version 2.01, published only a short time later to adress some bugs, suddenly rolls way too much. So. This call has to go to Dan, not Austin.
  6. Always keep a seperate demo install and test new betas on that one first. I'm also crashing on start-up, but that way, it is no issue. As long as it is beta 1 you can still go back to the latest version by unchecking the beta-box in the installer.
  7. read this (and the comments for Mac users) in order to get an update: http://developer.x-plane.com/2013/06/every-week-is-exactly-the-same/
  8. The drawings of e.g. the curves of the taxilines. Watch them change and get edgy with lower settings.
  9. World Distance: Only Medium and I'm used to it. This has been a FPS killer since ages, nothing new with version 10.
  10. As I said, please don't blame it on Carenado. It affects all planes that use SASL and Ben from Laminar does work with several developers in order to solve this for 10.30. At least that's all I know for now.
  11. try it and report back. did not help me.
  12. All SASL plane are affected in 64-bit. Background: http://forums.x-plane.org/index.php?showtopic=65052&p=724742 http://www.xsquawkbox.net/xpsdk/mediawiki/LuaJIT http://developer.x-plane.com/2013/05/aircraft-authors-view-luajit-memory-usage/ SASL 2.0 is ready, 10.30 not: http://forums.x-plane.org/index.php?showtopic=65052&p=739052
  13. That's the LUA issue only to be adressed with the combo of the new SASL 2.0 (just out) and X-Plane 10.30. Most common on Windows, but also existent on Mac. Especially with the C210 for whatever reason.
  14. ah, Goran. Stop Cameron from making second posts like that one in 2014
  15. seems to be true: http://forums.x-pilot.com/index.php/topic/4943-saab-340a-project-cancelled/?p=51388
  16. other necessary updates include stuff like lights etc.; but you'll get back the functionality of the plane by just replacing 1 folder. that's not too much trouble imho .
  17. only those that use SASL, of course. I run the Baron, the Caravan, the Seneca and the A36 in 64bit.
  18. SASL is arleady 64bit. Take one of the available files/folders* and replace the one in your caravan->plugins->sasl folder and the Caravan (likewise any other plane powered by SASL) will already work fine. * Carandos A36 * Challenger300 (see x-plane.org http://forums.x-plane.org/index.php?showtopic=65052) * Dash 8 * …
  19. one of the must have plugins just got an 64-bit upgrade: http://forums.x-plane.org/index.php?app=downloads&showfile=4455
  20. There's a great freeware for X-Plane. Flytampa converted: http://forums.x-plane.org/index.php?app=downloads&showfile=12363
  21. I use it. I beta tested the new version. I love it.
  22. http://forums.x-plan...&showfile=14790

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.