Quick Reply
Search this Thread
Mad Poster
Original Poster
#1 Old 22nd Jul 2025 at 7:47 AM Last edited by aelflaed : 22nd Jul 2025 at 10:43 AM. Reason: figured out one part of the answer myself
Default Autodrapes Multistate
I have successfully created Autodrapes out of the single-tile Simply Elegant curtains - a hope I have looked wistfully at for many years. I had to add a new subset for the rail, and ended up repoing that to the original rail.

I would love for the fabric to also use the many existing fabric recolours, but I wasn't able to set that up - any change of the subset names to do with the tsDesignModeSlaveSubsets results in difficulties, as far as I can tell. The least of these glitches simply removed the subset from being designable.

Is it simply a fact that autodrapes, with their multiple states, have to have separate recolours of their very own? Or is there still a way I can repo my new curtain to the original?

Thanks for your advice!

My new downloads are on my Pillowfort
Me? Sarcastic? Never.
staff: administrator
#2 Old 22nd Jul 2025 at 12:49 PM
Auto drapes are essentially lights. You'll have to edit str as well as the bhav's to change the subset names. Will it work? Unsure. I've tried. It either failed because it's not possible or because I did something wrong. xD Either are a possibility. I think the issue is the regular curtain texture takes the whole image size, and the open state uses part invisible. So they both can't use the same texture. This might more fit using two different meshes. And that will require editing bhavs.
Mad Poster
Original Poster
#3 Old 22nd Jul 2025 at 10:44 PM Last edited by aelflaed : 23rd Jul 2025 at 12:08 AM. Reason: partial success
I fixed another lamp that wasn't repoed correctly - mine nearly worked but didn't glow. PineappleForest gave me some tips for lights - perhaps those will work here too. I'll have another go.

In the meantime I did the other SE curtain that had suitable meshes ready to use - it was working well, but then I mucked something up and now the textures are not connected right. Hope I can see what is needed today.

So, I have partial success - the original recols can now be selected (yay!)...but don't show in Live mode...although they still seem to be selected when you go back to the recolour tool. In Live mode, the curtain shows the default texture.

Any clues about what is wrong there? I'll keep poking it after breakfast, anyway.

My new downloads are on my Pillowfort
Mad Poster
Original Poster
#4 Old 23rd Jul 2025 at 6:26 AM
(I think this thread may need to move to the Repair section. Asking questions wasn't enough!)

My current best-seeming version is now accessing the original recols for the fabric (and the rail - the rail part seems stable).

If I remove/alter the theoretically-redundant TXMT (closed_default_lit), the closed mesh goes blue flashy or text-covered.
If I update the 'closed' String in tsDesignModeSlaveSubsets to reference the fabric (fabric = open), the open mesh flashes blue.

Issues:
The Live Mode mesh, closed or open, doesn't show recolours. The hidden closed mesh does (and isn't hidden).

The state-change is happening, but both meshes are shown when 'open'. Possibly also when closed, but it's hard to be certain, as only the default texture is seen.

I do have a working curtain, with repo rail but standalone fabric (included) - but it would be so much better if the old recolours could be used on the new object.

Thanks for your assistance!
Attached files:
File Type: 7z  AE_SEautodrape-Help.7z (225.9 KB, 7 downloads)

My new downloads are on my Pillowfort
Back to top