535 réponses à ce sujet

[saltisgood]

Looking good Tarkov! Sooner or later I'll try and add DLC editing as well. It's slightly unfortunate but the DLC files appear to use a different compression to the stock game so I have to write a new reader for them.

[Tarkov33]

You're my freaking hero

[NatP]

Hey, so for ME1Explorer which file am I supposed to pick at the beginning?

[Tarkov33]

Oh wow I guess I didn't understand how bad the DLC-Main Game problem is, getting massive texture glitches on Grunt when he's in his DLC armor, and Zaeed no matter what o.O They usually look fine until you start talking to them close up, then they start artefacting all over the place

Modifié par Tarkov33, 18 février 2013 - 03:18 .

[llllshadowllll]

 I need help, i'm having problem when upscaling textures, more specifically when removing null pointers, i get this error:



Am i doing something wrong?

Modifié par llllshadowllll, 18 février 2013 - 03:35 .

[Tarkov33]

Well for starters, I know that I broke my game using single file mode to replace textures, had to use my backup files. Multi-File Mode is the way to go I believe <.<

[llllshadowllll]

Ah ok, thank you, i'll give it a try!

[Tarkov33]

Also: consider backing up your Mass Effect 2\\BioGame\\CookedPC folder as well as your My Documents\\BioWare\\Mass Effect 2 folder, as both of these have files altered by the ME2 Explorer

[saltisgood]

NatP wrote...

Hey, so for ME1Explorer which file am I supposed to pick at the beginning?

Due to the file structure of ME1 I would very much recommend going with the multi-file mode. I'd only use single file mode for extractions or just debugging purposes.

Tarkov33 wrote...

Oh wow I guess I didn't understand how
bad the DLC-Main Game problem is, getting massive texture glitches on
Grunt when he's in his DLC armor, and Zaeed no matter what o.O They
usually look fine until you start talking to them close up, then they
start artefacting all over the place

Yep, this is going to happen until I can start reading DLC files. The problem is that the trick we use to get around LODGroup issues in ME1 and ME3 doesn't work in ME2, which means we have to change the LODGroup sizes. And that of course causes the black texture bug. Once DLC import is working it's super easy to use remove null pointers to get rid of it though.

llllshadowllll wrote...

 I need help, i'm having problem when upscaling textures, more specifically when removing null pointers, i get this error:

***"This is not a pcc file. The magic number is incorrect"***

Am i doing something wrong?

That means that whatever the file was that it died on has an incorrect header. You could find out more information by looking at the debug output. It should tell you which file it was that it died on and what the magic number was that it returned. I'd very much like to know what the file was that it died on. That magic number is standard on all UE3 games so there's definitely nothing wrong with that.

And yeah, as Tarkov said, definitely back up all your files before doing anything like this. That's the number 1 rule of modding, especially for a mod unfriendly game series like Mass Effect.

[llllshadowllll]

Well, i tried changing to multi files mode, but guess what? Same error again, here are the screenshots
While trying to remove null pointers i get this:


And this when changing to Multi-Mode:

Modifié par llllshadowllll, 18 février 2013 - 02:50 .

[saltisgood]

I wasn't expecting anything to change when you switched file modes. Would you mind sharing your copy of that file? Because I can categorically say that the issue doesn't occur with my files.

[llllshadowllll]

 Here it is:
http://www.4shared.c...mnt10_500.html?

[saltisgood]

Well there's your problem.

I have no idea how you've done it but the first 1048576 bytes of your file are completely blank. Since that's exactly 0x100000 bytes it seems unlikely to be chance. And that's why the program registered your magic number as 0.

Modifié par saltisgood, 18 février 2013 - 04:32 .

[Tarkov33]

Sorry, didn't mean to imply multi-file mode would fix that specific problem, just that it's the best way to go for working texture replacement

[etjester]

Speaking of ME1 Explorer, switching to Multi-File Mode throws an unhandled exception for me. Says I'm missing \\exec\\me1tree.bin .

Any ideas?

[saltisgood]

Doesn't happen for me mate. Is it throwing the error pretty much as soon as you hit the button or is it after it finishes scanning? If possible tell me the where in the code it says it's failing.

[etjester]

Yep. 2 and 3 Explorers do the first time setup just fine, but 1 is less cooperative.

Debugger:

Load file : C:\\Program Files (x86)\\Steam\\steamapps\\common\\Mass Effect\\BioGame\\CookedPC\\BIOG_ASA_ARM_CTH_R.upk
File read
File already decompressed. Reading decompressed data.
Writing pcc to: C:\\Games\\Mass Effect\\dump.bin
Refreshing header to stream...
Opening filestream and writing to disk...

