669GL HDMI Resolution...
I purchased a 669GL double din screen with HDMI input. I have it running on an Asus eee Box, which has Nvidia Ion 2 graphics via HDMI.
So far, the lowest(and only) resolution I've been able to get it to run at without overscanning is 1176x664. While it's nice to have all the real estate, I'd like to run it at a lower resolution. I would imagine the cleanest looking image would be the native 800x480, though when I used powerstrip to force it, it was still overscanning instead of giving a nice 1:1 pixel ratio. There are a ridiculous amount of parameters that can be adjusted in powerstrip, so I may have had something wrong.
I'd like to try centrafuse, and riderunner. At this resolution, centrafuse does fill the screen, however, riderunner seems to stick with whatever resolution the skin happens to be. Any help here would be appreciated.
Does anyone have any experience in what resolutions and settings work best on these HDMI monitors?
Ride Runner can display any skin at any resolution.
Just open the General.ini file in the skin folder
and change the settings of SHOWWIDTH and SHOWHIGHTS
to your screen resolution.
Really? Nobody uses these screens?
What resolution do you guys run your 7" widescreens at?
I've learned to like 1176x664, but I'd like to figure out if other options are available.
bump for same question. I have the same setup and like the OP said, 1176x664 is the only resolution that doesnt overscan.
Anyone else get something lower to work and not shove all the icons off the screen edges?
i had similar native resolution problem with its big brother FA1011: click here
Originally Posted by str8dum
Change the input to 'DVI' on the 669GL, and this should solve the overscan problem (at least it did for me). You don't need to change any of the cabling, just the 669GL input. You'll probably need to recalibrate the touchscreen input afterwards.
I just posted the same info into the sticky "Almost everything you wanted to know about the Lilliput 669GL", assuming it gets approved.
A confirmation that the above solves the issue would be useful for others who might want to use the 669GL.
yup that fixed it! thanks!