scasm import

[bmorrow]

I'm having scasm import problems in build 136
My objects are not going into the locations defined by the code.
What am I doing wrong?
I decoded a BGL from FS98 to create the scasm code.
I tried importingit as was, and also importing it after changing all latitude and longitudes into deciaml minutes format. Neither worked, and I ended up getting graphdraw errors and objects that were misplaced drastically in longitude and marginally in latitude.

[Barney]

Why are you trying to import a *.sca file into Apt2.6? It can only open *.apt files. Anything written in an older code, like that done for a previous version of FS, likely can't be completely recognized by Build 136 anyway. Newer Builds have trouble with older *.apt files, even; the opening instructions tell you that.

Barney

[bmorrow]

I am attempting to restructure the Toronto airport and surrounding highways to take into account the new construction which is taking/has taken place on them. I also want to include a much more detailed coverage of the surrounding city areas. A couple of years ago, I created the cities of Toronto, Brampton, Aurora, Barrie, Newmarket, Pickering, Whitby, Oshawa, Nobleton, King City and Thornhill and the areas in between for my own use from detailed topographic maps, and I included in these sceneries as much landscape realism as I could, with swamplands, rivers, ponds, lakes, parklands,highways (all lanes and bridges for hwys 401, 404, 400, and 407)etc., but these have changed since, and I wanted to update them. Those things that have not changed, however, I wanted to keep, such as certain bldgs, towers, etc.

Are you suggesting that I should return to an earlier version of Airport in order to achieve the desired result? Or is there another way to deal with it?

[Jaybird]

>>I'm having scasm import problems in build 136 My objects are not going into the locations defined by the code. What am I doing wrong? I decoded a BGL from FS98 to create the scasm code.
I tried importing it as was, and also importing it after changing all latitude and longitudes into deciaml minutes format. Neither worked, and I ended up getting graphdraw errors and objects that were misplaced drastically in longitude and marginally in latitude.<<
**************************************
***I've done this a number of times in Apt. The way I do it is to edit all the Lat/Lon info in the decoded file, changing Lat to "%1", Lon to "%2". Also, any other relative parameters can be dealt-with the same way (heading, scale, elevation, etc). Although it's not absolutely necessary, I rename the revised decoded bgl to have a file extension of ".api" and copy it to the Apt\API folder. Then you call the api file as a "3D object" in Apt. You can then locate the decoded (now *.api) object(s) by wherever your "right-clicked" cursor is located on the Apt scenery map and use the other parameters to govern other requirements. For protection of copyrights, this, of course, should not be done with other people's bgl's without their permission. I get the impression you are the owner of the bgl's you're trying to transfer.***
********************************************************

>Are you suggesting that I should return to an earlier version of Airport in order to achieve the desired result? Or is there another way to deal with it?<

*******************************************************

On all my older .apt files I've tried, all were recoverable for use in later builds (revisions) of Apt26. A few conventions have changed, however, the old files are saved and you can re-do the necessary ones (roads, taxiways, etc to name a few).

Good Luck...

[Barney]

As long as you have the original *.apt file(s), yes, I'm suggesting you return to a version of the program that was current when the project was originally done. If you 'open' the *.apt file in Notepad, for instance, the version utilized should appear across the top. I have _some_ copies of older versions on file....quote me the one you need and I'll arrange to send it if I indeed have it.

BTW, if you should succeed in getting the original file to open within a version of Apt2.6, you will need to re-establish the links to the various folder locations wherein the *.api's reside. This can be tedious, dependant upon the complexity of the schematic.

Barney

[bmorrow]

Actually, I have now had some success.I used a code module constructed in Access to split the scasm file into individual files each containing one area block of the scasm file, and attaching to it a new header that encompassed the area taken up by the constructs in the area block, making sure that this header had a midpoint with an integer for its minutes, then imported each of these files using the option to 'add scasm to existing'. Wwhen the existing had been established with a midpoint identical to what was being imported, all objects imported properly.

Since I don't intend to distribute my recreation, and intend to use it soley for my own skills developement, I won't be violating anyone's copywrite. Perhaps, after I upgrade my computer and version of flightsim in the future, I will go through the whole process of doing it again and contacting all those who may have contributed portions of the end result, but since I intend to create my file based on things that do not yet exist in the real world and are only in the design/construction stages that won't be finished for years, I don't think it would be appropreate to release my constuct to the filghtsim community at this time.

Thanks for your help.