- May 3, 2017
- 655
- 1,817
1 - Yes I'm using AMD GPU. I do not have another system to hash textures for nvdia so rip.testing your stuff for problems/anomalyes......
so let's start for the top problem.....are you with ATI GPU right?
this mean than your release does no work here with NVIDIA.....not with the plugin you used at least for dump......
can you try yourself with another pc just for convalidate this points we found and still support....???
you will beliave wen you will see that!!!! or we just have to restart fom developing from point 0 lol.......
i have to rehash everything for me to get the correct md5 number compatible to uncen and such...
this was days ago......we fixed it in latest latest plugin with a new "argoritm" (don't ask that i am not the coder here)
than made possible having generate small texture with both same hash for both GPU....
this caused than uncen worked for ALL the position in first page but failed on 2nd because on that they are using big 2048x2048 than need a "different system to calculate"
we are still testing/fixing/trying here and here.......
so i can rehash mine but you need to get the newest plugin from him.....badly....
so at least we have only to rehash half the texture on your next release.........and not almost all lol!!!!
strangely icons work without problem...... uncen nope not even one.......
waiting for your response first or your gonna kill if i show you how much of others stuffs i have found..........(lol ???joke???)
ps:
the release on top is mine a least for now..... it was made to the intention of make possible a very compatible & safe enviroment to cut off any anomalyes/variant/result/errors during the developing of the plugin.....
can you please check the md5 calculation with your ATI gpu if are different from kumarinspecial and your actual version ????
also your files if work in both version???? using same plugin version don't forget!!!!!!
if not
can you please compare asset data lenght & data from kumarin special? bit to bit
this because for make sure what is doing here.........
take care see you next report!!!!
ps2: the new texture rocks!!!
2 - I noticed when rehashing textures that some texture were still sharing the same hash from previous version.
3 - I'll check his dedicated topic regarding the plugin later and see if he uploaded the newest version there.
4 - Ok, I'll try to compare the hashes later/tomorrow.
EDIT-1: QUICK COMPARE 1
Yep using Texture replacer 1.0.0.1 give out different hashes
Legend:
Translated = Using old hashes from version 1.0 (I guess?)
Untranslated = New hashes from v1.0.0.1
So if you update the old plugin with new one texture will stop working....
I'll rehash everything again tomorrow and update my post.
NOTE: Texture replace plugin will not be included from now on but I'll leave a link for it in the post.
EDIT-2:QUICK COMPARE 2
Plugin 1.0.0.1
(Mine) AMD HASH | Kumarin Special HASH
EDIT-3: TEST
So I decided to upload bothTexture_replacer.dll and the same file compressed in .7z to virus total....
No false positives. So my guess about the "cheats" in the previous .dll be causing the flag might have been spot on.
Last edited: