Thanks for testing. If I can't solve it by scaling the texture, maybe @Berion should use a bigger or boldface font.It is almost impossible to read the sub-line in my TV.
This is how it looks on the PC in the emulator... Even here the first E in "Designed" is hard to read:
View attachment 34677
@Berion
Closest thing to you are asking for is OpenTuna. On the other hand, OpenTuna payload ELF can be converted to an OSDSYS update KELF and signed against MG by using FMCB installer after replacing FMCB.XLF.@alexparrado can a memory card version be possible for slim ps2s? also can you change ule to square button as if you keep circle pressed when ule boot it messes up the default elf timeout
Does it init the OSD? Else, I don't advise doing that...On the other hand, OpenTuna payload ELF can be converted to an OSDSYS update KELF and signed against MG by using FMCB installer after replacing FMCB.XLF.
No, it doesn't. Maybe it could be done after performing initialization procedure described by sp193 (https://sites.google.com/view/ysai187/home/projects/initializing-the-ps2psx#h.p__bgtylxLfxfg). Do modchips initialize when user directly boots with dev1?Does it init the OSD? Else, I don't advise doing that...
Could You attach screen from emulator in native PS2 resolution?This is how it looks on the PC in the emulator...
Check below images for PAL and NTSC.Could You attach screen from emulator in native PS2 resolution?
Ok. I'll test later.I'll make 32bit and will try the results, ok?
no they dont neither do older fmcb releases before the splash screen was addedDo modchips initialize when user directly boots with dev1?
There you go, I don't see major difference.Pleas, try all three, and show us screenshot (NTSC one is sufficient).
Not every modchip does thatNo, it doesn't. Maybe it could be done after performing initialization procedure described by sp193 (https://sites.google.com/view/ysai187/home/projects/initializing-the-ps2psx#h.p__bgtylxLfxfg). Do modchips initialize when user directly boots with dev1?
1-The background is 640x480 but the NTCS screen is 640x448. Please, trim the image a bit or set NTSC to 640x480 (also valid)Check below images for PAL and NTSC.
Not true. Latest Matrix versions does initializes the system (at least the language is displayed properly)no they dont neither do older fmcb releases before the splash screen was added
I have no way to test if they do a complete init, but at least Matrix does partially (assumed, maybe complete) on latest versionsAre there ANY modchips which do initialization on the DEV.-modes? I mean COMPLETE init? AFAIK all of them either don't do it or only partially at best.
Yeah, they looks exactly the same. :/ Do You have maybe any idea what can cause this on code side?There you go, I don't see major difference.
Yes, damned texture filter!!.Yeah, they looks exactly the same. :/ Do You have maybe any idea what can cause this on code side?
It looks better now...Yes, damned texture filter!!.
I'm not checking available space at the moment. But it can be easily added.If I will fill "hdd0:/__system" enough to not left space for OPL+uLE, it should appears, right?
I tried to use freetype library along with the font file you provided at first, however I couldn't make it work with none of the backgrounds, it only worked with black background.It is possible to use TTF with crisp edges
I'm using fontm which is the ROM font in console.If You are using bitmap fonts, how did You create it (by what application)?