This week has been a blur of holiday food and family activities, but somewhere in all the festivities I managed to steal away and continue working on this level of mine. This week I wrote some blueprints, added terrain, ceilings, proxy rail roads, and played with lighting and post processing volumes.
The world is 100% made... Technically
When I last left off, my white-box was simply made of walls and floors. I've since wrapped up proxy placements of clutter, quest objects, and have even replaced the BSP floors with terrain. I'm slowly in the process of populating the environment with final assets.
Before I began populating some the cave, I first needed to locate an asset pack of rocks with a mesh that was of a medium complexity. I also preference packs that had a decent set of normal maps for assets.
Here are some progress shots in my level utilizing the processes described above.
All in all, I'm glad that I'm able to objectively define the strategies and processes I've tested and learned about thus far. I am eager to keep refining the process as I added new layers of detail to the environment.
I implemented some blueprint logic that highlights the edges of specific mesh when the player is within a certain range. These object are special to the quest I'm making and I wanted to make some elegant conveyance to the player that they should further inspect particular objects in the world.
Trace Back and Function Call
I began by making a unique collider name in my project settings and a blueprint actor given a tag name. Using a sphere tracer, I set the range and radius at which this will activate when the player is close to an item with the specified tag name. When activated it will process to the corresponding functions below.
function: start HIGHLIGHT Trace
while collision is detected: If the item is new and not already highlighted, turn on the highlight.
If it's already highlighted, leave on and do nothing.
Function: Stop Highlight Trace
When a highlighted actor is no longer colliding with the tracer, turn off the highlight on that actor, then nullify the function.
Week one has flown by and I am currently heading into my blueprint stage, but first, let me update you with what has been completed.
The purpose of this level design project is to demonstrate proficiency in level building including common pre-production and production practices.
look and feel
I will be basing my level's look and feel off of our newly formed Capstone Team's current aesthetic intent. While not 100% set in stone, our artistic tone is this:
Our capstone game will take place in a desert- like setting and we hope to utilize strong color theory and lighting in each environment.
A suggested environment for our upcoming capstone is a "poisoned water hole" and a "mining shaft". While we have no current specifics beyond this, I did want to use these initial locals as the basis of my level design.
The player will begin outside, just before Cavern 1. This is the 'water hole'. Here I will test outdoor lighting but most of my world will take place within the mine/aquifer. I would like to play with instances within the cave where light comes through holes in the roof.
GAME PLAY Considerations
I have a plan about implementing game play logic into my environment but I'll wait till next week, when I've got it built, to go into detail. Here is my plan as of now.
The WHITE-BOX is done!
Wrapping it all up
Here is a video blog I put together to sum it all up. Week two will be all about my blueprints and game logic. See y'all then!
SHow me what you got!
I am most happy when I design for player experiences. Tech art was more about designing development tools. Sparing the long story, I spoke with my professors at length and settled on a list of needs that I must fulfill to begin semester 2 as a Level Designer.
level design deliverables