Great great, Alexander is it fine for modifying the text, if we have an option not to modify the text but modify only the properties? It’s because if I did that, the script would want me to put the new text I need to add or I would get an error message, I’m not sure if it was necessary to say this but I was thinking of it.
You can just input the current text for now.
If you have a suggestion as for how you should be able to do this another way, let me know.
Sure, when I think about it, it might not work lel.
I think I found a little problem, since you added the new property of ScaleSize, it just makes the text disappear instead of resizing it. This goes for any type of the ScaleSize property. And I found the reason why. (This is the Y type of ScaleSize)
So the reason why it’s not showing because it’s ABSURDLY big.
This is an example of an character’s size:
I’m not sure if it’s meant to be like that since it’s multiplying the text size by the screen, but that might be too much.
It’s meant to be like that.
You’re supposed to input a very small decimal.
I could add a warning when the size is above 1, because that would mean one character is larger than the screen.
Can you give me a good number that would probably fit in a Gui?
I can’t really find one good number, even if I put a small number like 0.072 or 0.0072, it’s still going to be the same size… It would be nice if you could explain how it would work.
Or if you want you can look at the code I put in the script.
Well if you divide your desired pixel size by your studio screen size, you should get what you want.
You can find your studio screen size by selecting Camera in Workspace and looking at the ViewportSize property. Obviously you wanna use X if you have ScaleSize X etc.
Kind of works, but one character is just barely in the screen. It’s kind of working but maybe in the fundamentals or fine-control section you can show how to use this property. I’m still kind of clueless Alexander 
.
Do you mean that it’s still very big?
I definitely will update it, going more into detail.
Yes it’s still very big, maybe if it doesn’t work out a little rework could help.
Updating it will help more new users to know what it’s for and how to use it.
The size of it has atleast gone 40% more lower,
which is good:
I found out it actually doesn’t work correctly.
This is because of a previous minimum I set at 1. So you literally can’t go below 1.
In v1.8.1 it has been fixed along with another minor issue related to scale-sizing.
The section for this feature in the tutorial (under Fundamentals) has also been slightly improved.
Hey! Glad to see this resource getting tons of attention and updates since the last time I checked.
I’m having trouble with the LuaXML converter thingy becoming dysfunctional. I think it broke after having been used over and over again (I was testing multiple fonts at the same time LOL). I tried reinstalling it after it broke, but that didn’t fix anything…
Loving the updates so far, but I’m stuck until I figure out how to get the converter to work again. Think you can help me?
The converter had multiple problems previously.
Please verify that you have installed the newest version of LuaXML.
I installed the newest version, like you asked, and tried again.
Nothing — the problem persists. 
Can you send me your folder where LuaXML and your font file is? This way I can reproduce the issue.
The highlighted folder (“Convert Font Map”) is where I have the LuaXML file located. That’s also where I have my font file. I followed the instructions in the forum post, but I still couldn’t get it to work.
All of these files are under Documents.
Can you describe what exactly happens when you open the executable file?
A window pops up for a fraction of a second, which I believe is the executable file doing its work. Nothing else happens after that, even if I wait for several seconds.
Open cmd in the folder and type Convert.exe.
It should show an error.
Alexander in the custom fonts area, can we add extra characters? I don’t know if that would break the script or anything but is it a yes or no?