FlightGear Newsletter September 2014: Difference between revisions

Jump to navigation Jump to search
m
Cleared up grammar with DDS section
m (we need to update the newsletter template and add recurring stuff there ... (the DDS parapgraph should definitely show up in each upcoming newsletter))
m (Cleared up grammar with DDS section)
Line 3: Line 3:
{| width="100%" |
{| width="100%" |
| valign="top" width="33%" |
| valign="top" width="33%" |
{{Newsletter-cover-item|FlightGear 3.2 released (this time for real!)}}<br/><br/>
{{Newsletter-cover-item|FlightGear 3.2 released (this time for real!)}}<br/>
{{Newsletter-cover-item|DDS feedback}}<br/>
| valign="top" width="33%" |
| valign="top" width="33%" |
{{Newsletter-cover-header|(this is the second column)}}<br/>
{{Newsletter-cover-header|(this is the second column)}}<br/>
Line 11: Line 12:
</div>
</div>


We are looking for feedback about possibly adopting DDS textures in FlightGear:
== DDS feedack ==


* dds is a compressed format, hence the download size of the FG base package may be decreased
We are looking for feedback about possibly adopting DDS textures in FlightGear. There are several advantages in doing so:
* compressed dds can be directly used by many graphics cards, reducing also GPU memory consumption
 
* dds stores all texture resolution levels, i.e. no lower resolution levels have to be generated when the texture is used, hence it loads much faster into memory
* DDS is a compressed format, hence the download size of the FG base package may be decreased
* compressed DDS can be directly used by many graphics cards, reducing also GPU memory consumption
* DDS stores all texture resolution levels, i.e. no lower resolution levels have to be generated when the texture is used, hence it loads much faster into memory
* the resolution levels ('mipmaps') can be customized, allowing for some interesting effects at no performance cost
* the resolution levels ('mipmaps') can be customized, allowing for some interesting effects at no performance cost


Practically all commercial simulations use dds for these reasons.  
Practically all commercial simulations use DDS for these reasons.  


However, the dds compression algorithm is patented, which means that it is not readily available for OpenSource graphics drivers used by Linux distributions. Dependent on the specific hardware, this may or may not be a problem (modern graphics cards typically do not need the driver to process dds, for older graphics cards there are non-patented workarounds available which decompress the dds on the software level). The development team is concerned about making the Flightgear experience pleasant for all users, hence we would like to gather feedback how many users would be affected by a change in practice.
However, the DDS compression algorithm is patented, which means that it is not readily available for open source graphics drivers used by most Linux distributions. Dependent on the specific hardware, this may or may not be a problem (modern graphics cards typically do not need the driver to process DDS, for older graphics cards there are non-patented workarounds available which decompress the dds on the software level). The development team is concerned about making the Flightgear experience pleasant for all users, hence we would like to gather feedback how many users would be affected by a change in practice.


If there are no problems reported, FG will change defaults to textures in dds format with the 3.4 release, and then phase out the use of png textures.
If there are no problems reported, FG will change defaults to textures in DDS format with the 3.4 release, and then phase out the use of pngPNGtextures.
Continue reading at [[DDS Textures in FlightGear]]...
Continue reading at [[DDS Textures in FlightGear]]...


45

edits

Navigation menu