john9818a on 27/9/2019 at 04:50
unlock_all was mentioned in a search for Locked Resource. I've never had to use it but maybe it would have worked in your case.
Yandros on 27/9/2019 at 15:10
Quote Posted by uncadonego
I moved an old texture from rescor_2 to txt16, and changed the skin to that. I optimized after changing the other Jorge stuff to wood texture. I saved and closed. When I opened it up again, now I can load core_1 family again. Whatever burr was up its butt, it's gone now.
This is what Unna and I were telling you to do earlier, pointing any replaceable texture at anything under fam is just asking for trouble. It used to work in OldDark but I have noticed problems with it in NewDark and so have taken to only using obj textures for replaceables.
Tannar on 27/9/2019 at 15:26
I agree. Have had the same issues and now I make sure any replaceable object texture is placed in obj/txt16 and referenced there.
Yandros on 27/9/2019 at 15:57
In one of the DCE missions where Polygon or Moghedian had done this (point at a fam texture) when creating the architecture long before NewDark, and when we went to test it (in NewDark years later) it was misbehaving, and it took me a while to figure out what was going on.
GORT on 27/9/2019 at 20:18
Usually, unlock_all will grant access to the fam textures to be used for replaceable object texture whether in use or not. (At least, it did for me for all of my FMs.)
uncadonego on 29/9/2019 at 09:34
Quote Posted by Yandros
This is what Unna and I were telling you to do earlier, pointing any replaceable texture at anything under fam is just asking for trouble. It used to work in OldDark but I have noticed problems with it in NewDark and so have taken to only using obj textures for replaceables.
I acknowledge that is what you were telling me. I was more or less reporting that it fixed it.
