On Tuesday 22 March 2011 11:43:06 thorsten.i.r...@jyu.fi wrote: > Increasing aircraft texture size from 158 kb to 16 MB simply isn't viable > - if that roughly scales, it means that FGData would go from 4 GB to 400 > GB (!) - I barely have the harddisk to store that, having access to a > university T3 connection I also have the bandwidth to transfer it assuming > the server can keep up - but I doubt so many others have. If that means I > have to wait 3 seconds for a livery change instead of getting it > immediately, then fine with me, I'd stick with the 4GB. > > * Thorsten I haven't seen such a dramatic increase in filesize, if that's the case maybe the texture is in fact just one colour? The most dramatic increase I see is from 3.5MB to 21.3 MB (we're talking 4096x4096 textures here), and that's probably a texture I wouldn't convert.
For small files it might even decrease in size... (with mipmaps & all included). But, as I've said.. I'm not arguing for a complete conversion here, I'm just saying there are benefits in using these compressed textures... most important for me being the increased quality in bumpmapping... Btw: is there a way to monitor Video RAM usage in fgfs or osg ? ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
