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

BBOX display in MDLT2

scruffyduck

scruffyduck

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,981
Country
unitedkingdom
Arno

I have been comparing the output of my code with MDL Tweaker 2. in the section where you display BBOX data you show X, Y, Z min and max. I am wondering if you have Y and Z switched round in the display. Based on the RIFF Spec data is delivered x, z ,y. I get the same numbers as you but my Y is your Z and vice versa.
 
Hi Jon,

I think MDL Tweaker could be wrong here. At the moment I just took the data and showed it. It is FS that uses a strange coordinate system where y is the altitude instead of z. So the user would have to think of that himself :). I will probably change that in the new GUI I am working on at the moment.
 
Ah so I am wrong in what I am thinking then. In fact is is X and Z which are the footprint and not X and Y :o
 
Hi Jon,

Well, that just depends on how you define your coordinate system :D. I think it is easier to make a GUI that talks about width, length and height. That is something everybody can understand.
 
Hi Arno

I understand and agree with that - where I am confused (easy enough for me :) ) is if I am trying to tell a user what the width, lenght and height of the object is what do I use for each based on the co-ordinate system that wht mdl is using

x_max - x_min is width?
y_max- y_min is height?
z_max - z_min is length?

or something else..............
 
I think that is correct. But it also depends on your definition of length and width :D. It would be easiest if you just have an object you know the size of (simple test box made with GMax for example). Then you can very easily see what is what.
 
Yes you are right of course. I think the best way is to place a nice rectangular object like a hangar, or make a simple object as you suggest and then use CrossHair plus to measure it. :D
 
The only problem I can see here is that when you design an object you might not have a clear idea of which axis is length and which is width. I mean if I make a hangar the front side will probably be the width and the depth the length. But if you would design the same hanger, but with a rotation of 90 degrees you would call the other axis length I guess :).
 
You are right - I guess I am more concerned not to use height for one of the footprint axes. I am a cabinet maker and when building furniture length is always with the grain :) So maybe I will determine the two numbers and then use the largest as length.

I guess the issue for me is which is likely to be the 'front'. Now I come to think about it front and side make better sense becasue in senery placement you want to know which is the front :D
 
You must log in or register to reply here.
Back
Top