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

few question about animation

Hi, I can indeed also see the problem here. But can you also show me the ASM files (only of the origional GMax version is fine). Then I can check the bounding box and things like that.
 
It seems MakeMDL does not calculate the bounding box correct for animated object (goh, surprise yet another bug in MakeMDL). You can fix it by finding this piece of course in your ASM file:

Code: 
bounding_box_riff_start	label	word
    db  'B','B','O','X'   
    dd  bounding_box_riff_end - $ - 4
    real4  -2.170, 0.007, -4.691  
    real4  0.603, 5.041, 2.478  
bounding_box_riff_end label word

And then increase the size of the box. As I saw your object moved about 40 meters, I changed it to this:

Code: 
bounding_box_riff_start	label	word
    db  'B','B','O','X'   
    dd  bounding_box_riff_end - $ - 4
    real4  -2.170, 0.007, -4.691  
    real4  0.603, 5.041, 52.478  
bounding_box_riff_end label word

After this recompile the ASM file and it should work (it did here).
 
no more dissapearing!!

It works!!! It works!!...oh my god!!! thank you very very very much Arno!! :D :D :D :D you are really awesome :cool:

anyway what

real4 -2.170, 0.007, -4.691
real4 0.603, 5.041, 52.478
Click to expand...

mean ? is it a movement coordinates ? I would like to know this so I could fix them myself if this happen again in the future..

again thank you very much (thousand time)..for helping me out this mess..
 
Hi,

These parameters define the two extents of the bounding box. So the lower left corner and the top right corner. So they define the area that is covered by your object. So each set of three are a x, y and z coordinate.
 
In the AnimHouse.gmax that M$ made, there is a "Clear Box" object that takes care of this problem and establishes the bounding box when a scene is compiled. My only thought is since this box has a 0% opacity material applied to it is how it might affect other objects placed inside or that might overlap from either other bgl files or an aircraft that enters the box. I have had an experience of an aircraft that entered a hanger becoming invisible when viewed thru windows on the side of the building especially when reflectivity was applied to the windows. Looks really strange.

Lou
 
Another option to fix it in GMax might be to place a box the size of your total object (with animations) just under the ground. That should also make sure the bounding box is correct (as long as the animation is not in the Z direction as well). But that is not a very clean method of course.
 
Hi Lou.

I had looked at the ASM code after using a 'dummy' bounding box ( big box with 0% opacity ), and it had no effect on the rest of the code. The box isn't converted to ASM, so it can't interact with anything... it just resets the bounding box.

Dick
 
Very interesting indeed. So if you have a opacity of zero nothing is actually drawn. Always good to know.
 
Thomas said:
With the Attach-function enabled, you can simply click the other parts to make a single object of them.
Click to expand...

Sorry to come back to this old reply. But this function was also new for me, so I just gave it a try. When using attach you must be aware that no changes are made to the parts. So if they are partly intersecting, they will also be afterwards. The part that intersects is not cut out or so in any way.

Therefore this function is only useful when the parts can simply be added together. If some "calculation" is needed along the way, the boolean object is the way to go.
 
You must log in or register to reply here.
Back
Top