Stuart:

> 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.

Csaba:
> I want to see AI/MP aircraft in full detail when I am near
> one - or even inside.

Well, the only 2 ideas I have regarding this would be selectable options
within the FGRun GUI and/or the command-line:

1) An option to enable/disable the LOD capabilities of the program
2) An option to select either "AI Models (simple)" or "AI Models
(advanced)".
    a) AI Models (simple) would be AI Models which always appear without
their interiors/cockpit installed.  This would be effective for those people
who do not "hitch rides" or who want best performance at all times.
    b) AI Models (advanced) would AI Models which appear fully detailed at
the closest LOD limits.  This would be the best choice for those who like to
see their AI aircraft in full detail and jump onboard occasionally, like
Csaba.

Durk:

> So, if done correctly, we could happily use the regular
> aircraft models, also for AI /Multiplayer purposes, because most of the
time,
> only the lower LOD versions would be active. This would probably give
better
> performance than we currently have. In addition to that, we could also
make
> more effective use of the incredible collection of liveries made by Brett
> Harrison, which quite a few magnitudes better then the rather bleak ones I
> made for the AI aircraft.

As I have only recently noticed, there are only certain aircraft in my AI
Models folder - and not even close to the same number as I have downloaded
and installed.  This leads me to believe that only certain aircraft make use
of the AI Models directory and either a) those are the only AI Models that
you can have unless you create your own files or b) the other Models are
rendered as AI Aircraft from the original model files anyway.

If it is Option A, then I believe a solution to re-route our current AI
Models directory structure to our original models directory structure should
be implemented along with Stuart's control option to make it so that
separate AI Models would not have to be generated and stored separately.
This would reduce the overall size of FG (although probably not by much),
but it should also have the side benefit of simplifying some of the code
(since there wouldn't be 2 directory structures to do the similar actions),
correct?

If it is Option B, then we already have the file structure in place to use
Stuart's proposed modification to "auto-create" AI Models which would make
the AI Model tree unnecessary, correct?  Which would also mean that ALL of
our models would also be capable of being AI Models instead of only a
limited few.


Thanks,
Jason
------------------------------------------------------------------------------
Download Intel&#174; 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

Reply via email to