roesti

SU2 supports FSR3 Framegen natively, so the mod shouldn‘t be neccessary in the near future. You can select it in the graphic settings.

You can switch the comms over to your virtual co-pilot (top right button in the app), then he/she will handle the radios and replies to requests.

I feel you, it's a "little bit" frustrating. Bought ChasePlane when it was still OldProp, then it migrated to OrbX, rebought ChasePlane Pro. But now it seems only people who bought stuff in the //42 store for a certain amount of money can have it. Why? This store did not exist back in the day.. Is there any ETA for "normal" people and loyal customers from the past?

If for whatever reason Asobo doesn‘t add this data: Will it be possible to just create „custom tower views“ manually / some static external cameras that follow the aircraft? The same goes for runway views. IIRC, the previous versions of ChasePlane allowed to create all these type of views. I‘m looking forward to the release of this tool, especially if it brings the essential features like internal views, external views and static views all switchable with easy assignable keybinds. I really miss ChasePlane, the current camera system of MSFS is really lacking imho (I know others are fine with it), and getting this Tool back would be such a relief and enjoyment factor.

The reason is, that it’s most likely not possible to achieve. DLSS is an upscaling technique applied to the whole 3D screen space where AI is used to reconstruct a higher resolution frame from a lower resolution frame. The displays are part of these 3D scenes, they‘re basically just fast updating textures on a 3D object (and often the screen textures are behind other objects like modeled glass frames, which makes it even more difficult). I don‘t see any possibility to exclude certain textures from being affected by DLSS while it‘s altering the frame, just from how this technique works. I‘d be very surprised if Asobo really comes up with a solution one day, that would impress me. But I doubt it. NVIDIA are the only ones who could find a solution, but then DLSS needs to work differently. You can only exclude things like overlaying UI elements, that are „above“ the actual 3D scene and are not part of it.

Version 1.0.7 should be now available to the public (discord announcement). Changelog:

Very soon, most likely today, at least that is the plan. Collin (main developer) is asking around for issues and the feedback was positive. Signs are on "go", it would surprise me if it's not going live in a few hours at max.

What you call "snob release" 1,5 years ago was the release of the alpha version to early adopters. It was a very early "usable" barebones state of the plane with the basics done to play around with it in the sim for the first time, it was not beta. There were many obvious and known bugs and the plane wanted to kill you every 5 minutes with a nose dive. I wouldn't call it release, rather CE customers were given access to the development process at this point - there were not even sounds or spinning engines. This version is nowhere comparable to the first public release of the plane, because the differences are night and day. Internal QA and voluntary testers were and are doing their jobs good enough I'd say, everything is and was reported several times and in the end, it's in the developers hand to fix it. There's also a github page visible to the public with all former and still existing issues, so at least it was transparent all the time. Bugs like the one you mentioned seem obvious and "easy to fix", when in reality there are often dependencies or other stuff making it difficult to find a quick solution. The argument to delay the release to fix things like that first before give the plane to the public was already discussed more than once. But it is what it is, the past can't be changed. But I think one should rather be glad that important fixes are coming now, better late than never.

