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

why does this happen?

F747fly

Resource contributor
Messages
1,713
Country
netherlands
`So I did some booleean cuts, but my main model has gotten some weird texturing because of it:

Capture_zps132efce3.jpg


basic question: will it affect the model in FSX, and if so how do I fix it?
 
Yes it will... You can alter the model with Cut or Slice but Boolean is going to mung an existing mapping. We usually finish the shape of an object, then map it.
 
So is there a way to fix it without return ing to an earlier save?
 
No, go back to the earlier save but plan to map once the object is complete.
 
No, go back to the earlier save but plan to map once the object is complete.

Okay (luckily it's noth that muchwork since the last save) but should I then just use cut and slice instead of boolean?
 
Well... I use Boolean quite a bit where I need it: others use Cut and Slice because they hate Booleans or can't get on with them. Cut and Slice won't bork an existing mapping so some cut out doors etc after mapping and don't have to map the doors separately. I use Boolean to do these cuts and either map doors together with a fuselage or detach the resulting door polys after mapping the lot as one object.

There is always more than one way to swing a cat, and neither method is wrong. Now that I use Max there's also ProBoolean...
 
Well... I use Boolean quite a bit where I need it: others use Cut and Slice because they hate Booleans or can't get on with them. Cut and Slice won't bork an existing mapping so some cut out doors etc after mapping and don't have to map the doors separately. I use Boolean to do these cuts and either map doors together with a fuselage or detach the resulting door polys after mapping the lot as one object.

There is always more than one way to swing a cat, and neither method is wrong. Now that I use Max there's always ProBoolean...

okay, so how would this remapping go?

Because it seems like I can remove a sort of shadow object, and then the texture is normal again
 
Last edited:
No, either map (say) the fuselage and then cut or slice bits out of it; or do all the cuts, slices and Booleans and then map it. You can have the cuts etc all done without detaching the door, hatch or other objects from the fuselage: detach them once it's all mapped.

Now I have a curious finding to report: I took a finished, mapped and textured model and did a Boolean to cut a new access hatch in the wing's upper surface. It worked and didn't bother the mapping one little bit. The fuselage is mapped in two halves so I next tried a Boolean across the two halves. No problems. Wot? This needs explanation! :confused:
 
It might have to do with how the part is mapped prior to performing surgery on it?
 
I've noticed that Max is much better behaved when doing boolean cuts Tom. Just yesterday I had to make a new hole in a finished fuselage. I made a rectangular 'tool' and did a 'Pro Boolean' cut so it left just the imprint of the shape in the fuselage. I then detached the two polys created by the cut and cloned them to create the new vent top. I hid one part and re-attached the second to the fuselage and welded the vertices then extruded the polys downward to create the hole. I then used the new part to make the moving air vent.

Throughout all this process the mapping stayed true and the polys on the new part that came from the fuselage still retained their mapping locations. All I had to do then was map the newly created faces. For security I did drop an unwrap modifier on the fuselage to double check the mapping against the previously created texture map and everything aligned as it should.

It works well and surprised me a bit knowing just how bad boolean cuts in GMAX could go.
 
Then you'll share my bemusement Larry when I say that the above experiment was done in Gmax! :scratchch
 
I found it doesn't happen in move mode (but does happen in copy mode)
 
I'm usually using Reference in a Boolean with the operation Cut and Refine.
 
I'm usually using Reference in a Boolean with the operation Cut and Refine.

Well let it be said the I did the following:

- make a door shape spline, extrude, put through the fusalage.
- make a copy of the extruded spline.
- first use copy to get the intersection.
- uee copied spline to make the door opening (using move)
 
Last edited:
never EVER texture anything unless your external model has been fully completed! some exceptions are engines and landing gears! you can organize textures so much better once you have all of the components of the aircraft completed. you have learned a big lesson from this! focus on the model first then textures later!

And about boolean cuts, I stopped that bad practice a long time ago after some years with gmax. Boolean cuts are unpredictable nuclear bombs that in some ocassions may either crash your g/max or render your mesh a disaster.
 
I find booleans quite handy. :cool:

They are! What I meant to say was, you know how people abuse the zoom feature on their cameras and ruin a perfectly good video? Well, that's about it; too many Boolean operations on area where they aren't required drive everything pretty crazy.
 
As mentioned already, the ProBoolean in Max is a fantastic tool for us Boolean lovers. I would be absolutely lost without it!
 
Back
Top