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

GMax blows!

I have just downloaded FSDS, .... first theres the gamepack install.

Remember - FSDS 3 uses the relevant gamepack(s) (for FS9 and FS-X).

Gamepack (i.e., xtomdl/makemdl) issues are going to still be there.

now, dealing with attachpoints is really fun!! Think of the '56 Ford with the clutch pedal missing .. It can be done...
 
Last edited:
@Bjorn ... I didn't think the triangulation altered (smoothing is Lost however)
If each part is given a different material (eg the door) before export from Gmax .. they will be exported with discrete part names AA_LOD_100 AB_LOD_100 etc

Whilst the animations etc are stuffed you should at least be able to select each bit separately.

Never mind. I'll simply refrain from editing meshes in a way that greatly disrupts mapping in GMax and done.

It may be quicker just to remake the model completely of course :D

Redo nearly a whole airplane...

...

Nay.



P.S: German "Umlaute" can generally be written as "ae", "oe" or "ue" (ä,ö,ü) in an internationally compatible fashion. Or you find out their appropriate ASCII-coding to get them directly. :teacher:



Really? For all of my scenery purposes, I LOVE GMax! :D

Scenery =/= aircraft
 
Björn, did you chnage your avatar, wasn't this a speaking Goldfish or something? Can I have it if you are done with it?

And ... do you know the Lithunwrap route to texture mapping? You can take any part, collapsed stack or not, and produce a mesh map of the part's surfaces. Then all you have to do is use the UnwrapUVW modifier, pick the mesh map (not the real texture) in the Unwrap Editor , place your part's geometry exactly on that map and ... done. No?
 
Björn, did you chnage your avatar, wasn't this a speaking Goldfish or something? Can I have it if you are done with it?

Hm, I was just looking for it and it seems Klaus somehow went down the drain (no pun intended) after I've uploaded it him the web.

Sorry! :(

And ... do you know the Lithunwrap route to texture mapping? You can take any part, collapsed stack or not, and produce a mesh map of the part's surfaces. Then all you have to do is use the UnwrapUVW modifier, pick the mesh map (not the real texture) in the Unwrap Editor , place your part's geometry exactly on that map and ... done. No?

I had already checked out LU, but it wasn't exactly the remedy I was looking for. Unless of course I've overread that it supports normal mapping. :D

Furthermore, LU can only read .x files and the Pandasoft plugin has steadily
refused to cooperate with my GMax and FSX gamepack installation, no matter the plugin location and version.
 
LU accesses md3 files, which you can export-selected from within gmax via the Tempest plugin that gives you LU in the first place. So if you have your old FS9 fuse in gmax, you can save it as a .md3 model, open that in LU, save the map that LU generates and then use that to scale and position your mods from within UnwrapUVW. You may have tried all that ... but it is an excellent way of coming to grips with other people's texture maps.
 
Last edited by a moderator:
Noted for next time (should there be one).

Just tried the .md3 -> Lithunwrap way.
Doesn't make things more effective. I get the feeling that LU's unwrapper is even more feature deprived than GMax'.


Oh well, I just won't bother with unwrapping of complex meshes in Gmax anymore. If someone doesn't like the mapping or mesh, he/she is welcome to improve it him/herself with the help of the source files and done.

It surely could do with a few more polys and better triangulation around the fresh door cutouts and whatnot, but considering the source file is over seven years old it looks just fine to me.
 
... I get the feeling that LU's unwrapper is even more feature deprived than GMax'...

We don't use LithUnwrap to unwrap, we just use it to generate accurate bitmaps of templates for the already-mapped or unwrapped mesh. Like rendering a mapping to a texture directly in Max.
 
If you need an anger management problem, get 3DS Max, use it for a few years and abruptly switch to Gmax. *Cough*

Also works if you doubt whether 3DS Max was worth it!



That looks to be the old Greg Pepper gmax source?

It is. I've done some stuff to the model and made it FSX native and Tom Gibson gets the latest source files back afterwards to roll the "improved" model back to FS9 standard.



We don't use LithUnwrap to unwrap, we just use it to generate accurate bitmaps of templates for the already-mapped or unwrapped mesh. Like rendering a mapping to a texture directly in Max.

Okay. So the main stuff is still done with the absolutely useless unwrapper.
 
Just what were you trying to accomplish with the Unwrapper?

Simply remapping a fuselage.

In 3Ds Max, I can first use "render to texture" to create renderings of the maps and then, after modification, remap both halves of the fuselage at the same time on a high res, true to color bitmap with lots to get optimal, accurate results.
In Gmax not so much. The bitmap is low-res, there isn't a "render to texture" function in the first place (okay, there's LithUnwrap as a substitute) and lots of the tools as simple as "rotate by 90°" and "freeform scale" are missing.

And why does Gmax intend on creating a new vertex everytime I miss an exisiting one during poly creation?
And why do I have to reassign all my beloved 3DS Max keyboard shortcuts?
And, worst of them all, why do I have to quit Gmax when I want to change one parameter in the Modeldef.xml?


