.mischief.mayhem.soap.

Gave tr1::unordered_map a try, it seems to do perfectly average, nothing spectacular, nothing awful, except for predict_grow with 4 byte objects, where it’s almost 10x slower than the next implementation (that’s not an anomaly, it happens every time).

Big weekend news were EA releasing some of their codebase source, including parts of EASTL.

Few years ago I wrote a short article about dealing with heap corruptions (buffer over/underruns).

Recently, I’ve been getting mails asking about license that applies to various code snippets published here.

Few years ago I mentioned a nice little program by SysInternals - Process Explorer (task manager replacement).

Recently, I’ve been experimenting a little bit with different kinds of MT-safe containers.

On Sunday we’ve returned from a short vacations in Cuba.

In my previous note I mentioned that IDs are my favourite form of weak references.

Over the years, I’ve seen plenty of different code bases - open source projects, internal game engines, my own experiments.

One of the most basic truths about optimizing existing code is: there are no low hanging fruits.

Short list of tips & guidelines that every game developer should keep in mind.

Venice is truly one-of-a-kind city.

OK, I’m back.

As I mentioned - I’m flying for a quick vacations tomorrow, so I will not be able to update the GDC links.

About two weeks ago I had my last company beer/good-bye party at Starbreeze.

I’ll keep updating this post with links as I find them.

Data breakpoints are one of the most helpful debugger features when trying to hunt for memory overwrites/ninja variable modifications.

Simple technique that can help in making code more future-proof and easier to modify.

Little challenge posted by a workmate.

Few weeks ago I’ve been watching The Curious Case of Benjamin Button.

Another interesting photo technique (named after Michael Orton).

Been playing a little bit with tilt shift photography today.

Today I’d like to describe a relatively unknown feature of Visual Studio that can be extremely useful in certain situations - remote debugging.

(or rather: how & when to assert).

I played a little bit with my Load-In-Place system.

In a previous note I wrote a little bit about my experimental reflection system for C++.

Whether we like it or no - C++ is an ancient language.

1996 was one of the best PC scene years in my opinion.

I’ve read this note on Rachel’s blog and found out there’s tool similar to Cruncher, just for ELF, named pahole.

Duff’s Device is one of the most brilliant exploits of C syntax.

Everyone who’s done at least some vertex/pixel shader/HLSL programming has probably encountered mechanism called “swizzling”.

Recently, I’ve been reading “Coders At Work” book when commuting to the office.

Another Polish gamedev company.

I’m on a short vacations these days, just got back from Tenerife.

Took me a while to dig through this one, book is over 800 pages.

From time to time, when I have a spare moment, I like to run the game under profiler and see what’s changed since the last test.

Been doing some size/layout optimizations again, recently.

One of the things that game developers hate the most are ‘random bugs’.

Some interesting links: Recast & Detour libraries.

Untitled/Dust is IMHO one of the most underappreciated demos ever.

I’ve found my old USB stick recently and discovered a nostalgic picture there: That’s a photo I made with my cellphone 27th of August 2007, around 5am.

I must admit I kinda agree with Charles Bloom - information is so dispersed these days.

First, there was a NoooN (Ra only, hoped for Karl coding)+Excess+Andromeda invitation… Now, results & releases are available.

You know the drill, will keep adding links here: Beyond Programmable Shading 2009, NVIDIA papers, SG 2009 paper list by Ke-Sen Huang, (both links courtesy of gamedev.pl folks), Light Propagation Volumes in CryEngine 3 (A.

Pretty interesting internal presentation on Netflix company culture.

New Polish development studio, founded mostly by Painkiller veterans, who later worked with me at CDPR for a while as well.

Today I’d like to write about source code scalability in its most literal form, as in true source code scalability, ie - how much one would have to type if he’d want to extend existing codebase.

Just little fix (see original note comments for details) and one column more - padding/size ratio (lets me to find what structures waste most space, in relative terms).

Dropbox - wanted to make some weekend experiments, so finally gave it a try and it really is as good as people say.

As you’re probably aware - there ain’t such thing as ‘too much memory’.