On 02/21/2013 04:26 PM, James Turner wrote: > On 21 Feb 2013, at 15:54, Stuart Buchanan <stuar...@gmail.com> wrote: > >> On Thu, Feb 21, 2013 at 12:59 PM, James Turner wrote: >>> Suggestion - if z/Z are pressed with advanced weather enabled, make the >>> popup-message say 'disabled since visibility is being controlled by >>> advanced weather'. >>> >>> Another option would be to move the visibility control to a dialog, with a >>> slider / spin box, and explicitly disable it when advanced weather is >>> selection. Then we could lose the keybinding completely, which is something >>> I want to move towards for options that are infrequently used, but taking >>> up 'keyboard space'. >> I agree that it shouldn't be a keyboard assignment, and we should remove it. >> >> I'd need to check, but I thought this was already part of the weather >> configuration dialog. > We had a discussion about this keybinding (and some others, a larger issue of > mine) on IRC and discovered that all the people using it are developers / > scenery authors, to 'test stuff'. This makes me think it should be in a debug > option somewhere, or that we might need a 'scenery test mode' which for > example, disables weather of any kind completely. (Arguably fgviewer is the > right solution for this, though it would then be hard to test interaction of > scenery / models and different Effects options, I guess) > > I also think the FoV setting should move to a dialog, but I have the > impression normal people (not developers) *are* using that to look around 3D > cockpits and 'zoom' on details. Of course FoV and zoom are not quite the same > thing, but it does work in practice. > > James > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_feb > _______________________________________________ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel limit of EYE vision and limit of EQUIPMENT vision
the reason to be of the EQUIPMENT is to override the limit of the EYE vision. Are we doing the error to merging this two ? IMHO, and by logiX there must be out-here people NOT DEVEL, using z/Z && x/Z. I used to use it long time before diving in FG devel. I my case the reason was to "adjust" the weight of the GPU computing a better frame rate. 1. When the plane is on the tarmac, the weight is due to numerous building etc.... So the limit-of-visibility can help. ok. 2. When it go away from Airport climbing the number of "objects" is lower and frame rate raise up. 3. But at some fly level, the scope of view is so big that the number of visible "objects" increase and the frame rate decrease. (and I have a powerful card RADEON but unhappily with bad driver support) So what about user with less GPU power ??? The BIG weight of processing is the VISION So, is there not possible to separate the radar calculations ? I do not know, but just as hint, if we are avoiding to load a lot of TERRAIN to spare RAM, can't we have have radars reading infos from "NEW" files, much lighter, with info extracted from TERRAIN ? -- Lorenzo ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
