Theme portraits

[Agamon]

Since the update, I've noticed the Winter theme I was using for my campaign displays the PC portraits differently than the default theme. Winter theme, the portrait is constrained in a box, like a token. On default, it acts as it did before the update. I use the Big Portraits extension, and the effect is even more obvious with it.
Fantasy Grounds Screenshot 2023.09.16 - 12.25.33.38.png
Fantasy Grounds Screenshot 2023.09.16 - 12.23.23.32.png

Is it possible to make the themes work like default again?

[Zacchaeus]

The default portrait in the Winter theme looks like my image below. That doesn't look like either of your images. So I have to assume that it is the extension which is the problem (even if not enabled it may have left code behind which is causing a problem - or you have the extension loaded twice or some other extension is also affecting things).

Edit: One other thing I though of is whether yous FG client and ruleset is up to date. Can you say what version of the 5e and CoreRPG rulesets appears in chat when you load up.

[LordEntrails]

Yes, but each theme developer will have to update their theme. It will be best to post the details in the thread for each extension so that the theme developer knows and can make the updates.

[Agamon]

Hmmm, it appears I may not have been clear in my post. I'll try again.

Without the Big Portraits extension, yes, it looks as Zaccheaus posted. I'm just wondering why it looks different when using the extension. Is this a theme issue, or an extension issue? Because, as I posted, it looks as intended in the default theme, and worked in the Winter theme before the update.

Is there a thread for FG's themes? I thought since it's an official theme, I should post here.

[Moon Wizard]

This is an extension issue. All the rulesets and themes work together as expected; and the extension is provided by a community developer and is not an official extension.

Regards,
JPG

[LordEntrails]

It's related to the Big Portraits extension and will have to be solved by that developer. It sounds like the extension dev hasn't adjusted their extension to the changes in the window frames.