From: Citronnier - A. B. <ale...@gm...> - 2010-04-02 21:39:41
|
Stuart Buchanan a écrit : > In an effort to help with this I've been looking at two fixes: 1) A > control to disable sub-model loading for AI aircraft. This > effectively stops the model loader from recursing into <model> tags, > and therefore stops it from loading any sub-models such as cockpits, > instruments, pilots etc. > Comments? When using dual control like in Anders c172p-dual-control and ZLT-NT blimp, or the f-14b-bs, the copilot is actually flying in an AI model which needs all the eavy stuff we would like to disappear in most other situations. There is also a big demand of visual details and eyes candy from a important part of FG users and we can't neglect that. Now, this leads effectively to a huge waste of h/w resources and anyway much of all this eye candy stuff is not visible at more than 50ft. LOD animations works well for saving fps and the work spent on it worth it. The problem remains at AI aircraft load time and I think a majority of user doesn't need to wait for the Tomcat to load each minute or so. In any case we should have the ability to choose what level of detail we want. In a dream world this would be user definable and on a per aircraft basis. This could be something like: use only light AI models by default or define somewhere a list of aircrafts you prefer to see a high level of detail. In the cases like dual-control, modelers could add at run time the needed models to this list. Alexis |