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

SAMM1 models don't show in beta

Messages
172
Country
us-newyork
I hesitate...but.

I have a library of aircraft made with Don Grovestine's SAMM1 (SAMM1 models only in the library). Using the beta version of adex (1.52.4710), they appear with appropriate thumbnails in adex, but they don't display at all in fsx.

I also have a library (actually 2) made with SAMM 2 (SAMM 2 models only in these libraries), and they display just fine. The picture shows a couple of SAMM 2 planes with the missing SAMM1 circled.

Tonight, I tried using the "non-beta" ADEX (1.50.18.197) which I haven't used for a while. It also displays the SAMM 1 models, but when compiled, they display in FSX perfectly!

I have only one copy of FSX (the library is active) but the compiled SAMM1 models are simply not "making it" to FSX using the beta while they appear to compile and display fine through the non-beta version.

Wasn't sure whether to post here, or on the SAMM forum...but it seems it's a problem that ADEX is missing.

When the beta was first released, I had posted a problem with "some of my scenery not showing" . This was it.

Hope this makes sense. The pictures are of three SAMM1 models displayed with accompanying 1.50.18.197 screen; and the beta with SAMM2 and missing SAMM 1 FSX display, side by side with 1.52.4710 beta display.

I tried to search to see if this was already discussed. Perhaps cannot mix the two formats.

Thanks, and always, no offense will be taken when it's pointed out that this is something stupid I've missed.

Gary
 

Attachments

  • ade beta, miising samm1, samm 2 displayed.jpg
    ade beta, miising samm1, samm 2 displayed.jpg
    495.8 KB · Views: 389
  • adex 1.50.18.197 samm 1 planes display.jpg
    adex 1.50.18.197 samm 1 planes display.jpg
    370.3 KB · Views: 380
Can you please email me some samples of the models of SAMM1 and SAMM2 so that I can test here. If I can replicate the issue then I might be able to understand why the difference.

email to jon AT scruffyduck DOT co DOT uk
 
This weekend

Sorry, pretty rough couple of days at work
I'll try to get them out this weekend

Gary
 
emails sent

I've sent emails with the mdl files attached. I do all of my ADE scenery from the libraries rather than directly from the mdl files (The SAMM1 mdl files were not even on my current computer, but from the bgl they work in the "non-beta" version.)

The bgl files with textures were 80 mb which my email won't handle, so I sent three mdl files/folders from SAMM1 and SAMM2

The likelihood that this is a mistake on my part is very high. Please don't use your time unnecessarily on this. Going forward, I can just use the SAMM2 models.

Let me know if the emails or files didn't go through (email or here).

You can't underestimate me--I don't think I've ever "zipped" files before, just opened them.

Gary
 
OK I am not at all sure I understand what I am about to say!

First your SAMM1 mdl files appear to be generated for FS9. They have no inbuilt GUID. Both ADE 1.50 and the beta load them into the model list with the GUID set to 0000.....

In your SAMM2 zip there is a mdl suffixed FSX - this does appear to be a FSX mdl file and the GUID is available.

If your SAMM1 mdl files are added to ADE9 rather than ADEX then a GUID is generated by ADE. It is not generated in ADEX since that is expecting a FSX mdl file.

As far as I can tell if the mdl file has a 0000.... GUID it might compile but I am not at all sure if FSX would find it

If the mdl files are added to a library then chances are the library creation tool will generate a GUID for the model and all will be well.

So I suppose I am saying that I would not expect any version of ADEX to be able to sensibly compile and place FS9 models.

ADE should probably not accept them but it seems it does.

BTW the situation appears to be the same for what appears to be a FS9 model generated by SAMM2

As I do not use SAMM (sorry Don :o) I can't say how it generates models and if it generates differently for FS9 and FSX (I assume it would). If it does generate differently then the issue is generating the right mdl for the right FS/ADE version. I can't see that the version of SAMM is making a difference.

There may be a problem is ADEX with how it handles models but I can see no change in handling between 1.50.4402 and 1.52.4710 :o:o
 
Thanks

There's one thing I'm pretty sure of...I don't understand what you said!!!

When I open my SAMM1 library the individual files do have GUID associated according to MCX. And, in the library/object manager of ADE there is a GUID associated with them.

There is an easy work around for me...I'll just use the SAMM2 library.

I'll have to explore in the ADEX object/library manager if removing the .bgl file removes the individual files from my working list (all aircraft, regardless of which bgl they are in, I've assigned to the category "aircraft" for easy management.. so I need to remove my SAMM1 library(.bgl) and the 25 or so entries from that library that are in my "aircraft" category)

Don's tool works great (except for my mismanagement) and it's easy to add more to my working library if I want to replace any of the SAMM1 models.

With SAMM one creates the models, but then generates a library for fsx use (at least that's the only way I've ever got them to work). But I guess that's the same thing I do with sketch up buildings after mcx conversion to models--then to a library.

Many of the aircraft were original fs9 aircraft (HTAI Cessna package, for instance), so maybe that's why they show up that way?? Or, I probably did something wrong when I made the library (could it be!!!???). But they do make absolutely beautiful scenery.. I've never owned fs9, tho I do have a fs9 "dummy file" as a step to install MAIW packages.

Still curious (well, I guess baffled is a better word choice) to me how the same library (same file, everything) is handled differently by the two version of ADEX (beta and none beta)

Don't waste more time on this, please. The problem is in Upstate New York, not there!!! I have an easy solution

Thanks so much for the teaching and patience.

Gary
 
Hmm so you are saying that you are not getting SAMM1 objects to show up when they arein a library? I assumed you were adding them to ADE directly
 
Correct. Libraries only.

I believe (can't remember) that the SAMM 1 library was created from the models with Arno's library creator tool (part of the mcx download now)

SAMM2 includes a library creating tool. But I don't have SAMM1 on this machine, and the old one doesn't reliably start (that's why I built a new machine--and besides, every 6 years....)

Unfortunately the library files are large--70mb or so-and not amenable to email

Jon, unless you really think this might be an issue with your program that you want to work on....there is a good work around for me.

If it would help YOU, I can get the libraries on a CD or sd card and mail them to you...but only if you think this is important for the program.

For me, I have a work around.

Gary
 
To be honest I am not sure what is happening so at the moment, provided you have a satisfactory work around, I will park the issue :)
 
Back
Top