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

Static aircraft not showing...

Messages
19
Country
unitedkingdom
Hi,
As a first time user I have a problem with a static aircraft made by SAMM2 not showing in my airfield project.
I have done all the required steps to get my add-on aircraft made into a static and loaded it into the objects library for use with ADE9x...
The aircraft shows in the library object list and appears as positioned on the airfield map when added.
Having compiled and saved the new airfield when opened in game the add-on static does not show.
All the other objects placed by ADE from objects library do show but not the add-on static.
I am running FSX Acceleration on my system.
Any help appreciated.

Regards
DEEGE.
 
DEEGE. all you know at this point is that you have a file that contains something ADE recognizes as a valid object.

The static model is just another scenery object. The first thing to do is ensure the model converted properly. When you created the aircraft, did it show properly in the viewer? Did SAMM issue any error messages? Have you tried positioning the static model directly from SAMM? If so and it doesn't show, then I would suspect the library file. Are you sure the library file you loaded into your scenery was the same one you "gave" to ADE?

You can be certain if SAMM didn't object and it showed properly in the viewer, that the model is OK.

Don
 
Static not showing solved..............

Ron,
Thanks for your reply and info.
It was indeed a misplaced file/folder combination causing the problem.
With the statics library .blg and textures files placed in the Global/Scenery andTextures folders and the library .blg loaded into ADE objects it now works.
Thanks again,
Regards,
DEEGE
 
Trying to resolve a similar problem, but the solution above seems incorrect. I place scenery objects and textures in the addon scenery/ scenery and texture files. all my addon scenery objects are there.
So my problem is I ran a test with the airbus 321 in fsx it showed in the viewer it also does not appear. I am trying to place the Curtiss C-46 which has been converted but it will not show in the viewer.
what I have done;
Reran samm with admin rights, tried several different versions of the C-46
files were created and placed in addon scenery scenery and texture directories.
I activated the libraries with ADE all shows good
objects placed but do not show either the airbus or c-46
I then created a separate folder in addon scenery with scenery and texture files located there
then i activated in scenery library still no show.
what am I missing?
I have done this once before with no problem. now can't get a result.
I could believe the C-46 (which is a 2002-2004-FSX port over) did not work, but the Airbus should.
Do I have to do something besides generate a bgl? and texture files?
 
I activated the libraries with ADE all shows good
objects placed but do not show either the airbus or c-46
I'm a little confused by this statement. What do you mean by "activated the libraries".

Did you actually copy the library file to FSX, as well as the ADE .bgl and the textures?. If not, you must.

As I mentioned above, static aircraft are just scenery objects and are handled like any other scenery objects.

Don
 
Terminology issues:
In ADE I added the static object under tools/ library manager/ add single file. It successfully added the object to the "libraries" in ADE. I successfully placed the object in the airport design within ADE. When opening the airport in FSX (after saving and compiling) the object does not show. I tried several times doing different methods of SAMM. SAMM always created the MDL file and then successfully converted to use with FSX, then also compiled into separate scenery and texture files which I had SAMM place in a folder on the desktop. After that I simply placed these files in my addon scenery/ scenery directory, and addon scenery/texture directory. During the SAMM process,the whole SAMM program froze if I attemted to use the object viewer and displayed "various triangles removed" or something to that effect in a dialogue box.

As a test I tried creating and compiling the stock FSX airbus a321. It also created mdl, bgl and texture files, it appeared successfully in the viewer when prompted. But alas it was not visible when placed.
I have been working with objects a libraries for years, i know how that all works, I am not familiar with creating objects. I have a project where a placing a Curtiss C-46 would be required to fill out the scenery correctly, I would love to solve the issue if possible.
I am using the FS2004/FSX Curtiss C-46 Commando by Libardo Guzman, Greg Pepper, and Tom Gibson GMAX Version 1 3/2007

Can someone with SAMM experience test this?, Or can someone give me a fool proof test mule aircraft to try again. I feel I am missing a simple step or mis-understanding the creation process. many thanks for your patience.

rhb
 
In ADE I added the static object under tools/ library manager/ add single file.
What file did you add.

It successfully added the object to the "libraries" in ADE
ADE doesn't maintain libraries. ADE simply saves a reference to the objects in the file. You must still load the libraries into the sim (unless its a default library of course.)

then also compiled into separate scenery and texture files which I had SAMM place in a folder on the desktop
are you referring to a library file produces by SAMM or something else. If a library file, is this the same library you submitted to ADE?

During the SAMM process,the whole SAMM program froze if I attempted to use the object viewer and displayed "various triangles removed" or something to that effect in a dialogue box.
But, earlier you said you successfully created the necessary files.

