• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

SDSX design document for 3D models added to the wiki

lmoelleb

lmoelleb

Messages
268
Country
netherlands
I have added an initial design page on the Wiki here:

http://www.fsdeveloper.com/wiki/index.php?title=SDSX_Design

so far it only contains the document for 3D models (it is the same as I discussed with you Arno, except I moved the LevelOfDetail around so it is simply a conditional display option like everything else).

Noticed I have not wasted my life adding methods, fields, etc to the class diagram, and I do not see the need for such detail - it would just duplicate something that can as well be expressed in actual source code.

I am aware the information I provide with the class diagram is not enough, but I do not know exactly which parts people would find unclear. So please have a look, and post any questions here - then I'll update the wiki with details as required and we should get the details we need, instead of a 100 page document with trivialities everyone would know anyway.

If you have any suggestions to a different (and potentially better) domain model please post it here on the forum.
 
Hmm, I am starting a discussion with myself now - Currently the DisplayCondition is a property on all "Part" objects, while the transform is only available on the PartContainer. This is inconsistent, so I think the transform should be moved to the Part - it should be as easy to implement, and will limit the need for PartContainers consisting of a single part.
 
You must log in or register to reply here.
Back
Top