Mathias > > There is no intention to migrate as a whole to .dds: it is offered as an > > appearance and performance upgrade for those who wish to use it. It is > up to > > aircraft developers to decide which format they will use. Indeed - they > > could provide models with either format so that the user could choose. > > > > That said - why use drivers that cannot handle .dds compression formats? > > Because there is no other driver. Like for the intel ones for example. > Because work on other interresting system stuff gets much more annoying > with > any closed source driver. I just do not want to limit myself to flightgear > - so > I really apprechiate that you could do even serious development to the > closed > source drivers. > Because most stuff that the average linux user cares work perfect with the > open > source driver stack. And that makes manny people just use these. Then when > one > of them tries flightgear he will see that it does not work as expected and > most > of them will then just never again try flightgear. Some of them will land > here > and probably get saied that he should use an other driver. But most people > just don't ask and probably tell others that they have a new laptop but > once > they tried flightgear, that boring game just does not work anymore ... >
I don't fully understand the point - we're not using .dds, and fancy shaders as the default option - what else isn't working with open source drivers? FlightGear should be working just as it always was. Those unable or unwilling to use closed source or fully compliant drivers just don't get to see some of the fancier eye-candy, but that should be all. > > I > > assume closed source drivers are OK? > The ati and nvidia closed source drivers can do this. > > So, I think the mipmap generation hangs with the nvidia drivers are a > serious > problem. But just limiting everything to the use of exactly this driver > where > this problem is worst cannot be a valid answer. I haven't see such a problem - now I will look for it. > > I would like to have a flightgear that is by default just running on every > average system. Having this run faster on a special configured system with > some > better configuration options and hand tuned hardware and drivers is very > fine. > But without tuning it must at least work in an acceptable way. It should - and I thought it did - I see no problems here with shaders off and using the default materials.dds - where is the problem? > > I have checked in a change to flightgear to make the use of the compressed > internal formats a starttime configuration option. > I am still interrested if we have that hangs also with texture compression > disabled and without providing precompressed dds textures? > Yes - good idea - I'm using that now - unfortunately my system was working just fine before so it might be a little hard to see if there is any effect! I'm not entirely clear what bug this fix is trying to solve. Vivian ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
