Re: [Flightgear-devel] Improved Basic Weather integration with Atmospheric Light Scattering
Stuart On Fri, Apr 19, 2013 at 9:18 AM, Vivian Meazza wrote: I still use basic weather with mp so that I get the same clouds in both clients - is this still the case? The clouds are unchanged by this, though I don't think that you will get the same clouds in MP on both clients unless they are started at the same time. The only changes I made with this were to ensure that Basic Weather generates the appropriate properties for the atmospheric shaders. Your most recent change seems to have broken the manual input gui here - sometimes it works, and sometimes the values revert to the default. Hmmm, odd - I made the changes specifically to fix the manual input UI that I thought your Weather UI changes had broken! :) I still have the old version: seems to work fine. But I only moved the way it was accessed - not the gui itself. It might be that we have actually exposed some old bugs of course. I suspect that you and I are using the UI in a different way and there's something broken in the (complex) UI logic. I'll take a look over the weekend - sorry for the inconvenience. If you're able to nail down the specific actions that cause it to fail, vs. the actions that make it work that would be useful. First problem seems to be related to the mouse - here it gets stuck in the coverage field if you enter it (you don't actually need to). You can get out of it by hitting tab and then right mouse click. Second problem is that if you then close the manual entry window and then hit either OK or Apply the weather reverts to the METAR data and the manual entry fields are all set to the default value. Hitting close works OK and the manual data is applied. Third problem is that sometimes when I enter values on a cloud coverage line then move to another line to fill in data there, the first entry line reverts to the default values. I can't reproduce this reliably, nor can I identify any cause. I haven't seen any of these problems before, but I wouldn't claim that they weren't pre-existing: it is entirely possible that I never tested the right combination of entry conditions. They're pretty obvious though when you do encounter them. We seem to have lost the ability to use /NIL as a METAR input - very useful during fdm development to remove weather effects. I'm not sure when this broke, I think it might have been something James did. That shouldn't have been changed by anything I've done recently. No - I think the problem lies elsewhere as I said. Vivian -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Improved Basic Weather integration with Atmospheric Light Scattering
Stuart, Having talked about it for months (years?) I've finally written some property rules that improve the integration of Basic Weather with the Atmospheric shader. In particular the skydome properties are now calculated using formulae very similar to those of Advanced Weather so there's no need to set rayleigh/mie/density properties directly, and appropriate levels of ground haze are estimated based on the lowest cloud layer. Some of the integration is quite basic, and there's plenty of room for improvement in the Basic Weather METAR parsing to set up appropriate visibility settings in particular. Feedback welcome as always, though I suspect almost everyone these days is using Advanced Weather... This also removes another roadblock from possibly making the atmospheric shader on by (non-Rembrandt) default. Ooohhh, controversial :) I still use basic weather with mp so that I get the same clouds in both clients - is this still the case? Your most recent change seems to have broken the manual input gui here - sometimes it works, and sometimes the values revert to the default. We seem to have lost the ability to use /NIL as a METAR input - very useful during fdm development to remove weather effects. I'm not sure when this broke, I think it might have been something James did. Vivian -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Improved Basic Weather integration with Atmospheric Light Scattering
On Fri, Apr 19, 2013 at 9:18 AM, Vivian Meazza wrote: I still use basic weather with mp so that I get the same clouds in both clients - is this still the case? The clouds are unchanged by this, though I don't think that you will get the same clouds in MP on both clients unless they are started at the same time. The only changes I made with this were to ensure that Basic Weather generates the appropriate properties for the atmospheric shaders. Your most recent change seems to have broken the manual input gui here - sometimes it works, and sometimes the values revert to the default. Hmmm, odd - I made the changes specifically to fix the manual input UI that I thought your Weather UI changes had broken! :) I suspect that you and I are using the UI in a different way and there's something broken in the (complex) UI logic. I'll take a look over the weekend - sorry for the inconvenience. If you're able to nail down the specific actions that cause it to fail, vs. the actions that make it work that would be useful. We seem to have lost the ability to use /NIL as a METAR input - very useful during fdm development to remove weather effects. I'm not sure when this broke, I think it might have been something James did. That shouldn't have been changed by anything I've done recently. -Stuart -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Improved Basic Weather integration with Atmospheric Light Scattering
No ,Advanced weather forced 3d clouds on me even when i disable 3d clouds so i don't use it. Of course i could be doing something wrong , but Im not quite convinced yet to get a new computer. Looks like I'll have to pretty soon ;) Interesting, I thought the 3d cloud checkbox was a shader-disabling button and the 3d clouds would disappear for lack of a rendering technique. Anyway, yes, Advanced Weather doesn't support 2d clouds, so if you want them, you can't use it, and you're not doing anything wrong. * Thorsten -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Improved Basic Weather integration with Atmospheric Light Scattering
Hi All, Having talked about it for months (years?) I've finally written some property rules that improve the integration of Basic Weather with the Atmospheric shader. In particular the skydome properties are now calculated using formulae very similar to those of Advanced Weather so there's no need to set rayleigh/mie/density properties directly, and appropriate levels of ground haze are estimated based on the lowest cloud layer. Some of the integration is quite basic, and there's plenty of room for improvement in the Basic Weather METAR parsing to set up appropriate visibility settings in particular. Feedback welcome as always, though I suspect almost everyone these days is using Advanced Weather... This also removes another roadblock from possibly making the atmospheric shader on by (non-Rembrandt) default. Ooohhh, controversial :) -Stuart -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Improved Basic Weather integration with Atmospheric Light Scattering
Feedback welcome as always, though I suspect almost everyone these days is using Advanced Weather... No ,Advanced weather forced 3d clouds on me even when i disable 3d clouds so i don't use it. Of course i could be doing something wrong , but Im not quite convinced yet to get a new computer. Looks like I'll have to pretty soon ;) Syd On Tue, Apr 16, 2013 at 3:13 PM, Stuart Buchanan stuar...@gmail.com wrote: Hi All, Having talked about it for months (years?) I've finally written some property rules that improve the integration of Basic Weather with the Atmospheric shader. In particular the skydome properties are now calculated using formulae very similar to those of Advanced Weather so there's no need to set rayleigh/mie/density properties directly, and appropriate levels of ground haze are estimated based on the lowest cloud layer. Some of the integration is quite basic, and there's plenty of room for improvement in the Basic Weather METAR parsing to set up appropriate visibility settings in particular. Feedback welcome as always, though I suspect almost everyone these days is using Advanced Weather... This also removes another roadblock from possibly making the atmospheric shader on by (non-Rembrandt) default. Ooohhh, controversial :) -Stuart -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
