I got my Lumia 800 a few weeks before Christmas. Since then, I’ve used it on a daily basis. I just realized I never actually got around to doing a review. Since I work for Nokia, it is always a bit awkward doing reviews since I can’t basically do a negative review without upsetting some of my peers in Nokia. So, disclaimer: I work for Nokia, any opinions you read here are my own and do not necessarily represent any official Nokia position.
My general solution to this problem has been to simply not do a review of any Nokia product unless I actually like it and won’t have to lie to you. So yes, I’m biased and definitely not objective but at the same time I don’t work for marketing, and definitely would feel bad about propagating lies.
I had no problems doing an N900 review a while back or reviewing the N8. So, now it is the Lumia 800’s turn. The good news is, I like this phone. In fact, like it so much I’d recommend this phone and its little brother the 710 to anyone, including close friends and family whom I definitely would not want to burden with a bad product. To be clear, I don’t take this type of recommendation lightly because if I’m wrong, I basically have to deal with the consequences of people complaining about embarrassing short comings, etc.
Continue reading “Lumia 800”
Today I played a bit more with x-plane. I made two flights. One from Baltimore to Newark (with a King Air 350) and one from Philadelphia to Newark (Piper PA 180). Both planes were downloaded from xplane.org. More such goodies can be found there.
Additionally I played a bit with the graphics settings. What I found out was that the compress textures setting is really important. As noted in my previous post, the thing is mostly CPU bound. More objects require more CPU. However, with things like resolution and texture size, video ram is the bottle neck. Since I have a nice 7800 GT, there is 256 MB of memory. This may seem like a lot but there is quite a bit of textures in x-plane. Yesterday I found that it was impossible to set the texture size to extreme since that caused x-plane to reduce visibility to about a mile to keep up the framerate. Reason: I was running out of vram! The solution for that is compression, this is supported by the videocard and a common strategy for working with high resolution textures. Probably this should always be turned on unless the video card is really old.
With texture compression on (in the x-plane render settings), I can now have mega tons of objects, tons of roads (these are actual x-plane settings), extreme texture resolution and about ten AI planes in the air. That looks nice! Hundreds of textures have been included with the x-plane global scenery and they are quite good (compared to e.g. the shit that comes with ms flightsimulator).
With these settings, flying over New York is workable (though framerate suffers a bit). Outside of the cities, the number of objects is much less of a problem. Besides, most cities are quite a bit smaller than NY.
Another thing I noticed is that the scenery in europe does not appear to include objects. So flying outside of the US is a lot less fun. The Alps though are very detailed. Here the lack of winter textures makes them look unrealistic though. This time of year they should all be snow covered and even in the summer some of them remain snow covered. Not in x-plane. I suppose that is the limitation of the approach taken by the global scenery people (no custom modelling, only take in data from sources like satellite images). However, europe is still 4.7GB of data. Most of this data concerns data coming from various satellite images (high detail). Things like rivers, coastlines, terrain types and elevation are all accurate. So even though Amsterdam does not have objects, it still has the right textures in the right place so you can see where the city ends.