I don't know why it's doing that but while you figure it out you can try opening an existing jpg texture that works and then saving it as <new name> to see if that method helps.

Might be an encoding issue (RBG/CMYK/ 8bit/16bit Mode), maybe the extension is different (.jpeg) / uppercase (.JPG), ...

You can try asking in these discords which have a certain population of map-makers, courtesy of lolograde:

https://discord.gg/MaWZ9vp
https://discord.gg/R3bAaE
https://discord.me/defrag

There was something you need to disable when you save it but i forgot what.

I think it was making them RGB instead of CMYK.

I don't use it, but.

upload the texture which works and the one that does not.

You say textures are smaller, but are they the same dimensions and power of 2, if not make sure they are. i.e

256x256
512x512
1024x1024
2048x2048

etc

Don't have alternative dimensions.

Is the black texture alpha (transparent?) like a grating or something you can see through, if so jpeg will not work, try .tga which will support the extra 4bits.

Lastly, if you done all that, try opening the jpg inside mspaint (serious) and save it inside mspaint and then use that as the source file.

if you need to do a test, just use a texture you know works, opening it, put a red cross on it and save it as a different filename then apply it as a different texture. (don't change dimensions or texture format)

IF<<< that texture then fails to load, you know its an encoding thing, in which case, you find out which by simply saving multiple versions with different options, most of which will be on screen, if in photoshop switch between 8/18 bit RGB.

9

yeah. i have found the reason. textures appear black when they have some uneven offsets across the brush. when i have used 'fit' in surface inspector they started to work. anyway there was no such issue in q2. i could freely play with params in surface inspector.