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

New Version of SAMM Needs Testing

G

gadgets

Resource contributor
Messages
9,388
Country
ca-britishcolumbia
I have just added significant model editing capability to SAMM. In version 1.1.12a, all aspects of the textures and materials can be changed, the use of individual textures can be suppressed and the static pitch and c/g height can be adjusted from within SAMM. As well, this release fixes a few minor issues I encountered during my own use of SAMM.

With this release, it is no longer necessary to delete unused textures from the source texture folder or adjust the static parameters in the aircraft.cfg file.

The aircraft .mdl file saved along with the static model includes any updates you make. The updates may be re-used by starting with the updated aircraft .mdl file (from the Static Model File window) rather than with the original aircraft.

The changes to the code were significant. So, I'd appreciate it if a few "power users" gave Version 1.1.12a the "once over" before formal release. You can download it here.

Please don't just report problems. If you encounter any, please do report them in this thread. But, if you don't, please let me know that you tried.

Thanks in advance,
Don
 
Just to correct an error in yesterday's post and in the addendum to the User manual.

To use the edits in additional static models, start with the previously-saved static model .mdl file (not the updated aircraft .mdl file as noted.)

As well, I have discovered a bug in yesteday's release that causes the edits to the ambient and diffuse colors of certain materials to be overwritten with black and medium grey respectively.

Version 1.1.12b fixes this error and also replaces the Static Name text box with a combobox containing the names of the existing static models. It can be downloaded here.

Don
 
Since no one has yet responded, I'm going to take the optimistic view that the testing is going well. (But, I am curious as to why no one has discovered that the Static Position editor doesn't set the static c/g height properly:rolleyes:)

Anyway, that problem is now fixed, as is another one I discovered yesterday that may manifest itself in a variety of ways (all bad) if a texture file name includes the text string "TEXT". That too is now fixed.

As well, the user manual has been updated to cover the new editors.

Development Release 1.1.12(d) is available from the stuff4fs.com website. Navigate to the User Applications/SAMM page and click Development Release.

Don
 
Sorry Don,

I have to figure out so many things and also want to get done something decent and with that I have not been able yet to test your new SAMM versions.
You know that Samm comes in once you have the rest of the scenery done and I am not yet that far in many ways.
Once in a while I find time to try it out on some default scenery but have to force myself not to do it because I want to continue working on the more basic scenery elements.
I guess that you will only find some for testing that want to add a final touch to their sceneries by adding some static aircraft to the scenery.
I do update SAMM every time but have not the faintest anymore whether all functions well.
Sorry about that but do not feel like most of us are not interested.

Roby
 
Thanks Don , for the update . I will let you know , but I suspect there should be no problems .
 
I've been making extensive use of SAMM for the past week or so and have discovered a few issues. The most serious is that static models created by Version 13 or 14 cannot be reloaded by SAMM for further edits. This and a few other "irritants" have been fixed in development release 14a, available from the User Applications/SAMM page at http://stuff4fs.com.

Don
 
I have just finished reworking the model creation code portion of SAMM to increase processing efficiency, i.e., the static models should require less processing time and, hence their FPS "hit" should be reduced. The amount of improvement will depend on the number of animations involved; the more animations the greater the reduction.

I'd really appreciate it if a few of you would download and install the Development Release (SAMM 1114c.zip) from the SAMM page at http://stuff4fs.com. Please let me know of any issues that arise.

Thanks in advance,
Don
 
Thanks Gadgets, I need a couple of helicopters and and old airplane, and I thinks this is the time to try Samm, it's for my home airport :D:cool:
 
I made two new static airplanes, but when I try with another one I get a "not a fs8 or fs9 model.", and I can't continue with the program.
could be something to do with the fact the two firsts models were Fs9 models? and the third was fsx native. I tried unstalling and installing again, but the same.and it's weird because the box with "import from Fsx" is clearly checked.in anyway I can't get the program working again, regards
Just weird, I select an airplane which I suspeceted was for Fs9 before been updated for fsx, and effectvely I could load them. just weird.
Edit: well this could clarify the mistery "(SAMM will not convert aircraft models developed specifically for FSX or for FS2000 or earlier " as always just reading the tutorial.
 
Last edited:
Tejal, as the error message is telling you, SAMM will not convert FSX models.

The Get Aircraft From ... radio buttons simply tell SAMM which set of aircraft folders to display to you. Due to the dearth of FSX models, especially AI models, most people (and I suspect you also) have many FS8/9 models in their FSX SimObjects folders.

Don
 
That was what confused me, see the fsx button checked, anyway the only problem I had was that for that model only have the fsx version ,very difficult to find in Fs9, but I will find some model for the static object, greetings, anyway this is a clear example why people must read the manual of the programs.:o:D
 
Tejal Bernardo said:
...anyway this is a clear example why people must read the manual of the programs.:o:D
Click to expand...

...or at least keep up with the program's forum postings. This very issue with FSX models was the topic of a very long and involved thread just a week or so ago... :D
 
Hi Don,

Unless I did something wrong, there is something that does not work well in the material editor.
I tried to convert the E-2C Sunkings and it worked fine except for the fact that the cockpit windows were an opaque grey.
So I tried it again and found out (with the use of MCX that it was a color F313131 or something that I had to set to semi-transparent (no big deal in MCX but then I would have to make a seperate folder for the static aircraft with its own texture).
When I tried to do that with SAMM, it gave me an error and that was it. No way to turn the color semi-transparent.
So I thought, I do it with MCX, load the mdl again and the opaque cockpit is fixed.
Unfortunately SAMM then tells me it is not a SAMM converted model although it is.
Yours,

Roby
 
I'm plugging away hardly with gmax, sketchup, modeloconvertx, librarycreator, terrain resampling, and a little few things,... anyway it's clearly my fault.:whiteflag :D
 
So I thought, I do it with MCX, load the mdl again and the opaque cockpit is fixed.
Unfortunately SAMM then tells me it is not a SAMM converted model although it is.
Click to expand...
While its true you did initially convert the model with SAMM, the "secret code" must have been deleted by MCX. So the .mdl file has lost its identity as a SAMM-generated model.

When I tried to do that with SAMM, it gave me an error and that was it. No way to turn the color semi-transparent.
Click to expand...
You should be able to do this with SAMM. What was the error message?

Don
 
Morning,

Error = system: Argument out of range exception. Invalid argument= value of 152 is not valid for index.
Tried to set one color to semi-transparent. Depending on where exactly I put the slider, it gives me an error value (e.g.374) very different from the trnasparency value the slider indicates.
 
Last edited:
You must log in or register to reply here.
Back
Top