[SOLVED]Texplorer not applying changes

[realsurvivor686]

Hello all,

Context:
- Am trying to alter the textures in the "Marine_00" PCC, for both the Helmet and Body.
- Am ordering textplorer to make the changes to a pre-created, custom TFC. (I have successfully utilised this aspect with my Ashley mods)
- Am utilzing me3explorer 3.0, on Windows 7

Problem:
- None of the changes take effect. Although textplorer updates the thumbnail to reflect the change, in-game there is no difference!

Key Notes:
- Changes made to the Marine_00_Explore PCC are taking effect. As a result, James's texture are accurately depicted, during the squad-loadout and squad-power-evolution screens, before the missions introductory cutscene kicks in. However, when the mission begins proper, James reverts to his vanilla texture albeit over my modified meshes.

I would appreciate some help in this regards. It is extremely frustrating when textplorer decided to become uppity for no reason.

Much Appreciated

realsurvivor686

[giftfish]

1. Are you selecting your custom TFC as far as where the texture should be stored?
2. Are you certain the file is being modded and is pointing to the new texture?

The only time I've had this happen seemed to be the result of the game already having the vanilla texture in memory and retaining it rather than using the alternate version the modded file pointed to.

You can probably fixing by renaming the textures and pointing the material in the mesh to that new texture.

[realsurvivor686]

Thanks for responding

Response to Question 1:
- Yes, I am selecting the 'custom TFC' as to where the textures should be stored (i.e. I am selecting "Textures_DLC_CustomName") as the destination for the textures to be stored at.

Response to Question 2:
- Examination of the PCC, via the PCCEditor 2.0 shows evidence that the PCC has been 'altered' (there are references to "Textures_DLC_CustomName" in the right places), across the diff, norm and spec textures. However, the gameplay fails to reflect this.

Further examination reveals:
1. Only changes to the Helmet's diff textures are taking hold.

I will try the "renaming textures" tactic and let you know how it works out.

On a historical note: This issue used to pop up on earlier editions of me3explorer. I believe one of the developments noted that it involved 'multi-threading' and its interaction with McAfee and fixed it. Has there been any alterations to textplorer's multithreading capabilities since then?

[realsurvivor686]

Quick Update:

Attempted Solution 1: Run me3explorer in isolation
- I turned off McAffee, and my wifi. Ran the textplorer function.
- Same results: Only changes to the Marine_00_Explore PCC take effect.

Attempted Solution 2: Change the name of 'new' textures to match the old ones
- Same results: Only changes to the Marine_00_Explore PCC take effect.

Any ideas as to what is going on? Has anyone else ever encountered this weird glitch before?

[realsurvivor686]

Just to double check, I've tried replacing the textures for Kaidan's PCCs. Same results, albeit now that none of the requisite textures have been altered (i.e. Kaidan_00 and Kaidan_00_Explore PCC).

As far as glitches go, this one is pretty critical. If all that textplorer is doing is simply changing the thumbnails, then this is a VERY BAD GLITCH.

Am right now uninstalling and then reinstalling my .NET framework to see if that changes anything.

[ottemis]

You've rebooted I assume.

[realsurvivor686]

Yes. Will try letting textplorer create the automatic "CustTextures" tactic and see if that works.

[realsurvivor686]

Quick Report: Letting textplorer generate "CustTextures0" and then altering the PCC entry manually to the "Textures_DLC_CustomName" has worked.

Please consider this issue closed.

Thank you, to everyone, for all your assistance.

Much Appreciated

realsurvivor

[giftfish]

Mar 4, 2017 1:17:03 GMT realsurvivor686 said:

Quick Report: Letting textplorer generate "CustTextures0" and then altering the PCC entry manually to the "Textures_DLC_CustomName" has worked.

Please consider this issue closed.

Thank you, to everyone, for all your assistance.

Much Appreciated

realsurvivor

So.... I'm confused. This sounds like a bug, then.

Are you saying that:

1. Appending a new texture onto an existing DLC TFC wouldn't result in changes in game, but...
2. Making a new TFC from scratch and renaming it did result in changes in game?

That indicates there's a bug in v3.0 regarding texture appending to DLC TFCs, which would be a problem. I tested that feature myself in v2.0 and I know it worked.

kinkojiro , have you noticed this with v3.0 or v3.0.1?

[kinkojiro]

Not had any issues myself.

[realsurvivor686]

@gitfish

Correct. I must point out that as far as textplorer and the PCC Editor were concerned, the textures had been successfully changed. Yet when I loaded up the game, the textures were stuck in the vanilla state.

I must point out that I had altered the meshes before hand. Do the new versions of textplorer have issues with altered meshes?

Also: I was too hasty in believing the issue had been solved. This bug is back (I applied the texture to a PCC with an altered mesh) and it now affects even the "CustTextures0.tfc". At this point, something is going very wrong with my system and am going to try to roll-back whatever updates I made.

Systems Stats:
Windows 7 64 Bit
.Net Framework 4.6.2
Thinkpad T410

[giftfish]

Mar 4, 2017 14:48:34 GMT kinkojiro said:

Not had any issues myself.

And just to be clear, you've presumably used the append feature with v3.0/v3.0.1?

[giftfish]

Mar 4, 2017 15:10:39 GMT realsurvivor686 said:

Correct. I must point out that as far as textplorer and the PCC Editor were concerned, the textures had been succesfulyl changed. Yet when I loaded up the game, the textures were stuck in the vanilla state.

I must point out that I had altered the meshes before hand. Do the new versions of textplorer have issues with altered meshes?

If the modified mesh was the problem, it would have affected both replacement methods. There's no reason that appending should not work with mesh changes and building a new TFC from scratch does. At that point you are only dealing with the texture export references, not the mesh.

[kinkojiro]

Actually just checked I am using 2.0.15 for texplorer.

[giftfish]

Mar 4, 2017 15:10:39 GMT realsurvivor686 said:

Also: I was too hasty in believing the issue had been solved. This bug is back (I applied the texture to a PCC with an altered mesh) and it now affects even the "CustTextures0.tfc". At this point, something is going very wrong with my system and am going to try to roll-back whatever updates I made.

Okay, now this makes more sense.

Have you checked the material and texture references in Meshplorer? This sounds like a problem where they are pointing to different textures. Perhaps imported ones that aren't in the file.