About FMCB v1.8 Installer GUI
On old CRT TV due of overscan effect, I cant see the options and interlace problem hard on the eyes.![]()
|
|
|
|
Would you like to get all the new info from
PSX-Scene in your email each day?
Want to learn more about the team keeping you up to date with the latest scene news?
Read about them now! Check out our Developer bios, too! | ||
|
|
About FMCB v1.8 Installer GUI
On old CRT TV due of overscan effect, I cant see the options and interlace problem hard on the eyes.![]()
I have still using CRT tv and in 1.8 beta's I didn't seen any graphic glitches.
His TV set is probably badly trimmed, so that the edges of the picture go outside the visible area. This could cut off part of the command menu at the top, and also cut off portions of the leftmost and rightmost commands sideways.
I get a very slight such effect on my own CRT TVs, though here all of the command text remains visible, so his TV set must be very badly trimmed indeed. It could also be that there's some difference in the centering for PAL vs NTSC, since I (and presumably you too) only have PAL consoles for testing.
Best regards: dlanor
I also never noticed anything wrong with it during the beta tests with CRT TV or computer monitor.
I myself had no problems with the 1.8 installer on my B&O CRT either. Also, I only had the bad interlacing problems with the FMCB configurator that came with FMCB 1.7 (it obviously always used the NTSC mode on my PAL TV), the latest one seems to finaly run in PAL mode, i.e. not hard on the eyes at all.
Could your issue be similar to the issues I had in earlier versions?
This isn't really a problem with FMCB or the installer, but with the TV in question. Some CRT televisions try to display larger than the physical screen size, causing part of the picture on each edge of th screen to get cut off.
In this case, the installer menu is close enough to the top edge of the screen that the text can be partially, or even completely hidden.
Owning one such TV, I'm quite familiar with the issue.Though I haven't seen any interlacing artifacts, so I'd say that problem may be unrelated.
| « Previous Thread | Next Thread » |