[SOLVED] Texplorer: infinite Prefetching Export Name Data

[mcgregor777]

Hi,

I got an issue with some textures when I try to change them by using Texplorer. It ends up doing the Prefetching Export Name Data infinitely, no way to cancel except by closing the window. I got it on ME1 downloaded via Steam, with DLCs installed. I installed MEUITM for ME1 too. I run on Windows 7 x64. I'm using the latest MEExplorer on Nexus.

I also tried with TPFTools, but it ends up not installing the new texture.

Is there anything I'm doing wrong or is there any fix for this ?

Thank you by advance.

[giftfish]

Please provide:

1. A screenshot of the debug/error output provided by each tool.
2. A link to the texture mod(s) you're trying to install.
3. A more thorough description of how TPF Tools behaves when you attempt the replacement; most users should not need to replace via Texplorer.

Also, presumably you've created a texture tree and referenced the wiki articles on Texplorer and TPF Tools?

[mcgregor777]

Here is TPFTools window after trying to install the texture, with the debug window right next.
www.dropbox.com/s/i28al2myvi8a5l4/TFTools.jpg?dl=0

Same for Texplorer :
www.dropbox.com/s/swscp3j0viix23h/Texplorer.jpg?dl=0

I'm trying to install the face texture for Liara in ME1 (it worked on a previous installation) :
www.nexusmods.com/masseffect3/mods/19/?

With TPFTools, I drag and drop the .dds texture into the window, I click "Analyze with Texplorer", returns no error, I click "Install Valid", and I end up with "no mods installed!".

And yes, I made the tree before doing any modification on ME1.

[kfreon]

A curious bug...
Might want to post that one on the github issues page.

[giftfish]

I wonder if it has something to do with being the ME1 version of Steam. When I tested ME1 texture replacement for The Great Testing Slog for v2.0, my game is a physical disk copy.

mcgregor777 -- Have you tried any other textures? Also, you may consider trying the replace with v2.0 of the toolset. Also, a straight ME3 face texture for Liara will not look right in ME1. The lighting between the two games is just too different and it will be far too dark. You're going to need to modify it a bit.

[mcgregor777]

I've replaced the EYE_Spec texture by the HD Eyes texture from social.bioware.com/project/8266/ , no issues there. Would you recommend me any specific texture to test ?

Thanks for the advice for Liara's face texture.

[giftfish]

May 19, 2017 0:12:53 GMT mcgregor777 said:

I've replaced the EYE_Spec texture by the HD Eyes texture from social.bioware.com/project/8266/ , no issues there. Would you recommend me any specific texture to test ?

I have a suspicion that the issue is with CDAMJC's file. I've ran into some wonkiness trying to replace textures on top of the EXE install of MEUITM. If you really want to know the answer for sure, you'd need to revert to a vanilla game to find out. Then install into the vanilla file.

I could be wrong, but it's a possibility.

[mcgregor777]

I just managed to change the texture (after giving it some more brightness) using TPF/DDSTools from ME3Explorer 2.0 (had some specular issue when tried to change with Texplorer 2.0). Looks good imo, and adds consistency to Liara's appearance throughout the trilogy.

[giftfish]

May 19, 2017 6:37:09 GMT mcgregor777 said:

I just managed to change the texture (after giving it some more brightness) using TPF/DDSTools from ME3Explorer 2.0 (had some specular issue when tried to change with Texplorer 2.0). Looks good imo, and adds consistency to Liara's appearance throughout the trilogy.

Glad it worked.

Unfortunately, that's not good -- at least for the toolset. There have been very, very few changes to TPF Tools between v2.0 and 3.0 (there really should have been none, since we tested the crap out it and then deemed it archival), but it means that one of the changes we tried to sneak in -- that we thought would create no problems -- is indeed causing texture replacement issues with ME1.

Most importantly, this bug won't be fixed. It's far, far too risky to address without causing any other problems. Which is ironic, considering it's a result of us tampering with things that we thought wouldn't cause problems.

Booo.

----

If you want, mcgregor77, you can report the bug on Kfreon's fork of the toolset on GitHub. It should not be reported on the toolset's main GitHub, as it will not be fixed.

[mcgregor777]

At least I managed to dig out an issue, I think it's still positive to be aware of this kind of thing. I'm gonna report this issue to the linked github, so the one in charge is aware too. Thank you for your time and advices.

[kfreon]

I'll eventually get to it.
A curious one to test though.