Page 2 of 3

Re: returned back to 2.5

Posted: Sat Nov 27, 2021 10:14 pm
by davoodice2
house10 wrote: Tue Nov 23, 2021 2:54 pm d lastest version is nothing to write home about,

still trying to make a 2.5d mesh its will crash.
2 out of 10 times psd work file else u get a missing file
later i was getting a script issue.

3.5.2 should be removed
If you created custom folder in library, remove that, I have this problem before because of that.

Re: returned back to 2.5

Posted: Mon Nov 29, 2021 4:43 pm
by synthsin75
When you're having so many problems that others are not having, the problem may be you.

Re: returned back to 2.5

Posted: Mon Nov 29, 2021 7:56 pm
by synthsin75
house10 wrote: Mon Nov 29, 2021 6:16 pm
synthsin75 wrote: Mon Nov 29, 2021 4:43 pm When you're having so many problems that others are not having, the problem may be you.
when am having problems n u not d issue might just be u also.
or what u think
Yeah, that must be it. I'm the problem because the software works fine for me. I must have cursed your copy or something. I'm a terrible person.

Re: returned back to 2.5

Posted: Mon Nov 29, 2021 11:08 pm
by Greenlaw
house10 wrote: Mon Nov 29, 2021 8:50 am someone said import as png instead of psd.
wow really.
I thought I clearly explained why you might want to do that instead. IMO, in 13.5.2, either PSD or PNG works fine in many situations but there are specific differences in behavior. You should choose the method that works best for your production or workflow.

In my case, PNG worked better in the past (pre-13.5.2) for the reasons explained. At present, I think PSD will work fine for me because of the recent updates. TBD since so far I've only used the new PSD features in tests, not on a production level project.

Hope this clarifies why this was my suggestion.

Re: returned back to 2.5

Posted: Mon Nov 29, 2021 11:13 pm
by Greenlaw
I'm curious but are you using any non-English characters in the path or filenames? That seems to be a common link between the few users who are having problems with the latest build.

I know the path naming issue was worked on in the previous build but maybe something got broken in the latest. In any case, using 'safe' naming conventions seems to solve this problem for now. (FWIW, I always use 'safe' names in every program I use just to avoid potential network problems.)

Re: returned back to 2.5

Posted: Tue Nov 30, 2021 3:24 am
by synthsin75
In the entire path to the PSD file?

Re: returned back to 2.5

Posted: Tue Nov 30, 2021 3:54 am
by Greenlaw
Oh, I didn't even think about layer names. Yeah, layer names too, but maybe more importantly path and filenames.

Re: returned back to 2.5

Posted: Tue Nov 30, 2021 5:29 pm
by synthsin75
Doesn't matter what you name each file. If there's a non-English letter anywhere in the destination path of that file, it could be the problem.

Or just give it a miss and enjoy 12.5.

Re: returned back to 2.5

Posted: Tue Nov 30, 2021 5:40 pm
by Greenlaw
I wonder if it has to do with the source of the file. Which program created the PSD? Maybe there's a setting required to make it more compatible?

Even when exporting a PSD from Photoshop there are settings necessary to insure compatibility with other programs like Moho.

TBH, if I was having this much trouble with layered PSD's, I'd switch back to PNG layer exports. It's pretty easy to do with the export layers scripts for Photoshop and Krita I described elsewhere.

There is also that Export Layers To Moho script that comes with Moho. This script tells Photoshop to save PNG layers and then it creates a Moho project file for you with the PNG layers already in place. The project file it creates is .anme but this coverts on import for 13.5.2 just fine.

To be clear, so far I'm not seeing problems with the new Layered PDS feature but, as mentioned, I'm still testing this feature for full production use. At this time, if I was using Moho for an actual commercial production (like at my workplace,) I'd still be using PNG layers because I know this works reliably.

Re: returned back to 2.5

Posted: Wed Dec 01, 2021 12:50 am
by chucky
House10 , are you naming every layer of the PSD file with a unique name?
IT won't work otherwise, why don't you upload the file for us to look?
if you are sensitive a the contents erase the images but lave the layers as you have them.

Re: returned back to 2.5

Posted: Wed Dec 01, 2021 5:17 am
by Greenlaw
I think the system falls back on layer id if there's a layer naming conflict (e.g., two layers with the same name.) But I haven't stress tested that situation yet.

Re: returned back to 2.5

Posted: Wed Dec 01, 2021 5:29 am
by chucky
Greenlaw wrote: Wed Dec 01, 2021 5:17 am I think the system falls back on layer id if there's a layer naming conflict (e.g., two layers with the same name.) But I haven't stress tested that situation yet.
I've not seen a file work with conflict, it just breaks the file as far as I've seen

Re: returned back to 2.5

Posted: Wed Dec 01, 2021 7:08 am
by synthsin75
What is the full path to your PSD location?

Re: returned back to 2.5

Posted: Wed Dec 01, 2021 4:26 pm
by synthsin75
house10 wrote: Wed Dec 01, 2021 7:45 am
synthsin75 wrote: Wed Dec 01, 2021 7:08 am What is the full path to your PSD location?
what
Where is the PSD file located on your computer? Something like: C:\Users\*user*\Desktop\Example.psd

Re: returned back to 2.5

Posted: Wed Dec 01, 2021 10:23 pm
by synthsin75
house10 wrote: Wed Dec 01, 2021 9:30 pm
synthsin75 wrote: Wed Dec 01, 2021 4:26 pm Where is the PSD file located on your computer? Something like: C:\Users\*user*\Desktop\Example.psd
desktop in a folder for moho files
What is the literal path? The whole thing.