Ok Now I am confused… Within MSFS 2024
Just changed livery from GBYA to USN427CV and have received different results!!! In USN427 I am able to start the engines!!! I was even able to successfully land and take off in the water (something that I was not able to do
I have switched back to GBYA and not able to get the enginees started!! So it appears that there are some operational differences between the various liveries.
THanks
Hello,
You should know that to know the differences between two models, only the consultation of the file aicraft.cfg can inform you.
In the file aircraft.cfg we see that the two models mentioned are managed by the model.blisters and that only the texture changes, therefore there is no particular treatment in either of the delivered. Theses two models are managed each one by Extern_Blisters.xml and Intern_Blisters.xml only.
If there is a problem, it is located between the chair and the keyboard 
PS: it is not necessary to specify “the developers”: I always work alone since 2008.
CANCELLED :
Why ?
1/ for unknown reason since 3 days running MSF2024 with some mods is random : freeze during loading betwwen 89 et 100 % (with log file), infinie wheels during flight loading, task manager mandatory to close it. WITHOUT change anything.
2/ I’ve tried 6 times to lands on this watersurface… With PBY, Goose from BigRadial and MFS Goose : always crash after landing. Bad rendering water surface.
Next : return to MFS2020, less issue.
Tomorrow fligh in VR with PBY to try land (and takeoff :p) from old hydrobase Saint Ferréol (France). Will be available on my twitch. Not a big challenge near 1400meters to land
approch little more risky. WInd direction will be the biggest risk.
Just got a hold of a VR headset (meta quest 3)… In order to use them with MSFS I had to upgrade my pc to have a newer GPU and higher rate CPU. On a quick blush the graphics of this in VR are fantastic!
I have not yet had a flight in the PBY in VR mode yet (having some setup issues in getting things working… easy on some aircraft.. hard on others.) THere is an error message that pops up saying that this aircraft is not compatable with the controlers that come with the VR (Many are not but you can use the reqular xbox controlers or a yoke)
In general the VR mode on MSFS is great makes it easier to seamlessly manage the aircraft
Going to chime in here quick to confirm the behavior PatrickSifford is seeing in MSFS 2024. I can only start the plane when I select the USN427CV livery. I tried every single other livery and it simply won’t start in any other one. The USN427CV works fine.
In MSFS 2020, I’m able to start the engines in any livery, every time.
I did note that there were some differences in the default state of some of the cockpit controls between the USN427CV and the other liveries in MSFS 2024. In every livery but USN427CV, all of the cockpit switches, fuel selectors, etc. are all “off”, as you would expect, and the two mixtures are set to full rich. However, this was not true when I loaded up USN427CV.
When I load into USN427CV, the mixtures were set to “off”, and there were multiple nav lights and other switches that were flipped on. I flipped all these off, set the mixtures to full rich, then proceeded with the startup procedures and it immediately cranked right up.
I’m wondering if something in MSFS 2024 is causing the default state of some of the controls to be set differently than in MSFS 2020 but the true state of those controls is only shown in the USN427CV livery and “hidden” in the others? So you aren’t aware that the mixture is off or other controls aren’t set properly and therefore can’t properly start the engines in any but the USN427CV, where the true state is shown and you can correct it.
This aircraft was originally planned for FSX/P3D. In 2023, I configured and adapted it for MSFS.
Sorry this aircraft has never been tested for Virtual Reality because I do not have this equipment.
For the moment, adapting to MSFS 2024 is not my priority. If the SDK stabilizes, I will study the possibility of transforming it into 2024 native in the second quarter of 2025.
I have to release the AERONCA 7AC Champ by the end of June and then I will get back on the Canso project but for MSFS 2020.
Regarding the management of different aircraft, I remind you once again that all share the same CFG files and the initialization/configuration files of the PANEL.
There are only 2 different models for managing internal animations: with blister or without blister.
I have just reviewed the two XML files, there is simply a difference in processing in the blister model at the level of the interior animations file for the alternator.
For technical problems, please address them directly to me by email (my email is in the documentation which is in the Documentation directory of this add-on)
[EDIT]
I am on the SU3 Beta (1.5.9.0) and since this morning all aircraft made for MSFS 2020 cannot be loaded in the new Beta: CTD at each time after the SHIFT+C step …
=> It was a NVidia driver concern: the 576.80 release seem not functionnal with this Beta and my 3060 Ti. Return to the 576.52 and it’s perfect !
Hello,
The development of the Canso PBY-5 has resumed for a few days and I am in the process of listing the things to do as well as the issues encountered by some.
The goal is to be able to distribute a next version 1.0 by the end of the summer.
One thing is certain, given the SDK proposed by Asobo, this version will be developed for the 2020 SDK and if it can be used under FS24, so much the better otherwise …
For this, I will open another post solely dedicated to this new version.
FYI, the OP has created a new discussion topic just for the Consolidated CANSO PBY-5 here:
I have been flying with the VR in MSFS 2020 and a little in MSFS 2024. The graphic look and feel fantastic in VR mode. I do run into some issues unique to the VR mode but those are MSFS issues and not yours.
If there are things you would like for me to try in VR I would be glad to do so and let you know how they go.
As the moderator wrote, I have opened another post on which I will continue to present the progress of the project therefore I will no longer respond on it.
Moreover, I don’t have any VR-type devices so it’s impossible for me to test and validate anything. This addon is simply a freeware 
.
Closed at OPs request. As mentioned 3 posts above, users can continue the discussion about the PBY-5 here:
