Thread: Can't View TGA files.

Originally Posted by MaKe_OuT_33

i did the same thing hub. i found that you can go into your config and where your bind F5 key is you should change it to jpeg. i forget the exact command but if you use google search you will find the suggestion.

The console command is "screenshotjpeg". I use it.

There are many free programs that can view TGA. Irfanview is a good one. But I don't think saving in TGA is worth it*** (even though I am a photographer and a file format snob). The TGA's can be a couple MB depending on your resolution, and the JPG's are so much smaller.

*** for something as simple as a screenshot, which btw most people butcher when they webpost anyway and make completely illegible. Someday I'm going to make a tutorial about posting screenshots that you can actually read.

Originally Posted by Veovis

id appreciate the tutorial as everytime i post a screenie, it is too small to read. its not a thumbnail or anything that small but it is impossible to read any text. what i do is upload the jpg file to photobucket and post the img code in the forum. even when you click the image to make it bigger, it is still illegible.

Well in short, here it is. The maximum image width allowed on TTP is 700 pixels. If you post an in-line image that is larger than 700 pixels, it will be re-sampled in your browser and will end up looking all pixelated since web browsers do a shitty job of re-sampling. So, you must re-sample it yourself in a decent image editing program (Gimp is free) first, so it is no wider than 700px (all this takes is a simple "scale" operation). Then it gets posted at "full" resolution in the browser (meaning the browser won't have to re-sample it).

Here is an example, but not as bas as in some other cases (I'll explain why):



[img width=750 height=468]http://www.matthoover.com/tf2/tf2_screenshot_05_bad.jpg[/img]

Try reading the text at the very bottom (captures, defenses, domination, etc).

The text is much harder to read in the second example. The first example is a true 700x438 image. The second example is a 1680x1050 image that TTP is forcing to be 700x438 in your browser so it gets rendered poorly. I've seen it happen even worse, and I suspect what's happening is that somebody uses a Photobucket account or something similar (I use my own webhosting) which re-samples the images once (but larger than 700px wide) and then TTP re-samples it again at 700px wide and it ends up REALLY illegible (from being web-resampled twice in a row... it's like making a cassette tape copy of a cassette tape copy... it will sound like crap).

Keep in mind, that at this small scale you are never going to get an image that is perfectly legible. But that's no excuse to do stupid operations on it that make it 10x worse.

Hope that made sense for you...

You can also run a sharpening on the image AFTER final re-sampling with your image software... that will make the text pop more.