I should have remembered this earlier. You can't prevent Blender from adding the numerical suffixes. Each object and material must have a unique name, otherwise the suffixes will be appended when encountering an object or material with an identical name. Sure, you can copy materials from one object or a select number of polys to other geometry, but the names must remain unique. It's like to trying to have two files with the same name in the same directory. If that was allowed to happen, neither Blender or you would know what was what.

Blender ships with an addon called Material Utilities. It is not enabled by default, so you just need to go to preferences and turn it on. Shift Q brings up its menu and the documentation link is available via preferences. There is a function called Copy Materials to Selected that might be what you're looking for. I just gave it a quick test and it seems to work OK.

And yes, Blender appending numbers to everything is a royal pain in the proverbial.

I run Linux Mint 21.1. I have DS 4.21 running flawlessly under Bottles, as I'm currently developing a store product for DS.

I can highly recommend Bottles, rather than going the manual install route for WINE. It's a pain and can can cause all sorts of problems, at least in my experience.

I'm just being provocative. Eh.... The new versions of Blender are seriously good. I'm out.

One or two versions. No, not one or two versions, but multiple versions. Ah well, live happily in the past.

Harsh and inaccurate? Not really. Blender evolves and improves at an astonishing rate. 2.79 was a major improvement over previous versions but it it has had its day. Time to move on and enjoy all the new stuff that the current iterations are offering.

2.79 is defunct. Really, the 2.80, 2.90 versions are so much better, including the UI. These newer versions incorporate so many advances that it's impossible to overstate how far Blender has come in the last 2 years or so. And that's without mentioning add-ons like Boxcutter, HardOps, Fluent, Meshmachine et al that all keep pushing the envelope of what we can do in 3D. It really is worth diving into the latest versions. The improvements are vast, to say the least.

Big difference to a node based workflow. I'm confident you misunderstood my post. Never mind then.

I think you guys may have the wrong end of the stick with regards to procedural modelling. My understanding of how Houdini works (I may be wrong) is this. You create a cylinder with 32 sides. You save the file and come back tomorrow and realise that 32 sides is way too low. When you created that cylinder, a node was automatically created for you. You now want your cylinder to have 64 sides. You go to that node and up the count to 64. Now that is powerful modelling. Non-destructive and totally editable until you freeze the mesh.

Sure, the boolean workflow is a big part of HOps, but it doesn't rely on booleans being used. It helps out with so much more. That was what I was getting at.

They can be a bit overwhelming to start with. I don't find Jerry's videos that helpful, unfortunately. Watched a lot of videos on YouTube to get the hang of things. In the end though, they are pretty great tools.

Hard Ops and Boxcutter, TexTools (yes it works with 2.80+), Drop It, Gaffer, Material Utilities. I am really starting to get to grips with Hard Ops and am loving it. It saves an enormous amount of time and has some pretty sophisticated tools. The Step operation is amazing. SilentWinter, Hard Ops does not rely on boolean operations at all. It is probably best described as a tool that packages a whole load of steps into one or two mouse clicks and adds some extra goodies on top. As a small example, in vanilla Blender you need to right click an object, shade smooth, then turn on auto smooth and set the angle accordingly. In Hops, you hit Q, then select the Ssharp operator and it's all done for you. Use Csharp instead and a bevel modifier gets added as well. The time saving is enormous.

I'm a bit late late to the party on this one, but yes, definitely looks like ngons, which Poser and Daz Studio refuse to render properly. Any object intended for use in Poser or DS absolutely must be made up of quads and/or triangles. Also, Blender's .obj export function is basically borked. I had serious issues recently with getting a Blender mesh to render correctly in DS. It was all triangles too. I imported the Blender exported object into Wings and exported it straight out again. It then worked fine in DS.

Quote - First, just calm down.

Well well well.. I had completely forgotten about this thread. Unfortunately I re-discovered it while searching for something else, and now, even after this length of time, feel I must reply to your rubbish. I won the argument, mr know-it-all, and that's what drives you nuts. I notice that you mention ego without even a hint of irony. Hilarious. It's interesting that you had to practically write a book to justify yourself to me. Hey, if you need to, you need to. After you started the insults and name calling I lost interest though, so most of your billious drivel went unread.

You yell at people who disagree with you, tell them to shut up, and then if they still keep disagreeing with you, you start on the insults. You're a bully, pure and simple, and the so-called moderators on this site should have shut you down a long time ago. For some reason, no-one's ever had the guts to call you out on it. I really do pity people who have to deal with you on a daily basis. It must be intolerable for them. I'm sure there will be a reply, because you always have to have the last word, and you'll probably spew all sorts of shit, but I've said what I have to and that's that. I'll make sure I never read anything of yours ever again so don't bother yourself, small man. Yeah, I threw that in their to demean you. You really are a nasty, worthless little unit.

Are you sure the landing gear bays are not attached to the rest of the mesh? Try selecting just the polygons in the landing gear bays, cutting them and then pasting them back in, and then see what happens.