Nicolas314

All my geeky stuff ends up here. Mostly Unix-related

  • About
  • Norhtec Microclient Jr

Worst game eva

Posted by nicolas314 on Thursday 5 January 2012
Posted in: gaming, ripoff. Tagged: assassin's creed II, gaming, ripoff. Leave a Comment
Stay away from this game

Complete waste of time

Imagine you want to try Assassin’s Creed II on your quad-core PC equipped with 4 comfortable gigs of RAM and a decent gamer’s graphics card. Since you have an account on Steam and you trust them, you would purchase it on their site, start the download and expect to play in 1-2 hours.

The actual procedure is a tad more complicated than that, though.

Let me elaborate:

  • Open your Steam client, select Assassin’s Creed II for purchase
  • Your credit card payment is refused, start again
  • After 14 unsuccessful payment attempts, spend an hour on various forums
    to discover variations around “Have you tried turning it off and on?”.
  • Contact Steam support, let them know you cannot purchase on their site
  • Wait a couple of days
  • Get a helpful answer from Steam: “Have you tried turning it off and on?”
  • Wait a couple more days
  • Try purchasing again, just in case: this time your payment goes through
  • Click Install Game
  • Wait a complete night for the download to complete
  • Next day, start up Steam and select Play Game.
  • Wait through DirectX installation
  • Wait through VC++ 2005 re-distributable installation
  • Steam client halts. Re-start it, select Play Game
  • Witness “Startup client installation” for about 10 minutes. This time you get a progress bar.
  • Witness “Startup client installation” for another 5 minutes. Same progress bar, a bit faster this time
  • A login window appears, asking you for a username and password. What? Click “I do not have an account”. Your browser opens up onto the Ubisoft web site, asking you to create an account.
  • You painfully create an account on a page filled up with legalese. You provide your name, birthdate, postal address, email, and authorize Ubisoft to spam you forever.
  • Back to the Assassin’s Creed II login window. Enter the username and password you just created. Get a login error.
  • Open up your email: you see two new mails from Ubisoft. One contains a link to click to activate your account. Click the link. Your browser opens again on the very same account page.
  • Back to the Assassin’s Creed II login window. Enter the username and password you just activated.
  • The next window asks for an activation code that can be found in the box. What box?
  • Back to Steam FAQ: if you need an activation code it will be given to you upon startup.
  • Re-launch Assassin’s Creed II: notice the little window at the bottom of the screen. Copy the activation code to clipboard
  • Back to the Assassin’s Creed II login window. Enter the username and password you already entered twice. Now paste your activation code.
  • Switch to full black screen: admire Ubisoft animated logo
  • Switch to full white screen: an error message lets you know that Ubisoft servers cannot be reached, therefore your game will halt until this is corrected.
  • Follow the only option on screen and quit Assassin’s Creed II. Re-launch
  • Back to Assassin’s Creed II login window. Enter the username and password you already entered three times. This time, tick “Remember me”
  • Admire Ubisoft animated logo, then a couple more animated logos. Get a warning about the fact that people who worked on this game have different religions.
  • A game menu appears. Select “New Game”
  • Wait a couple of minutes for the game to start
  • Actually this is not the game yet. First you absolutely must watch 45 minutes of a bad movie that has nothing to do with a medieval assassin. You cannot leave the movie or skip scenes. You are also not allowed to leave the room during the movie, since you will be requested to press a button at random intervals to show you are still there.
  • You are still not allowed to play the role of a medieval assassin, you must follow a story about some guy who does not understand what is happening (neither do you) but is finally allowed to sit in a chair.
  • At that point you see your first glimpse of a medieval street. It would be tempting to play but keyboard and mouse controls are just impossible to use.
  • Quit the game, hook up an old game controller, let Windows find and install a driver for it, go through controller calibration.
  • Re-start Assassin’s Creed II
  • You notice the framerate is catastrophic. You lower down all graphical parameters until you get something half decent. On a quad-core. With 4 gigs of RAM.
  • You may now try to play Assassin’s Creed II. Pray your Internet connection does not stall, your local, single-player game will not function without it.

The game itself cost me 7 euros on Steam, which sounded like a fair price. On the other hand, waiting several days and spending a complete evening fighting my way through to get a right to play is a bit beyond what I can stand.

I knew I should have downloaded a cracked version. At least you do not need a constant Internet connection or a Ubisoft account, and you get better support from the forums.

