johnnovak

Greetings fellow Nim adventurers! Below you will find 16 handy Nim tips & tricks I came across while developing a medium-sized GUI program this year, Gridmonger (and related libraries). Some of them are about less known or undocumented Nim features or standard library functions, a few are workarounds for some rough edges of the language, and there’s also a handful of useful techniques I read about in forums or have invented on my own.

Not divide by two; you have to use the gamma transfer curve.

Looks like you missed all the other artifacts I gave examples for, which are all calibration independent (colour blending, compositing, rendering etc.)

More even = an even gradation from black to white.

If you read the article carefully, you'll realise that this is not just an optimisation (check for example the sections on colour blending and rendering; those artifacts are gamma calibration independent.)

Care to elaborate on the technical inaccuracies you spotted in the article? I would like to correct them, that's why I'm asking.

Thanks for the suggestion, I'll look into the scrset thing!

Yes, we need greater precision, ideally floats, but maybe 16 bits would be enough (haven't tested this or thought much about it.) But for multiple passes of processing floats are definitely the way to go due to rounding errors. I don't think you'd get worse performance when using floats on current hardware.

Instant upvote :)

Cheers, corrected!

That PDF looks excellent, thanks! I will link to it in the further reading section.

I highly doubt you perceive light intensity radically differently to your fellow humans... :) Most likely your monitor is miscalibrated.

Try a few different gamma calibration images from other sources (Google Images -> "gamma calibration") and if they consistently indicate that your monitor is miscalibrated, then you have your answer.

Sorry, I can't magically fix all the mobile device screens of the world so they will start displaying images in a gamma-correct way... The fact is, the owners of such devices will never see gamma correct images on their screens, at least until the manufacturers fix this. It sucks but I can't help there.

Anyway, I think you have bigger problems than gamma with those devices anyway (glare, reflections etc.), so that's probably the least of your concerns.

Thanks, I'm glad you enjoyed the article. The only way I could get Photoshop to resize correctly was to convert the image to 32-bit first, do the resizing, then convert back to 8/16-bit (there might other simpler ways, though, but this is guaranteed to work). The image description actually describes this process.

It's wrong in CS6, and that the only version of Photoshop I could test it with.

Thanks, good catch! No matter how many times I proofread my writings, some of these errors always slip through...

You need to calibrate your monitor then.

Ah, the title again... I'll promise I'll choose my title more carefully next time, so many people are hung up on this...

Thanks for that, I'll fix it later today!

It's not an opinion, check the references section for further info.

It's always refreshing to meet people who never make spelling errors! :) Other than that, try calibrating your monitor!

It's most likely an iPad thing. Try viewing it on a real desktop monitor!

I'd say scanline rendering is "more of a hack" than ray tracing, but both can produce useful looking results, of course. They are both crude approximations of reality, but ray tracing is a closer model and it makes non-local phenomena easier to model (especially if you do things in a physically-correct way, respecting the law of conservation of energy etc.) Arguably, you would end up writing a "Universe simulator" if you wanted to accurately model absolutely everything that's happening in the real world :)

By the way, I've written about this exact same topic in my initial ray tracing post:

http://blog.johnnovak.net/2016/04/28/the-nim-raytracer-proje...