February 26, 2013
This is not going to be a technical blog, but rather my final thoughts on the GSP 261 class as a whole.
This was the first GSP class that I actually had to sit down and think about what I was doing. I am not the world's greatest modeler, but I can do somethings fairly well and can work my way around Maya. Having to learn 3DS Max was a huge threshold for me as I do not entirely like the program. I feel that Maya is a much better modeling program, and Max should really only be used for animating. But, those are just my thoughts on the subject. The part that I had the most trouble with was the character modeling and animating. I learned very quickly that I was not cut out to be a character artist nor an animator, and not everyone is. Shannon was an amazing modeler and animator, and I was lucky to have her in my group. Matt was an amazing modeler as well, as he has had years of experience working with Max. I picked a pretty decent group.
Every other part of the class was relatively easy, but some were more tedious than others. The audio portion of the class was probably the most tedious, as only certain effects could generate the sounds you were looking for from the source audio. It did get easier as I worked on more pieces of audio, and in the end I was able to produce some pretty decent sound effects, for being a student that is.
The cinematic turned out fantastic. There were a few things pointed out to us during the presentation that would have made it so much better, but in the end we produced a very respectable cinematic. Every part came together beautifully and seamlessly.
I enjoyed this class very much, and I will be able to use what I learned in almost all of my forthcoming classes.
Tuesday, February 26, 2013
Friday, February 22, 2013
Group Update #4
February 22, 2013
I know this is horribly late, but I still need to get it done.
The group has gotten all of the audio bites done and imported into UDK. I began, on Tuesday, by first making a Matinee sequence in Kismet and setting up all of the cameras we were going to need. Here is a screenshot of the final Matinee sequence with everything added and animated:
As you can see, it is quite a complex mess. This is our first real work done with Matinee, and I think we did pretty well. The cinematic came out to be exactly 2 minutes long, which was a real shock as I had some reservations about how much content we had and if we were even going to make it to 1 minute. I did run into a ton of problems doing this cinematic, however. Most of the issues arose from movement tracks for different groups, but the main one was the chase camera we use to show the main character from behind. This camera was a complete and total mess to work with. Whenever I tried moving the camera and setting a new key in the movement track, after one had already been set, the camera would move in weird ways. I also ran into an issue with Matinee itself, as when I would close the Matinee editor, it would sometimes move things around that were supposed to remain where they were originally located. The main culprit was the chase camera for the main character. That was a complete nightmare. I am still having an issue with playing the cinematic in PC mode. The issue is that the PC mode will come up, but crash before it even gets to the cinematic. It is really irritating.
The cinematic is finished now, I am just waiting for an email back from the professor regarding the crashing issue. Otherwise, all is good.
I know this is horribly late, but I still need to get it done.
The group has gotten all of the audio bites done and imported into UDK. I began, on Tuesday, by first making a Matinee sequence in Kismet and setting up all of the cameras we were going to need. Here is a screenshot of the final Matinee sequence with everything added and animated:
The cinematic is finished now, I am just waiting for an email back from the professor regarding the crashing issue. Otherwise, all is good.
Tuesday, February 12, 2013
Group Update #3
February 12, 2013
This week our group put together the environment that our cinematic will take place in. The level was built in UDK using Additive Geometry, with Subtractive Geometry used to make doorways. This process was relatively easy for me, as I have done it so many times before. I build the level, Matt added in the lights and Matinee for flickering lights and Shannon found textures for all of the walls, floors and ceilings. Here is what the main laboratory chamber looks like in the editor:
I really do think the blue specular color is a nice touch. I do not know how Shannon managed to get that effect into the specular map, but it looks really cool. The idea is to have the hero, Jane, run through an abandoned asylum full of mutants. The initial entry point and first area where action will take place looks like this:
This week our group put together the environment that our cinematic will take place in. The level was built in UDK using Additive Geometry, with Subtractive Geometry used to make doorways. This process was relatively easy for me, as I have done it so many times before. I build the level, Matt added in the lights and Matinee for flickering lights and Shannon found textures for all of the walls, floors and ceilings. Here is what the main laboratory chamber looks like in the editor:
I really do think the blue specular color is a nice touch. I do not know how Shannon managed to get that effect into the specular map, but it looks really cool. The idea is to have the hero, Jane, run through an abandoned asylum full of mutants. The initial entry point and first area where action will take place looks like this:
Around the corner in this screenshot there are more doors. One of them is propped open, where our legless mutant will come crawling out and chase Jane around the level. My one concern is that we do not have enough in here to make a 1-2 minute cinematic. We shall see when that part of the class rolls around. I made the asylum really big in comparison to the character size. I wanted it to have the feel of being almost not real, but real enough to scare the player. I want to add in blood splatters around the level to give it that really creepy feeling. That will come later when we put the final touches on the level and get ready to film the cinematic. The lights in the whole level flicker constantly, which adds another layer to the ambiance. We hope to find some decent sound effects including screams, footsteps, slithering (for the legless mutant), maniacal laughing and others, just to name a few. We are most likely going to have 2 music tracks that will play during the cinematic, and one will shift into the other at a certain time. I think it is coming along nicely.
Tuesday, February 5, 2013
Group Update #2
February 5, 2013
This week our group was tasked with creating two characters for our final cinematic, texturing, rigging and animating them. I had the job of UV mapping and texturing the mutant model (made by Matt) and rigging the Jane model (made by Shannon). I did learn something from this, however. When Shannon was finished creating a custom running animation, I immediately tried porting the character to UDK. Aside from forgetting to rename the second spine in her model (oops!), nothing was wrong. It ported just fine to fbx and then just fine into UDK. The problem came when I tried previewing the animation in the Skeletal Mesh previewer. When I set the AnimSet and the correct animation sequence and clicked play, nothing happened. I was puzzled for a good hour. I tried everything from re-exporting the fbx to force deleting everything in the package and re-importing. It came down to me opening the model back up and taking a closer look at the animation layer of the CatParent. When I looked at the animation in Max, I noticed nothing at first. Click play and the animation played just fine. However, I looked down at the timeline and there was the problem. Can you guess what it was?
The problem was that when Shannon made her original animation, she edited the default running animation, which has no keys set on the timeline. It is built directly into Max. Since her animation had no keys set, the fbx file had no keys baked into it, but no information at those key marks. So when UDK tried to play the animation, nothing happened because it had no information on what was occurring in those key frames. This was such a simple fix. All I did was find the end point of her animation (which was 30 frames in), then set keys every 5 frames for a smooth animation. When I re-exported and imported back into UDK, the animation worked. Huzzah! Such a simple fix, but I overlooked it a thousand times trying to figure out what was wrong. Occam's Razor is indeed true.
EDIT: Turns out she didn't just edit the default walking animation. She created her own. I still don't understand how keys were not used in the animation.
This week our group was tasked with creating two characters for our final cinematic, texturing, rigging and animating them. I had the job of UV mapping and texturing the mutant model (made by Matt) and rigging the Jane model (made by Shannon). I did learn something from this, however. When Shannon was finished creating a custom running animation, I immediately tried porting the character to UDK. Aside from forgetting to rename the second spine in her model (oops!), nothing was wrong. It ported just fine to fbx and then just fine into UDK. The problem came when I tried previewing the animation in the Skeletal Mesh previewer. When I set the AnimSet and the correct animation sequence and clicked play, nothing happened. I was puzzled for a good hour. I tried everything from re-exporting the fbx to force deleting everything in the package and re-importing. It came down to me opening the model back up and taking a closer look at the animation layer of the CatParent. When I looked at the animation in Max, I noticed nothing at first. Click play and the animation played just fine. However, I looked down at the timeline and there was the problem. Can you guess what it was?
The problem was that when Shannon made her original animation, she edited the default running animation, which has no keys set on the timeline. It is built directly into Max. Since her animation had no keys set, the fbx file had no keys baked into it, but no information at those key marks. So when UDK tried to play the animation, nothing happened because it had no information on what was occurring in those key frames. This was such a simple fix. All I did was find the end point of her animation (which was 30 frames in), then set keys every 5 frames for a smooth animation. When I re-exported and imported back into UDK, the animation worked. Huzzah! Such a simple fix, but I overlooked it a thousand times trying to figure out what was wrong. Occam's Razor is indeed true.
EDIT: Turns out she didn't just edit the default walking animation. She created her own. I still don't understand how keys were not used in the animation.
Subscribe to:
Posts (Atom)