Yep this is the result I'm getting on that clock I posted.
(read more to find out why!!)

I thought there was nothing wrong with the texture or the model because it looks perfect in T3D Edit. I've also installed the Quesa at the root library as well as the local user library just in case, and restarted and still crud.

By the way the texture in that model is 72dpi and only 124x124...

AHA THAT IS THE PROBLEM!!!!

IT MUST BE A POWER OF 2 (how annoying)

32x32
64x64
128x128
256x256

Man that was frustrating. Hope this helps everyone who is having texture problems.

Please note the textures in the T3D download may not be power of 2, sorry for any inconvienance.

Has anyone used the T3D app yet? I'd like to see some screen shots of your models in a composition instead of all alone in a Meshwork preview.

I'm surprise noone has commented on that sexy lo-res model in the download.

Hey you, stop looking at my wife that way!

If you are like me and use Command Control Shift 4 to make screen shots you may get a shock when the T3D view moves when holding the control key.
To screenshot without this happening, click into finder,
the 3D view stays available, then do your screenshot.

Quote:Original Post to Meshwork List by Jeff Quan The best optimization I know of is use as few materials as you can possibly get away with (read: lots of pinned mapping). As far as I know (Joe can correct me on this) the graphics file format is irrelevant, since 3DMF stores the textures uncompressed with the mesh. If the above statement is true, using jpegs could hurt your textures -- all jpeg compression artifacts would be visible on the models.