Here are two different objects with the same texture. The one on the left is a .3ds format object, the other is a vue cube. The texture is something I'm working on right now and is a "mixed material." Why is the .3ds object not acting like the vue box?

I think the 3ds object has to be mapped in the software where it was created. Then it imports fine in Vue. But there is another way, maybe. If your 3ds object is in only 1 piece, you can try to split it first and to map it in Vue piece by piece. That's a little my 2 cents, because I have no software that can export 3ds files. Somebody else can explain it better for sure. Guitta

thanks, the object is one piece. I was just trying to see what the texture would look like on a rounded corner. I've tried .3ds files before and hadn't had this problem. The .3ds file probably got corrupted when I was writing it. Who knows.

First is just give the 3ds object a texture like the ground so you can see the shape of the mesh. If that works well then remember the cube is solid and the 3ds texture is not. This is why I love procedreal textures. Sometimes you get the weirdest results. You just fight and fight with them. When it's like that I use pictures mixed with materials. Your using math to make a cage now your applying that texture to not a solid cube so the math is different. Make sence? You get weird results.You can texture it no problem in Vue cause I do it all the time. You don't have to map it in a different program although that gives way more control.

Okay, figured out what I was doing wrong. The distribution of the 2 textures mapping setting should have been set to faces. For some reason it mattered to a .3ds object.