|
|
Post by celinde on Feb 3, 2019 16:16:24 GMT -5
|
|
|
|
Post by Mathcope on Feb 3, 2019 16:28:44 GMT -5
Share your files.
|
|
|
|
Post by celinde on Feb 3, 2019 16:36:13 GMT -5
|
|
|
|
Post by Mathcope on Feb 3, 2019 16:54:28 GMT -5
Thank you, but we also need the textures files you are importing, otherwise we have nothing to compare. You say you tried with both .png and .dds and had the same result? I usually try both to see which one is better, it depends on the project. What is the texture you are seeing in blender?
|
|
|
|
Post by celinde on Feb 3, 2019 17:10:26 GMT -5
|
|
|
|
Post by freeasabird on Feb 3, 2019 18:06:03 GMT -5
I have had this problem as well, in fact it was so bad I had to totally remake the make up counters (cream) 5 times before I thought the texture was acceptable. I even showed a friend that was here as it was happening because I thought I was doing something wrong every time. But he saw it too. The textures degraded on import whether they were .png or .dds files to such a degree they were unusable. I still dont know why eventually it stopped.
|
|
|
|
Post by minimonster on Feb 4, 2019 17:48:41 GMT -5
I would like to jump into this thread and add a 'Me Too' to it. Never *used to* have much of a problem with the importing of textures. Now, while I have switched over to DXT5 for ALL of my alpha-related needs (not just for CAS), there are still a few issues with importing textures (specifically with the spec & spec mask on CAS items adding 'extra' squares around edges of the texture).
I have long wondered (from a programmatic point of view), whether the native texture format from official files is compressed as .dds, or if it is 'translated' by the import/export process. Same with the ability to use .png (which I never have done, anyways). So, my question towards the devs would be: Is there a 'translation' that happens with the texture process in & out of Studio, or is it a byte-by-byte import?
Thank You in advance for any response! Cheers!
|
|
|
|
Post by celinde on Feb 9, 2019 5:29:39 GMT -5
It sucks because I think with the latest S4S update, the problem got worse but not a lot of people notice it, so now unless we use the HQ mod, the textures look really bad in S4S.. it really sucks!
|
|
|
|
Post by celinde on Feb 9, 2019 5:55:55 GMT -5
Thank you, but we also need the textures files you are importing, otherwise we have nothing to compare. You say you tried with both .png and .dds and had the same result? I usually try both to see which one is better, it depends on the project. What is the texture you are seeing in blender? Can you offer any solutions? |
|
|
|
Post by Feyona on Feb 9, 2019 8:17:12 GMT -5
It sucks because I think with the latest S4S update, the problem got worse but not a lot of people notice it, so now unless we use the HQ mod, the textures look really bad in S4S.. it really sucks! Nothing changed in Studio's code with the latest update. When you work with texture you see a different picture from how it is actually compressed if you save in .dds. DDS is a highly compressed format. Try re-opening your picture saved in .dds, and you will be surprised. When you import in .png Studio converts it into .dds using own algorithm. Sometimes it gives better result than .dds saved in photoshop, sometimes photoshop .dds gives better result. Your texture is ultra small, I measured and it is roughly only 193 by 50 pixels which is even less space than EA uses on the map for EA's clothes. Doesn't matter than you increased the size by 2. Game still sees it as 1024x2048 texture unless you turn HQ settings on. This quality is due to your texture size and the way you mapped the mesh. Move uv into a bigger place, increase the size of this white pattern. Studio did not decrease quality of your picture.  |
|
