I told you I could mess up hardware easily, which is why I've yet to build a PC of my own until now (again, a very loose use of "build", there are only three components involved with the Brix). At least nothing electrical or mechanical broke. That was my biggest fear. My cat is nothing but static electricity, so I had to chase her off last night as I put it together. I love her, but I wasn't about to lose $300 due to her "curiosity" :p
NaturalViolence Wrote:Have you tried forcing 1366 x 768 through a custom profile? What GPU do you have?
Sadly yes, but to no avail. It's an Intel HD Graphics (no numbers like 2000 or 3000 were given to the Mobile Ivy Bridge, according to
Notebookcheck. I can "rectify" it using the xrandr command, but not without tearing and lot of experimentation. It's definitely the TV's fault; I've tested 5 other HDMI devices in the past two years (running Windows, Linux, and Android) and each had this issue (3 were fixable to various degrees). Like I said, for some reason, SDL's fullscreen mode results in zero cropping, so whatever it's doing works, but most OSes don't seem to do it themselves.
Anyway, the games just have to play without issue, and so far they do. I don't actually have to see the rest of the OS except for a window (KDE's Kickoff) that pops up (which I've set up to appear "centered" on my TV, same size and position on boot) so I can browse my gaming collection. I envision things going like this:
1) Power up the Brix, autologin into user account. Automatically map joystick input to mouse movements and clicks.
2) Press button on joystick to bring up Kickoff.
3) Browse games, launch with one "click"
4) Play games, live it up, get wild, cut loose
5) Press another button to close the emu, jumps back to Desktop with the menu
6) Power off. Repeat later.
Previously, this was not possible due to the limitations of my Raspberry Pi (not strong enough for a fullblown KDE install) or my ODROID-U2 (Slackware was nigh impossible to install for me, Ubuntu sucks for what I want to do), and neither had QJoypad easily available, which is pretty necessary as I need to just plug in a USB joystick and go. Most of what's left now is the behind-the-scenes Linux work that needs to be done to achieve steps 1 through 6. I've done them all separately as part of different projects and experiments, just have to put them together into the Brix. Having said that, doing an emuconsole really is a lot easier when I'm 1) not messing around with underpowered hardware and 2) not messing around with inadequate software. Slackware "just works" for me, since I've been using it so long (5 years now I think?) and with Mesa and an Intel IGP, there are no iffy GPU drivers and no requirement that an emu supports OpenGL ES 2.0.
The only downside to this purchase: it came at the wrong time! I'm pulling long shifts at work; get there early, leave late. No time to play with toys.