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.

Luis Hernandez

Members
  • Joined

  • Last visited

  1. There's a guy here that runs FS2024 in a 5600X, but a 3060Ti (strangely, he hasn't chimed in yet). But he flies in 1080p. What resolution do you use? Also, you may struggle with VRAM, specially if you use 8K textures for aircraft and sceneries. If so, textures can be resized to something more manageable: Since this, I never ever again use 8K textures. My 5060Ti no longer sees over 12 GB of VRAM usage, and camera changes are now quick.
  2. Thanks, Umberto! Would implementation be the same as in 2020 (BGLs that only worked with default, unaltered airports) or would it be something more similar to the old FSX/P3D L2 jetways (the ones that replaced every single default jetway in the sim)?
  3. Hopefully it works in default airports and also AFCAD ones (as it was in the old FSX/P3D version). The MSFS2020 jetways had the problem that they only worked with default airports and any add-on would render them useless
  4. Last time I installed it, the winglet version was also installed automatically. There should be 2 folders for the Level-D 767 in SimObjects\Airplanes. One of them is for the winglet version
  5. Just tried again last night in my laptop, setting FS9 in fullscreen mode, and enabling antialiasing in Settings>Hardware, and not only it works, but apparently I get better performance than in windowed mode. Apparently the issue is in FSX only (and I thought it affected both sims). This changes everything I knew about FS9 in Win10/11. I stand corrected.
  6. I agree, man. I'm currently in FS2024, but sometimes I fire up P3D, and not precisely because of the 747. In 2024 I have the 772 ER and the 738. In P3D I had all Boeings but the 748-8 and 772 ER. I can't say I hate them, but I'm disappointed. With that behavior of theirs (and their value of two coffees), I'm not sure about getting the rest of the fleet for 2024. Yes. I understand PMDG updated all legacy installers to the latest version, so that no updates are required anymore. If only they had downgraded OC2 so that it could install offline PTPs...
  7. Tinmouse! I had some great flights in this plane in FS9 (and some IRL, as passenger), with all variations (mechanical HSI or the ISG EHSI, and both Sperry 77 and 177 autopilots). I hope the brave one that decides to develop this plane considers these variations 🙏🏻 PS: your username checks out😉
  8. If I were you, I'd only use FLCH for descent when doing an expedite or emergency descent. In all planes I've flown in the sim, it was too harsh and unstable. Either VNAV or VS were a lot smoother. The beauty of the E-jets (either FSS base, FSS experimental or even Wilco/Feelthere) is that the FPA mode can be used*. I simply set it to -3.0 degrees and that's all. At least it worked for me last night. But well, I'm not a pilot, an actual one may say something different 🤷🏻‍♂️
  9. After watching some YouTube tutorials, I find the problem is located between stick and seat: looks like the procedures I applied years ago with the Wilco E-jets are not the same as the FSS ones 🙈 With that, I was able to do a flight with the basic version (replacing VNAV with FLCH for climb, and FPA for descent). For $28, I liked it. That will have to do until FSS fixes their Updater for the Experimental version.
  10. Found it: for some strange reason, FSS doesn't like to use Throttle Axis, even if I use a single lever. I had to create a new profile in MSFS2024, and map the same throttle lever to both Throttle Axis 1&2 (0-100%), and then it finally worked. Now I have to deal with the navdata: base version reports correct AIRAC, but I can't see any procedures. Experimental version, apparently I'm doomed until FSS allows Navigraph Navdata (the non-Ultimate) users to update ours.
  11. Got it last night, but I've been unable to update the navdata, it's stuck in 2603. I try to use their Updater, but, as soon as I approve connection to my Navigraph account, the Updater CTDs. When I reopen the Updater, I have to authenticate Navigraph again. Obviously, I can't see any runways or procedures in the MCDU. The only Embraer experience I had was the Wilco/Feelthere ones. How did you manage to update yours? In the base version I can't either see any runways or procedures (but I guess it uses MSFS navdata). Also, for the throttle, I have it binded in MSFS to Throttle Axis (inverted, because of some quirks with VKB gear). Somehow, it always gets stuck, despite calibrating it. How did you do it? I'm not able to set it into TO/GA. The throttle issue happens in both experimental and base versions.
  12. May be garbage, but the other option I have is the FS9/FSX Feelthere ones (either native or badly ported to P3D). For $28, I'll give it a shot.
  13. I've just checked. I don't know how to say this in English, but you can definitely see his anger (specially considering PMDG locked a thread he opened some days ago) 😂 Hopefully PMDG can keep caring a not-allowed-word about P3D and leave us and our workarounds alone.
  14. Although I dislike Discord, I see that, in this case, there's no option left. Go to his Discord>free-flight-sim-assets. And hope no one posts about this in the PMDG Discord. Knowing people, anything can happen 🤦🏻‍♂️
  15. I understand UT2 has its own injector. If you find a way to export its flightplans to either BGL or AIGFP formats, it might work, but you'll end up using FSHud for injection instead.

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.