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

FS2004 Easy texture map modifying

Messages
5
Country
norway
Beeing a long time CFS2-FS8-FS9 skinner I now have come in the position where I need to do some minor modifcation/correction to a the texture mapping of a FS9 aircraft model. I have the Gmax source file, but have not yet used the GMax SW. (I have some experience with the FSDS V.3...) My question is.. what would be the alternatives for me? Is it possible to convert it to FSDS? Is there some other SW/tool for simpler mapping/texturing? Or do I have to do it the hard way and learn GMax mapping/texturing?
 
Morten, there is no way that I know to convert gmax source to FSDS.

Your best and easiest approach is to find a gmax knowledgeable someone who would be willing to make the changes for you.
 
Mapping in GMax isn't actually all that hard, but there's a process involved. I totally empathize with you, as I went from FSDS to GMax sometime in FS2002, and learning to map textures was the worst part for me. That's irrelevant to us, though, because you're only in the mood to modify, and we've got a tool for that - unwrap UVW.

Max (and its derivatives, like GMax) are very hierarchical. What I mean is that all the controls have classifications and classifications within classifications. It's very orderly, but the directions don't start with telling you how the order works! So, if you came in from FSDS, you're bound to be lost. The main control panel, on the right of the screen, has lots of little buttons on it that determine what set of controls you're going to use. There's a tab to create things, a tab to modify things that you've already created at the subobject level, a tab to play with pivots and whatnot, a tab to assign different kinds of motion controllers, a tab to tell the program how to display things, and a tab for tools that can be used to fix problems (or make your problems worse!). We're concerned, at the moment, with modifying objects at the subobject level. Click the "modify" button to open up the real meat and potatoes of how we edit objects - the modifier stack:

1.JPG


The object in our case is the quick and dirty imagineered DC-9-ish windows I threw together for another mini-tutorial. I've gone ahead and mapped an old photo of a warehouse dock to it and collapsed the modifier stack (I'll get to that later) so it appears as it'd probably appear if it were part of a finished model.

Remember what I said about Max being obsessed with hierarchy? The modifier stack is a literal stack of changes that apply cumulatively, with the most recent changes being at the top. Let's say I want to change the mapping on just the front part of the window frame. I'm going to first want to select the polygons I want to modify. We could simply click the little plus sign where it says "editable poly" and select the polygons there, but I want to add a modifier to perform this function, so you can get an idea how modifiers work. Since this is an editable poly object (which is a minor detail that isn't important to you, but has certain consequences if you start building models), I'm going to use a "poly select" modifier. Click the list, and select "poly select."

2.JPG


The only thing this modifier does is allow you to select the things you want to select, so that the next modifier only affects what you selected. If I click "polygon" and select a few polygons, then the next modifier will only modify those polygons. If a decide, instead, to click "vertex" and select some vertices, then the next modifier will only apply to those vertices. If I click "polygon" and select some polygons, then change my mind and click "vertex" and select some vertices, then the next modifier will only affect the vertices. If I add a modifier on top, and play with it, then decide to click on the poly select modifier, the changes will "undo" (because they haven't happened yet) until I select the next modifier again. Here's where things can go south if you don't know what you're doing: if I decide to click on the poly select modifier, then just click "polygon" - without doing anything else - then the polygons I originally selected will still be selected, and if I then click on the next modifier (whatever it may be), then the next modifier will instead modify those polygons!

It sounds confusing, but it's not. The last thing you did in the poly select modifier is going to be the thing the next modifier in the stack modifies. Deleting a modifier will cause the object to act as if the changes never happened, and this is really handy if you want to try something without doing permanent damage. Right clicking in the stack and selecting "collapse all," however, will make all of your changes permanent, so collapse a stack with extreme caution. Now that we have a basic understanding of how we stack modifiers on top of each other, let's do something with the polygons we selected. Click on the list of modifiers again, and select "unwrap UVW."

3.JPG



4.JPG


Now click "edit." Things will start to look a little more familiar to you now...

5.JPG


...because this reminds me a whole lot of the mapping editor in FSDS, except that instead of having fields to enter text, which changes the size of a box, which tells you how big the object is on the texture, you've got the object projected on the image, and you can modify the UV coordinates (the little vertices) to your heart's content (I think you could do this with individual faces in FSDS, but my memory fails me). The controls at the bottom right allow you to pan and zoom around the little 2D world, and you can work fairly precisely if you zoom in far enough. Let's click the "move" button and move these UVW points to another part of the image:

6.JPG


Now the middle frames are mapped to another part of the image. We can do more, though. Click and hold where it says "UV" and select "VW."

7.JPG


8.JPG


This demonstrates something very useful - textures are mapped in 3D space, and by selecting different "views" in which to edit them, you can treat them as though you were modifying 3D objects to create some strange mapping. This is a side view of the mapping coordinates. Notice how they look "squashed." I used a simple planar map, and Gmax doesn't allow us to modify the "depth" of the mapping coordinates when we do this. That's fine; it doesn't matter - but if you decided to rotate the UVW coordinates, things might get a bit out of proportion. For your purposes, though, you needn't bother. Just stay in UV view and move things as you see fit. I only told you about the ability to view things from other directions so you can get an idea of the real power behind some of these seemingly simple functions.

Note that many materials (the material is what you "make the object out of" - i.e. the skin you put on it, and includes the texture maps) have more than one map (image) specified for different effects. In the upper right corner, where it says "map #0" you can change the backdrop of the unwrap UVW window to whatever map you want to view - just in case the one you want to see projected isn't the one that shows up right away.
 
Last edited:
Morten, there is no way that I know to convert gmax source to FSDS.

Your best and easiest approach is to find a gmax knowledgeable someone who would be willing to make the changes for you.
There was a pair of dxf importer/exporter plugins for FSDS and GMax that allowed for things to go both ways, but I don't know where to find it these days (it's how I got my original 737, DC-9, and Learjet models from FSDS to GMax for mapping and animation). You'd lose all your animations, though.
 
Last edited:
Thanks guys! And ErickC, that's a great start!! Ok, it may be a steep learning curve as with all complex sw, but I think it could be very useful for me to be able to fix mapping issues.

Morten
 
Note that when the white vertices show up on the image background, you will need to drag the mouse across the vertices to turn them red. Then the move button (that 4 headed arrow button) will allow you to hold the mouse down on one of those vertices and move them to another part of the image. You can move specific vertices by choosing only those, but keep in mind this will usually cause stretching of the mapping. When I want to keep something like a window to the same proportions, I limit myself to selecting all vertices, then using only move, rotate, flip, and uniform scale operations.
 
Hello!

You already have a great way to begin (thanks to Erick). I will provide some links that will bring some help for you:

Gmax UVW Mapping Tutorial (Video Tutorial):
https://mega.nz/#!gMZWSDrQ
Key:
!T33k10PkmBp74JFT-hGX27_zrP2Dmq19msywnfpgTgk

UVW Mapping in Gmax – Full Tutorial and Resources
https://mega.nz/#!NUhiAK5Z
Key:
!4Cz7FEDLcYftUi_klPYYmrpA8ay8Kg_g3gSaS3po800

This material, has been "packed" by me and it was kindly provided by Milton Shupe, Hairyspin and several kind souls.
Good luck, take your time and begin to experiment with some basic shapes first.

All the best,
Sergio Kauffman.
 
Thanks Paul. Might check it out later, but now I'm already working my way into the GMAX mapping secrets thanks to Erick and Sergio's good beginners steps.
 
I have one more question: if I also want to export the AC mdl to FS2002/CFS2. Is that possible? What kind of additional installs do I need?
 
I don't know about CFS2, but FS2002 export will require the FS2002 gamepack. Be advised that XML animations will not work in FS2002 (but can be added to models exported with the FS2002 gamepack for use in FS2004, which is how we did it before the FS2004 gamepack came out!).
 
Nice thread....great tut on gmax uv editing, Erick. Morten, be careful....at some point the ui concepts in gmax will make a lot of sense, at which point you are officially addicted. I was also an fsds user, back in early days. Switched to gmax when it first came out. Never looked back. The modifier stack is Extremely powerful. I know people who make nearly every change on a different edit poly modifier.

By the way, many tools in max (whether gmax or 3dsmax) are maintained for backward compatibility, but have been replaced by better tools. You can convert a primitive to either "editmesh" or "edit poly". Edit poly is more modern and is recommended. Other tools in gmax really don't work properly, and you just have to learn that and avoid them. Mirror tool in the ribbon works differently than the mirror modifier in the stack. Use the modifier, and you see more predictable results. Polygons are naturally one sided, but you can make max show them as two sided.....just don't forget that they are really one sided.
 
I think "addiction" was actually the idea; the problem is there is no clear upgrade path. The thing with 3DS is it's well above and beyond its competitors in terms of price point. Case in point: the commercial version of Lightwave, which you might remember from such films as Avatar, Star Trek, and Skyfall is roughly $700 on sale and $1000 not-on-sale. Even if you only used it a year, you're still paying 44% of the cost of a year's subscription to 3DS - and the returns diminish more and more as time goes on - even if you spent $400 on upgrading Lightwave every year, you'd still come out at 45% of a three-year 3DS subscription. 3DS just ain't that much better, but I've gotten used to its workflow, so, for me, I'm uncertain about where to go as I re-evaluate how useful GMax will be in the future. I definitely can't stand Blender. AC3D looks attractive, but it errs on the side of simplicity, and its mapping functions seem a bit primitive. I don't know if any of the other moderately-priced CGI programs offer the ability to use smooth groups, either - I think it's a Max thing - because I'd rather use a different smooth group that introduce unnecessary polygons to create a lobe crease (which also introduces another side effect - dimensional inaccuracy for the sake of a visual effect).

It'd be nice if Autodesk came out with a mid-range Max product to cater to what appears to be a healthy market (after all, Lightwave ain't going anywhere). The day they introduced the subscription model was the day I said "bite me."
 
