Re: Questions from a small fgdata-next cleanup check

Hi Erik, James,

Thanks, that clears up quite a bit.

For the DDS/PNG runway texture split, I will check whether the DDS material
path is still used anywhere meaningful. If it really is just leftover from
the pre-local-cache system, that sounds like a possible cleanup issue/MR.

For the source files, that distinction makes sense. Aircraft paintkits
being kept with aircraft is understandable. I will not treat those as
bloat. I may look more specifically at instrument source files and also
check whether these are only in the git tree or included in packaged
downloads.

For WS30, thanks for the explanation. I had assumed ws30_old was a fallback
path, but it sounds like the non-tessellated path is still the
practical/default one, and the tessellation path is the
experimental/incomplete one. In that case I agree that renaming ws30_old
probably does not help much right now.

Marking the tessellation rendering option as Experimental sounds like the
more useful small cleanup. I can look into where that label would belong.

Kind regards,

Philips Nguyen

_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel