Does anyone know how to solve these?
-
-
RE: Couple of Things
A few things you might try, Damon
- Check that the 'transparent' parts of the textures are pure blue/black: sometimes resizing a texture or reducing its colour depth can change these colours slightly.
- Check that the dimensions of the textures are all powers of 2 (32, 64, 128, 256...).
- Check that you have specified the transparent colour properly in the object code. Remember that if you are using .X format, the transparent colour must be pure black.
Cheers
Simon -
RE: Couple of Things
Resized it and it worked. Thanks!!!Comment
-
RE: Couple of Things
This I suspect has been raised before, but I've been away from BVE for about 2 months. So I'm rather rusty!
I can't really see any advantage in using the .x file over my the .csv file? What more things can the .x file support? I'm only asking because, I code in .b3d (Yes I can't work out .csv, so I use .b3d) and then convert the .b3d to .csv, but I might just convert to .x if I can see any point.
NickComment
-
RE: Couple of Things
>This I suspect has been raised before, but I've been away
>from BVE for about 2 months. So I'm rather rusty!
>
>I can't really see any advantage in using the .x file over my
>the .csv file? What more things can the .x file support? I'm
>only asking because, I code in .b3d (Yes I can't work out
>.csv, so I use .b3d) and then convert the .b3d to .csv, but I
>might just convert to .x if I can see any point.
>
>Nick
Hi,
.x files have a few properties that .b3d and .csv don't have. For instance: glosiness (if you want shiny surface), self-iluminating (in the dark textures glow), and I think BVE4 is optimised for .x files because it seems to load them way faster than .csv ones.
Bogdan
Comment
Comment