Posts: 123
Joined: Mar 2015
Reputation:
3
Hi,
I have just updated my development branch to merge with master, and my fresh Kodi built will not display my skin. The skin is not listed in the skin selection dialog, even though it is present in ~/.kodi/addons as it has always been.
Is there a new way to declare a skin for kodi to see it ??
Posts: 123
Joined: Mar 2015
Reputation:
3
ok I had the <import> part figured out, but I was missing the "enabled" bit... thank you for the tip, it is loading now....
Posts: 378
Joined: Jan 2011
Reputation:
27
Textures are case sensitive. I remember having a similar issue with textures disappearing and it came down to case sensitivity.
Posts: 123
Joined: Mar 2015
Reputation:
3
Hi Bumpaneer,
I checked my xml files, and the case is correct. I believe it could be related with the file format, it seems the problem only concerns the files I have modified. I am still using some texture files I copied from Confluence and those seem fine...
Is there something like a maximum size, resolution, or whatever else the image files should respect?
Posts: 123
Joined: Mar 2015
Reputation:
3
2016-04-10, 11:38
ok, after doing all sort of tests, I just realized that if I *remove* the Texture.xbt file from my media directory, my textures are correctly loaded and displayed.
So I am a little confused, on one hand it is good because things are working back as usual for me, but on the other hand I really don't understand what is going on...
Posts: 15,263
Joined: Jan 2009
Reputation:
727
ronie
Team-Kodi Member
Posts: 15,263
i don't mind having a look at it, is your skin available for download?
Posts: 8,283
Joined: Jul 2014
Make sure to build your textures with the latest version of the texture packer, otherwise it won't work with Krypton
Posts: 123
Joined: Mar 2015
Reputation:
3
Hi,
I think it must be related with the TexturePacker I am using. The issue is that no version information is provided with --help.
Also it seems the method to build texture packer has changed in Krypton, so I am not too sure I am building it properly. What would be the right method to build the tool in the current master branch?