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

Editing an ground poly

What error message do you now get then? The object in the other thread about this opcode works fine now.
 
Seems that every single bgl has a different error message. Mostly the error message is:

"Unsupported command SetVar in line XXX"

But the first file I´ve tested has exactly the same error message like the file in the thread I´ve mentioned above and this one works fine now!
 
An unsupported command is a warning, not an error. MCX will continue load the object in that case. It might be the IfVis check is coded so that it should fail for the object to show, in that case skipping it as unsupported will not give the desired result. That might give you an empty object.
 
This is an extract of one file with such warnings. The lines which are begin with SetVar are the ones which force the warnings. If I´m delete the lines the warnings are gone but the file still doesn`t load. But it makes sense as you have said this are only warnings.

; ----------------------------------------
; XXXX_Ground.BGL disassembled by BGLAnalyze (c) on Sat Jan 27 13:44:55 2018

; ----------------------------------------
Header( 1 N53:26:34.47 N53:24:40.70 W006:15:29.23 W006:15:29.23 )
LatRange( N53:24:40.70 N53:26:34.47 )
; since SCASM does not support multiple latitude ranges
; the range has been set to the minimum/maximum latitude.
; LatRange information in the BGL file is given as comment.
; If you want to use band separation, you must edit
; the source file manually.

; Insert the "Set( FSVers 0x800 )" instruction at the beginning
; of the file, if you want to use the FS2002 instructions
; for the facilities section
mif( [$Version < 285] )
Error( You need at least SCASM version 2.85 to compile this code )
mifend

; ----------------------------------------
; Procedural scenery
; ----------------------------------------


; LatRange( N53:24:40.31 N53:26:36.41 )
; ----------------------------------------
; ----------------------------------------
; Object # 1, offset: 0x000A size: 973562 bytes (0xEDAFA)
;; Lat: 0005A98E8h Lon: 0FB8CBE78h
; ----------------------------------------
Area( C N53:25:37.58 W006:15:29.23 100 )
IfVarRange( :L00002E 0346 2 32767 )
LayerCall( :L000034 12 )
LayerCall( :L00007E 16 )
:L00002E
Jump32( : )
:L000034
RefPoint( rel :L0000C8 0.50 N53:25:37.60 W006:15:29.23
V1= 10000 V2= 1756 )
:L000054
Jump( :L00005C )
:L000058
; unreachable code, possibly data area
Dbx( 0D 00 1E 00 )
:L00005C
VarBase( :LFFFFFFF8 )
SetVar( 0000 2 )
SetVar( 0002 2 )
VarBase( :[0] )
Return
:L000076
; unreachable code, possibly data area
Dbx( 8A 00 54 00 00 00 22 00 )
:L00007E
RefPoint( rel :L0000C8 0.50 N53:25:37.60 W006:15:29.23
V1= 10000 V2= 2539 )
:L00009E
Jump( :L0000A6 )
:L0000A2
; unreachable code, possibly data area
Dbx( 0D 00 1E 00 )
:L0000A6
VarBase( :LFFFFFFF8 )
SetVar( 0000 2 )
SetVar( 0002 2 )
VarBase( :[0] )
Return
:L0000C0
; unreachable code, possibly data area
Dbx( 8A 00 3A 75 01 00 22 00 )
:L0000C8
Return
:L0000CA
; unreachable code, possibly data area
Dbx( BC 00 00 08 00 00 B7 00 02 00 00 00 )
Dbx( 00 00 01 00 00 00 FF FF FF FF 00 00 )
 
Thanks again all for your help! With your support I was able to find the right solution. Modifying the sca file gave me the opportunity to load the file into MCX. There after it could easily compiled to a ground poly which is not longer invisible in P3Dv4.
 
Thanks again all for your help! With your support I was able to find the right solution. Modifying the sca file gave me the opportunity to load the file into MCX. There after it could easily compiled to a ground poly which is not longer invisible in P3Dv4.
Wonderful! Be kind enough to return the favor so that others can benefit from the community's effort in the same way you have, thanks so much!
 
Hey Rick,

as already said and with respect to the developer I will not post a tutorial or a how to. What I can say is that "SetVar" are the showstopper. You just have to delete it in the sca file. It typically looks like this:

:L0000A6
VarBase( :LFFFFFFF8 )
SetVar( 0000 2 )
SetVar( 0002 2 )
VarBase( :[0] )
Return

Delete the whole thing and save. Thereafter you are able to load it into MCX.
 
End-User License Agreement (EULA)
This End-User License Agreement ("EULA") is a legal agreement between you and The Developer

This EULA agreement governs your acquisition and use of our software ("Software") directly from The Developer or indirectly through a authorized reseller or distributor (a "Reseller").

Please read this EULA agreement carefully before completing the installation process and using the software. It provides a license to use the software and contains warranty information and liability disclaimers.

By clicking "accept" or installing and/or using the software, you are confirming your acceptance of the Software and agreeing to become bound by the terms of this EULA agreement.

This EULA agreement shall apply only to the Software supplied by The Developer herewith regardless of whether other software is referred to or described herein. The terms also apply to any updates, supplements, Internet-based services, and support services for the Software, unless other terms accompany those items on delivery. If so, those terms apply.

License Grant
The Company hereby grants you a personal, non-transferable, non-exclusive licence to use the software on your devices in accordance with the terms of this EULA agreement.

You are permitted to load the software (for example a PC, laptop, mobile or tablet) under your control. You are responsible for ensuring your device meets the minimum requirements of the software.

You are not permitted to:
  • Reproduce, copy, distribute, resell or otherwise use the Software for any commercial purpose
  • Allow any third party to use the Software on behalf of or for the benefit of any third party
  • Use the Software in any way which breaches any applicable local, national or international law
  • use the Software for any purpose that The Company considers is a breach of this EULA agreement
  • discuss the specifics of the Software in any way, especially in regard to personal modifications for using the Software in simulator platforms that are not supported by The Developer.
  • use the term "SetVar." However, if you do so, The Developer thanks you in advance for any hints on how to make the Software available to additional licensees through newly accessible platforms.
Intellectual Property and Ownership
The Developer shall at all times retain ownership of the Software as originally downloaded by you and all subsequent downloads of the Software by you. The Software (and the copyright, and other intellectual property rights of whatever nature in the Software, including any modifications made thereto) are and shall remain the property of The Developer.
 
Back
Top