MontyModMonster

No joy yet, I'm afraid. The CDPR forum is infested with dickheads and moderators who hold modding in such high esteem they merge all discussion into one useless megathread, and direct people back here. :mad: Anyone know how to get a Twitter hashtag campaign going?

Thanks for the kind words. I've just been doing some work with SparrowPrince, and I really want to get it into the game. Makes sense to do what I can to pool the findings, so we can put our heads together and get it done.

Generally I would agree with you. But CDPR have an unusually good record of responding to their fans, so it's worth a try. Also, they've touted modding as a selling point, and if it takes off like Skyrim modding, it'll certainly boost sales. By giving us an override folder (and if it's not present, it wouldn't take much work to implement), the modding community will be encouraged to develop a lot of quality content before they even ship the Redkit.

That's a good one, cheers. That's a good point - we don't know for sure how to recreate valid XBMs once we've edited the DDS files, so we could get false negative results.

The actual Witcher3Compressor seems fine - it's not doing much but zipping modded files into bundles. The question mark is over the hacky workaround of moving the default bundles into a new folder structure, and generating a new metadata.store. Presumably this step is needed because no-one has figured out how to edit the metadata.store file properly. I'm still keen to try this out, to see if placing the full texture files in bundles works at all. Creating a cache file is a much more difficult proposition. EDIT: Have any of you guys determined textures that are likely to be very easy to immediately identify if successfully modded? Geralt's starting armour, perhaps, or some gui elements?

I stumbled across this mod, which has some interesting info about creating bundle mods. http://nmm.nexusmods.com/witcher3/mods/25/? So, the plot thickens - the metadata.store file is significant in which bundle files are picked up. What is puzzling, is that bundle files seem to contain some xbm files, but these appear to be tiny thumbnails only. I don't know if packing the proper xbm files in bundle files rather than cache files will work. I do know that bundles and cache files have different structures. I didn't play with modding W2 either, but IIRC, the override was as simple as creating a 'cookedpc' subfolder in the main game folder, and putting modded files in there.

I would also like this. Either a dedicated subforum for requests, or one for technical discussion. Part of the reason that the modding-talk forum has so little tech discussion in it is that it is so overwhelmed by requests, that it hardly appears to be the correct place to discuss the technical stuff. There's techie talk scattered all over the forums, with no clear and suitable place to centralise it.

Hmm... Looking at the folder \The Witcher 3 Wild Hunt\content\content0 It seems that in addition to all the cache and bundle files, it also has folders for 'engine', 'levels', and 'movies'. These are also subfolders within the extracted texture.cache, which leads me to believe that they might be overrides. Need to experiment with modding some stuff, then just putting it in the proper subfolders under \content0.

If we can succeed in importing edited xbm files back into the texture.cache files, then we have all sorts of options - the original cache archives in the content folders, or perhaps in the patch0 folder. However, I haven't suceeded in doing that yet, and AFAIK no-one else has. The problem is that the QuickBMS reimport process relies on the way it renamed the files when it exported them. Unfortunately, QuickBMS has problems extracting the textures from the cache files, which is why I had to use those Lua scripts to get them out. So, because QuickBMS didn't extract them, it doesn't seem to know how to put them back. Also, using QuickBMS to reimport back into the cache and bundle files is hacky, and has a major limitation - the modded file cannot be larger than the original. This isn't such an issue for mods that are just modifying strings in xml files, and that is already being done successfully. But for those of us looking at modding textures and models, it's a major drawback. An override mechanism is what we really need.

Thanks. The script saves me time faffing around trying to remember how to manipulate text strings and filenames.

I like your thinking - this is an interesting idea. I'll have a look later on. One question will be whether the files in the DLC folders are loose, or whether they are also bundled up in cache archives, which would leave us with the same problem.

Yes - some broken files don't surprise me, at this stage. They might be fixable by removing the .dds hex header which the lua script is prepending. If you upload the python script for me, I'll sort and reupload to a better file host.

That's a good idea. The override folder is the Holy Grail at this point. Hacking the textures back into the cache is far from ideal, if it will work at all. If we had the override, we could do a ton of great modding without the Redkit. We could really do with raising the profile of the question, to get their attention.

Yes, there's about 13gb of it, and it's a very early dump of unsorted files. I didn't really upload it in a way that's convenient for downloading the whole thing, it's more so that people can have a browse. It's not a great experience, because Mega doesn't seem to handle large folders very well. Also, because the scripts are targeting .dds textures, in some cases they have extracted other file formats (which may include models), slapped a DDS header on them, and renamed them to .dds. These may be fixable. These have the original extension as part of their name, like image.png.dds. At the moment, I'm focussing on figuring out how to get the textures back into the game after we've modded them. In time, I'll upload a better version of the dump, organised into the proper folders, and perhaps split into zip archives for easier downloading.

I've made a few more discoveries. It seems that QuickBMS is capable of putting edited textures back into the cache files, provided they are no larger than the originals. The format of the textures used in the cache archive is DDS, but with the headers stripped out. So, the process seems to be that we edit the extracted dds files, then strip out the hex headers, then use QuickBMS to merge them back into the cache, much like with the .bundle files. Haven't figured out how to make it work just yet.