Maya owning textures

[Steve Davy]

It used to be possible to overwrite and even delete file textures that were being read into an open Maya scene file. While obviously a little risky, this was actually a hugely useful and necessary part of the texturing workflow -- at least when primarily working in Photoshop.

This now seems to have changed, and it's not even possible to delete a texture that HAS been read into a Maya scene, even after the scene itself is closed.

Does anyone know when, how and why this changed? Keeping track of current textures has always been a pain in Maya, especially when doing look dev and possibly saving out multiple versions of something, but at least it used to be possible to overwrite and delete on the fly. With this new behavior this becomes immediately more messy with greater potential to end up with a ton of texture files you don't want to keep.

I'm on Windows 10.

[joiec...@gmail.com]

Well, that were always the case BEFORE Arnold came into scene. Since using Arnold, I've been unable to resave a loaded texture until MAYA is closed completely.

Using software renderer or Mental Ray was very possible and desirable.

Now it can't be done, which is a pain in the ass.

[Steve Davy]

Perhaps it's Arnold that is causing this then?

I don't use Arnold -- I'm a Vray guy -- but I've been having Arnold loaded recently for work reasons. Strange that I've never noticed it before.

It certainly is a pain in the ass, especially as even textures that have been loaded but are then UNLOADED can't be overwritten, meaning that when doing lookdev you can't just get around this limitation by doing texture1 texture2 and back again, but are forced to keep adding increments and saving out more and more files. It's incredibly stupid and doesn't account for how this work actually gets done in practice.

---

From: maya...@googlegroups.com <maya...@googlegroups.com> on behalf of joiec...@gmail.com <joiec...@gmail.com>
Sent: Tuesday, November 2, 2021 4:51 AM
To: maya_he3d <maya...@googlegroups.com>
Subject: [maya_he3d] Re: Maya owning textures

 

--
You received this message because you are subscribed to the Google Groups "maya_he3d" group.
To unsubscribe from this group and stop receiving emails from it, send an email to maya_he3d+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/maya_he3d/cb28d667-5aee-43b3-8403-82c498641462n%40googlegroups.com.

[Deke Kincaid]

Are you using VP2 with textures on? VP1 didn’t support mip mapped .tx file but VP2 does so in the past you didn’t have textures in the viewport.  Either that or do you use Vray RT/IPR?

To view this discussion on the web visit https://groups.google.com/d/msgid/maya_he3d/BYAPR07MB586147D4188E75724941BC8FDD8B9%40BYAPR07MB5861.namprd07.prod.outlook.com.

[Steve Davy]

"Are you using VP2 with textures on?"

Probably some of the time, why? And yes I use IPR all the time.

The issue is that this NEVER used to be a problem with Maya before -- no matter what you were doing you could overwrite textures.

---

From: maya...@googlegroups.com <maya...@googlegroups.com> on behalf of Deke Kincaid <dekek...@gmail.com>
Sent: Tuesday, November 2, 2021 8:22 AM
To: maya...@googlegroups.com <maya...@googlegroups.com>
Subject: Re: [maya_he3d] Re: Maya owning textures

 

To view this discussion on the web visit https://groups.google.com/d/msgid/maya_he3d/CAOOm49QSk9-2uaSviFE-NqY_2BRETP1tq7sx6pvAp472ceUtqw%40mail.gmail.com.

[joie]

In my case, the problem was introduced with the use of Arnold, not before.

And I don't usually use vp2 with textures.

You received this message because you are subscribed to a topic in the Google Groups "maya_he3d" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/maya_he3d/Qxy_W_-yTd4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to maya_he3d+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/maya_he3d/BYAPR07MB5861489F99F38A5423DEB3E6DD8B9%40BYAPR07MB5861.namprd07.prod.outlook.com.

[Szabolcs]

If it's an Arnold issue than probably OIIO is keeping the texture cache in memory and locking the file.
You can manually flush the texture cache from the Arnold menu and let go of all texture files, sacrificing some texture re-reading time by the next render.

Cheers,
Szabolcs

--