MCX MCX - BUGREPORT - BGL Reading - Coordinates - OBJECT PLACEMENT & CONVERT WIZARD

[BASys]

Hi Folks

Arno -
My apologies for not having raised these issues previously.

I only investigated properly after loading an unrelated BGL yesterday
where I'd observed a totally unexpected model HEADING

MCX - Development version - 01/08/2020

For a BGL containing multiple objects -

MCX - SCENERY OBJECTS EDITOR -
Only lists the OBJECT MODEL
Does not list any of the - 3137 LIBRARY OBJECT PLACEMENTS

Not unexpected,
and MCX displays the OBJECT MODEL correctly

However -
- MCX - OBJECT PLACEMENT
- MCX - CONVERT WIZARD
both return LLAH data from one of the 3137 LIBRARY OBJECT PLACEMENTS
rather than LLAH data from the displayed OBJECT MODEL



ISSUE - TEST FILES -
I've attached a zip containing the following files -
- XML source for the BGL
- BGL
- Textures for the OBJECT MODEL

XML - EGNL_TEST_08_Saipem_12k_-_WPolaris+2___DS_MODU___201708___VISUAL_X.XML
BGL - EGNL_TEST_08_Saipem_12k_-_WPolaris+2___DS_MODU___201708___VISUAL_X.BGL

BGL contains -
- Static scenery model of a drillship
- Placements for library based light models (non attachpoints)



XML SOURCE FILE relevant sections -

EXPECTED LLAH data to EXACTLY match this - OBJECT MODEL -
<!-- Saipem 12k - WPolaris+2 - DS at TEST 08 -->

XML commencing - LINE 81

lat="53.975"
lon="-3.3"
alt="35.5"

pitch="0"
bank="0"
heading="315"

altitudeIsAgl="FALSE"



RETURNED LLAH data CLOSEST matches this - LIBRARY OBJECT PLACEMENT -
<!-- ELEMENT - VISUAL - HELIDECK - CAP437 - STATUS - _ODG_Light_Marine_Helideck_Status_OFF.MDL - PORT - TRUNCATED

XML commencing - LINE 114074

lat="53.9748802414183"
lon="-3.30008495615719"
alt="36.0814263916016"

pitch="0"
bank="0"
heading="249.307111568792"

altitudeIsAgl="FALSE"



ISSUE - MCX RETURNED DATA -

MCX - OBJECT PLACEMENT -

Launched MCX
Used MENU - IMPORT file-open dialog
Selected & loaded BGL
Clicked OBJECT PLACEMENT
Noted values
Closed MCX

Sorted as LLAH AGL NOCRASH -

53.9748802408576 - Matches XML LIBRARY OBJECT PLACEMENT to 8 DP
-3.3000849187374115 - Matches XML LIBRARY OBJECT PLACEMENT to 7 DP
36.081 - Matches XML LIBRARY OBJECT PLACEMENT to 3 DP
-110.6982421875 - Matches XML LIBRARY OBJECT PLACEMENT to 2 DP (OP HDG - 360)

AGL == False - Matches XML LIBRARY OBJECT PLACEMENT
NOCRASH == False - WRONG - LIBRARY MODEL is TRUE



MCX - CONVERT WIZARD -

Launched MCX
Used MENU - WIZARDS - CONVERT AND PLACE OBJECT WIZARD
INPUT - Selected & loaded BGL
Noted values
Closed MCX

Sorted as LLAH AGL NOCRASH -

53.974880241 Matches XML LIBRARY OBJECT PLACEMENT to 9 DP
-3.300084919 Matches XML LIBRARY OBJECT PLACEMENT to 7 DP
36.081 Matches XML LIBRARY OBJECT PLACEMENT to 3 DP
-110.69824 Matches XML LIBRARY OBJECT PLACEMENT to 2 DP (OP HDG - 360)

AGL == True - WRONG - XML LIBRARY OBJECT PLACEMENT is TRUE
NOCRASH == False - WRONG - LIBRARY MODEL is TRUE



SUMMARY -
Data matches xml LIBRARY OBJECT coordinates
Data should match xml OBJECT MODEL coordinates



PS
Whilst testing this issue,
I'd accidentally dragged the source XML into MCX
and was surprised to see MCX then load and display the object model
Nice feature I'd previously been unaware of.



HTH & Many thanks
ATB
Paul

 

[arno]

Hi Paul,

I'll have a look at your files later and will try to reproduce it.

One quick observation, the Convert & Place Object wizard is not designed to load BGL files that already contain placement information. This wizard is made to load a single object and then designate where it should be placed. So I would not use it with a BGL file that contains multiple placements.

 

[arno]

Hi,

When I load the BGL file this is the placement information I see. This seems to match the XML file quite well (lat and lon are slightly off, but that is the accuracy of storing them in the BGL file). The AltIsAgl is also set correctly.

I don't understand what you mean about NoCrash, as the XML file contains no NoCrash statement for this model.