With my computer still out (the repair company asked me to send it back after I wrote a summary of my thermal management problems, so it seems to me they did something bad with the BIOS) and no real idea when it comes back, I am starting to see a problem.
Local Weather as currently committed is in an inconsistent state. The GUI fits the old mode-based system before I started switching to the new cloud system, but the package is using the new rendering system for all clouds it should except Cb. So, as Durk has noticed a while ago, some options lead to errors when ticked on startup. In addition, there is probably (I haven't gotten around to see it) an altitude problem - cloud layers are appearing with an offset to the altitude they should be. Cb clouds currently utilize a mixture of old and new clouds, which is bad if they drift in wind, because then they are pulled apart as half the cloudlets move, the other half doesn't. All this needs to be fixed for a release, and I originally planned to have it fixed four weeks ago or so - before my hardware crash. Unfortunately, even if I get my computer back tomorrow, by now I have such a large backlog of work-related stuff plus the task of getting the cmake environment to run that I'm not sure I can resume Flightgear development before Xmas holidays. On my spare computer, it's basically hopeless - I have currently 2.1 GB harddisk space left - that's not even enough to hold an FGData pull. So, I'd need some advice on how to handle it. If we want to strictly stick with the release plan, then I'd need a volunteer helper to make the necessary changes to the code before the deadline, rewrite the GUI and commit the thing. None of this is big, basically it's routine changes of numbers or duplicating and slightly modifying existing cloud definitions, inserting if clauses and flags and do xml work for the GUI - but it's difficult to get right when working completely blind without any chance to test for bugs. The other option is that I make the relevant changes in January despite feature freeze. Or the third option is that the old version of Local Weather gets shipped with 2.6 - the flag to do so is still in the code. Please let me know what you think! Cheers, * Thorsten ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
