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

Mapping THIS thing!

Messages
10,163
Country
us-arizona
Hey all,

Not asking for advice, just sharing my stress.

I am presently remapping the interior of my new baby. This part is the headliner of the cabin, bottom view looking up. What you dont see are tons of changing, multiple curved surfaces that hide on side profile views, etc, so multiple angles have to be photographed of the meshes many sides so that I can keep the leather 'bite' or visible grain 'visible' in FS9. I am breaking everything large into 2+ parts (half) to fit them on full size sheets to get maximum texture capacity so the leather grain is visible.

A daunting task. I am now considering cutting the fuselage into 2 texture sheets to add to the crispness of the fuselage graphics.


Why? Why not model in FSX purely and make these 2048 and 4096 sized textures!??#@

............because.. I really really like FS9. :D

A view of the leather, you can see the grain in it. I had hoped that 'tilling' various chips/swatches of the materials onto the interior would have sufficed, but the result was little to no interior shading, so I had to remap everything... the real way.. arrgh.
 
Last edited:
You probably not going to want to read this.

But in FSX you can use detail and bump map tiling on a texture. You only need a small texture to define the basic colour and shading and then you can tile on a detail and/or bump map to give it detail far beyond even 4096x4096 textures.

Very nice for making vinyl textures like this:

453012_Vinyl.jpg
 
Anthony...

That makes me drool. If only it could be done in FS9 with shading and highlights. Nice to know it works in FSX though. Thanks for the heads up.


Bill
 
Anthony...

That makes me drool. If only it could be done in FS9 with shading and highlights. Nice to know it works in FSX though. Thanks for the heads up.


Bill

I'm with you lionheart, we all love a challenge ... FSX makes it too easy =P
 
You should go FSX only. Why miss out on so many cool options and results.

Nice panel. Did you use 4096, wow. That's a big texture. I bet 2048 would look
just as good from the actual vc pilot position. But up close I am sure it's twice as good. I have never used 4096. Does it take more frames to double in size?

DG:cool:
 
You should go FSX only. Why miss out on so many cool options and results.


DG:cool:


FS9 is much easier to make planes for. I almost quit making FSX planes altogether. If only it were easier to make planes for FSX then FS9, and if only it ran as nicely as FS9. Cant have both though I guess. At least I can make planes for both.


Bill
 
I have to tell you. That headliner took me 2 full work days. I wanted the texture of leather to be visible, so I had to map it around edges. I used a new technique I have have stumbled onto, where I adjust the part in Gmax at an angle, snapshot, Alt/Tab to Photoshop, paste in the snapshot into the texture, cut around the edges, place in the area in the texture sheet, save, Alt/Tab to Gmax again, reload texture, click-add UVW Map, click Align Planar to screen, add UVW Unwrap, adjust/edit, Voila. Repeat via Polygon selections of zones, work around the edges, done.

On this one though, I kept having to get weird angles and screen captures, and was using a dual material texture, so I had to be careful with not moving things around, with selecting Polygons for that particular texture sheet, etc.

The price of 'as-close-to' perfection..
 
FSX is faster. I was like you for the last 7 years and was not sure i wanted to
convert over to FSX, since I am not sure on what it took to convert.

Over the last year I have found I create faster and pretty much the same method with more features where you want them. Most of my parts do not have bump or world reflections only the needed ones. So I find I lose no time there. But i gain time where I don't have to write down group names within group names. That part is tough. FSX manages of all your input for parts. Saves so much time. So in the long run I find i save 20% time and another 10% for having to open these groups to work again. That's the nightmare when you need to get back into a group that is located within another group.

Export saves another 40% to 80 % of time you waste.

Got to love it!:tapedshut
 
Last edited:
You do realize that the use of "Groups" is both completely unnecessary but contra-indicated I hope... :eek:
 