Last edited:
GMax really shows its age in Windows 10. There's a few threads with the known bugs around here. In the long run, there'll be no way around Blender.
 
First of all, Eric's point << The thing with 3DS is it's well above and beyond its competitors in terms of price point>> presumes you know who max is competing with. What this community does with max is like using 1% of its capability. The real competition for Max is the other professional tools used to create Video Games, movies, top end advertising and architectural visualization, and in that world Max is just one of many tools that inter-operate forming a suite of development and back end compositing and editing to create products that are vastly profitable.

And to Heretic's point, its not just Gmax....all versions of 3dsMax have had more problems with Windows 10 than with Windows 7. Its the primary reason I still run Windows 7. Autodesk had resolved many of the problems, but then Msoft pushed out an update to win 10 and broke features all over again. I don't know who's at fault, but the Autodesk-Microsoft connection is clearly flawed.
 
Oh, I definitely agree that in the FS world we use a tiny fraction of what Max is designed to do. You'll note my main comparison was to Lightwave, which is comparable to 3DS and sees use in similar applications. Lightwave is much more affordable, but it's different, and I'm pretty lazy. I'm sure the difference in price point stops mattering once you've invested $8000 in plugins (hey, it's just like the difference between ProTools and REAPER!). Any of the other tools I mentioned were solely me rambling on about my quest for an affordable Max substitute that works for what I actually use these tools for. I'm good at rambling; you'll discover that.

Windows 10 is just awful all around. Supposedly, it's a godsend for latency in music production, but I had so many issues just upgrading my DAW computer to Win 10 that I ended up staying with Win 7. I managed to get it running on another computer, and I didn't care for the forced updates one bit. I guess Microsoft thought that the way to beat Apple was to act like them? The computer's performance also seemed to suffer a fair bit when going from 8.1 to 10. I rolled the OS back. To be fair, it's an underpowered laptop I used solely for web browsing, but I was less than impressed.

Like I said - I'm good at rambling.
 
Last edited:
its all good....I just looked at lightwave for the first time. Looks targeted to specific needs. Appears to have fewer tools, but max would also have fewer tools if it had been developed more recently. Looks like Octane is the lightwave renderer....their website describes Octane as a physically based renderer....At least in max-speak physical renderer (for example ART in the newest max 2017) means that effects like ambient occlusion, gradient maps, or non-shadow casting objects are not supported. Can't swear to Octane in those terms.

The interface reminds me a bit of Rhino. Not my preference, but its what you are used to.

Cheers
 
And to Heretic's point, its not just Gmax....all versions of 3dsMax have had more problems with Windows 10 than with Windows 7. Its the primary reason I still run Windows 7. Autodesk had resolved many of the problems, but then Msoft pushed out an update to win 10 and broke features all over again. I don't know who's at fault, but the Autodesk-Microsoft connection is clearly flawed.

Negative on my part. Max 2015 and Windows 10 works perfectly together. Max 9, however...



Windows 10 is just awful all around. Supposedly, it's a godsend for latency in music production, but I had so many issues just upgrading my DAW computer to Win 10 that I ended up staying with Win 7. I managed to get it running on another computer, and I didn't care for the forced updates one bit. I guess Microsoft thought that the way to beat Apple was to act like them? The computer's performance also seemed to suffer a fair bit when going from 8.1 to 10. I rolled the OS back. To be fair, it's an underpowered laptop I used solely for web browsing, but I was less than impressed.

Windows 10 runs on my dektop, on both of my laptops, my phone and my parents' computers and it has never given us more than easy to solve trouble (save for some program incompatibility). Once you get it out of NSA-mode and replace the dreadful Windows Defender, it runs smoothly. On my 2008ish Thinkpad, it runs even better than Windows 7 ever did. It's all a matter of starting with a clean slate, as you did with all Windows releases thus far.
 
Negative on my part. Max 2015 and Windows 10 works perfectly together. Max 9, however...

Interesting, like any conclusion its difficult to collect complete info. Thanks for this. There are folks that find bugs in parts of max that I rarely use, that may also be a factor. "works perfectly" may be more accurately stated as "all uses of max I've attempted have worked perfectly".

Still, to use an "advanced" os that forces its updates on me whether or not my applications are prepared for that update is unacceptable.
 
Back
Top