• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

An old project brought up to date: Canso PBY-5 of SAGQ

Success downloading the latest update. This model has the nicest water behavior. I really get the impression of plowing through the waves. The water spray effect is the best I have seen executed in either sim. Hope to see a few US Navy paints soon.
 
On FS2024 AP follows no flightplan with KAP140 correctly. But you can use HDG, ALT and VS without problems, if you ignore heading select bug display on HSI, which is running with turns.

Thomas
 
Thomas do you have any idea what autopilot is in the B-24 conversion/port that one works great, but I have no idea which one is modeled or being used, as I would like that one in the PBY if possible.
 
I am not using B-24 on my FS2024 rig. So I have no idea. But it seems FS2020 and FS2024 have different AP codings on their KAP140 systems.

Thomas
 
Hello guys,

First, thank you for the compliments on the effects, it’s a part that asked me a lot of tests to arrive at this result and again I didn’t arrive at what I wanted regarding the wake of the floats at the wing tip.

For the headlights on the wings, I made it clear that in this version I had not worked on the lights in the general sense that this will be done in the next version. Already at the level of the headlights, I used 2 empty to position the effects and I added an emissive texture on the headlight polygons which the Microsoft compiler does not appreciate and I get a warning with each compilation so I will see this problem soon.

For the concern about the AP, thank you Tiar for the info about the difference in coding FS20/FS24 on the AP 140 that I did not know.
Nevertheless, before drawing inferences from it, we should see how the AP are coded between the B-24 and the PBY.
The B-24 is a FSX/P3D port to MSFS. the XML code that describes the animations is in FS9/FSX format because it uses whereas the one from the PBY only uses ModelBahavior.
The PBY directly calls in his panel.CFG the component KAP140.html which is a component coded by Asobo and includes in the simulator. It is this component that could be coded differently between FS20 and FS24 if I understand.
As for the B-24, there is no call in its panel.CFG regarding this instrument so I think that the AP function used is the one that was included in FSX/P3D and that was called via CTRL+H / CTRL+MAJ+H (Heading) and MAJ+Z / CTRL+MAJ+Z (Altitude) if I remember correctly. It seems that this function has been keep by Asobo in the code of MSFS (in the Stearmans, this AP can be used also).
So it is quite possible to leave the KAP140 of the PBY off and call the same AP function via the two keyboard shortcuts ... at least I suppose, to test.
Still, since the 2 implementations are different, it is difficult to compare them.

Then there is the setting of the autopilot which is located in the {AUTOPILOT] section of the system.CFG.
The settings are undoubtedly different between the two aircraft. It is possible after saving the system.CFG of the PBY to override the [AUTOPILOT] section of this file with the parameters of the corresponding file of the B-24 and to test ... (I have quickly verified the parameters values between the two files and more than 10 parameters are differents).

Finally for the fact that Jan Kees has no effect in his simulator, I would say that the effects I used are those included in FS: they are standard and they are not effects that I created; moreover, there is a slight difference in rendering between FS20 and FS24 because some effects have been changed between the two simulators.
Therefore, and given the number of tests, if these effects do not appear, it is because there must be a declared addon in the Community that uses the same GUIDs and which causes this issue.
 
Hello guys,

First, thank you for the compliments on the effects, it’s a part that asked me a lot of tests to arrive at this result and again I didn’t arrive at what I wanted regarding the wake of the floats at the wing tip.

For the headlights on the wings, I made it clear that in this version I had not worked on the lights in the general sense that this will be done in the next version. Already at the level of the headlights, I used 2 empty to position the effects and I added an emissive texture on the headlight polygons which the Microsoft compiler does not appreciate and I get a warning with each compilation so I will see this problem soon.

For the concern about the AP, thank you Tiar for the info about the difference in coding FS20/FS24 on the AP 140 that I did not know.
Nevertheless, before drawing inferences from it, we should see how the AP are coded between the B-24 and the PBY.
The B-24 is a FSX/P3D port to MSFS. the XML code that describes the animations is in FS9/FSX format because it uses whereas the one from the PBY only uses ModelBahavior.
The PBY directly calls in his panel.CFG the component KAP140.html which is a component coded by Asobo and includes in the simulator. It is this component that could be coded differently between FS20 and FS24 if I understand.
As for the B-24, there is no call in its panel.CFG regarding this instrument so I think that the AP function used is the one that was included in FSX/P3D and that was called via CTRL+H / CTRL+MAJ+H (Heading) and MAJ+Z / CTRL+MAJ+Z (Altitude) if I remember correctly. It seems that this function has been keep by Asobo in the code of MSFS (in the Stearmans, this AP can be used also).
So it is quite possible to leave the KAP140 of the PBY off and call the same AP function via the two keyboard shortcuts ... at least I suppose, to test.
Still, since the 2 implementations are different, it is difficult to compare them.

Then there is the setting of the autopilot which is located in the {AUTOPILOT] section of the system.CFG.
The settings are undoubtedly different between the two aircraft. It is possible after saving the system.CFG of the PBY to override the [AUTOPILOT] section of this file with the parameters of the corresponding file of the B-24 and to test ... (I have quickly verified the parameters values between the two files and more than 10 parameters are differents).

Finally for the fact that Jan Kees has no effect in his simulator, I would say that the effects I used are those included in FS: they are standard and they are not effects that I created; moreover, there is a slight difference in rendering between FS20 and FS24 because some effects have been changed between the two simulators.
Therefore, and given the number of tests, if these effects do not appear, it is because there must be a declared addon in the Community that uses the same GUIDs and which causes this issue.
I'll say one thing, Lagaffe - you leave no stone unturned! You look at it all, in depth, and that is certainly appreciated by the community.
 
@Bushpounder
It’s a professional distortion: I worked for 38 years as a research and development engineer, mostly on Linux, and the best way to understand software is to read the provided code, which sometimes takes up a lot of time but in the long run is very profitable.

Regarding the known bug of the wheel that is not directional, I found perhas a solution.
The first version of this aircraft was for FS2004 and the code was written for this version. The animation was created on 200 keys:
- the first 100 keys do nothing
- and the rotation is done on the last 100 keyframes.

Under MSFS, this kind of animation is generally done on 100 keys in a basic way. Yesterday I tried to modify my animation (I have 6 different models so if I found how to do it for one model, I would save a lot of time) and in the end I managed to find the trick:
- the first 100 keys must be removed
- the last 100 keys were shiffted to start on key 0
- it is only then that one can modify the existing keys to achieve what one wants.

1761396854379.png
Nevertheless, even by doing this, my latest version that gives satisfaction under Blender does nothing when the plane is in the simulator.

To test, I also use the SIMVARS software from the SDK and in the latter, I view the variable A:GEAR STEER ANGLE.
With the DC-4 this variable changes value when the wheel turns (by modifying the rudder position) but with the PBY while turning the plane nothing happens at the wheel level and the variable remains at 0 so ... the current parameters of the plane in the system.cfg or flight_model.cfg files do not currently allow a directional wheel ... to be studied again
 
Very nice screenshots Jankee.

It is a beautiful airplane for sure and water ops work very well too. Lagaffe has given us a really nice airplane to fly in the simulator.

I don't think you are using FS2024, but in that sim I am getting water spray.

There is a paintkit in the documents section and do you have any plans to do any paints for this PBY?

I hope so!

Thanks. Ed
 
Very nice screenshots Jankee.

It is a beautiful airplane for sure and water ops work very well too. Lagaffe has given us a really nice airplane to fly in the simulator.

I don't think you are using FS2024, but in that sim I am getting water spray.

There is a paintkit in the documents section and do you have any plans to do any paints for this PBY?

I hope so!

Thanks. Ed
I definitely have plans...
 
Back
Top