On mer 19 mars 2008, Vivian Meazza wrote:
> Hi all,
>
> A few days ago the data in cvs was reorganised with several directories
> being moved from Models to AI/Aircraft. This not only broke the carriers
> (because the move wasn't completed correctly), and lumped ships and
> aircraft in the same directory, but also misunderstood the purpose of the
> AI/Aircraft directory. This is intended to hold "lightweight" models for
> use by the AI Traffic Manager and Multiplayer, usually, but not
> exclusively, in the form of xml wrappers which actually point elsewhere,
> either to the appropriate Aircraft or Models directory. It was not intended
> to be a heap for anything which didn't fit conveniently elsewhere. This
> change has neither been discussed nor agreed.
>
> Subject to there being no substantive objections here, I intend to revert
> this change over the coming weekend. This has been discussed with and
> agreed upon by fellow core developers, This is also the consensus view on
> *IRC*.
>
> Now, this probably isn't the best solution, and putting ships under
> Models/Geometry is, to say the least, a bit eccentric. So we can work on
> deriving a better answer, once we have got back the status quo ante.
>
> Vivian
>
Ships are objects like any others.
Since i am working (very slowly  :( ) on carriers and others military ships 
from the French Navy,  i can see the advantage to keep it in Models/Geometry. 
I am wondering about to use the same models (with livery variant) including 
it at some specific places (harbour)  or  randomly on the sea.
So they won't be, only, managed with AI/Scenario.

Cheers
-- 
Gérard
http://pagesperso-orange.fr/GRTux/


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to