After almost a month working on textures and paintkit, I have arrived at a result that seems convenient to me.
Everything is not perfect but overall the UVs of the fuselages and wings should no longer change. Now they are in PBR format: albd, comp and nrm.
The inner part of the fuselage where the wheels store during the flight has been revised in 3D but also in PBR textures as well as the landing gear which have been reworked for more details.
Note:
These NRM textures cause me some problems: the rivets seem a bit big and although correct under 2020, under 2024 they seem square! It’s a point that I will try to improve in the final version scheduled for the first quarter of 2026.
Sorry to answer too late but when I ask you if you have installed something, your answer was NO … honestly, I didn’t believe you.
This afternoon trying to install the Working Title product on MSFS 2020, I got the same screen
I conclude that when last October I asked you if you had installed something, apparently you hadn’t answered correctly, besides I presume you didn’t even know it.
When installing addons, you should at least inquire and find the necessary documentation unless you like surprises.
In any case as a developer, I support my creations … not those of others.
Nevertheless, at the moment for needs related to the management of the autopilot, with my testers we decided to recommend the installation of the GNS Working Tile which is free and available on the MarketPlace.
Its installation overloads the native GNS from Asobo and significantly improves the behavior of the AP. That said, this does not prevent you from finding out for yourself how to interact with this third-party Working Title product.
A good video “HowTo use the WT GNS” can be find here:
Yesterday I took all this information into account and modified the version being developed to give all this information in a PDF and advise to use the product WT GNS in addition to the PBY under MSFS 2020. This will be the v0.9.6g release currently in tests.
As for users wanting to use the PBY under MSFS 2024, in this next version there will be 4 files “aircraft.cfg.24” to rename , files that will directly use the v2 code of WT GNS, since it is provided free of charge in MSFS 2024.
This is yet another example of a user who downloads a freeware and complains without giving any information, it’s up to the creator to understand EVERYTHING thanks to the images …
Apparently your images seem to demonstrate that you use this addon under MSFS 2024.
The CANSO PBY was developed as a native FS 2020 aircraft. It was also usable under MSFS 2024.
Since SU4, Asobo has made changes to the rendering engine requiring creators to place the outer windshield in the outer 3D model and the inner windshield in the inner 3D model. Until now, this was not the case and I do not believe I have read anything in the SDK regarding this technical point.
If I placed the two windshields in the outer model, it is due to technical requirements related to export plugins, moving the inner windshield would be equivalent to losing the management of icing and scratches on the windshield as well as the tablet as it is currently programmed.
Today a version v0.9.6g will be released which solves the headbug issues and the management of AUTOPILOT for FS2020 and FS2024. Some textures implies in the windshield material has been improved to decrease that kind of display baut it’s always here.
Regarding these too strong reflections under FS2024, I will see in the coming months if a solution can be found.
For more information, read this post:
[EDIT]: French-VFR home site has been updated with the last version: V.0.9.6g
The display bug under FS2024 is slightly improved but not definitively resolved currently !
Having got up close to one of these at the air museum at Bull Creek in Perth, Western Australia, I have to say I really enjoy this project, thanks to the developer for your commitment
This is very enjoyable now though i do think there is to much Yaw going on in straight flight, also how do you get the anchor to work is there supposed to be a visual sign its deployed?
When the anchor is deployed, the parking brake is set to ON (this serves no purpose on water but it is a visual signal).
As for the final documentation, I am in the process of doing it in a lost time because I started another project concerning a DC-4 Skymaster which will be completely redone as a native 2020 model starting from the FSX/P3D model from Flight Replicas that gave me their agreement last November.
All the aircraft I am currently creating are made with the 2020 SDK which allows me to develop as quickly and well as possible. Nevertheless they are all compatible with 2024.
Despite numerous requests to Asobo, they did not want (for internal and code reasons, I suppose) to relaunch the QuickReload function which was quite useful under 2020, forcing developers under 2024 to compile via the Dev Mod GUI and therefore with the simulator loaded. I tested twice, and each time I lost my configuration files …
The only problem encountered on the PBY in 2024 concerns excessive reflections on the interior windshield. This point has been technically isolated and I am considering a solution that does not require me to review all the technical choices made for this model.
Well that’s up to you but there is most definitely a huge yaw issue in the flight model, look at the ball you can even see it wallowing left and right it quite often flies completely uncoordinated WITHOUT Autopilot. How do you deploy the anchor? clicking on it nothing happens and the plane still drifts around the water.
The development of this aircraft has resumed since July 2025 and has been regularly discussed on SOH on this post:
Many people have tested version 0.9.x and apart from the issues with the autopilot management, no one has commented on how the plane flew without using this autopilot.
Only one person had problems: Brian (post #375) who was notably using the auto-rudder and the legacy Flight model … This is a native FS20 aircraft so modern flight model is recommended.
Last point, in MSFS there are 3 levels of turbulence which are not gradual levels but values adapted to the aircraft’s dimensions: 1 for small planes, 2 for twin engines, 3 for four-engine and liners. The recommended value for the Canso is 2.
I have constantly harped that I wish they removed the option from the main options and put it as an option in Developer mode where it belongs… Legacy flight model has no reason to be used.
