So i'm trying to cook up a quickbms / or (some other type of script) that could take my textures header ".XETU" and spit out the file 100% unmodified except i need the header replaced with ".XETV" i'm working on a simple bms script but i need to see a sample to know exactly what...

http://himeworks.com/redirect.php?type= ... =pvrtc_pvr

thats the same script that comes with the Noesis installation

i think chrrox abandoned support for this script years ago :mrgreen: i made an adjustment to it on line 49 that uses the header size so it will go to the start of image data, before it was just using a fixed value and started reading at the wrong offset when there is different header length. fmt_XBO...

UnityEX can open the __data files and you can export files from them :D http://www.zoneofgames.ru/forum/index.php?showtopic=36240 it does not support compressed meshes yet though so you can't export the mesh as source, only as compressed data :( UnityCache\Shared\0b7c13d0d3ca8a9fc57b33b5671356f0e0e9...

.... with the new Death Star DLC, DICE seems to have added a new .meshset file format. The actual .meshset file is much larger than expected, and there is no corresponding .chunk file... it really appears as though DICE has simply merged the two files -- like the chunk data picks up immediately fol...

herbert3000 wrote:Is there any need for this program AND should I continue adding new features?

never question the need for something you enjoy working on, people
typically don't know what they want until you give it to them.

i would give it a try but it won't launch on XP
i have Java 1.8.0_101

use the command prompt or a bat file and run this like shakotay posted here
viewtopic.php?p=103783#p103783

after extracting 00001012.dat from 072.x with offzip

And this is the 'magic' code snippet where the face data being created: face_data = [] for n in range(data[3]): f(8) i(40) var = i(4)#;print var face_data.append(var) #print plik.tell() Is that code really for creating face indices? i looked through the script but i could not follow it, i don't kno...

made a Noesis python script to open the msd model files split from skin.wpk with the bms script supports geometry and UVs

this is all i have seen so far :D all data is little-endian except the vertex data 0x10 - pointer to COLL chunk 0x658 - total number of vertices 0x65c - number of submeshes(?) vertex data table (16 byte blocks * number of submeshes) 0x6b5 - first submesh offset relative from 0x708 0x6b9 - vertex str...

.. how do you know texture coordinates like that in hex ? is there a special hex number for width, height, format ? i start by opening the unknown texture in TextureFinder and seeing what the size and format is then i search that file in a hex editor for where that width and height is stored and co...

okay i updated the texture script in the previous post

here is Noesis python plugin to open your xmt texture samples :D tex_AloneInTheDark_PC_xmt.zip supports dxt1 and dxt5 because those were the only types in the samples yeah, I won't support insane developers. :D i hear that :D i started to assemble a python script for Noesis based on your Hex2obj pro...

point cloud of policeman_ragdollbase_4647DAEE90C7AF.xmg :D policeman_ragdollbase_xmg.png the vertex data is big-endian and the face indices are little-endian so you can't display the results in Hex2obj because there is no option to set independent endianness on different data types, but this is only...