As far as what you have written here:
1) As I understand this, it basically does exactly the same thing as going
through the individual model files and removing the cockpits/interiors/etc.,
correct? If that is the case, I find this to be an excellent replacement
for having to depend on each individual modeler to create an AI model file
for every plane they generate. This should significantly increase the
framerates within the MP environment. My questions are these:
a) Would this work on single-player?
b) If so, would we still have to maintain the AI model files or, with this
patch included, would the AI aircraft be able to be "read" from the standard
models folder thereby eliminating the needs for an AI "branch" on the FG
tree?
2) I don't 100% understand how LOD works, but if I get it basically
correctly, LOD reduces the resolution of a model based on the distance from
your viewpoint that it is? If this is the case, would it not stand to
reason that there should be several different stages of LOD? For example, a
model made with 2048x2048 textures would be at full resolution within 5nm.
>From 5.1nm-10nm, it would be rendered at 1024x1024. From 10.1nm-20nm, it
would be rendered at 512x512. Or am I way off-base here? Is this even
possible?
-Jason
On Thu, Apr 1, 2010 at 5:52 PM, Stuart Buchanan <stuar...@gmail.com> wrote:
> Hi All,
>
> A number of people on the forums have mentioned performance issues on
> lower-spec system on MP, particularly due to loading complex models
> for other aircraft causing stuttering.
>
> 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. Note that this is generally better than
> having a LOD node on the cockpit, because it doesn't even get as far
> as loading the file, nor does the cockpit take up any space in the
> scenegraph
> 2) A control to set the LOD for AI aircraft. Currently this is
> hardcoded to 50nm, which is probably too far for most purposes.
>
> I've got basic patches that allow these controls to be set by
> properties at runtime, but which I think requires a bit more work
> before submission.
>
> Comments?
>
> -Stuart
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
