fbpx
3 Post Moderation Rule for New Boarders (25 Jan 2021)

New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.

Particles, replicator and fonts are reset when re-opening

More
02 Feb 2016 14:32 #72841 by nicohk92
It's been happening to me for a while now and on different projects.

But now that I'm working on something loaded with particles and replicators, it becomes really bothersome.

Here's the deal:

Everytime I open a project:

- The fonts are a bit screwed up. For example, they are back at regular when I saved them as bold. And so I have to go over each text again to check.

- Both particles and replicators (especially when made out of image sequences)see their start point and start offset reset. I have to go over each one, delete the source, re-import and reconnect for these effects to remember how they were set.


I've tried fixing the fonts, delete prefs, caches and other things offered by the digital rebellion tools but nothing gives.

Has anyone else experienced this?



Thanks

Please Log in to join the conversation.

More
02 Feb 2016 18:41 #72851 by bogiesan
I have not experienced this kind of weirdness.
Do you know someone else who uses Motion? Send them a copy of your project file. If it opens correctly on their system, you've got a bad installation of Motion on yours. If your project does not open properly, you've still probably got a bad installation. For some reason Motion is writing bad files.

Deleting and reinstalling Motion is easy.

Please Log in to join the conversation.

More
04 Feb 2016 11:30 #72904 by nicohk92
Thanks for the reply.

I deleted and reinstalled Motion. It still does it.

I've also tried resetting P-ram or create a new file and copy all layers in it, no success.

I can't use image sequences with my replicators and particles anymore cause their settings are unstable and so I made video files to use instead.

But the problem with the font is constant. some bold portions becomes regular and some regular portions become bold at random either when I'm re-opening the project or when I export from it.

Please Log in to join the conversation.

More
04 Feb 2016 12:01 - 04 Feb 2016 12:02 #72908 by BenB
That was weird... never mind... odd duplicate posting...
Last edit: 04 Feb 2016 12:02 by BenB.

Please Log in to join the conversation.

More
04 Feb 2016 12:02 #72909 by BenB
What OS X version?
What Motion version?
What fonts are you using, exactly?


Run Disk Utility to Repair all drives.
Run Disk Warrior to Rebuild the directories on all drives.

Please Log in to join the conversation.

More
04 Feb 2016 12:08 #72911 by nicohk92
OS 10.11.3
on a late 2013 retina display Mbp with 16g ram

Motion 5.2.2

I tried disk utility and fsck. didn't try disk warrior yet.

Right now I'm trying to see what's up with the font. It's Brandon. I'm using light and bold typefaces in this project.

Please Log in to join the conversation.

More
04 Feb 2016 14:10 - 04 Feb 2016 14:11 #72923 by BenB
fsck is redundant after Disk Utility.

Brandon? That's a third party font. I'd verify it, maybe re-download and re-install, after removing it with Font Book and rebooting my Mac.

Could be the font, not Motion. Try an OS X system font, like Ariel, and see if that has the same issues.
Last edit: 04 Feb 2016 14:11 by BenB.

Please Log in to join the conversation.

More
05 Feb 2016 03:59 #72962 by nicohk92
They removed permission repairs in el capitan so I wasn't sure if fsck was included in first aid. Didn't hurt to do it.

I also rebuilt directories booting disk warrior from a thumb drive. Although it needed rebuilding and made my system a bit faster, it didn't solve the issues with Motion and the font still switches typeface at random.

I'll try your last suggestion.

Thanks


(I don't suppose doing the recent motion update would help would it?)

Please Log in to join the conversation.

More
05 Feb 2016 12:48 #72990 by BenB
Permission repairs is just automatic now. It's just a very simplified GUI, but the functionality is still built in.

As far as the recent Motion update, couldn't hurt. But I honestly think it is the specific third party font. I've seen this several times before with third party fonts.

Please Log in to join the conversation.