Magic Wand not working after 2 selections

Forum|Forum|2 years ago
July 3, 2023
3 replies
948 views

Please help me.

When I try to select a selection with the magic wand and make it a different material, I get stuck on the loading screen. It without fail will work the first time, and then the second selection will make it stuck. After it gets stuck, I cannot do anything and am forced to force quit.

I have tried different files, unistalled and reinstalled Stager, shutdown and restarted my computer, nothing is working.

I am new to this, but I have made 30+ renders of the product in different color schemes and it just now stopped working on Friday and is still not working today (Monday).

Thank you for any advice!

Materials

This topic has been closed for replies.

Correct answer AlanGilbertson

This is a bug that's been there for quite a while.

One way to reproduce the problem is to add a parametric cube to a new scene, convert to a regular object, then use the Magic Wand to select one face and add a decal. Position the decal. Deselect. Use the Magic Wand to select another face of the same cube. At this point, the Stager UI becomes unresponsive, and it's no longer possible to switch to a different tool, move anything in the scene, or open any of the menus. The OS doesn't see Stager as unresponsive, and Task Manager shows constant CPU activity one one or two cores. If you wait long enough (more than a minute, sometimes as many as ten, depending on the scene), Stager recovers and starts responding again.

This has been 100% reproducible on all my systems (Win 11 Pro), and goes back, iirc, at least to the first release of v2. Obviously it's a real production-killer if you have to add several decals to the same object in a scene.

Here's today's log. I ran several tests that demonstrated the bug. On the last one, I waited out the CPU activity so I could quit normally.

AlanGilbertson

Community Expert

@J. Liggett Help out by sending your logs to substance3D-bugs@adobe.com or attach here. A sample Stager scene might also be useful, but see my reply to @Cyril Dellenbach. If you hang in there long enough, Stager will start to respond when the CPU activity stops.

J

J. LiggettAuthor

Participant

Thank you Alan for verifying that it does indeed happen. I responded to Cyril and attached my log from this morning. I'll attach it to this response aswell.

What can I do to fix this bug? I need to create a list of things for work and this is really putting a damper on my flow.

Thank you.

AlanGilbertson

Community Expert

There isn't a fix at the moment. That will come from the engineering team, but in the meantime there are workarounds.

Try not adding decals sequentially to the same object. Add one, do some other stuff, then come back to the first object and try adding it there.

You can also add a decal, save, close, reopen and continue. I know that's tedious, but (depending on your machine and the size of your scene) it's usually quicker than waiting for whatever Stager is doing in the background to complete and return control to the user.

Instead of using the Magic Wand, export the UVs, open them in Photoshop and add the decals there. If you're not familiar with UVs, this might take a bit of head scratching and looking up the documentation, but it is the most reliable way to put a graphic exactly where you want it on the model.

If you're feeling brave, exceptionally nerdy, and have a lot of these to do, use Substance Painter. Export the object as a model, open it in Painter, add what you need, save it out and reimport into Stager. In the long run, this is probably the most flexible workflow. Depending on the kind of work you're doing and how long-term the project(s) is, time learning Painter is probably well-spent.

Cyril Dellenbach

Community Manager

Hello @J. Liggett,

Thanks for the message.

I wasn't able to reproduce the issue. Would you mind sharing your last log? You'll find it under:

C:\Users\UserName\AppData\Local\Adobe\Adobe Substance 3D Stager

Let me know,

Cyril Dellenbach (Micro) | QA Support Artist | Adobe

AlanGilbertson

Correct answer

Community Expert

This is a bug that's been there for quite a while.

One way to reproduce the problem is to add a parametric cube to a new scene, convert to a regular object, then use the Magic Wand to select one face and add a decal. Position the decal. Deselect. Use the Magic Wand to select another face of the same cube. At this point, the Stager UI becomes unresponsive, and it's no longer possible to switch to a different tool, move anything in the scene, or open any of the menus. The OS doesn't see Stager as unresponsive, and Task Manager shows constant CPU activity one one or two cores. If you wait long enough (more than a minute, sometimes as many as ten, depending on the scene), Stager recovers and starts responding again.

This has been 100% reproducible on all my systems (Win 11 Pro), and goes back, iirc, at least to the first release of v2. Obviously it's a real production-killer if you have to add several decals to the same object in a scene.

Here's today's log. I ran several tests that demonstrated the bug. On the last one, I waited out the CPU activity so I could quit normally.

Stager-2023-07-04.zip