As for your selection of aircraft, if you are using FSX, any aircraft that SAMM will convert should display correctly. I doubt this has anything do with the aircraft. Rather, I suspect the problem is your file manipulation. But, if you think it's aircraft related, any FS9 or FSX stock aircraft should work.

Don
 
I wrote a clear and concise explanation using the correct terms, sorry if you can't understand. I know the difference between a library and a library object.

I added the .bgl file of course, it is all you can add in ADE
I did not mean libraries of ADE, I assumed you would understand that. both objects were placed in the appropriate scenery libraries before "selecting" them in ADE. Does that make it more clear?
Yes the SAMM program processed the files fine, and produced both scenery .bgl files and texture files. But when I (on subsequent attempts) tried to view the plane or object in the model viewer it crashed the program. but it still generated, produced, made, both scenery (.bgl) and texture files.
 
Last edited:
I did a test. here is a mustang placed with ADE, the nearest was a freeware download, the far one missing parts was generated using SAAM version one some years ago, it is missing textures because of the limitations of SAMM, some modern complex aircraft would not compile correctly as stated in the SAMM documentation of that time. Between the two there is supposed to be a C-46. I added all these aircraft the exact same way. May I suggest that the SAMM version 2 is not compatible with ADE at the present time? I suggest you check it out. I am at a loss.
c-46.jpg
 
I see you had second thoughts about the last comment in your penultimate post and deleted it - and just as well. (The forum sends me a copy of the original.)

SAMM generates scenery objects. ADE places scenery objects. There is no interface to be more or less compatible. Indeed, since you state you placed the two static models in your screenshot with ADE, it's not clear why you would suggest incompatibility between the two. First-time users are often at a loss to understand/explain when things go wrong.

As for your "clear and concise explanation using the correct terms", had that been the case, I wouldn't have had to seek clarification. You referred to "file" (without clarifying file type, contents or how it was generated) and "object". And I'm supposed to understand? That you "know the difference between a library and a library object" doesn't help me understand since I have no idea what you understand or don't.
If you send me the full aircraft folder for the aircraft you are converting (or a link to it), and the SAMM\Models folder that resulted, I'll see if I can determine the issue.

Don
 
Thanks for the nice freeware program, I appreciate the effort you have made to offer such a tool for the community. You've done enough already, thanks.
 
If there is a bug somewhere, I'd like to find it. So, if its not too much trouble, please send me the requested files.

Don
 
I really think it is a local problem with something corrupted on my end. I have tried converting at least 5 different aircraft. Originally SAMM produced an MDL file along with an .XML, (I think I remember seeing these in the model folder of SAMM under FS9). last time when I generate an MDL there is none to find in any of the model folders but there seems to be something in the work folder. I am trying to cite this from memory as I now have deleted all traces of SAMM, so my descriptions may now be inaccurate.
Before I uninstalled SAMM permanently, I uninstalled it re-installed it and ran it and got a message I never got previously, something to the effect that FS9 models need a file from the FS9 SDK, (which I don't have), it further says to delete the DAT file that refers to this SDK file and try again, if you want to. I did and got locked in a cycle of repetition. At that point I got discouraged and wiped it from my computer.

As an academic exercise I will try to re download SAMM and see what ensues. I have some other projects at hand, so it may be a bit before I get to it. Thanks.
edit; added link; http://simviation.com/1/download?file=c46ga.zip
 
Last edited:
Problem solved finally;
After I realized the MDL and xml files were not going to the SAMM directory where they had placed when I first ran the program, I went looking. I found that SAMM was dumping all the dds files and MDL,XML files in my root directory C:/. there resided unbeknownst to me the MODEL directory with the fs9 and fsx folders and dds files scattered about outside those folders.
the only way I could get things to work, was to use Model Converter and convert the SAMM MDL file to a .bgl I could place in the scenery. I don't know why but that's it. I could not get SAMM to generate a .bgl that was usable in my case.
c46.jpg
 
Glad you finally got it to work. Given the nature of your difficulties, however, you must be using a very old version of SAMM. The current version is 2.2.01.

In the much earlier versions, model and library files were saved in the SAMM folder. In the new version, you (the user) specify where your library of static aircraft is located. The .mdl, etc. files are saved there. When you create a library file, you must also specify where it is to be saved. (SAMM remembers these locations from the previous sessions so, if you want to save to the same place, you only need enter it once.) If you are using the latest release, perhaps you didn't notice you were saving to some earlier-used location. It's also not clear why you felt you needed to use MCX to convert models, since FSX displays FS9 static models just fine. Of course, SAMM will do the conversions for you if you ask - using the MCX .dlls.

In summary, I converted the FS9 C-46 you sent me with SAMM 2.2.01, asked it to generate a FSX model (not necessary, but since you thought the conversion was necessary, I did it too) and placed the model. It appeared with all parts and textures rendered properly.

Don
 
Back
Top