I will fix known problems and try to get it into a pdf format that doesnt destroy the quality of the pictures, many of which should make everyone happy.
Printable View
I will fix known problems and try to get it into a pdf format that doesnt destroy the quality of the pictures, many of which should make everyone happy.
There is only one format of pdf and I've never had any trouble putting a high quality image into it.
Since this is just an overview, 'tag limits' is an alright description. 'Cache tag limits' would be more definitive without going into too much detail which the programmers should be handling and taking care of on teams. The tag index and tag pool memory were both increased. While the tag index increase applies to both development and runtime environments, the tag pool memory only really applies to the runtime (read: cache) environment.
At least Dwood is giving effort; taking a step where others aren't. If anyone wants to give harsh criticism you should think first about what you've done for the community to try and better the problem at hand. Also, I'm pretty sure Constructive Criticism is a requirement in this subforum.
Whelp, I chopped off half the width, shuffled some stuff around, fixed grammar, made it suck less, gave it another new color scheme, etc. I'll edit it one more time and then call it good if no one else has any complaints about it. lookpic, my preferred image host is taking ages but when the current image gets uploaded I'll post it here. E: here being in this post
http://lookpic.com/t/84/B3z0fa7t.jpeg
Crap something's wrong with the upload... my internet sux.
Turns out the other file was corrupted so here: http://dwood15.deviantart.com/art/We...o-OS-156795693
Whelp, something was screwed up with the last one and I had to recover it all from an lolhueg pdf with 8.5" and 11" at 300 pixels per inch. I managed to size it down but if everyone clears all the facts we'll have one final one that has a good format.
http://lookpic.com/t/363/KUhpJCVx.jpeg
Edit: I just realized I left out adding campaigns. Will do that next time around.
Thats pretty cool!
State the name Open Sauce once, then say you will be using the term "OS" from now instead of "Open Sauce".
"I have personally identified 3 parts to Open Sauce"
Change to
"Open Sauce can be split into 3 parts".
"Buildup" is not 1 word.
In the buildup of and for the release of the SDK there was an amazing amount of hype over this mystical extension we call "Open Sauce".
Change to
"There was a lot of hype surrounding the release of the SDK, known as OS"
"Maknig" needs to be "Making"
You clearly state, the programming section is the area that will require the most work, but you fill the information up with just quotes, actually put some information there. Currently "the mapper" section has the most information.
"Currently, this is probably the part in the extension which has the most"..Has the most what? "that needs to be done by the programmer"...Going by the wording, that section should be in the programmer part of your text.
"There's only one way to go about this, and that's by every tool available".
Why is "There's" abbreviated? There is, is the correct grammar. The same goes with "that's", it should be that is.
Heres what I see dwood, I do admire you doing this, and I;m not saying stop, however to me it reads as though your explaining it to some one on MSN, or Xfire. Not an actual written up guide.
My drive died but im trying to recover it... I for sure wont be able to get back the .psd however ill do another if korn asks after os2 is released. Thanks for the crit tho.