Large texture file sizes not importing to object

I'm not clear what's happening here. It looks like you went to Adobe Stock from Stager via the CC desktop app, and you found and presumably downloaded the material.

I don't have any problem importing that material and even larger scan-based materials to a simple object using the File menu or by dragging and dropping from Bridge or the OS. It takes only a couple of seconds. I'm on a more powerful machine with GPU support, but even so, you should see decent performance.

Try to narrow the target. What kind of object are you trying to apply the material to? If it's an externally created model, can you import that material onto a sphere or cube from the Starter Assets? (If so, neither the material nor Stager's import function is likely to be the problem.) Can you apply complex Substance materials from the Starter Assets to the model, and do they show up correctly? Does the model have UVs, or do you need to generate them?

From my experience with .obj exports from other CAD programs, I suspect that shapr3d's .obj export may be the source of a number of problems. CAD programs "think" entirely differently from a 3D authoring tool like Maya or Poser and from vector design tools like Illustrator. (Open any architectural drawing .dxf in Illustrator and you'll see.) They are fundamentally different in focus and architecture from 3D CGI/art/design tools. Add to this the fact that .obj is not a rigid standard.

There is a similar situation with PDF. Many applications can export a PDF, and there are many PDF readers out there, but not all PDF exports support all PDF specifications, which leads to unexpected results. A PDF from AutoCAD is a very different beast from a PDF exported by InDesign.

I'd suggest that anytime you run into a problem and it involves a CAD-generated model, check whether you can recreate the problem using a model from the Starter Assets or another known good model. Always send a sample to the Stager team via substance3d-bugs@adobe.com for them to take a look at.

If you've verified that the CAD-generated .obj file is not the source of the problem, post here with all the details.