if this is from a mobile game best try PVRTexTool to convert it to usable format.

Would you mind telling me how you done this and how I can do it with other .tex files just input the settings like you see in the image, -set the width of the image -set the shift to account for where the data actually starts -set the pixel format how are you supposed to know what settings to choos...

512x512 dxt5 image with 52 byte header
width at 0x28 and height at 0x32

cool it finally launches on XP :D and i can load the truck.d3d and d3d.xml you had in the 0.5b release example, now how do you save it out to obj, "File>Save file as..." is greyed out. i can copy the entire contents of the window to clipboard but it isn't formatted properly when pasted. wh...

z22901206 wrote:latest version of Noesis? it didnt work...DX10 file...

must be your graphics card i guess

add ".dds" extension to your sample and open with native Noesis DX10 support

you're saying and asking too many things at once that i don't fully understand yet. :D the script is a work in progress and definitely not perfect but i think the rat is not a good example of the issue because it is too simple, you must look to the character models, like camoufla-dc_dododo etc i don...

yeah see thats what i mentioned before, the UVs are correct but that file has many material
groups and i would need to break it up into submeshes, this is not a quick fix for me because i
have not found where this information is stored yet.

here is first draft of Noesis python script for your "MGS HD collection PS3" samples :D fmt_MetalGearSolidHDcollection_cmdl.zip supports geometry and UVs i don't know what problems you had with the maxscript but this is the best i can do for now. i couldn't test UVs because there were no t...

daemon1 wrote:I parsed the whole data structure properly.

i hope so, you are a programmer and i am not!

since daemon1 is likely going to make a complete tool i will just share the work in progress
bms script i have so far for texture data extraction so it doesn't completely go to waste.
this bms script extracts the texture data with names and adds headers.

looks like the \f in the path is being interpreted as the escape sequence \x0c which is a form feed. 3 ways to fix this posted here :D http://forum.xentax.com/viewtopic.php?p=127222#p127222 raw string r"D:\Steam\steamapps\common\firstassault\Data" double backslash "D:\\Steam\\steamapp...

here is a better way to decompress your bin samples in batch with a bms script :D # script for QuickBMS http://aluigi.altervista.org/quickbms.htm comtype zlib_noerror get ZSIZE asize math SIZE = ZSIZE get NAME basename string NAME + ".dat" clog NAME 0 ZSIZE SIZE i'd like to phase out using...

you can use the same instruction i posted here to at least get the model and textures
viewtopic.php?p=128377#p128377

256x256 RGBA8888, the first 8 bytes are the width and height