Re: FGAddon: pa38 added to /branches/release-2024.1 but not to trunk?
Adrián Fernández <[email protected]> Mon, 13 Jul 2026 18:06:46 +0000
| Newsgroups | gmane.games.flightgear.devel |
|---|---|
| Message-ID | <GVXPR02MB120172E7E49EF2585374F0C9DAAFA2@GVXPR02MB12017.eurprd02.prod.outlook.com> |
--===============3096123126806568646== Content-Language: es-ES Content-Type: multipart/alternative; boundary="_000_GVXPR02MB120172E7E49EF2585374F0C9DAAFA2GVXPR02MB12017eu_" --_000_GVXPR02MB120172E7E49EF2585374F0C9DAAFA2GVXPR02MB12017eu_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Ludovic, the reason I haven't uploaded the aircraft to the trunk branch = is because, if I understand correctly, the compositor will change in versio= n 2024.2.x, and this aircraft, as it's currently developed, won't work or d= isplay correctly in the new compositor. I'm working on compatible HDR versions of all the aircraft I maintain, but = it's a huge undertaking in terms of research and programming to ensure each= one displays correctly and all animations, lights and controls work proper= ly. I've been researching and testing for months. The PA-11 is quite far al= ong since it's very simple plane. The rest of the aircraft will take longer= to become available. I'm trying my best, considering I'm neither a developer nor a designer. All= my work is based on research, try, seeing how "those who really know" have= done it, and trying to replicate and adapt that in my aircrafts. Kind regards Adri=E1n Fern=E1ndez G=F3mez ________________________________ De: Ludovic Brenta <[email protected]> Enviado: lunes, 13 de julio de 2026 14:44 Para: flightgear-devel <[email protected]> Asunto: [Flightgear-devel] FGAddon: pa38 added to /branches/release-2024.1 = but not to trunk? Hello, I just noticed a new and excellent addition to FGAddon, namely the Piper PA-38 Tomahawk by awall86. Thanks for this! However, this aircraft is available only in the 2024.1 branch and not on trunk. This might not look like a problem but, right now, people using next or any past release of FlightGear cannot see this aircraft in the launcher. Furthermore, when the a new version of FlightGear is released and a new branch is created in FGAddon, the Tomahawk will disappear from the launcher for people migrating from 2024.1. The recommended way to develop aircraft in FGAddon is to to this in trunk and optionally to merge (backport) to release branches, as described in [1]. I'm unsure what to do. I could do a one-off merge myself, or I could provide guidance (if and as required) for repeated merges but ultimately, awall86 should decide on the preferred workflow. There is no urgency to do anything, obviously, as the real problem will only become visible the next time a release branch is created. [1] https://wiki.flightgear.org/FGAddon#Development_scenarios -- Ludovic Brenta. _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel --_000_GVXPR02MB120172E7E49EF2585374F0C9DAAFA2GVXPR02MB12017eu_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-= 1"> <style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo= ttom:0;} </style> </head> <body dir=3D"ltr"> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> Hi Ludovic, the reason I haven't uploaded the aircraft to the trunk branch = is because, if I understand correctly, the compositor will change in versio= n 2024.2.x, and this aircraft, as it's currently developed, won't work or d= isplay correctly in the new compositor.</div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> <br> </div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> I'm working on compatible HDR versions of all the aircraft I maintain, but = it's a huge undertaking in terms of research and programming to ensure each= one displays correctly and all animations, lights and controls work proper= ly. I've been researching and testing for months. The PA-11 is quite far along since it's very simple plane. The= rest of the aircraft will take longer to become available.</div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> <br> </div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> I'm trying my best, considering I'm neither a developer nor a designer. All= my work is based on research, try, seeing how "those who really know&= quot; have done it, and trying to replicate and adapt that in my aircrafts.= </div> <div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, = Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> Kind regards</div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> <br> </div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo= nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> Adri=E1n Fern=E1ndez G=F3mez</div> <div id=3D"appendonsend"></div> <hr style=3D"display:inline-block;width:98%" tabindex=3D"-1"> <div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" st= yle=3D"font-size:11pt" color=3D"#000000"><b>De:</b> Ludovic Brenta <ludo= [email protected]><br> <b>Enviado:</b> lunes, 13 de julio de 2026 14:44<br> <b>Para:</b> flightgear-devel <[email protected]>= ;<br> <b>Asunto:</b> [Flightgear-devel] FGAddon: pa38 added to /branches/release-= 2024.1 but not to trunk?</font> <div> </div> </div> <div class=3D"BodyFragment"><font size=3D"2"><span style=3D"font-size:11pt;= "> <div class=3D"PlainText">Hello,<br> <br> I just noticed a new and excellent addition to FGAddon, namely the Piper<br= > PA-38 Tomahawk by awall86. Thanks for this! However, this aircr= aft is<br> available only in the 2024.1 branch and not on trunk. This might not<= br> look like a problem but, right now, people using next or any past<br> release of FlightGear cannot see this aircraft in the launcher.<br> Furthermore, when the a new version of FlightGear is released and a new<br> branch is created in FGAddon, the Tomahawk will disappear from the<br> launcher for people migrating from 2024.1.<br> <br> The recommended way to develop aircraft in FGAddon is to to this in<br> trunk and optionally to merge (backport) to release branches, as<br> described in [1].<br> <br> I'm unsure what to do. I could do a one-off merge myself, or I could<= br> provide guidance (if and as required) for repeated merges but<br> ultimately, awall86 should decide on the preferred workflow. There is= <br> no urgency to do anything, obviously, as the real problem will only<br> become visible the next time a release branch is created.<br> <br> [1] <a href=3D"https://wiki.flightgear.org/FGAddon#Development_scenarios">h= ttps://wiki.flightgear.org/FGAddon#Development_scenarios</a><br> <br> -- <br> Ludovic Brenta.<br> <br> <br> _______________________________________________<br> Flightgear-devel mailing list<br> [email protected]<br> <a href=3D"https://lists.sourceforge.net/lists/listinfo/flightgear-devel">h= ttps://lists.sourceforge.net/lists/listinfo/flightgear-devel</a><br> </div> </span></font></div> </body> </html> --_000_GVXPR02MB120172E7E49EF2585374F0C9DAAFA2GVXPR02MB12017eu_-- --===============3096123126806568646== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============3096123126806568646== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel --===============3096123126806568646==--