Incompatibility?

[RAPHAEL]

Is there limits to the image sizes or something with new textures?

So I tried my textures (the ones I've been tinkering with making which worked fine on a new world in 0.4) on a world that was created in 0.3.1 and all the new graphics aren't added due to the following errors:

4:26:18: INFO[main]: TextureSource::buildMainAtlas(): Not adding "default_brick.png" because image is large
04:26:18: INFO[main]: TextureSource::buildMainAtlas(): Not adding "default_furnace_front.png" because image is large
04:26:18: INFO[main]: TextureSource::buildMainAtlas(): Not adding "default_furnace_side.png" because image is large
04:26:18: INFO[main]: TextureSource::buildMainAtlas(): Not adding "default_grass.png" because image is large
04:26:18: INFO[main]: TextureSource::buildMainAtlas(): Not adding "default_junglegrass.png" because image is large
04:26:18: INFO[main]: TextureSource::buildMainAtlas(): Not adding "default_leaves.png" because image is large
04:26:18: INFO[main]: TextureSource::buildMainAtlas(): Not adding "default_stone.png" because image is large
04:26:18: INFO[main]: TextureSource::buildMainAtlas(): Not adding "default_stone.png^gemstones_emerald_stone.png" because image is large
04:26:18: INFO[main]: TextureSource::buildMainAtlas(): Not adding "default_stone.png^gemstones_ruby_stone.png" because image is large
04:26:18: INFO[main]: TextureSource::buildMainAtlas(): Not adding "default_stone.png^gemstones_sapphire_stone.png" because image is large
04:26:18: INFO[main]: TextureSource::buildMainAtlas(): Not adding "default_stone.png^mineral_coal.png" because image is large
04:26:18: INFO[main]: TextureSource::buildMainAtlas(): Not adding "default_stone.png^mineral_iron.png" because image is large
04:26:18: INFO[main]: TextureSource::buildMainAtlas(): Not adding "default_tree.png" because image is large
04:26:18: INFO[main]: TextureSource::buildMainAtlas(): Not adding "default_tree_top.png" because image is large
04:26:18: INFO[main]: TextureSource::buildMainAtlas(): Not adding "default_wood.png" because image is large

I presume this is maybe some incompatibility created by copying over an older world to the newer version but not sure.

Each of those images average about 10-30KB. The gemstones are much much smaller. Like less than a KB generally.

[dannydark]

The images should still load, they just are not being added to the texture atlas to be loaded faster (I think).

The reason it doesn't get added to the atlas is because the image dimensions are too large (not file size) so basically if your textures where all something like 64 x 64 then chances are they wouldn't fit onto the atlas, as the atlas itself is of a certain size (i think 1024px but not sure).

If you changed your textures dimensions to something smaller i.e. 16 x 16 then it should add them to the atlas no problem

[RAPHAEL]

I forgot to mention that the furnace graphic (unsure about the other graphics listed) wouldn't load in the game. They were replaced by the unknown block graphic. When I looked at the debug the only thing i could tell was the above and a bunch of these:
04:26:13: ERROR[main]: draw_hotbar(): mainlist == NULL

[dannydark]

hmmmm....I've noticed that the error "ERROR[main]: draw_hotbar(): mainlist == NULL" floods the console even using the default textures but with a few mods that contain more textures installed.

When I get this error it also connects me to the game but with a black screen and I have to wait for the above error to finish looping before it shows me anything in game.

[RAPHAEL]

hmmmm....I've noticed that the error "ERROR[main]: draw_hotbar(): mainlist == NULL" floods the console even using the default textures but with a few mods that contain more textures installed.

When I get this error it also connects me to the game but with a black screen and I have to wait for the above error to finish looping before it shows me anything in game.

The way I know it wont load is by seeing the "unknown block" in place of custom textures. Also even waiting over 10 minutes nothing changes. Hence why I felt I should try to see if this is a known issue or if I'm just not doing something right.

[dannydark]

@Raphael Its definitely not something your doing wrong as this happens to a few other people also, I do plan to look into the issue further just haven't found the time out from work yet.

I think the only difference between what you have and what me and a few other people have is that your textures get replaced with the unknown block texture, for me it just generates a dummy image or well a solid colour.

It seems to be more of a problem with single player rather than multiplayer as I don't have the texture not loading issue on my dedicated server, only the "ERROR[main]: draw_hotbar(): mainlist == NULL" spam. which I believe is caused by the textures not being fully loaded when I join the game, Strange thing is though I would expect this to happen when connecting to a remote server on say a slow connection but to have it also exist on single player is strange.

I will try and make time to look into this issue and hopefully find a fix for it soon ^_^

EDIT: Also just out of interest are you using a windows build or linux? I've haven't yet made a build for my Linux platform to test only my Windows system.