While I get the frustration not having the update right now, I think there is some kind of misunderstanding. These updates are not official yet and are in testing / QA. The order how people receive updates has always been the same from the start: Internal QA -> CE Users -> Public. It is not like that CE Users get final updates which are "held back" for Non-CE users, it is more like CE users are part of the test process on a volantary basis. Which makes sense, since CE customers were part of this process when the plane was still in alpha (and barely flyable). Even then, internal QA had updates before CE users, eventhough these updates were far away from being polished. So during alpha it was the same situation with updates already in the pipeline, but CE users had to wait until it passed internal QA. I think it's done this way to prevent disappointment about newly broken things. And indeed, the new update(s) broke a few things, even if minor. That is the reason they give it a few days. If these updates would have been released earlier, there would also be people who (rightfully) complain again why something goes out untested / not tested properly enough and I'd agree with them then. Like the release version. To be fair, the upcoming update should have been the original release version. TFDi could made their lives easier by just holding back the plane a few weeks and everybody would have been happy. Of course I can give only thoughts and no reason why it's done like that, but I guess for TFDi it makes sense, because the CE userbase is larger than their internal QA (large enough to have a good sample size of different setups), they helped testing the plane for quite some time which worked out so the developers have some reliable bunch of people who are enthusiastic about this plane and bought it way back when it was not even clear when and if this plane eventually arrives. What they also did is offer CE users an option to "opt-out" of the test branch and switch to stable, to prevent people getting annoyed by unfinished updates breaking things. One could argue here they could also introduce some kind of "opt-in" for other people eager to help testing new updates and maybe I can make a suggestion to the devs and perhaps they consider it (no promises). I can only encourage to remain patient, I'm very sure the update will come for everybody in the coming days / this week and it will be worth the wait. Edit: There is now an ongoing discussion about this topic on discord amongst CE users, with pro and contra arguments allowing all customers accessing test builds. No staff response yet, my personal opionion is: Give everybody access, but only the devs can make a decision here, so let's see - but don't have high hopes.

TFDi released a new update (I think currently only to Collector's Edition owners, I guess public release will follow very soon) which really improved pitch stability / trimming behaviour. There are still things that can be improved / fixed, but after a test flight, it felt way better than before, controlling the plane was way more "believable" and hand-flying was fun. Didn't felt like I was just an "observer" anymore like before, hoping the aircraft will somehow land on the runway while fighting the controls. Approach seemed very stable and managable. I think it's on a good way forward now.

They were. Some bugs are in there since the beginning, people who had access to the plane all the time (the 1000 "Collector's Edition" customers) were asking to delay the release, especially after one staff member dropped the info that the PW engines won't be ready for release (which was only communicated a few days prior to release. Early buyers / testers can still use this engine variant, but it's not complete regarding EPR simulation etc.) The conversation was quickly shut down, and TFDi said something like "It's their problem to deal with the reactions of the community". Which is true of course, but the warnings from the testers was not "hateful" or something like that, people wanted only the best for the developer and wished for a decent simulation of their favorite aircraft to be released in a stable state - and feared some kind of negative backlash from the community. LSAS / pitch-problems is something that has been around for quite a while. To be fair, the difference between the first release of the aircraft to the customers (which was more like a pre-alpha, heavy in-development state) and todays version is huge, they have come quite far. They put many hours of work into it, but in my opinion they should have shown a little bit more patience and release the plane a few months later, maybe do some kind of christmas release. The argument of TFDi was, that there will be never a perfect state of the aircraft, as there are always bugs and they have to commit to this release. One can only speculate whey they chose this date, I won't. In my opinion, for the price they're asking, a little bit more polishing would have been great. Also I think it was a little bit "unfair" towards the testers, because customers could get the impression QA wasn't doing a good job with some kind of obvious issues still in the release version. But everything was reported for quite a while and they still released it. Anyway, I hope they will continue improving the plane quickly, it has the potential to become a very good addon. But imho, in it's current state it's too expensive.

Hello Ray, I sent you a PM with the file I created a while ago for P3D v5. I don't know if it still works because I haven't flown P3D for a very long time. Let me know if it helps.

There's also the option to create an exclusion file with ADE. I remember doing it for this specific airport, but I realized you have to be careful, becasue if you just draw one big rectangle aroundthe airport, many of the houses nearby will vanish as well. The process is not that hard, maybe 10 minutes of work: - Load up the AFCAD file in ADE - Draw smaller exclusion rectangles instead a big one along the runways, then compile with the option "separate BGL" files. You can then just take the "obj.bgl" as exclusion file, copy it to the scenery folder and ignore your compiled AFCAD I don't know if sharing an exclusion file is allowed here on this forum, but feel free to send me a PM if you want, then I can give you the file I created myself and test if it works for you. (It's just a 4KB big .bgl you have to move to your LICJ scenery folder)