Thursday, March 5, 2015

3D: film gimmick, gaming fantasy?

Occasionally I remember a conversation I had about games in which, on discussing how I'd tried out 3D glasses (imagine the old red/blue things) with some games, I was told "3D can stay the f*** out of my games. I was taken aback at the time, and it still seems odd to me now; enough that I've mulled it over sufficiently to want to rant about it.

It's popular these days to either love or hate 3D; however, I think that to do either of these things for all 3D media is misguided.

I can think of some compelling arguments for why 3D simply isn't a good fit for a lot of cinema. Much media has gotten used to being presented from one direction; cinematography and TV is filled with scenes where everything is essentially occurring well away from the camera (in TV shows, especially live ones, this is so prominent that I'd argue this is a significant reason for the relative lack of 3DTV adoption). Additionally, depth isn't a hugely important dimension in storytelling in most films.

As the technology becomes more familiar, I think this will change to some extent. Watching Lindy Beige (not necessarily a film expert, but he is a persuasive talker) in his video on the introduction of 48 fps (particularly his point near the end about zooming techniques), it seems to me that cinematography techniques will always take some time to adapt to new technology. By extension, I think cinema can adapt to 3D... When it feels it necessary. After all, there are numerous theatrical styles, but there are not all adopted all of the time.

The goal behind 3D, in my opinion, is to draw the viewer into the experience. If you were to think of this in theatrical terms it would similar to invisible theater, which brings the action right in front of you. It must be spectacularly difficult to produce a story that is spatially distinct, which you can navigate and interact with; however, games take such an idea and allow you to experience it at your leisure.

In most games, you become an actor in the theater. It thus makes sense to me that if you are an actor in the story then this story should be occurring all around you. What's more, gamers have had the freedom of exploring their game worlds in 3 dimensions (albeit via the 2D of their screens) for years, and while I think 3D is going to take time to mature in the cinema, games developers have been thinking in 3D constantly for years now. Even some existing games would work spectacularly well.

Yes, there will need to be adaptations, but mostly nothing that wasn't already on the to-do list: more detailed actors and props, better physics implementations, and more attention to details such as the placement of actors during important plot points (For example, in Skyrim you may sometimes find other actors or props obscuring your view of someone you're in conversation with). Very few things need to change in games that would be unnecessary if 3D didn't exist.

So, I still disagree that 3D screens/goggles are in any way bad for games. Luckily for those who think otherwise, implementing such technology requires almost no changes to the mechanics of a game, so we both get what we want.

But anyway, give it another 5 years, and no one will want to consume 3D games on a 2D screen any more.

Monday, March 2, 2015

Breathing life into sluggish Android devices: Samsung Galaxy Fame GT-S6810P

Another departure from all things Japanese to talk about making technology easier to manage. In particular, I want to commit to writing the method for installing a fresh operating system on the Samsung Galaxy Fame GT-S6810P (before I forget it). Off-the-shelf, it is atrociously slow, but it can be improved a lot by installing Cyanogenmod 11 on it (nothing miraculous, but it feels much more responsive).

All of the necessary information can be found on this thread; however, having never tampered with my phone at all, it took me a while to get the job done, plus having just installed cyanogenmod on my Nexus 7 I had gotten cockey and by skipping a step got the "status 7" error, which was caused by having the wrong recovery for this installation (see below).

Before proceeding, as with the thread above, you tamper with your phone at your own discretion, preferably with a backup phone on-hand in case you screw up, because I can't help you if you do. Phones come in many models, and some may not be compatible with the following instructions, if you attempt to tamper with your phone without being sure you wont brick it, then it is ultimately your fault when it dies.


0a) Turn on USB debugging on the phone
0b) Get a copy of adb.  You can use adb by going to the command prompt, navigating to the folder where you have adb, and then just typing adb and a command. E.g.
cd C:\Path\To\ADB
 adb devices
the "adb devices" command queries for the plugged in android devices. If you dont see your phone on the list, you will need the USB drivers for the phone.
0c) Get the USB drivers for your phone! I'm not sure if I needed them, since adb recognized my phone without them, but I installed them anyway, so I recommend it.
1) I downloaded ODIN 3.07 (don't forget to virus scan the file, and be careful where you download ODIN, as my internet security went haywire on a couple of sites).
2) I followed the instructions on this post
   2a) I flashed CWM6 using ODIN (turn off the phone. Plug the phone in, then hold the power, home and vol down buttons at the same time - keep holding until the download mode appears - then, in ODIN, add the CWM6 tar file to the PDA section of ODIN and click start)
  2b) in command prompt I ran adb like so:
          adb reboot recovery
  2c) this reboots the phone into CWM6, a recovery system. From here you can sideload a second recovery which is either more compatible with the phone, or more compatible with the Fame version of Cyanogenmod 11. This is achieved by selecting the menu option to install a zip by sideload, then use adb again:

adb sideload C:\Path\To\Recovery\GFameAngerManagementRecovery.zip
and when that is finished:
adb reboot recovery 
  2d) install cyanogenmod through sideload again:
adb sideload C:\Path\To\Cyanogenmod\cm-11-20150129-NIGHTLY-nevisp.zip
  3) At this point, I rebooted the phone (adb reboot) to check that it was usable. Sure enough everything was working. However, there were no google apps. Thankfully, the author provides a link to the google apps on his post (same post as before). This can be installed by sideloading as before (reboot into recovery, then use adb to sideload it in)

Now my phone works better than it has ever worked before. It's slowed back down a little after I choked it with all my "must have" apps, but it is still faster than before the tampering.