Denroth There seems to be a problem for some when trying to uncook the eyes. I was not able to solve the problem myself, but TudorAdrian is surely happy to share eye models with you. As for your last image: there went something very wrong with your uncook process.
as you can see from my folder, the uncooked files are much bigger in size.
I included a picture of my W3Oven setup as well, maybe this helps you to determine the path structure, etc.
as you can see from my folder, the uncooked files are much bigger in size.
I included a picture of my W3Oven setup as well, maybe this helps you to determine the path structure, etc.
CAPA14 I came across this post of yours
and I am faced with the same problem as you. But since you played around with the uncooking process a bit, do you have any explanation as to why .redcloth files are not uncooked? The ModEditor can handle them in their cooked version (obviously) and as I remember, @skacikpl said some time ago that importing works. I just wonder why the reverse process does not. I am sure though that if we put our heads together we can make it work (somehow).
Unfortunately, if we are to modify the skirts, we will have to mess with the original armors that contains them, because I could not make the redcloth unique as it cannot be "DLCed". It's indeed a shame
Btw, if someone knows how to make a custom DLC of a redcloth(the redcloth itself, not the w2ent that loads it) please tell me
and I am faced with the same problem as you. But since you played around with the uncooking process a bit, do you have any explanation as to why .redcloth files are not uncooked? The ModEditor can handle them in their cooked version (obviously) and as I remember, @skacikpl said some time ago that importing works. I just wonder why the reverse process does not. I am sure though that if we put our heads together we can make it work (somehow).
MasterOfTheRings;n8125120 said:
Nope... even if we put 1k heads together won't work because the apex version used by W3 is legacy and closed to the public. Based on skacikpl research on the matter.
Yes he did cook an apex(.apb) file with wcc_lite but resulting redcloth itself didn't appear ingame.
That is rather unfortunate. Anyways, thank you for clearing things up.
I just used oven 0.8b along with modkit 1.3. Most things work for me except the w2mesh that contains the eyes, eyelash and teeth/tongue. Has anyone figured this out or is it just me.
Hyadum;n8424860 said:
yes when using blender its all clear. the xml is pretty much empty too
its a cube in blender and in visual stuido
Hyadum;n8425300 said:
had to use a gui i got from nexus called "Mod Kit Gui" strange that w3oven did not work.
paulscotttt;n8425440 said:
Hi paulscotttt, what do you mean that w3oven exporting of meshes results in a box? Can you elaborate? I have just started using w3oven myself, when I unpack official dlcs I can see the meshes fine in 3d paint for example,
Edit: It's true, while besides W3Oven, the quick modding tool by xtcislove wasn't able to export thos fbx files properly, the Mod Kit Gui proposed by paulscott, actually did the job! Maybe that was the reason I had some unexpected fails recently...
Last edited:
I've uncooked a few texture mods that I wanted to edit a bit. Keep in mind that I'm a huge newbie at this stuff. When I uncooked the mod, I had tga set as the texture format. All of the files that were uncooked are xbm or mesh files. I've tried a few recommended xbm file viewers (irfanview/xnview), but they are all giving me errors (Can't load plugin: "Formats.dll") even though I'm using the latest versions. Did I do something incorrectly when I uncooked the mods? Do I need to set texture format as something else?
Can this tool be used to extract texture files from already-existing mod for the purpose of re-packaging them for personal need? The UHDP texture pack merging results in WCC Out of Memory errors for some reason and I wonder if repacking it would help...
Can this tool be used to also fix the issue of Texture Group texture mods not merging with Mod Merger??? COMPILATION is a nice texture pack, but texture group export feature was used to make it happen and that means no glitch-free merging with Mod Merger can happen... But what if some of those textures are re-cooked or somehow re-packaged???
Can this tool be used to also fix the issue of Texture Group texture mods not merging with Mod Merger??? COMPILATION is a nice texture pack, but texture group export feature was used to make it happen and that means no glitch-free merging with Mod Merger can happen... But what if some of those textures are re-cooked or somehow re-packaged???
Last edited by a moderator:
