JYW

I must be dreaming 🫨 The old EFB was the antithesis of rational.

You're very early in a journey that will see you enjoy both Boeing and Airbus's flight management philosophies. Both are great and provide interesting contrast. If you go into learning the Airbus with a fixed Boeing "LNAV/VNAV" mindset, it'll be harder for you. You need to unlearn the Boeing philosophy and you'll soon find the Airbus approach refreshing, intuitive and quite straightforward. There are still LNAV and VNAV provisions/analogues in the Airbus; think of it that they're simply already armed. I suggest you watch a lot of YouTube videos and tutorials on the Fenix. You won't get along well in the learning process if you just try to find your way and adopt the Boeing approach as your yardstick.

There is no EFB .............. There are a few option for the M600 in the default 2024 EFB. That's it. There is no FSR EFB with all the realism options. This is a really basic addon in terms of ancillary features.

I pressed the HALO button last night. I was 30 miles from Mammath-Yosemite and the plane correctly headed back there. It descended and went onto final approach (all looking good) then it started doing a never-ending hold 10 miles from the airport. I believe it was doing this because speed was too high (200kts at 2000 AGL!). I've noticed that the AT cannot fully 'take over' the throttles and that the user's throttle position seems to interfere with it. With AT on, if you move your throttle axis, it moves the throttle in the cockpit and upsets the AT, but doesn't disconnect it. In short the AT is borked at present, as per my observations. The failed HALO autoland may also have been due to a HOLD as part of the target airport's procedure. But the real HALO system would disregard any holds. Compared to the FFX 2024 default Visionjet autoland capability, the M600 was pretty disappointing.

Agreed. I think anyone who has the M500 will be shocked at how much lower the quality is of the M600. The jagged stripes on the default liveries are appallingly low resolution. Cockpit textures are fuzzy and LODs are too aggressive. There is no FSR EFB, just some options accessed via the 2024 EFB. There is no passenger simulation and in general it is striking how more of a basic, default-style addon this is. One thing - the sounds are absolutely stellar.

I'm afraid that is how it's being adopted. I was on the FSR Discord last night and a few commented on how there is no new 'M600' section of the Discord server, and someone (I don't know if part of FSR or not) said that any and all bugs and changes will need to be fed to MS via Zendesk, and they will need to (exact quote) "give Raul more $$ for any changes to the existing release". So it's definitely positioned as a separate, 1st party release from MS. It's also notable that Raul hasn't joined any discussion on the M600 on there at this point. That's not a judgement, just an observation, before anyone gets upset! When the FSR 300E released Raul was all over it. I think it will be problematic as there are some small issues and potential bugs or changes. I don't think we're going to see these addressed quickly by FSR and rolled into early updates. The M600 is firmly part of the "MS machine".

Welcome Pedro! It's a fantastic first aircraft release. Feels very immersive. To bring the G1000 version towards realism, I'd say the focus could be on :- Removing the AP buttons from the G1000 PFD and MFD Integrating the stock Asobo KAP140 into the cockpit (it normally sits under the PFD and MFD, in the middle, in early G1000 aircraft). There are other things that could be explored, like disabling the Flight Director (may work by setting the Flight Director = 0 flag in the [autopilot] section of the systems.cfg (I'll have a check at my end!). But just the above two changes would go a long way and make it realistic 😎 As a reference, the Carenado C182T G1000 addon from early MSFS2020 uses this correct approach; G1000 (with no FD) and KAP140. Of course, being Carenado, there are many bugs but the general panel layout is correct. One last thing, not related to the G1000 version. In a AA5 with the Century 1 and a GNS430 (as with your addon), the Century should be able to track the GPS course - which should show on the HSI - if the GNS is set to 'GPS' mode. This currently doesn't work on the addon. When the GNS430 is set to 'GPS', the course deviation is not shown on the HSI and so the 'VOR tracker' mode of the Century 1 currently can't lock to an established GPS course on the HSI. You've done a good job in simulating the Century 1 but, as it's such a limited device, I wonder if it would be good to have a further option in the POH popup, to have the KAP140 in the cockpit (in all of the variants; Traveler, Cheetah & Tiger). Many AA5s have been upgraded beyond the Century 1, usually to a KAP140, STEC 30 or Century 2000. Look forward to seeing how the pack develops!

Resolved after 6 restarts of MSFS2024. Almost certainly an MS issue rather than FSR. I haven't flown it yet, but the M600 seems mighty nice! 😎

[NOW RESOLVED] I bought the FSReborn M600 an hour ago, and despite 4 restarts of MSFS2024, I get this in my Library :- Any clues anyone? I'm guessing that MS, in their infinite wisdom, releasing a City Update and a highly anticipated aircraft addon at exactly the same time, are closing the servers, preventing people installing products they've just bought. I saw that some people are getting the same message as above, when trying to install the new City Update. But that is free... this is not.

It might just be you. I had a flawless flight in it. Performed excellently, hand flew nice (which V1 also always did) and the new EFB is stellar compared to the old one. We'll see what others chime in and say,

Are you sure that's not the M500 (by the same dev) ?

Yes it is, I've been flying in it for the last 40 mins. It's really nice! Are you on 2024?

What is going on today?! The best day in FS history 😄 Grumman AA5, Black Square Commander 114 around the corner, iFly SP1, City Update 15.............. now this!

The new update to the P-Mentor has been released to the Marketplace today. I sent a list of requests to Aerosachs, based on my real world experience with the type. I am very happy to see that they have implemented them all! The extremely loud fuel pump has gone, the green arc on the G3X PFD has been corrected and they have split the available aircraft liveries into some that are LSA registered (which show the Engine RPM, which is what I've always seen in Tecnam LSAs) and some that are GA registered, which have the RPMs set to the prop (which is how I've learned they are set up when registered as full GA and not LSA). I couldn't be happier and this is now an extremely fun, realistic little LSA, which flies very nicely and convincingly when compared to the real aircraft. I would most certainly recommend this nice little aircraft to anyone who likes modern LSAs, equipped with high-end avionics 😎 Circuit breakers are all modelled, the G3X implementation is excellent and there's both PMS and TDS GTN650 support, to provide IFR navigation capability to the G3Xs. Really great work @erasam !

FIXED! I had plenty of storage on my C drive, but the issue seems to have been with the TEMP location that is set in the FSW installer app. When I changed that location, the install worked 😎 The same temp location had worked fine for the last 10 or so updates, but after installing the latest version of the installer, it didn't like it. But all sorted now. Thanks for the help guys!