Re: FGAddon: pa38 added to /branches/release-2024.1 but not to trunk?
James Turner <[email protected]> Wed, 15 Jul 2026 09:55:23 +0100
| Newsgroups | gmane.games.flightgear.devel |
|---|---|
| Message-ID | <[email protected]> |
--===============7362804622970411791== Content-Type: multipart/alternative; boundary="Apple-Mail=_892908FD-B4E7-4590-8E0C-CC4B853E3EC3" --Apple-Mail=_892908FD-B4E7-4590-8E0C-CC4B853E3EC3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On 14 Jul 2026, at 00:52, Ludovic Brenta <[email protected]> = wrote: >=20 > Well this raises several questions. >=20 > Fist, what changes will the new compositor require in all 500+ = aircraft > in FGAddon? I hope none, or only minor and scriptable ones. For this much larger topic, see the other thread from Josh about HDR / = PBR. But we do expect this to be a major change, breaking aircraft = compatibility. And we expect to produce tooling and scripts to ease the = transition, *but* also to have some unavoidable re-work manually for = each aircraft. (Especially, re-creating the textures) The expectation is = that =E2=80=98next=E2=80=99 might be released with only 5-10 compatible = aircraft, and then more will gradually be ported over the following = releases, and some unmaintained aircraft may never be ported. Kind regards, James --Apple-Mail=_892908FD-B4E7-4590-8E0C-CC4B853E3EC3 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html aria-label=3D"message body"><head><meta http-equiv=3D"content-type" = content=3D"text/html; charset=3Dutf-8"></head><body = style=3D"overflow-wrap: break-word; -webkit-nbsp-mode: space; = line-break: after-white-space;"><br = id=3D"lineBreakAtBeginningOfMessage"><div><br><blockquote = type=3D"cite"><div>On 14 Jul 2026, at 00:52, Ludovic Brenta = <[email protected]> wrote:</div><br = class=3D"Apple-interchange-newline"><div><meta charset=3D"UTF-8"><span = style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: = 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; = letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; = text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; = -webkit-text-stroke-width: 0px; text-decoration: none; float: none; = display: inline !important;">Well this raises several = questions.</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: = Helvetica; font-size: 12px; font-style: normal; font-variant-caps: = normal; font-weight: 400; letter-spacing: normal; orphans: 2; = text-align: start; text-indent: 0px; text-transform: none; white-space: = normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; = text-decoration-line: none; text-decoration-thickness: auto; = text-decoration-style: solid;"><br style=3D"caret-color: rgb(0, 0, 0); = font-family: Helvetica; font-size: 12px; font-style: normal; = font-variant-caps: normal; font-weight: 400; letter-spacing: normal; = orphans: 2; text-align: start; text-indent: 0px; text-transform: none; = white-space: normal; widows: 2; word-spacing: 0px; = -webkit-text-stroke-width: 0px; text-decoration-line: none; = text-decoration-thickness: auto; text-decoration-style: solid;"><span = style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: = 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; = letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; = text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; = -webkit-text-stroke-width: 0px; text-decoration: none; float: none; = display: inline !important;">Fist, what changes will the new compositor = require in all 500+ aircraft</span><br style=3D"caret-color: rgb(0, 0, = 0); font-family: Helvetica; font-size: 12px; font-style: normal; = font-variant-caps: normal; font-weight: 400; letter-spacing: normal; = orphans: 2; text-align: start; text-indent: 0px; text-transform: none; = white-space: normal; widows: 2; word-spacing: 0px; = -webkit-text-stroke-width: 0px; text-decoration-line: none; = text-decoration-thickness: auto; text-decoration-style: solid;"><span = style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: = 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; = letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; = text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; = -webkit-text-stroke-width: 0px; text-decoration: none; float: none; = display: inline !important;">in FGAddon? I hope none, or only = minor and scriptable ones.</span></div></blockquote></div><br><div>For = this much larger topic, see the other thread from Josh about HDR / PBR. = But we do expect this to be a major change, breaking aircraft = compatibility. And we expect to produce tooling and scripts to ease the = transition, *but* also to have some unavoidable re-work manually for = each aircraft. (Especially, re-creating the textures) The expectation is = that =E2=80=98next=E2=80=99 might be released with only 5-10 compatible = aircraft, and then more will gradually be ported over the following = releases, and some unmaintained aircraft may never be = ported.</div><div><br></div><div>Kind = regards,</div><div>James</div><div><br></div><div><br></div><div><br></div= ></body></html>= --Apple-Mail=_892908FD-B4E7-4590-8E0C-CC4B853E3EC3-- --===============7362804622970411791== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============7362804622970411791== 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 --===============7362804622970411791==--