Friday, November 13, 2015
DeVivo, Nicholas - Checkpoint/Respawn Tutorial Remastered
Despite getting my laptop back from having it's broken hard drive
repaired, it's been a decidedly off-week for me. Suffice it to say,
remaking my tutorial took longer than I thought, and I didn't have time
to do anything else. Hopefully, I'll make up for it next week.
Friday, November 6, 2015
ET49 - Nicholas DeVivo - Week 8 ... Stuff
My laptop is in the shop for repairs this week, but I managed to get some work done. Unfortunately, I did not get pictures our video of any of it. Most of it was refining what I had already made, so there wasn't much to look at anyway. The controls should be a little tighter now, and I managed to get jump pads to work better with the ball. That's pretty much it.
Friday, October 30, 2015
ET 49 Week Seven - Nicholas DeVivo - Marble Magic Falling Damage
In our game, you have to get the ball to go downhill without falling and breaking. I managed to find and refine a fall damage blueprint on-line and so far it works fine.
Below is the video demonstration. After ramming into a wall to show it has to be falling to die, I use a keyboard command to teleport the ball to an aerial checkpoint. From there, it falls to the ground, dies, respawns, falls, and dies again.
Below is the video demonstration. After ramming into a wall to show it has to be falling to die, I use a keyboard command to teleport the ball to an aerial checkpoint. From there, it falls to the ground, dies, respawns, falls, and dies again.
Friday, October 23, 2015
ET 49 Week Six - Auto-Zooming Camera - Nicholas DeVivo
I'm continuing to look into fine-tuning the ball controls, but I'm not making much headway. I also can't get health to display on the HUD because the tutorial I'm following uses a widget with "Cast to Character" in it, which the ball isn't compatible with it and I have yet to find an analogous substitute. HP can probably work without it, though.
This week, all I have that I can actually show is a camera that zooms into the ball when something gets in the way. This sort of thing is the default in the third-person template, but in the rolling ball template it isn't. All you have to do is go to the ball's blueprint, click on the spring arm component to view it's details and click "Do Collision Test."
You can see the results in the video below. Those blocks have a low clearance, so the camera gets in pretty close.
This week, all I have that I can actually show is a camera that zooms into the ball when something gets in the way. This sort of thing is the default in the third-person template, but in the rolling ball template it isn't. All you have to do is go to the ball's blueprint, click on the spring arm component to view it's details and click "Do Collision Test."
You can see the results in the video below. Those blocks have a low clearance, so the camera gets in pretty close.
Friday, October 16, 2015
Nicholas DeVivo - ET 49 Week Five - Marble Magic Camera Control
This week, I made the camera controllable. Zoom in and out with the W and S keys, and rotate left and right with the A and D keys. The next step will be to make it move on its own in response to the environment. Next will be health, but the tutorial I got from Advance Level Design isn't completely compatible with the ball for some reason. I'll keep working on it.
Here's the stuff for the camera controls.
Friday, October 9, 2015
ET 49 Week Four - Marble Magic Terrain Test... Success?
So I spent this week fiddling with physical materials and blueprints to create terrain that will slow down the player. I tried adjusting friction, but that only seemed to affect how quickly I could change direction. Everything else I tried seemed to either have no appreciable effect or caused the ball to just ricochet off the terrain. In one case, it actually pushed the ball to the side continuously. Here's what I finally did:
This blueprint is appended to the end of the ball's controls. Not pictured is the blueprint that detects a "terrain" blueprint and sets the boolean variable that branch is testing. The vector variable "Drag" is set to 2.0, 2.0, 2.0, hypothetically cutting velocity in half.
As you can see, the ball now stops completely after a couple centimeters and you have to keep pushing it to continue moving. I think that qualifies as "Slowing down" for now.
This blueprint is appended to the end of the ball's controls. Not pictured is the blueprint that detects a "terrain" blueprint and sets the boolean variable that branch is testing. The vector variable "Drag" is set to 2.0, 2.0, 2.0, hypothetically cutting velocity in half.
As you can see, the ball now stops completely after a couple centimeters and you have to keep pushing it to continue moving. I think that qualifies as "Slowing down" for now.
Friday, October 2, 2015
DeVivo, Nicholas - ET49 ASSIGNMENT 03 GAME LEVELS BLOCKED OUT
Saturday, September 26, 2015
Subscribe to:
Posts (Atom)