Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Updating a mogrt does not fix font issues

Advocate ,
Sep 16, 2025 Sep 16, 2025

I have a very simple mogrt I've created. It's really just a placholder until I get the proper font, background etc. It's just one block of text that fades on. It's some random font (Calisto) which will do until I get the proper font. I've plopped this mogrt into my sequence multiple times, and edited the text on each one according to the edit's script. Nice.

 

Right - now I have the proper font. I've updated my mogrt comp in AE with the new font, and removed the font overrides that were previously switched on in the Essential Graphics panel (why is this still called Essential Graphics and not Graphics Templates?) in AE. I've exported the mogrt, hopped back to PPro, deleted the old mogrt from my Graphics Templates panel, and dragged in the new mogrt into the Graphics Templates panel. I then alt-dragged this new mogrt onto one of the old-style mogrts in my sequence, and said "yes, I DO want to update all occurrences of this mogrt in the project". Lo and behold......nothing. It's still the same old font.

 

As a test, I then changed the bg colour in AE, end re-exported the mogrt, deleted the old one from PPro's Graphics Templates panel, dragged in the new one, alt-dragged it to replace the old mogrt in the sequence...and the background has updated (on all occurrences) to the new colour. But it 's still the same old (wrong) font.

 

I then tried turning ON the font override options in AE's Essential Graphics panel, re-exporting etc etc, but it's STILL the same old (wrong) font. I've used this mogrt about 20x in my sequence, and would rather not have to go through every one and manually change the font to the proper one...isn't auto-updatery of this kind of thing exactly why  mogrts were invented??!?!?!?!? Grrrrrr.

 

The comp I'm changing in AE is the ONLY comp in the ONLY AE project associated with this PPro project. I have not duplicated nor deleted any comp(s) in AE at all.

Bug Acknowledged
TOPICS
Bug
253
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Pinned Reply

Adobe Employee , Oct 14, 2025 Oct 14, 2025

Hi @hellopaul4,

 

I did some digging. The different behavior from mogrts exported from 24.x versus 25.x was confusing for me, however that qualifies as a bug as opposed to what we're seeing in 25.x. 

When a mogrt is alt+replaced, the expected design is that control values will be preserved (whether or not they've been customized) and added/removed/moved controls will update. We don't know if you've changed the value, or if it's something you wanted to keep or replace when the mogrt is alt+replace

...
Translate
6 Comments
Adobe Employee ,
Sep 24, 2025 Sep 24, 2025

Hi @hellopaul4 ,

 

Thanks for your report. I'm able to repro the issue on our side. I'm thinking this could be fallout from when we expanded text expressions that are now conflicting with the custom font option in the font control. You can workaround the issue if you open the Effect Controls panel and reset the text control to update to the new font after alt+replacing, or by not using the custom font option. I'm going to chat with the team about what we can do here.

 

Sorry for the inconvenience.

 

Thanks,

Theresa

Status Acknowledged
Translate
Report
Community Expert ,
Sep 24, 2025 Sep 24, 2025

@hellopaul4,

 

Kudos for the successful bug report! Your regular participation is a good thing. Staff might have caught this at other points, but perhaps you have saved a bunch of users from frustration!

 

@Theresa Rostek,

 

As always, thanks for the quick repro and (coming soon to a Beta near you) fix.

 

Stan

 

Translate
Report
Adobe Employee ,
Sep 25, 2025 Sep 25, 2025

@hellopaul4 

 

I wanted to clarify, does your text control have Custom Font option enabled or not?

 

-Theresa

Translate
Report
Advocate ,
Sep 26, 2025 Sep 26, 2025

Hi Theresa, 

  • It makes no difference whether or not 'custom font' is enabled. My original comp/mogrt had custom font enabled, then when the updated version did not work, I removed 'custom font' from the mogrt, but it did not help.
Translate
Report
Adobe Employee ,
Oct 14, 2025 Oct 14, 2025

Hi @hellopaul4,

 

I did some digging. The different behavior from mogrts exported from 24.x versus 25.x was confusing for me, however that qualifies as a bug as opposed to what we're seeing in 25.x. 

When a mogrt is alt+replaced, the expected design is that control values will be preserved (whether or not they've been customized) and added/removed/moved controls will update. We don't know if you've changed the value, or if it's something you wanted to keep or replace when the mogrt is alt+replaced. This is where the reset parameter control in the ECP will come into play. However, there were bugs fixed in 25.6.0x102 regarding updating and alt+replacing a a mogrt with an updated text control causing a crash, so use the beta or next release if needing to reset the text control when it uses text properties.

As for the font not updating when alt+replacing if there is no custom font option, it should work as expected and I can't repro it at the moment.

So, the behavior when using font options is as designed, but the workaround should work for you.That being said, this feels like it could lean into feature request territory. If you were to alt+replace something, how would you want to be able to pick and choose what gets updated?

 

Theresa

Translate
Report
Community Expert ,
Oct 14, 2025 Oct 14, 2025
LATEST

Maybe not exactly the same, but feels like it ties into a 'design flaw' that recent changes 'fixed' regarding how EG works when data is altered outside it's comp. Because Source Text houses everything regarding a font rather than just the string of text.

It forced us to use EG base text templates with guide text layers as the EG text input, with the designed text layer sourcetext referencing it, to prevent total mayhem when the design font needs to change, which wasn't the case in older AE before it was possible to expose the styling into the EG panel.

 

https://community.adobe.com/t5/after-effects-bugs/bug-essential-graphics-font-styling-not-updating-a...

 

Translate
Report