Console:

Entering multi-file mode...
Found MassEffect.exe : C:\\Program Files (x86)\\Steam\\steamapps\\common\\Mass Effect\\Binaries\\MassEffect.exe
Cooked Folder : C:\\Program Files (x86)\\Steam\\steamapps\\common\\Mass Effect\\BioGame\\CookedPC\\
Searching files...
Performing first time setup. Don't worry, this only has to be done once.
File scanning finished. Tree file saved. Reloading...

Exception:

************** Exception Text **************
System.IO.FileNotFoundException: Could not find file 'F:\\textures\\Binary\\exec\\me1tree.bin'.
File name: 'F:\\textures\\Binary\\exec\\me1tree.bin'
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access)
   at ME1Explorer.Texplorer.LoadFromFile()
   at ME1Explorer.Texplorer.backgroundWorker1_RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e)
   at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e)
   at System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(Object arg)

It's certainly correct in that there is no me1tree.bin in the \\exec\\ directory.  It's also weird that it's looking for C:\\Games\\Mass Effect\\dump.bin since there is no C:\\Games\\Mass Effect\\ to begin with.

Modifié par etjester, 19 février 2013 - 05:17 .

[saltisgood]

Ah ok.
1. The dump.bin thing is something I've accidentally left in. When I'm testing this stuff I like to get raw dumps of the files to read them myself and that was one of them. It wouldn't have caused any issues but I'll take it out for next update.

2. It runs the file reader right after it finishes writing the tree file to disk. If it can't find the file then I guess it's not creating the file. Here are some things you could try:
a. Extract the whole binaries folder to your main hard drive and run it from there.
b. Try starting ME1Explorer from the new folder as an Administrator.
c. From the original folder just try to save a file through the ME1 PCCEditor into the exec folder. So find a random package file from your steam folder, open it and try saving it. That may let you know if there are any issues saving to that directory.

In other news, it seems I can now open ME2 DLC files. Fingers crossed that the ME2 DLC authorisation is a little looser than that for ME3 so we can modify them however we want. I'm kinda doubtful, but also hopeful. As it turns out, the stock and DLC files use the same compression standard but the implementation of the decompressor we were using was a bit buggy and it kept throwing errors incorrectly.

[etjester]

Ha! Just had to create an empty Games\\Mass Effect\\ folder on my C drive, and it cleared everything up.

Thanks for the help. =)

[PSUHammer]

Saltisgood. Awesome work. Any hints on if you are releasing anymore updates after 4??

[llllshadowllll]

Hey guys, i need i little help with ME2, does anybody knows where's located the Zaeed and Kasumi files?I can't seem to find them through texplorer!

[Tarkov33]

Zaeed and Kasumi are both DLC characters, Texplorer can't do DLC content yet, sorry <.<

[saltisgood]

PSUHammer wrote...

Saltisgood. Awesome work. Any hints on if you are releasing anymore updates after 4??

Yes I'm going to be releasing more updates after v4, but first I'm redoing the mod from scratch. The "first" version of this new mod will be up to the same level as v4 so once that's out I should be able to release some more updates without a huge delay.

llllshadowllll wrote...

Hey guys, i need i little help
with ME2, does anybody knows where's located the Zaeed and Kasumi
files?I can't seem to find them through texplorer!

Zaeed and Kasumi's files are in your BioGame\\DLC\\DLC_HEN_MT and DLC_HEN_VT folders. Currently you can't open them in ME2Explorer because of a decompression error, but I have that solved on my end. The reason I haven't updated it yet is because I've been testing out some DLC editing stuff first.

I'm not sure how much of this I can discuss openly on a BioWare forum, but the DLC authorisation is actually even stricter in ME2 than ME3. And while it's definitely possible to mod certain DLCs, others may prove troublesome. At the last check, out of all the DLCs there were 4 that lost authorisation when edited:
1. Normandy crash site
2. Zaeed
3. Arc Projector
4. Cerberus Weapon and Armour

I'm not a code ****** so I don't really know why these DLCs are different to the others. But perhaps someone else might be able to.

[llllshadowllll]

Too bad, anyways it's already awesome to be able to use these textures without texmod, so thanks!

Modifié par llllshadowllll, 22 février 2013 - 05:07 .

[Didact2401]

Here's another bug (or feature?). The first outfit that femshep wears uses the same texture name for both the clean and dirty versions so only one shows up in texplorer.

The texture in question:
HMM_ARM_CTHi_Diff