# Font Previews

**URL:** <https://forum.logik.tv/t/font-previews/7063>\
**Category:** Flame Questions\
**Tags:** text\
**Created:** [November 8, 2022, 2:25pm UTC](https://forum.logik.tv/t/font-previews/7063 "2022-11-08T14:25:12Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lightningad](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/lightningad/32/2191_2.png) [@Lightningad](https://forum.logik.tv/u/Lightningad)\
**Post date:** [November 8, 2022, 2:25pm UTC](https://forum.logik.tv/t/font-previews/7063/1 "2022-11-08T14:25:12Z")

</div>

Anyone know of a way to get Flame to show letters other than Aa on all the previews for font selections?

When trying to match fonts its almost never the A that’s the relevant shape that needs to be found!

adam

---

<div class="post-metadata">

**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\
**Post date:** [November 8, 2022, 3:57pm UTC](https://forum.logik.tv/t/font-previews/7063/2 "2022-11-08T15:57:30Z")

</div>

Near the bottom of the init.cfg file there is a line. If it’s commented out I think it defaults to Aa. I seem to recall trying to change it once but don’t remember if it worked. I think you might need to wait for it to regen all the proxies. I have over 4000 fonts.

---

<div class="post-metadata">

**Author:** ![Lightningad](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/lightningad/32/2191_2.png) [@Lightningad](https://forum.logik.tv/u/Lightningad)\
**Post date:** [November 8, 2022, 4:08pm UTC](https://forum.logik.tv/t/font-previews/7063/3 "2022-11-08T16:08:56Z")

</div>

thanks Tim…i’ll check that out when i get a chance.

---

<div class="post-metadata">

**Author:** ![Sinan](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/sinan/32/155_2.png) [@Sinan](https://forum.logik.tv/u/Sinan)\
**Post date:** [November 8, 2022, 4:16pm UTC](https://forum.logik.tv/t/font-previews/7063/4 "2022-11-08T16:16:52Z")

</div>

If you use the Text module to write your text, and go to change your font, your text will be used as the preview text.

Ah but you need to select the font for that. My bad.

---

<div class="post-metadata">

**Author:** ![Lightningad](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/lightningad/32/2191_2.png) [@Lightningad](https://forum.logik.tv/u/Lightningad)\
**Post date:** [November 8, 2022, 4:31pm UTC](https://forum.logik.tv/t/font-previews/7063/5 "2022-11-08T16:31:17Z")

</div>

it’s more a problem with the small preview of each font - when you have hundreds its a pain having to select each font to see the full preview. Often the Text i’m matching doesn’t even have an A or a, and one of the letters has a certain style - so if i could set that letter as the reference, it would be much easier to scan through the list of fonts.

---

<div class="post-metadata">

**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\
**Post date:** [November 8, 2022, 6:20pm UTC](https://forum.logik.tv/t/font-previews/7063/6 "2022-11-08T18:20:36Z")

</div>

The text module could use some modernization. The last update was when they deprecated cuniform.

---

<div class="post-metadata">

**Author:** ![johnag](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/johnag/32/573_2.png) [@johnag](https://forum.logik.tv/u/johnag)\
**Post date:** [November 12, 2022, 11:07pm UTC](https://forum.logik.tv/t/font-previews/7063/7 "2022-11-12T23:07:52Z")

</div>

Yes font matching is a pain. What I do sometimes is use a web service called “what the font” to get me the name of the font I’m matching to.

> **[WhatTheFont Font
            
           
           
          
           
  ...](https://www.myfonts.com/pages/whatthefont?gclid=Cj0KCQiApb2bBhDYARIsAChHC9tBL-VXg-fykpm0u5_K7QJLmLUUeIxlPeBkUDmPTnmufNPxvcUv0RkaAqMQEALw_wcB)**

---

<div class="post-metadata">

**Author:** ![digitalbanshee](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/digitalbanshee/32/1160_2.png) [@digitalbanshee](https://forum.logik.tv/u/digitalbanshee)\
**Post date:** [November 13, 2022, 3:40pm UTC](https://forum.logik.tv/t/font-previews/7063/9 "2022-11-13T15:40:54Z")

</div>

Yes! I always start here.

---

<div class="post-metadata">

**Author:** ![GPM](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/gpm/32/4224_2.png) [@GPM](https://forum.logik.tv/u/GPM)\
**Post date:** [November 13, 2022, 6:30pm UTC](https://forum.logik.tv/t/font-previews/7063/10 "2022-11-13T18:30:46Z")

</div>

Is Flame text used for anything but legal disclaimers? Going strong since 1997!

---

<div class="post-metadata">

**Author:** ![Lightningad](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/lightningad/32/2191_2.png) [@Lightningad](https://forum.logik.tv/u/Lightningad)\
**Post date:** [November 13, 2022, 7:42pm UTC](https://forum.logik.tv/t/font-previews/7063/11 "2022-11-13T19:42:59Z")

</div>

I use it, specially when I don’t need anything too complex.

---

<div class="post-metadata">

**Author:** ![johnag](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/johnag/32/573_2.png) [@johnag](https://forum.logik.tv/u/johnag)\
**Post date:** [November 14, 2022, 8:55am UTC](https://forum.logik.tv/t/font-previews/7063/12 "2022-11-14T08:55:56Z")

</div>

I recently used it in a motion graphics job.

---

<div class="post-metadata">

**Author:** ![Owen](https://avatars.discourse-cdn.com/v4/letter/o/b2d939/32.png) [@Owen](https://forum.logik.tv/u/Owen)\
**Post date:** [March 23, 2023, 6:04pm UTC](https://forum.logik.tv/t/font-previews/7063/13 "2023-03-23T18:04:12Z")

</div>

Why can’t you cycle through fonts with the up and down keys? Drives me mad.  
Also in older versions of flame when you went back into the text tool it took you to the font you had selected… now you have to scroll down to find it.

Its the little things!

---

<div class="post-metadata">

**Author:** ![AndyBrown](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/andybrown/32/708_2.png) [@AndyBrown](https://forum.logik.tv/u/AndyBrown)\
**Post date:** [March 23, 2023, 6:10pm UTC](https://forum.logik.tv/t/font-previews/7063/14 "2023-03-23T18:10:35Z")

</div>

I once did a graphics job using 3D text and Wingdings. Pushing the envelope…

---

<div class="post-metadata">

**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\
**Post date:** [March 23, 2023, 6:44pm UTC](https://forum.logik.tv/t/font-previews/7063/15 "2023-03-23T18:44:56Z")

</div>

Don’t get me going . . . .

---

<div class="post-metadata">

**Author:** ![johnag](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/johnag/32/573_2.png) [@johnag](https://forum.logik.tv/u/johnag)\
**Post date:** [March 31, 2023, 7:44am UTC](https://forum.logik.tv/t/font-previews/7063/16 "2023-03-31T07:44:14Z")

</div>

> [@Owen](#):
>
> Why can’t you cycle through fonts with the up and down keys? Drives me mad.  
> Also in older versions of flame when you went back into the text tool it took you to the font you had selected… now you have to scroll down to find it.
> 
> Its the little things!

I have a request in to fix or add that back in.  
I’ll see if I can find it. It was a couple of years ago now.

---

<div class="post-metadata">

**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\
**Post date:** [March 31, 2023, 2:20pm UTC](https://forum.logik.tv/t/font-previews/7063/17 "2023-03-31T14:20:48Z")

</div>

Text is so old, particles calls it grandpa. . . . . We’ve been asking for updates for text for 20 years or more. Just bring it up to the 21st century is all I ask.