Firefox updates are just a pain

Posted by nicolas314 on Friday 11 November 2011
Posted in: firefox, osx. Tagged: fail, firefox, osx. Leave a Comment

Firefox updated itself to version 8 on its own yesterday on my Mac and broke everything. Clicking links mostly does not work. Sometimes it takes a few seconds until the browser reacts, sometimes it does not react at all, sometimes I need to triple-click a link to get a reaction. Images are not displayed correctly: only the upper half is shown and then freeze. Flash does not work either. Typing ‘youtube.com’ in the URL bar does not show anything at all. All my extensions are reported as incompatible. I cannot log into reddit. I cannot log onto GMail. Quitting the browser lets it hang forever and ends up in a Force Quit.

Interestingly, Safari and Chrome have absolutely no trouble whatsoever.

With Firefox’s new way of updating itself like Chrome does, and the soon-to-be absence of version numbers like Chrome does, it is impossible to revert back to a known working browser. Update, and now play a game of find-what-is-broken-and-repair-it-yourself. Lovely.

  • I deleted Firefox and reinstalled. No result
  • I deleted Flash and reinstalled. No result.
  • I saved my bookmarks, moved the Firefox preferences folder and restarted. No result
  • I deleted Firefox, suppressed Flash, removed the Firefox preferences folder, removed everything that contained either Firefox or Mozilla from my account, and then re-installed from scratch. Now it works.

My guess would be that some extension was not successfully updated at some point. Since I have no way of knowing and no interest in pursuing further, I will just leave it at that. Chrome extensions have never choked on an update. To be honest, I have never noticed Chrome updating itself.

This leaves a bitter taste. Seen from here it looks like Mozilla is in awe of what the Chrom team did and desperately tries to replicate it without putting in the right efforts, and certainly not achieving the same level of quality. My trust in Firefox is decreasing with every new release.

Daily Fallacies

Posted by nicolas314 on Wednesday 26 October 2011
Posted in: programming, software engineering. Tagged: fallacies, software engineering. Leave a Comment

To the question: “Why do we do things this way?“, you often get three different kinds of answer:

Argument by Longevity
“Because we have always done things this way”, also known as “It is known.”
Argument by Numbers
“Because everybody does it this way, there must be a reason.”
Argument by Authority
“Because the experts say it must be done so.”

These arguments are examples of fallacies. A large number of examples and counter-examples are provided on the Wikipedia page, I will merely provide some here:

  • Longevity: Humanity has survived 100,000 years without need for toothbrush, therefore toothbrushes are useless for human existence.
  • Numbers: Most people believe that if you toss a coin 10 times and heads come out 10 times, the next time you toss the coin it has less chances of coming up with heads. Therefore it must be true.
  • Authority: My favourite singer votes for candidate X, therefore I will vote for candidate X.

A fallacy derives from the fact that there is no link between the premises, leading to a wrongly acquired conclusion. A statistical fact is independant from belief, it is a mathematical truth that can be demonstrated. Adding more people or time to the fact does not influence the demonstration in any way. Somebody claiming to be a math expert declaring that the 11th toss has different than 50/50 chances could easily be proven wrong.

A science experiment on monkeys was apparently carried out in 1967 (Did the monkey banana and water spray experiment ever take place?). The experiment could be summarized as:

Five monkeys were locked in a cage with a banana hanging from the ceiling. Whenever a monkey tried to get the banana they were all sprayed with ice-cold water. After a while they stopped trying. Next step: they replaced one of the monkeys. The newcomer tried to get to the banana but the others would beat him up before he had a chance, knowing perfectly well that touching the banana triggered a cold shower. The researchers kept replacing monkeys one by one until the ones left had never been sprayed with cold water but kept beating up any newcomer who would dare get close to the banana.

The story is often told to illustrate why large organizations tend to cristallize around age-old processes, even when they stopped making sense a while ago. In fact I have seen it happen in nearly every company I have ever visited, no matter how big or small, in a dozen countries in Europe, Africa, and Americas.

Who has never spent a half-hour filling up expense forms for sums largely inferior to what is actually spent in people’s time filling up and processing these forms? Why should it be done otherwise? The rules are the same for one or a thousand euro expense, everybody has always done it this way and nobody ever complained. I know only one company who would pay systematic and fixed lumpsums for travel expenses. You only had to fill forms if you could justify spending more than the allowance.

