

Joined: Tue Apr 04, 2017 11:44 am

Posts: 236

Huili wrote: Thanks for the quick response. Yes, I set everything up, now everything is loaded normally. I thought about the texture problem, can this be a problem of export and import? Ie when importing/exporting information about mipmap disappears? Just a similar problem (pixels instead of images) I saw in Skyrim, when I forgot to generate a mipmap for the first time.

I hope I translated it normally.



that can not be the issue, as I never touch the pixeldata for export or import. so if you reimport the same dds, you get a byte exact copy. its about this rangeStart and rangeEnd, its for "where in the COMPRESSED data does this chunk start and end" and logicalSize and logicalOffset are the offset and size, once its loaded to memory (UNCOMPRESSED). I mean the only byte difference is that when the import gets compressed again (with my tool) the resulting size is different, because I dont know their exact compression settings they used, but it also shouldnt matter. once it imports the pixeldata (of original texture) to a cas file and makes the cat file point to it , it then scans through all or one (depending on setting) sb files, to fix their fields to the new compressed size. im also pretty sure, if I would just reimport the original COMPRESSED data, it would keep size, no sb has to patched and then it should work, because those fields mention above match it, even if its in another cas. just its pretty useless^^ so again, the only difference when importing the original is the change in compressed size, so there has to be some issue with that



greetz



PS: im currently away from my pc, can someone check the corresponding ebx to such a texture? do they have size information maybe too? that can not be the issue, as I never touch the pixeldata for export or import. so if you reimport the same dds, you get a byte exact copy. its about this rangeStart and rangeEnd, its for "where in the COMPRESSED data does this chunk start and end" and logicalSize and logicalOffset are the offset and size, once its loaded to memory (UNCOMPRESSED). I mean the only byte difference is that when the import gets compressed again (with my tool) the resulting size is different, because I dont know their exact compression settings they used, but it also shouldnt matter. once it imports the pixeldata (of original texture) to a cas file and makes the cat file point to it , it then scans through all or one (depending on setting) sb files, to fix their fields to the new compressed size. im also pretty sure, if I would just reimport the original COMPRESSED data, it would keep size, no sb has to patched and then it should work, because those fields mention above match it, even if its in another cas. just its pretty useless^^ so again, the only difference when importing the original is the change in compressed size, so there has to be some issue with thatgreetzPS: im currently away from my pc, can someone check the corresponding ebx to such a texture? do they have size information maybe too?



