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

FS2004 Creating Array and killing shadow

I checked the system configuration and it is set as requested by the compiler (infact v.1.1.0.3 works fine). Decimal separator is set as "." period. But AFLT still continues to output the C2002 Error in which it says that cannot find the xml file. Infact I noticed that in the Array folder the xml file is created only when I clic OK on the error window.

What I did not understand is why AFLT 1.1.0.3 works correctly with the same .def file (except for the color coding in the supplementary data (as requested by Colors.txt file).

Anyway, what kind of differences are there if I use AFLT v.1.1.0.3 or 2.0.12 for FS9? Are there any differences in the way AFLT works to produce the array or something else? Are there any differences in mdl used?
I was interested in trying the new version to check if it could be a solution to my G3D.dll crash.

EDIT: just to be sure the error would not depend by my pc, I tried to use AFLT with all the related folder on the other pc wher I have FS installed. The problem is exactly the same.
 
Last edited:
Just to remind you, I can create the .xml files and compile them (using your files with the version I sent) without problems.

Version 2 differs from Version 1 in many ways. Those from the user's perspective are described in the user manual. To list all the changes would take a lot of time and be of little if any benefit. But, I can confirm that fundamental processes such as submitting a .xml file to a compiler are quite standard and used in all my utilities.

You have confirmed that the reported-missing file actually exists. I notice from the C2002 message above you are running AFLT on the desktop. UAC won't like that, unless you are running as administrator. Being the administrator for the system is not sufficient. You must also "Run (AFLT) as Administrator". (Don't blame me, blame Windows!) If you are not Running as Administrator, give it a try.

Don
 
gadgets said:
.

You have confirmed that the reported-missing file actually exists.
Click to expand...

Yes it appears in the folder after I accepted the error by clicking over OK.


I notice from the C2002 message above you are running AFLT on the desktop. UAC won't like that, unless you are running as administrator. Being the administrator for the system is not sufficient. You must also "Run (AFLT) as Administrator". (Don't blame me, blame Windows!) If you are not Running as Administrator, give it a try.

Don
Click to expand...
AFLT is installed (its folder) in C:/Program Files x86, on the desktop there is only the library folder. Anyway, UAC service is shut down on my system because I ate that kind of messages every time.
I also tried to put the library folder in C:/temp because I thought the length of the path could be a problem.

I'll give it a try following your advice.

Strange that after the first time, leaving the old .xml file into the array folder, the error does not appear but the bgl obtained has the guids different from those of the new xml.
And also strange that v 1.1.03 seems not to be affected by this problem.

I perfectly understood that in your system all works correctly but I have the same problem on both my computers.

Bye
 
I'm out of ideas. I presume you tried running as Administrator.

If the compiler gave an error message, it did not create a .bgl. So, the .bgl in that folder is not associated with the .XML just generated. (Check the date stamp.) Consequently, the different guids are a "red herring". (I suspect Italians have a different saying.)

I can think of no reason why the compiler should not be able to access the .xml to be compiled - which we know exists where it should be, other than due to some permissions issue. Unfortunately, I can't help you with that. Since I cannot reproduce the problem, and since I can do on my system - with your files - what you claim not to be able to do, I can only conclude that whatever the problem, it lies within your system configuration.

I'm happy to continue to explore this issue with you, but there seems little point in doing anything further until you discover why the compiler doesn't see the .xml file. Of course, you can always revert to Version 1.1.03, but I will not be able to render any support for it.

Don
 
Don, I tried to execute AFLT.exe "as administrator" even if UAC is disabled in my system, as I said yesterday, and my account has full administrator rights. The problem is still there.

Using the AFTL verison you kindly posted me (v.2.0.12) I also noticed that in the xml file (produced after the error) the line

altitudeIsAgl=

uses lower case instead of uppercase for the value. so the line is the following
altitudeIsAgl="False" instead of altitudeIsAgl="FALSE" (produced by the v 2.0.11a)
I noticed that because I got the xml file produced after the error and I dragged it by hand over the bglcomp.exe in the FS9 Compilers folder. Doing that I received the following error

Error3.jpg

Apart from this problem, it seems that doing in this way (but with the v 2.0.11a) I obtained the bgl and after that I also (using AFLT this time) could create the related library.

My opinion is that (apparently on my PC) it seems AFLT searches the xml file, to get to the compiler, before it generate the xml itself. And this generate the error advising that the xml file is not in the folder where it is searched for. Then I clic on OK just to accept the error alert and in the folder appears the xml file.
The reason for which I'm saying that is the following (I just tried to explain in a previous post but I think it is useful to underline it again).
After the above, in the Array folder I have: .def file and the corresponding .xml file. I clic again on the Make Array button and I select the same .def file as before. Now AFLT makes its work and produces the bgl (and another .xml file different from the first one, i.e. different GUID used). Using this bgl and the library generated in the above described way the two file are correctly related. This makes me think that the last bgl created automatically by the procedure and the one created by hand are made using the same xml that it isn't the last one generated.
And if it could be a proof, using BglAnalyze9.exe the two bgl are exaclty the same.
This create difficulties to make the library after making the arrays if I use all the AFLT procedures.
Hope my english was not too poor to be clear.
;)
 
altitudeIsAgl="False" instead of altitudeIsAgl="FALSE" (produced by the v 2.0.11a)
Click to expand...
There must be more than one version of the FS9 compiler, since "True/False" is accepted by mine. Anyway, I have changed the code to always be upper case, i.e., "TRUE/FALSE".

My opinion is that (apparently on my PC) it seems AFLT searches the xml file, to get to the compiler, before it generate the xml itself.
Click to expand...
And you are right!!! Thanks for persevering. That error was never generated on my system because there was always an earlier version of the .xml file in the folder to compile. And, of course, when I checked the .xml file after the compile when you first reported the problem, the new version had already been saved, so all looked normal.

This is why beta testers are needed. Thank you.

New version of the .exe attached
Don
 

Attachments

gadgets said:
There must be more than one version of the FS9 compiler, since "True/False" is accepted by mine. Anyway, I have changed the code to always be upper case, i.e., "TRUE/FALSE".
Click to expand...

Ok, I'm using the one included in the packets downloaded from your website (even the v.1.1.03 and v.2.0.11a)

And you are right!!! Thanks for persevering. That error was never generated on my system because there was always an earlier version of the .xml file in the folder to compile. And, of course, when I checked the .xml file after the compile when you first reported the problem, the new version had already been saved, so all looked normal.

This is why beta testers are needed. Thank you.

New version of the .exe attached
Don
Click to expand...

Oh this is a marvelous news and I'm very happy to had the possibility to contribute to your useful work. I just tested it and all is working perfectly.
I thank you because you were very kind till now without "sending me to the devil"... :)

Ok, now I'm trying to understand what is creating the G3D.dll crash. I'm quite sure that the problem is in the array, because I reduced the scenery only to 1 Afcad, 1 exclude, 1 flatten, the lights library and the bgl of the array, without anything else. But maybe this could be another Thread...

Thanks a lot till now.
Ciao
 
You must log in or register to reply here.
Back
Top