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

MCX - Request - Attached Object Editor - Platform - Position - Vertical offset from model origin

BASys

BASys

Messages
1,361
Country
scotland
MCX - Request - Attached Object Editor - Platform - Position - Vertical offset from model origin

Hi Arno

BACKGROUND -
MCX's 'Attached Object Editor' currently does not report
any platform's offset coordinates from model origin, (all entries are ZEROED).



REQUEST -
Could you please have a look at tweaking MCX
to report a platform's vertical offset from the model origin,
(lateral and longitudinal are not required).



DECIMAL PLACES -
Currently coordinates are only displayed to 2 decimal places, (i.e. nearest cm),

The fields do accept 3 DP,
but the dialog automatically rounds the displayed value to 2 DP.

Could you make all fields display at least 3 decimal places,
i.e. to the millimetre,
Though preferably to whatever DP the user enters.

Running the 'Generate Object Report' currently does report that user entered 3 decimal place value.

If 4 DP, or greater, is not preferable in the 'Attached Object Editor' dialog,
instead could the 'Generate Object Report' display the full DP value as entered ?



REASON -
I've lots of pre-existing models containing platforms for helidecks
all requiring vertically accurate colocated AFDs.

I've tried deriving accurate vertical offset data
using data from saved flights for -
- Platform only
- AFD located at model origin
- AFD located at platform (estimated)
All with an appropriate 'Ocean Flatten'
but results are inconsistent at different geographical locations.



ATTACHMENT -
I've attached an example model which has a platform.



Many Thanks
ATB
Paul
 

Attachments

Hi,

Let me see if I fully understand, since your request is talking about more than the attached object editor.

The attached object editor shows the position of the scenegraph node. For the platforms there altitude is set in the geometry of the platform if I'm not wrong (couldn't see in your model, since that one is located around z=0 anyway).

The amount of decimals in the display is just for viewing, internally the numbers are not rounded. I'm not sure if I can tune that easily in the property grid control, need to check that.

in the user report I can easier tune the resolution, that's just something I have in code.
 
Hi Arno

Cheers for taking a look at this.
I'd also like to say many thanks for your continued support of all MSFS variants,
and additionally conversions to/from other platforms.



The previously attached example model's origin -
- Is located on the underside surface of the helideck structure.
- Lateral & longitudinal offsets are approximately near the helipad's centre.

The attached platform is on the top surface of the helideck structure,
and is vertically offset from the model origin by approx + 450 mm.

My apologies for not posting originally.
I've now zipped and attached some WIP textures to this post,
which hopefully might make viewing in MCX easier.
(P.S. Forum's 'Attach Files' button doesn't support DDS, BMP, TGA)



For other models,
potentially their origins might be displaced -
- laterally/longitudinally by, substantially > 100 metres.
- vertically by > 20 metres



I'd intended addressing the following,
and other MCX related issues,
in a series of separate issue specific posts.

In attempting to measure the platform's vertical offset -
I'd also tried using MCX's grid, set to high resolutions,
and 'Camera View' set to each of Left/Right/Front
to hopefully accurately measure
this model's platform's vertical offset from model origin,
but when attempting to zoom in,
viewport culling inhibited any accurate measurement thereof.



MCX's 'Generate Object Report' displaying internal DP values
would suffice for my current needs. :)



HTH

Many thanks
ATB
Paul
 

Attachments

I think showing the info in the object report or in the hierarchy editor would make most sense indeed. I'll check.
 
Hi,

I have modified both the hierarchy editor and the object report to show the bounding box of the platform. It will be in the next development release.
 
Hi Arno

Such prompt service.
Works beautifully.

Gives me a consistent baseline to work from.

Was it entirely coincidence that the Z is millimetre perfect,
or is the reported Z being rounded to the nearest millimetre ?

Many many thanks.

ATB
Paul
 
3 digits are used by default in the hierarchy editor and the object report. So it's rounded.
 
You must log in or register to reply here.
Back
Top