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

FSXA Create Array error

D

Daniel Smith

Messages
39
Country
unitedkingdom
Hi,
I have been using this tool version 2007 without problem for a while now using the stock models and it does a fantastic job, thank you.
But i now want to develop my own models for use and seem to have run into difficulties.

When i click the array button i get the error "Unhandled exception" "Failed to compare two elements in the array"

My process is to create a model with empty attachpoint in Gmax and export using the FS2004 Gamepack.

The model is usable in FSX placing it with modelconverterx.

I copy the line in Types.txt for Split and paste it at the end of the document and amend the name and model to reference my MDL.

I then go to create the array and get the above message.

Any help would be appreciated.

Thanks,
Danny
 
Danny, it's not clear you understand the purpose of arrays in AFLT. The placement of models is the purpose of the array. That you are placing the model with MCX leaves me uncertain as to what you are attempting to do.

In any case, I am travelling at the moment and unable to provide any meaningful support. I suggest you review the manual on the construction/use of custom models and arrays. Then, if you still have difficulties, post again. I may be able to be of some further help but, if not, perhaps other users will jump in.

Don
 
To update... I have found a work around.

In the Types.txt file instead of adding a line at the end of the document referencing my mdl I alter the original line for example the split line and change the reference to one of my mdl's.
This method works perfectly but it means i have to split my array file into different light type sections to different array files, and change the reference to my mdl in the types.txt....

so i would have 1 array file for the white centerline lights, rename the types reference to my white mdl and process array and library.
change to red/white array and again rename the reference in types......and soforth.

I initially thought it was a problem with my mdl but this method appears to say not.

Danny
 
Hi Don.

Thanks for taking time out to reply

I only placed the model with MCX to test it was working after i came across problems with the array.

Good travels.....

Danny
 
Can't even imagine why that works but the other (proper) approach doesn't. Unfortunately, I'm not in a position at the moment to investigate.

Nonetheless, AFLT should never throw an unhandled exception. SO, clearly, there is a problem. It would be helpful (once I get back home) to have the details of the exception message, a copy of the types.txt file with your original modification and a copy of the array definition after you edited it.

Don
 
Hi Don,

Attached are the files you requested.

I have been trying to resolve the issue and have found a curiosity.... If I replace the first line in the array referencing to my model with Split_LO, the array will compile but the created mdl in lights folder has no colours assigned to it. I can then create a fs9 library for FSX but the created bgl has no light attached.

Another method that appears to work is to compile the array using your stock models and then editing the created XML file to reference my models GUID and manually re compiling to a BGL using bglcomp. Then creating a library using other software on this site. the bgl file has working lights in FSX.

If you require my full file structure including my mdl i can upload it to google drive or email it to you as you wish.

Safe travels,

Danny
 

Attachments

Hi Don,

No rush to answer as your travelling but I noticed that the colours file in release 2007 references effects that don't exist in the zip downloads from your website or the effects file.

Is that correct?

Thanks
Danny
 
Based on your comment that the colors file refers to effects not in the archive, it appears you have installed a development release without first having installed the general release on which the development release relies. That's not your fault, however, since I never posted a general release for Version 2; it has simply been a series of development releases. Unfortunately, I neglected to include the all the necessary update files in the latest development release - and am unable to do so at this time.

However, I think if you download and install the file http://stuff4fs.com/Applications/AFLT/Downloads/AFLT2005.zip, and then install AFLT2007.zip on top of it, you should be OK.

Don

EDIT: Belay that last instruction. I've found enough bandwidth to create and upload a new archive containing all the files. Simply download the latest Development Release AIFP2007(a).zip.
 
Last edited:
Hi again Don,

The files I uploaded with the error message are now not applicable to the new release 2007a.

I'm getting different errors this time but i would like to make sure i'm following the correct procedures before uploading the new error message.

I will try and have a go this weekend if work allows.

Thanks again,

Danny
 
Hi Don,

I finally got chance to work with the lights toolkit 2007a and will explain what is happening.

I've added a reference to my MDL in the types.txt copying the data from Split and put it at the end in a new line of the document.
I've written the Array def for a row of center lights.
When I press "Make Array" I get the following error message........

Color "" missing from "colors.txt" or is invalid

Then a complaint about dayglo followed by a compiling error screen.

If I change the reference in the array to Split and not my mdl it compiles perfectly.

for ease of use I have reduced my array to only 1 light.

Please find attached the types.txt, colors.txt, centerline.def and 3 screenshots of the error messages.

anything else you need let me know.

Many thanks,

Danny
 

Attachments

The problem (or at least a problem) is the incomplete entry in the .def file.

For splits, you must have Front color / Back color / # of bulbs as supplementary data. You have not provided # of bulbs.

Given that error, which is responsible for the first message, it's unlikely the compile could be successful.

So correct that error and try again.

Don
 
Thanks Don,

The .def file now reads...
CLRWW | 0 | 0 |0 | Rwy-Med/Split-Red/2

The error message is the same as attached above.

As in the original problem if i change the types.txt to read.....
Split |CLRWW | SPLIT | 1 | 180 | 90 | | True | M | 0/0/0; 0/0/0

and change the .def to Split instead of CLRWW It compiles perfectly.

I can work using this method but it makes what has been an easy program up till now slightly more complicated now i want to use my own models.

Thanks again for your continued support.

Danny
 
That would seem to suggest there is also a problem with the .mdl (i.e., it is not equivalent to the split base model), since switching to type split compiles OK.

Rather than continuing in this vein, i.e., feeding me information bit-by-bit, should you need to post again, please include your entire library folder, the base .mdl file for CLRWW and, if you developed that element with Gmax, also the Gmax file.

Don
 
Hi again,
please find attached library folder, base mdl and gmax file for the above problem.

Thanks for the quick response.

Danny
 

Attachments

I was unable to attempt a compile because the INI folder in the archive you sent was empty.

However, I believe I understand what is the problem - at least the next layer of the onion. Your custom light model uses a custom texture. AFLT failed to handle that texture properly and the attempt to apply Day-Glo colors aborted. I have no idea at the moment whether or not this is something I can work around. But, if you use "Rwy-Red" or "Obs_Red" as your lens color, that difficulty should disappear.

In the meantime, I'll investigate a possible fix.

Don

PS: with 700+ polys in your model and 200 copies of that model, I would expect a VERY significant FPS hit.
 
Don,

Sorry to inconvenience you but i just noticed the array def file i uploaded is corrupted for some reason.

I've re uploaded the zip file below with the correct def.

point taken on the poly count. My final model is going to be considerably smaller but thought i would see how far i can push it.
As a point of interest, using my previously stated method of compiling this model i have placed 440 copies of this model in my scenery with only 1 fps drop.
That being said i have not added any other scenery yet so 1 frame here and there will quickly add up to a significant drop.

Thanks for your input.

Danny
 

Attachments

You must log in or register to reply here.
Back
Top