Comments for GameClay

Comment on Assigning Per-Shape Shader Values in Torque3D by Daniel Buckmaster

Daniel Buckmaster — Thu, 03 Feb 2011 06:00:03 +0000

Brilliant! Your articles have really helped me get started with T3D’s new graphics features… I’d love to see more written on these sorts of subjects, it’s incredibly helpful!

Comment on Assigning Per-Shape Shader Values in Torque3D by Ross Pawley

Ross Pawley — Sat, 25 Sep 2010 17:58:52 +0000

Nice article Pat! It seems that adding TSRenderState paid off even more than I’d hoped

Comment on Build it Like GameClay by FuzzYspo0N

FuzzYspo0N — Thu, 09 Sep 2010 15:49:30 +0000

Another fine post indeed, Pat.

Comment on Working with Git at GameClay by Sagan

Sagan — Fri, 14 May 2010 22:39:09 +0000

http://whyhgisbetterthanx.com/

Comment on Extending the Torque3D Material System by JoZ

JoZ — Tue, 16 Mar 2010 23:11:44 +0000

Tnx Pat, very very usefull… By the way tnx also to Konrad for mentioning a link to this!

Comment on Build it Like GameClay by Novack

Novack — Tue, 16 Feb 2010 13:56:22 +0000

Excellent, much appreciated!
Indeed, there you have material for another post

Comment on Build it Like GameClay by Pat Wilson

Pat Wilson — Tue, 16 Feb 2010 05:24:59 +0000

The CI Joe builder command is a ruby script which runs the generateProjects.bat and (slightly modified) compile.bat files from Torque3D. If the build worked, CI Joe executes the .git/build-worked hook, and that hook is coded to add the .EXE and .DLL into a ZIP file and make it available via a Sinatra route.

There is a bat file in the project that looks like this:

util\curl\curl.exe https://server:port/route > latest.zip util\7za.exe e -ogame -y latest.zip del latest.zip

This uses a CURL command (which can be customized to include authorization etc) to download the zip file which was built by the CI Joe server, and extract the needed EXE/DLL files to the non-coder’s machine. I should probably do a blog post on this part of the process as well.

Do NOT zip assets into big files. That was part of the “bad” example hehe. It does terrible things to the size of the repository, and is really not a correct use of version control.

Comment on Build it Like GameClay by Novack

Novack — Mon, 15 Feb 2010 21:59:10 +0000

Awesome post indeed!

Im curious about what each build process involves, specially under windows, a bat file? How deep into this processes you use ruby? Would be intersting to hear some experiences on the low level, as how you made the handled the process of building, packaging and uploading to a repo the latest build, in the different plataforms.

For the wip art assets, we just use a different folder in the svn, so the standard update doesnt get cloged with them. Why zip’em into big files?

Comment on Build it Like GameClay by Timothy Aste

Timothy Aste — Mon, 15 Feb 2010 01:15:29 +0000

Awesome blog Pat. I love build servers and fresh binaries since we know how well artists trying to compile code goes.

One thing that has worked out pretty well for the last few projects on the art side strangely enough is Dropbox. It keeps a 30 day history of files and allows us to share and keep art source files in one spot without bloating SVN for everyone else. Love me some Dropbox.

Comment on GameClay Moves In by Novack

Novack — Fri, 22 Jan 2010 00:31:42 +0000

Hey Congrats and good luck!