Substance 3D Stager

Hello. This is happening pretty much all the time. I work on a file and then when trying to open it again to continue working I get a notification that says Unable to Open Document. The only option it provided is to copy the log and describe the issue in the forum.   

I can import some .fbx models, but this one doesn’r import. Why?

I am having the Adobe Substance Stage Black Screen issue…. Everything was working fine but now when I open the project I have the black screen. There are multiple links and artwork in the file. I deleted the cache + folders, cleared logs and still nothing….. I want to note that I am using a Mac Studio M3 Ultra computer so as Apple thought it would be a good idea to remove the powerful GPUs and give us some little integrated garbage chip I am not sure how to fix this. Any ideas?

I'm encountering a couple issues.  Anyone else on an an M1 Mac noticing that none of the Generative AI features work at all?  Like, there isn't any notification saying "this feature isn't available" or "unable to…" or anything.  No progress bar or indicator that stalls, literally just nothing happens.  Am i the only one that's happening to?  Plus, 50% of the time I do a "replace object…" it's another instance where nothing happens.  It's not a full crash, because I can still click on menus and palettes, just nothing that would actually trigger an action within the document.  Any ideas?

I am using the latest version of Stager and like many others, am experiencing the blank screen problem. I have tried every suggested -- deleting aero$ folders, checking graphics card, all of it. Nothing works. I can't even close the program without using forced quit. Unless someone can suggest something that actually works, I'm going to uninstall and try to forget this program. Adobe? On windows 10.

I'm on a M1 Max Macbook Pro and just started trying to use Substance 3D Stager specifically to try to use the generative AI features.  I set up the prompt, i pick options (or leave the options unchanged) and hit the generate button and nothing happens.  No "worrking on it," no "failed," no "generative features unavailable" no nothing.  Any ideas how to actually make this stuff work?

Anyone know where is the "Wall with Windows" effect is that may have been in previous versions? I saw this in someone's YouTube video. The goal is to to create walls with windows. This isn't an easy find in SG. Any help is appreciated. 

Hi everyone!  I'm Jeanette Mathews, lead product manager for Stager!  Stager is a powerful and approachable staging application for building scenes in 3D.  The team can't wait to hear from you and will be here to help you on your journey with the app!     These forums are primarily for questions and project support.   Remember you can check out the app documentation for lots of details on what functionality exists already: https://www.adobe.com/go/stager-documentation   And check out these tutorials for hands on learning of how to use Stager: https://www.adobe.com/go/stager-tutorials     Can't wait to work with you all to build a better app! Cheers!Jeanette

I can't export a model that I previously made in Painter, directly into Stager. It gives me the "Unable to Import Model" error. I did update my software (it worked before that), so it might be a compatibility issue. But it shouldn't be, considering there is a workaround that more or less contradicts that: The model is fine, as I can send to After Effects without issues. Since After Effects doesn't "import" files, but links them, a temporary GLB file is created. I located that file from within AE in Windows explorer and imported it without issues into Stager. Assuming Painter tries to export to Stager similarly (either sending a GLB directly to Stager, or creating one in a temp folder like with AE), the error thus seems to be with the software itself. The file works. Painter exports fine and Stager imports fine. It's the link between those programs that seems broken somehow. I can work with this for now, but I figured it would be handy to let the world know!

I have dowloaded an image as glb from the poly.cam, since that is the only way to download as free. But I can't open it in the Stager. Can you help me how to bring it to the 3D Stager. Any one who knows this issue. Thanks 

This software is quite possibly one of the worst   Everything in here is available for free elsewhere and is incredibly easy to use.  Gemini NanoB is free, tessellation of heightmaps, grayscale, export of STL from picture, mesh creation of Image, Everything Everywhere All at Never again.   THIS PROGRAM IS UNUSUABLE.   Slow, unintuitive, completely and utterly the worst workflow I have ever come across outside of Fusion 360.   Having a Pro subscription does not cover this software, its $60/mo.    [abuse removed by moderator]    

Hi. For me the Exponential preset dosent loop, it clicks a couple of degreas when going to last frame. I spent hours trying to figure out why, i can only conlude its a bug? Dose enyone have a work around?  Kind regards,Martin

Hi there! 😊 I hope you’re doing well. I wanted to ask — how can I remove or reduce the white cast that appears on my renders in Adobe 3D Stager?

오류가 진단되었다는 창이뜨면서 앱이 정상적으로 작동하지 않습니다  로그파일 같이 첨부드립니다 지원을 요청드립니다감사합니다

Why are my GLB files from Polycam App not able to import into 3d Stager?

I have been having issues with Substance Stager since it's release, and this is about to push me over the edge with Adobe.  I have no issues with other 3D software(maya, blender, fusion 360, houdini) as I am working on a $10,000 workstation designed for this line of work. This software has cost my business a ridiculous amount of time and money all to fall short over and over again.  I am going to be requesting a full refund for the last year, as it continuously does not meet the demands of basic work let alone professional application. I have attached an image below showing what my screen looks like every 2 minutes.

エラー

Hi everyone,   Some of you have reported a blank viewport at launch, preventing the use of the application. After an investigation on our end, it seems to be a compatibility issue with the latest NVIDIA drivers and our latest updates. We are already working on solutions with NVIDIA, but in the meantime, rolling back to version 537.x drivers seems to fix the issue.   We are sorry for the inconvenience, and thankful for your reports.