|
|
Post by Callisto-Sims on Jan 13, 2017 19:58:45 GMT -5
Okay so I had taken BG poster and done a bunch of pictures on it, ofc. I tested it a few days ago and everything worked fine. And now, I've removed/added some swatches and when I go to test there's a transparent ? over it and the catalogue image displays really far away and some swatches don't show at all. PLEASE can someone tell me how to fix this asap?! I've started a new package & it looks fine in S4S.
|
|
|
|
Post by inabadromance on Jan 13, 2017 20:20:13 GMT -5
hi! There's a new s4s version. I would suggest re doing the package with this version. |
|
|
|
Post by Callisto-Sims on Jan 13, 2017 20:26:58 GMT -5
I've already updated it to the most recent patch and it's still not working. A poster I made a few days to a week ago, which uses the same poster, works perfectly fine. & this one I did have, a HP collection worked when I first made it and now it doesn't. Appears fine in S4S, but there's a giant ? over them all and some don't show at all. inabadromance |
|
|
|
Post by inabadromance on Jan 13, 2017 20:28:25 GMT -5
Can you please share the package file?
|
|
|
|
Post by Callisto-Sims on Jan 13, 2017 20:31:36 GMT -5
Can I private message you it? I'm not wanting it released yet.
|
|
|
|
Post by orangemittens on Jan 13, 2017 21:09:21 GMT -5
pixo, we just released a new version of Studio less than 2 hours ago. If you cloned this or worked with it using the version of Studio that was updated yesterday, the .package is most likely corrupt and you will need to reclone using the new version. The new version is a hotfix version for a critical bug that was in last night's version.
If you cloned the item with Studio 3.0.0.7, post the .package or PM it to me. Include any images or .blends you've imported into it. Also, please do not post about the same issue in multiple places.
|
|
|
|
Post by Callisto-Sims on Jan 13, 2017 21:41:06 GMT -5
The original package was made like 3(+) days ago and it worked perfectly fine. I updated the studio twice and I'm still having the same error.
I've made package after package with it updated, and I'm still having the error. I didn't mean to post the issue in other places, I just wanted to report the error message I got and figured I should say what it was relating to, sorry.
|
|
|
|
Post by orangemittens on Jan 13, 2017 21:45:07 GMT -5
No worries. If you send the .package and related files I can take a look.
|
|
