Jump to content

Fiorentoni

Members
  • Posts

    4,807
  • Joined

  • Last visited

  • Donations

    0.00 USD 

Reputation

5,442 Excellent

Profile Information

  • Gender
    Male
  • Location
    EDDF, final approach of 25R

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Is that MSFS 2020 or 2024? And what texture resolution setting inside of MSFS? I have 12 GB VRAM, but I'm worried that I couldn't run the A380 even with medium textures.
  2. No need to make instalattion changes, you can even use both Mobiflight and SimAppPro at the same time running. I do that for the iFly 737-8 because the SimAppPro profile is missing the magnetic switch being turned off when I disconnect the AT. I added just that via a mobiflight profile and run both together
  3. Yes, mine 🙂 https://flightsim.to/file/92630/pmdg-777-200er-300er-f-winwing-pap3-profile And no, no python is needed for the MCP or FCUs, only for the MCDU/CDU hardware. It's really just start mobilflight and click on "run", done.
  4. Using only the PAP, but to answer: I think only Mobiflight works with 2024 at the moment, they haven't made the 772 compatible for 2024 with SimAppPro yet IIRC. I am using Mobiflight and it works just fine in 2024 (I also use it for the 772, actually, with my own profile).
  5. As in the post you quoted me, I use the windows key instead of ALT+TAB. It still freezes occasionally (but less than with ALT+TAB), and then I hit CTRL+ALT+DEL and open the task manager and then it unfreezes again. It's a bit annoying but at least it's predictable
  6. Yes, from their Discord: "The next major feature to come, VFR. We are starting to frame up behind the scenes how we plan to undertake VFR, it is highly likely we will deliver it in chunks with more depth being added over time. More on this when we have something more concrete to share."
  7. Disclaimer: See my signature, I'm not neutral in this. I do post here as a private person though and without any consent nor approval by anyone. That's because they cannot ever make their ATC "rock solid". An LLM is not able to do these kind of operations reliably, it's a language model. It can do all crazy stuff with languages (coding entire websites and apps, writing books, creating text for cabin crew addons), but it's unable to do proper mathematics and even more so in 3d space. It can not even do states (like current state: "aircraft is in cruise and not yet reached TOD") reliably, which is why it will sometimes simply forget you. They've reached their limit pretty early in development (mid last year) and consequently turned onto monetizing other things a LLM actually *can* do (cabin crew, grumpy tour guides, ground crew etc. basically anything that's more communication than mathematics), which is why you still see and experience the same ATC errors and failures from a year ago, at least judging by my subscription from mid last year and the current videos of SI in action. To improve upon their ATC they'd have to resort to classical coding and scripting (like BATC), which they apparently have no interest in so far.
  8. Ah yes, so we are two then. Was it also kind of micro freezing during the whole flight for you? I've never seen that before with any other add on. I did not use the EFB map by the way
  9. It was 8 miles out and it did capture the localizer actually (showing LOC green), it just did not fly it but instead flew a course 80 degrees to the right.
  10. Yes, I've seen two other reports of that. It was one of the ILS approaches to ENGM (by Aerosoft...), the actual sim-navdata of the localizer is okay, have flown there often enough with other aircraft. Also using Navigraph by the way. The CRJ v1 on MSFS 2020 never did that on a localizer, by the way. It had its own problems, but this was none of them.
  11. The couple of german guys over at cruiselevel.de seem to think MKStudios' version is better.
  12. 2024, no beta, full SU2. I've looked through reddit and other forums and other people have had WASM crashes and the localizer issue as well. I mean I know sometimes all the bugs come together on one flight, but for a mere 1 hour (!) flight that was just too much for me. I mean WASM crashes are bad enough, but at least ini and PMDG have them too, but you just cannot release an aircraft that intercepts the localizer and flies into the wrong direction. Bugs like these are unfortunately very common for Hans Hartmann and... I don't know I'm just too old for that ****. I'm glad it works for other people, but I gave it a chance and it turned out dead on arrival for me. I have so many other great aircraft to spend my time on.
  13. V2 is the worst release I've had in all those years. Did one flight and put it back to where it belongs (trash bin). 2 WASM crashes in one flight, constant microfreezes (which I've never had with any other aircraft before) and when it intercepted the localizer it just flew a 80 degree offset. Once again I feel ashamed for Aerosoft being a German company. We usually do much better than that.
  14. It's not like Asobo accidentally changed the LOD - they did it on purpose performance. A lot of stuff was done in MSFS2024 to improve performance, like more strict LODs, lower satellite photo resolution (also kind of bound to LODs) etc.
  15. BATC works as good as with 2020 in 2024.
×
×
  • Create New...