I usually i have many groups for visibility. So it depends on what your building.
If you need to hide pilots and bombs and many other objects, this saves me time. Like for example my skydiver has 2 heads, 4 arms, 4 legs and many more parts. So i had to spend 2 weeks in just opening these and closing them.
So If I had done these projects in FSX it would of been a breeze.

So even with out the groups time. The manger and export time is faster with security you don't mess it up.

I hate when a part is selected and you hit a shortcut to move to another part to work on and you actually renamed your part without noticing.
So in fs9 the part fails, in fsx it works no matter what name. An you can have duplicate names so you can merge parts and save time.
Plus you better hope you notice you broke a part....There no security there!

So I conclude that group work is a huge factor and can save you major time by using fsx.

DG;)
 
Last edited:
You roll the dice and take your chances. Should you ever encounter the dread "This project has an OBED Scaling applied. This should not be done." error, you won't be so sanquine about it any longer. I can only conclude that "someone" likes you very much... ;)

In any case, if you insist on using Groups, never do an "Ungroup." Use "Open Group" and "Close Group" instead.
 
I do not use groups.

I do use Hierarchies which one needs for linking parts to a door, gear, etc.

;)
 
I have never found Groups necessary. All visibility characteristics of a parent part are inherited by the children.
 
Like for example I usually i have many groups for visibility. So it depends on what your building.
If you need to hide pilots and bombs and many other objects, this saves me time.

Named Selection Sets. Sticky at top of this forum; hugely versatile and no OBED errors, not ever.
 
i have seen this message before: This project has an OBED Scaling applied

i forgot what causes it. I don't think i have seen this error since FS2004.
Can you get this in FSX game packs?

In any case, if you insist on using Groups, never do an "Ungroup." Use "Open Group" and "Close Group" instead.

What's the difference? Would that allow you to work on parts or just rename parts?

It's been a while since I used so many groups. Now I use a couple for organization.

DG
 
Open Group does most (but not all) that Ungroup does, and avoids the scaling error message during Compile that the Ungroup/Group procedure often causes.

Again, I see no advantage of grouping things over using a Hierarchy...

Hope this helps,
 
Open Group does most (but not all) that Ungroup does, and avoids the scaling error message during Compile that the Ungroup/Group procedure often causes.

Again, I see no advantage of grouping things over using a Hierarchy...

Hope this helps,

Oh, one could argue that shortening the list of parts might be a big advantage... :)

On the other hand, risking having all of the parts in your "Group" have rounding errors introduced into their scaling simply isn't worth the advantage, IMHO.
 
i have seen this message before: This project has an OBED Scaling applied

i forgot what causes it. I don't think i have seen this error since FS2004.
Can you get this in FSX game packs?

It has nothing to do with the export module at all. The error(s) occur within GMax because sometimes the "Ungrouping" process introduces a rounding error into the part's x,y,z scales.

In other words, instead of X:100.0 Y:100.0 Z:100.0 you might wind up with X:099.8 Y:099.9 Z:099.8, which of course is quite incorrect!
 
I had a chance to look at a very nice model, one by Milton, and I was to add a part to it. I had never seen nor heard of Groups until then, and I never did figure out how to maneuver in that model to get the work done. Quite embarrassing.

Sounds like it is a bit difficult to manage. I'll stick with raw Hierarchies.... :D
 
Bill, the only guaranteed "safe" way to work with any project that's already been "Group"ed is to use the Group/Open to gain access.

The individual objects will be "unpacked" into the partlist for selection and editing, just as if they had never been Grouped to begin with. It's kind of like viewing the contents of a zipped file. You aren't really unzipping the file at all...

To add a new object to the Group, simply Link to the "Groupname" that's still displayed in the partlist.

When done adding to, modifying, etc. you then select the "Groupname" in the partlist, then click on Group/Close to "save your changes."

In any case, it's inadvisable to "Ungroup," and for God's sake never even think about clicking on Group/Explode! :yikes:
 
Back
Top