Today is my first day at home after leaving my job at Rockstar San Diego. Deciding to leave was a decision I didn't make lightly and I can only hope my future projects will be as satisfying as Red Dead Redemption.
It is a strange feeling to be on my own again after working so long for and with other people. It is an exciting time for me and I plan to take a some time to absorb the change and reorient to the new situation.
This is a plug in for Microsoft Expression Encoder that allows you to publish directly to your YouTube account.
Please review and agree to the license in the attached zip before use, and then read the installation.txt file for installation instructions.
Thanks
Just starts XSI with memory limits to keep it from going crazy on the virtual memory. If XSI starts using too much memory, memory allocations will begin to fail, preventing XSI from hogging the system. This may and can result in XSI having an application failure of some sort.
It is provided as a Visual Studio 2008 project.
The default memory limit is 1 gig.
You must review the code for correctness and suitability, compile and build it yourself to use.
Use at your own risk.
I've been using the Visual Studio 2008 beta for a while now, and recently I discovered the built in support for unit testing. It's pretty slick, well integrated, and soon I found myself using it to answer some performance questions that had been lingering for some time related to how to best pass large value types around in C#. In my case, I'm interested in Matrix3D, a struct with a 4x4 matrix for a total of 16 doubles in it weighing in at 128 bytes. That's quite a chunk of data to pass in as a parameter to a function or to copy from the stack as a return value. Because I have so much code that depends on passing matrices and other large value types around, I decided to use the new unit testing features to try to measure which approach would produce the best performance. This is what I found out.