Re: HDR / PBR / compositor info
Josh Davidson <[email protected]> Fri, 10 Jul 2026 06:40:12 +0000
| Newsgroups | gmane.games.flightgear.devel |
|---|---|
| Message-ID | <SA0PR07MB774017317BB81CDDD8CFD16FCCFD2@SA0PR07MB7740.namprd07.prod.outlook.com> |
Well, wiki also says: Transform -> +Y up Make sure to keep this OFF. Blender uses a +Z up convention like FlightGear, so we do not adhere to the glTF standard (+Y up). So does that mean glTF's will be +Z up? -- Josh Davidson ________________________________ From: Josh Davidson <[email protected]> Sent: Friday, July 10, 2026 01:32 To: FlightGear developers discussions <[email protected]> Subject: Re: [Flightgear-devel] HDR / PBR / compositor info About next... https://wiki.flightgear.org/Howto:Convert_from_AC3D_to_glTF This doesn't make sense. In the AC3D system, Y is up/down, in FG Z is up/down, in glTF, Y is up/down. Someone made a conscious choice to make Z up/down in FlightGear a VERY long time ago. Can't that choice be duplicated so we don't end up with having to rework 1000s of lines of code to move to glTF? Also wouldn't reworking it mean coordinate schemes are now different for the model vs the FDE/etc? If so, that would be horrible... but as would having to swap axis' on the FDE's as that would ruin everything. So emotional annoyance aside, wouldn't it be possible to simply swap -Y and Z again on glTF just like is already done on AC3D? Reminder, in AC3D, Y is up/down... no idea why when blender got involved that changed to Z, or why FG moved it to Z as well. Basically, it would be so cool if we could reduce the amount of "unnecessary breaking" occurring in the glTF migration. I would also like to ask why the emission animation was removed? What about existing AC3D models? What if I need to make something light up conditionally? What do I do then? In all honesty, I'm really not thrilled about how much reworking I'll have to do when next releases if things continue this way... -- Josh Davidson ________________________________ From: Wayne Bragg <[email protected]> Sent: Sunday, June 7, 2026 23:18 To: [email protected] <[email protected]> Subject: Re: [Flightgear-devel] HDR / PBR / compositor info On 6/7/2026 9:44 PM, [email protected] wrote: > --disable-ai-traffic Thanks, that is what I was looking for. Any idea about the Livery issue? Wayne _______________________________________________ Flightgear-devel mailing list [email protected] https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fflightgear-devel&data=05%7C02%7C%7Cbbd40ada79cc460904d208dec5151e87%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C639164891710612798%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=hekN4nOxooY%2FMk3Tq1AZUxQz39SI1R1f%2BOgyoy8l938%3D&reserved=0<https://lists.sourceforge.net/lists/listinfo/flightgear-devel> _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel