木洩れ陽のノスタルジーカ – Thoughts

Finally it’s over.

Hm… It started off with a fair bit of potential, it kept this potential up throughout the common route and it was a nice touch for most of the routes to shift the events that happened in the common route by a fair amount. This made replaying a little less boring however, perhaps as a price of this, they created a large irritation. More on that later.

After the events of chapter 1 which I covered in the previous post, they continued on with uncovering Cinema’s functions. Essentially every heroine route revealed a bit more about Cinema and probably more importantly, the identity of the person who created Cinema. The final episode unlocked after finishing all 4 heroine routes shows you the big picture.

Summing things up, Cinema was created as the “daughter” of a genius, and by genius we’re talking about an overall genius. He excelled at every field it seems. In any case, Cinema was stuffed with technology that you wouldn’t imagine to be something 50 years old.

The person who created Cinema, going by the alias of “manager”, was captured by authorities for hacking attempts shortly after hiding Cinema. Because of his capabilities however, he was in the end used as a researcher and produced many results. He met his wife there and had a child. This child happens to be Shouta’s father, making the managers identity to actually be Shouta’s grandfather.

Unfortunately despite being blessed with talent, as if to make up for that, his life was short. Just 15 years after being caught, the manager died of illness. This is going to be a bit of an abrupt jump but essentially Cinema not only has a terrifying hacking program stuffed in her, she also has (omitting explanations) the ability to bring back the past that humanity lost 50 years ago in the war when the data center holding the mass majority of humanities past was destroyed.

It was the result of the manager being undecided on whether or not he should recover the past, as even if the past came back, perhaps humanity will just repeat itself and end up causing yet another war. So he placed a bet and gave the choice to the people who find Cinema.

Well in the end they, or rather Cinema, chose to recover the past and as a result of studying the past as she went through it, came out with a fairly matured personality. Too bad we only got to see it for the last few moments before the story ended.

This summary is probably insufficient and doesn’t make much sense on some counts but I don’t have enough interest to bother with any more detail. In the end, the story basically revolved around Cinema’s growth. I’m pretty sure it was tailored to be a touching story but… it felt like it missed the mark by a bit in that department.

Continuing what I talked about above, as said the story started up with decent potential, the characters are fine and the art is… somewhat hard to get used to as it’s relatively unique but nevertheless still fine. Everything past the first route was a bit bad though. I don’t know why but the story was extremely formulaic. And by formulaic, I don’t mean the sort of “it’s been done 100 times already!” sort of complaint. I mean it’s like the writer had a workflow and tailored the story exactly to that workflow.

Meaning everything (more or less) after common route happened like: Shouta gets confessed to by the heroine. In 3/4 of the cases Cinema is sitting by staring blankly at the entire situation. In 3/4 of the routes Shouta struggles with his feelings for half of the route before finally resolving to the fact that he likes the heroine. In 4/4 of the routes as soon as the relationship is settled something kicks in to move the Cinema related storyline.

Once that is resolved, which typically doesn’t take long as entire routes basically take 1~ hour to finish, the story ends. If you want to know, the only person who slightly deviated from the formula for some reason is Itsuki whom confessed and basically had sex with Shouta right there. Without Cinema’s presence at that. Her story was a bit more interesting but still short. Also makes you wish that Shouta came to conclusions as fast as he did in that route.

Anyway, summing up the issues, they would be that it was a bit lacking in length and more personally I didn’t like how everything seemed to be put together systematically.

I did like how the world was made, once setting aside how ridiculous some parts of it is. It made me wish that we had such technology but at the same time, it also makes me reflect on the fact that even now, we’re fairly blessed when compared to technology a century or so ago.

The AI talk was also relatively interesting to hear, even if it’s technologically unachievable at the moment. It’s nice that they addressed some common doubts you’d hold with AIs, though it appears I was overthinking things with Furou’s route as… well… her route wasn’t much of a rough ride after all. I was questioning how on earth you’d put together an android-human relationship but apparently they were more surprised by the android falling in love and basically shrugged off the rest of the problems as it couldn’t be helped.

Not exactly the answer I was seeking for but it works in its own way. Her route gave a good few laughs. Hearing a discussion about what sort of gentials should be installed onto Furou (as she doesn’t have any by default, why would an android need one?) was pretty surreal.

I’d probably call the story about average and leave it at that though. Honestly could’ve been better but at least it wasn’t a landmine so that’s fine in its own way.

Next up is Love-ressive which I didn’t intend to pick up until I heard it was a good comedy. Let’s see how this plays out.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s