View Full Version : 3D objects not found
hakanunal00
10-18-2001, 10:27 AM
I've installed both Build 118 and 119, but it rejected my api files with beginning "@" symbol which were created by Nova. Any solutions, suggestions?
thanks
Hakan
jhirsch
10-18-2001, 03:53 PM
I offer this solution with hopes that it will work. You have, no doubt, made the conversion from build 11x to 118 or 119. This was done when you first tried to run either of the new builds. The result was a new .APT file which is located in your main AIRPORT FOR WINDOWS folder. You cannot use this new file in a previous build of Airport for Windows because of the coding changes that were made.
Now edit this new .APT file with your favorite text editor. Search for double @ symbols in those 3D polygon sections and simply remove one of the @ symbols. Also, make sure that the path to your 3D macro is correct in that same line.
Hope that this will solve your problem.
Regards, John.
hakanunal00
10-18-2001, 05:03 PM
John thanks for the help. But it didnt work for me cause one of the @ symbol belongs to Airport's own file navigation system and the other one is a must for NOVA libraries. I'm using them and I have to cause these files helps to keep frame rates high. I hope Tom will fix it, or Pascal will change his coding.
But here is another issue, if you can help;
When using ANY (without @)user supplied api files in old scenery project, airport dont let me change any settings of them. Lets say that, I've changed the heading or scale, next time I compile scenery, it says "Error - create SCASM code for user object @c:\......\xxx.api file not found".
thanks again and regards
Hakan Unal
http://ltbj.aerofox.net
jhirsch
10-19-2001, 12:13 AM
Sorry that my solution couldn't work for you, Hakan, we tried. Since I have no experience with NOVA libraries, I can't offer you much additional help. As for your second problem, not being able to change that values of any parameters within a macro, I've not run into that one. I've had success with changing X and Y values of points that define line segments and I've changed the values for scale factors, again with no problems. When Tom returns, perhaps he can address this.
Again, Hakan, I'm sorry that I couldn't be of further assistance.
Regards, John.
Powered by vBulletin® Version 4.2.0 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.