Anyways, I've just finished up the Convair project. Maybe I'll be in the mood to build a new 500k-poly-every-rivet-modeled-and-textured-with-4096px²-maps 580 from scratch for Flight! 2020...in 3DS Max or whatever fancy up to date tool the SDK will support. ;)


Converting aircraft in GMax? Yes, please.
Editing and mapping more complex geometry in GMax? No, thanks.
 
And why does Gmax intend on creating a new vertex everytime I miss an exisiting one during poly creation?

And why do I have to reassign all my beloved 3DS Max keyboard shortcuts?

And, worst of them all, why do I have to quit Gmax when I want to change one parameter in the Modeldef.xml?

1. I'm not certain what you are asking about...

2. You only need to do that once. Since I rarely use the keyboard (which is one reason why I throughly dislike FSDS), I don't let that bother me. I work faster with the mouse... ;)

3. That's an excellent question, since the FSXAnimation.ms scripts are identical...

...for that matter, why the heck don't the things from modeldef.xml get sorted alphabetically in the GMax tools? Once again, the scripts are identical. :rolleyes:
 
For an accurate rotate, use Angle Snap.

In Customize User Interface, load an alternative keyboard map from gmax/ui - there's DefaultUI, MaxKeys and MaxKeysClassic - but first save the one you're using if you've already made some reassignments.

The UVW editor window only displays textures up to 1024x1024 afaik, but with LithUnwrap you can produce higher resolution textures easily - I use 2048x2048 routinely.

HTH
 
Tom, does the "Angle Snap" function for "Angle Rotation" work in the UV Editor? I know that the Undo and Redo functions work, but honestly I've never thought to try enabling "Angle Snap"...

I've also used 2048^2 textures in the UV Editor of GMax with no problems.
 
Last edited:
1. I'm not certain what you are asking about...

In Max, whenever you miss clicking an edge vertex when creating a poly, you'll have to start over.
In Gmax, you'l get an extra edge vertex somewhere in the scene. It's as if "create poly" and "create vertex" are unified into one single function.

2. You only need to do that once. Since I rarely use the keyboard (which is one reason why I throughly dislike FSDS), I don't let that bother me. I work faster with the mouse... ;)

I find using "1" to "5" for switching from vertex to "element" submodes or "Q" and "W" for the translation or rotational tools much better than always having to click their buttons.

...for that matter, why the heck don't the things from modeldef.xml get sorted alphabetically in the GMax tools? Once again, the scripts are identical. :rolleyes:

They do for me...I think.



In Customize User Interface, load an alternative keyboard map from gmax/ui - there's DefaultUI, MaxKeys and MaxKeysClassic - but first save the one you're using if you've already made some reassignments.

Now that's a better basis to start from than the default keys.

The UVW editor window only displays textures up to 1024x1024 afaik, but with LithUnwrap you can produce higher resolution textures easily - I use 2048x2048 routinely.

What about the colors?

My Gmax has a slight problem with red and green...
 
Tom, does the "Angle Snap" function for "Angle Rotation" work in the UV Editor? I know that the Undo and Redo functions work, but honestly I've never thought to try enabling "Angle Snap"...

I've also used 2048^2 textures in the UV Editor of GMax with no problems.

Yes, Angle Snap works just fine. As far as texture size goes, I also use 2048^2 textures in the UV editor, I just thought I'd read somewhere that gmax only displays them to a maximum 1024^2 resolution. It's not really a problem.

Heretic: What about the colors?

My Gmax has a slight problem with red and green...

You can change the colours of lines and selected vertices if that's what you mean via Unwrap Options button on the top toolbar
 
Last edited:
Yes, Angle Snap works just fine. As far as texture size goes, I also use 2048^2 textures in the UV editor, I just thought I'd read somewhere that gmax only displays them to a maximum 1024^2 resolution. It's not really a problem.

Thanks for that! I'll have to remember that, because it's always been a PITA not knowing about that. Max of course has it's own set of Angle Snap icons, which is probably why I never thought to look in the GMax Help file(s).

The one major advantage to Max's UV Editor is that selected vertices in the UV Editor also show up in the active Viewport! Nice! :cool:
 
You can change the colours of lines and selected vertices if that's what you mean via Unwrap Options button on the top toolbar

No, I mean the colors on the bitmaps.



The one major advantage to Max's UV Editor is that selected vertices in the UV Editor also show up in the active Viewport! Nice! :cool:

That's another thing I'm missing, lol.


Anyways, the project is out of the hangar. Time to do something with less potential for fits of rage. :D
 
No, I mean the colors on the bitmaps.

Ah, the colours supplied by LithunWrap are what you get... unless like some you're mapping one object at a time and adding the bitmap as a layer to a file in Gimp/PSP/Paint.NET/Photoshop. Then each and every object is coloured blue!

But you can edit bitmaps to change colours, surely? Something I ought to learn...
 
Back
Top