I've been using blender to produce some simple building models for a map I'm making, and most of them have come through alright, however I've been having a bit of difficulty with a few of them. I've been using cube projection to uv them, as I'm only using one texture per model. Anyway, most of them have worked totally fine, but with a few others, if i uv using cube projection, the texture does not import into swbfviewer at all. The model is completely white. I've experimented, and found that using smart projection/standard unwrap export the textures just fine.

Any help getting the textures to export using cube projection would be greatly appreciated. I'm thinking it might have something to do with overlapping uv's on the uv editor, but I'm not a pro and as such I'm not sure.

All these props are meant to fit together like lego, and using cube projection the textures have all been to the right scale, however if i try manually uving the remaining two, it would be extremely difficult to get the scale right...

Could you post a screenshot of your UV layout? The projection you choose is just selecting the technique blender should use to unwrap them, the end product should be, technically, the same.

The type of projection you've used may have resulted in a weird layout, so that's why I'm asking for a screenshot.

Here's the image. The UV's are pretty cluttered and have a weird layout, so yeah.

IMageshack has disabled the directlink option on their images.

http://imageshack.us/f/98/94783931.jpg/

lucasfart wrote:Here's the image. The UV's are pretty cluttered and have a weird layout, so yeah.

IMageshack has disabled the directlink option on their images.

http://imageshack.us/f/98/94783931.jpg/

Oh hey look, the direct link.

When you upload a single image, it "disables" the direct link field so you can't copy paste it. However all you have to do is right click the image in the link you provided and then copy the image's link. A little hard to explain, grammar is not my best skill. I think you can can figure it out though.

Haha. Thanks for that. I immediately saw the greyed out direct link and gave up.

EDIT: I'm posting this now for the benefit of others, who may have a similar problem in the future. I managed to fix this problem, and while i still don't completely understand how it occured, i get most of it.

What happened, was that i used a texture off the internet with one of those weird letters/numbers mixes. I used this original name when i first uv'ed the models, and afterwards i decided to change the name to something more memorable. I then went back through and changed the textures for which the uv's had been applied. For some reason, which i still do not know, some of the textures refused to update properly, so when i exported, i mistakenly assumed that there had been a problem exporting due to the white texture on my model.

The way i found and fixed this was to open the .wrl in notepad ++ and found this section (The section with the colour tags around it: In order to fix the problem, i updated the name of the texture on both those lines to the current texture name and voila! Perfect textures....

lucasfart wrote:

Code: Select all

texture DEF Fortress_-_Wall ImageTexture {
			url "Fortress - Wall.png"

I'm pretty sure the first mention of the image is just a name that defines that section hence "DEF" preceeding it. I'll look into the VRML syntax later to confirm. The second line is the one with the actual image file name. You also shouldn't leave spaces in file names.

Fortress - Wall.png
should be
Fortress-Wall.png
or
FortressWall.png
or
Fortress_Wall.png


EDIT
The DEF syntax gives a name to a node
You can name any node
Names can be most any sequence of letters and numbers
Names must be unique within a file

Yeah i only thought of that after, but they worked fine ingame and in ZE, so i didn't worry about it too much...

So what you're saying is that i can put anything in the first line near DEF and that it's just a title of some sort?