What is this error and why am I getting it?
“Warning: could not load font system. Using default font.”
It isn’t using a default font, everything seems to be working, and all looks as expected!? --Using my custom font… Any ideas?
Thanks
What is this error and why am I getting it?
“Warning: could not load font system. Using default font.”
It isn’t using a default font, everything seems to be working, and all looks as expected!? --Using my custom font… Any ideas?
Thanks
Never seen that before.
Is this on OS X, Windows, Android or iOS?
Also what type of custom font are you using, and did you create it?
The messages are on windows… Android has no errors, haven’t checked iOS
Everything is working and looks fine though… that is the weird part.
It is a custom font that I took and modified to my liking.
Sorry, in that case I can’t be of any further help as I don’t use Corona with Windows.
From what you describe it seems to be some issue in the Windows version of the Corona Simulator.
If your custom font is working, this could be a no-harm, no-foul type error that can be ignored. What version of Corona SDK are you using?
2014.2511 : The one released for 64 bit builds
I’m confused. There were some changes around font handling in 2560 which should not happen on on 2511. Still it seems like a harmless error message if things are working.
Rob
Sorry for the confusion… I am using 2014.2511 on my PC, where most of my development is done. This is the version that’s giving me the error.
The 64-bit comment… I don’t use the sim on the mac so I haven’t checked for the same error… But I will on my next build there (which is using 2015.2545 )
It’s likely something weird with Windows. Unless this is causing your fonts not to work or its causing issues on device, I wouldn’t worry about the message.
You could go ahead and file a bug report, but since its on Windows, there are so may possible variants of setups, there is no guarantee we would be able to duplicate it. And since it’s not causing any issues, I would expect it won’t get a high priority when we are deciding what we need to fix.
Rob
So… The errors show up on:
The ipad but not the Mac Simulator (2015.2545)
The win simulator but not the Android Phone (2015.2511)
Super annoying when trying to debug… as It’s repeated over and over… Like when the game inventory is updated.
I wonder if it’s specific to my font?
I assume it’s a TTF font?
If so, and you don’t mind, I could test it on my devices.
I’m only on Mac, but as you said you get the warning on iPad I could test in on my devices.
It would be really easy to test if it’s the font or not.
Never seen that before.
Is this on OS X, Windows, Android or iOS?
Also what type of custom font are you using, and did you create it?
The messages are on windows… Android has no errors, haven’t checked iOS
Everything is working and looks fine though… that is the weird part.
It is a custom font that I took and modified to my liking.
Sorry, in that case I can’t be of any further help as I don’t use Corona with Windows.
From what you describe it seems to be some issue in the Windows version of the Corona Simulator.
If your custom font is working, this could be a no-harm, no-foul type error that can be ignored. What version of Corona SDK are you using?
2014.2511 : The one released for 64 bit builds
I’m confused. There were some changes around font handling in 2560 which should not happen on on 2511. Still it seems like a harmless error message if things are working.
Rob
Sorry for the confusion… I am using 2014.2511 on my PC, where most of my development is done. This is the version that’s giving me the error.
The 64-bit comment… I don’t use the sim on the mac so I haven’t checked for the same error… But I will on my next build there (which is using 2015.2545 )
It’s likely something weird with Windows. Unless this is causing your fonts not to work or its causing issues on device, I wouldn’t worry about the message.
You could go ahead and file a bug report, but since its on Windows, there are so may possible variants of setups, there is no guarantee we would be able to duplicate it. And since it’s not causing any issues, I would expect it won’t get a high priority when we are deciding what we need to fix.
Rob