Argumenting by authority is quite common in the workplace. An example would be external consultants who come up observing for a day or two, go back to their office and end up sending a large report describing how work processes should be changed without giving any other alternative or trying to argument their suggestions. I have seen that happen more times than I am willing to admit.

I do not believe an expert just because he declares himself such. Experts are knowledgeable people so what I expect from them are clear arguments, new data, and demonstrations. I need to follow the same path if I want to end up with the same conclusions. Of course, a talented and biased expert could only provide data pervasive to the point he is trying to make. This is another kind of fallacy and it is pretty hard to detect as soon as things get outside your own fields of expertise.

Fallacies are common, they are everywhere. We all do it because it is easier than a completely logical train of thought that requires mental exercise. They tend to convince people easily, especially when they end up with a correct conclusion. Example: “Most people these days brush their teeth, therefore it is a good thing. Experts will confirm this.”

Yes, dentists will confirm it. And brushing your teeth is definitely good for your health. But you should do it because it has been proven that it helps you keep your real teeth longer and suffer less from cavities, not just because lots of people do it. Proven? Quite a bit: do a bit of search for yourself (hint: use the tubes, Luke), though this will be left as an exercise to the reader.

Coming back to my field of expertise, fallacies in software engineering are a dime a dozen.

  • A large majority of developers can code in Java, therefore my project should be coded in Java.
  • Many programs I use daily are coded in C++, therefore my project should be coded in C++.
  • 95% desktop users are running Windows, therefore I should use Windows
  • CORBA has been designed by a panel of experts, therefore CORBA is an expert-level technology, I should use it in my project.
  • Software is made of lines of code, therefore coding is all that matters in a software project. A programmer’s productivity is measured in the number of lines s/he writes every day.

A closely-related fallacious trait commonly found among young software engineers:

  1. My program crashes
  2. My code is bug-free
  3. Therefore: the environment around my code is faulty

I once coached an intern who told me: “I double-checked my programs and there are no faults, but the binary crashes every time I launch it so the compiler must have introduced bugs in it.” Other young colleagues have found numerous bugs in interpreters, libraries, the operating system, and when all else fails: blame the incompetent user. Yep, all these things can have bugs, but maybe you should first look into the most recent element added to the system, i.e. your own code, before looking into other directions.

Not a day goes by without meeting a young engineer who lectures me about software engineering, usually answering my “why do you do it this way?” by “this is the way we have always done software here”. I am ready to accept any kind of debatable argument but not the longevity fallacy coming from people who have not defined the rules themselves. If things have always happened this way, what was the reason for it initially? Is it still valid today? Are we in the same context now? Why can’t we touch the frigging banana?

The only lesson I got from this over time is: pick the banana, always. Best scenario: you now have a banana. Worst-case scenario: now you know exactly why nobody touched it, even though nobody could explain it to you before.

Posts navigation

← Older Entries
  • Archives

    • January 2012
    • November 2011
    • October 2011
    • September 2011
    • August 2011
    • June 2011
    • April 2011
    • March 2011
    • February 2011
    • January 2011
    • November 2010
    • October 2010
    • September 2010
    • June 2010
    • May 2010
    • April 2010
    • February 2010
    • December 2009
    • November 2009
    • October 2009
    • August 2009
    • June 2009
    • May 2009
    • March 2009
    • August 2008
    • June 2008
    • April 2008
    • January 2008
    • August 2007
    • July 2007
    • June 2007
    • June 2006
  • Categories

    • android
    • books
    • cyanogenmod
    • darky
    • Debian
    • desktop
    • dns323
    • dockstar
    • dropbox
    • e-books
    • encryption
    • firefox
    • fun
    • gaming
    • gnome
    • google
    • hardware
    • hp
    • iphone
    • ipod
    • junior
    • KDE
    • kindle
    • lego
    • mobile
    • music
    • network storage
    • optware
    • osx
    • palm
    • perl
    • programming
    • python
    • ripoff
    • router
    • software engineering
    • truecrypt
    • Ubuntu
    • Uncategorized
    • Unix
    • webapp
    • windows
    • xfce
  • Recent Posts

    • Worst game eva
    • Firefox updates are just a pain
    • Daily Fallacies
    • iPod on Ubuntu
    • Programming for kids
Blog at WordPress.com. Theme: Parament by Automattic.
Follow

Get every new post delivered to your Inbox.

Powered by WordPress.com