Al Anselmo - Game Designer and Level Designer

[selmitto]

Thank you!

I couldn't see what's your profession so I've wrote "game industry". As you'll notice on some portfolios there's a profession right next to the name:

I have the profession written right below the logo:

Maybe it's not THAT much visible? Damn...

I'll see if I can include the "Game Industry portfolio" close to that

Cool, but it's hard to find a correct place for it. You could make Personal and Professional parts of portfolio (inform about it in description and in header of the projects' list). I was trying to make such thing on my website but I had only one personal project.

Currently I have no Professional projects in my portfolio. When I worked as Game Designer in a Serious Games company, I got a lot of relevant work experience, but the projects we developed there don't seem (to me, personally) really relevant to display in a portfolio focused in the Entertainment Industry.

I created some documents that I find interesting, such as a spreadsheet of game balancing and powerpoint presentations with the game wireframe. However, I don't know if "boring" documents like those are interesting materials to provide in a portfolio. My guess is that they might not be - people usually like to watch videos, view screenshots and etc.

-> That said, what I currently have are "Personal" and "Academic" projects (ones that I developed in a team while I was graduating in Game Design. That's the reason why those aren't labeled as "personal projects"). So, it would be like this:

I'm thinking that this might not be yet the case to separate the projects by kind, until an Entertainment and Professional project pops up. So, I would keep the "Personal Projects" line in the header of the projects and its descriptions - to explicit that I did them all by myself, without any external help.

Any thoughts?

(damn, I need to develop something professionally. Anyone in need for a Junior Game/Level Designer? )

If the game is running on Source Engine it means that it's OK If you used GTKRadiant instead of Hammer, just type it in your skills section in resume.

That's great to know! I actually used the Perpetual Testing Initiative (PeTI) to build the maps. I'll add it in the Software section of my Resume then.

Move it to portfolio as a part of Professional or Personal Work. It's a part of your folio and it should be on one page so it will be easy to print/check on mobile phone. I think that "Portfolio" page (main page) should contain all your works. Only one page. The second page is Resume (with contact) and the rest are up to you (Artices, Dev Blog, Links and so on).

Hmm I'll try! I'm wondering if there will be too many different kinds of things displayed when a visitor opens my site (joining my current projects with: a scheme of a GDD, Beta Tests, art and animation projects). I'll test it and show the result.

-> But, this made me think: I'm starting to wonder if the content (and this kind of content) that is currently presented in Design Docs and Extra Skills really add some points to me when someone is seeking for a potential employee.

With the clearer menu (which I'm really considering to apply), there would be three pages then (considering that I might remove Design Docs and Extra Skills, depending on what you guys say ):

Portfolio | Resume | Articles

I took another look in your portfolio, minos', briscoes' (and others') and noticed this "trend". Three simple menus - with slight name variations, but all leading to the same kind of content -, with all the relevant information. Simple and effective! ;D

[mjens]

First I've overpainted the Game Designer & Level Designer and then I was looking for your profession That's why I didn't noticed that

[selmitto]

First I've overpainted the Game Designer & Level Designer and then I was looking for your profession That's why I didn't noticed that

Oh, no problem

I did all updates!

I changed the font, added separators (they improved the sexiness!) and worked on the other points that you suggested.

I did that test with the clearer menu.

I really want to make it looks good, but I'm not 100% sure if, in this case, (almost) everything being displayed on the first page of the portfolio is a good thing.

• I mean, are the content in Design Docs/ Beta/ Extra Skills "adding points" to me when a potential employer is viewing my portfolio? What do you think?

I have yet to include the Bug Report & Beta Feedback I did in Diablo III, btw.

I'm afraid that "(A) deleting the sections above", or "(B) including everything in the home page" can be the only ways to use the simple and clean menu...

And here are the results:

-> My portfolio

-> Clearer menu test: http://anselmo.gd/clearermenu_test.html

• Any thoughts?

(Now I'm feeling a LOT more confident after had implemented the redesign you suggested, thanks)

[mjens]

I think that menu should me centered or aligned to left. It's more comfortable The rest looks great, good job!

[selmitto]

I think that menu should me centered or aligned to left. It's more comfortable The rest looks great, good job!

Thank you! ;D

Final question (ta-da!)

• Using the clean menu, do you think that I should keep everything on the same page, even the extra skills? Do they worth that?

(I aligned the menu to the left, so maybe you need to refresh the page to see it)

[selmitto]

Broken Bridge

Hi guys, I'm looking for your feedback here.

Recently I was requested to build something in Unity, so I've whiteboxed a small level in the engine to demonstrate some lighting and shader usage (post-processing and optimization as well but the former could easily harm the latter, so don't consider them here).

Even though I started with a daylight scene, baking lightmaps using Bioshock Infinite as a reference for the light and shadow tones, I later on decided to change for a nighttime because I thought that way the light usage would be more evident.

So, I ended up creating a level set in an outdoor area and during the very night. (I'm not sure if that was the best decision to make because I guess it made things more difficult ).

To help to communicate possible team members about the level in question, I did a sketch and wrote a one page level design doc to outline the current storyline/ context, what the level design goal was and how that should be played:

I've got three questions for you all:

1) Is it really possible to light a level and achieve GREAT results, even though ALL you have is blocked out/ whiteboxed geometry (no props, no artistically-created textures etc)?

2) How could I improve the lighting in this scene?

Take a look at the screenshots below or download the executable here (~25mb) to play it.

3) What exactly do you understand as "shader usage"?

I'm not an environment artist, but I got some diffuse textures that fitted the level's theme and created their normal maps afterwards. To conclude, I created materials in Unity to receive those textures and applied them accordingly. With that, I believe I could prove that, providing the right textures, I was able to create the materials and apply them to the scene.

I don't know if I'll include it in my folio in the future, but I'm sure there's an opportunity to improve things here.

This is very important to me and I'm really looking forward to any feedback you can give (even opening my eyes to how much I suck would be ok, I guess). I'm currently available in the market and doing projects on my own, so I count on you guys to give me some pointers on how to improve my craft

Thank you so much!

Edited May 2, 2013 by Al Anselmo~Intelect0

[2d-chris]

The key to a solid early implementation of a design is to keep it clean, clear and consise ... I always liked the way Naughty Dog and Valve do it (we also do this at Crytek)

Heres and example of a scene broken down into basic white/grey box

The problem with texturing and lighting is your already distracting the observer before you've even proven the design. Sure, at some point you will add lights but assigning really ugly textures doesnt help get the point across.

You could take this maya scene above and add some simple text describing the player path and events - if lighting will play a major roll in the design, then it's worth showing before and after, explain why the lights are there.

The bridge scene can be explained with a few screenshots from a 3d scene, extremely low poly. First showing the view at the start, so setting up the scene. The second being after the bridge has collapsed, with arrows or pointers showing the intended path.

Your sketch is really good, and is quite clear what you want to do, the only issue I see is the presentation in 3D, your attempting to make the scene more complete than it needs to be.

Edited May 2, 2013 by 2d-chris

[selmitto]

[Feedback]

Thank you, Chris!

I appreciate and agree with all you said.

I didn't feel very comfortable of applying the art and lighting there, because I was aware that being part of a game that should be playtested, lots of things could be changed/ iterated. I would avoid any aesthetic element. But, as I was requested to show off lighting and shaders in Unity, I ended up doing that.

So I believe that in the end I wasn't so crazy of thinking that applying those things in a whiteboxed phase wasn't a good idea...

Is this presentation in 3D better now? More readable, isn't it? ;P

Webplayer of the whiteboxed version (1,2mb)

Edited May 2, 2013 by Al Anselmo~Intelect0

[2d-chris]

yup that defo gets the design across much better ^^

I'm not sure just the bridge requires it own document though, but it's good practice. You can describe the basic design of an entire mission on a few pages ^^

[selmitto]

My portfolio has been updated! (resume as well)

 

Improved the layout, added a new game and removed clutter. With less sections, I could move the menu higher up, making it easier and faster to see the projects. I believe my portfolio has become more relevant with this update

Added Monaco.

 

EDIT: forgot one of the most important things: including the first game I was credited for contributing!

Edited August 20, 2013 by Al Anselmo~Intelect0

[Puddy]

Okay, my main feedback is that your portfolio is very heavy on the text, analysis and thinking and thin on content. I'm assuming 99 out of 100 game studios prefer solid content (released maps, projects, mods) way more than text detailing your design process etc. If the content is good, it speaks for itself and they assume you know your stuff.

 

Monaco QA: I'm assuming this was an unpaid position. Also, was it an actual "position" or did you simply have access to the game and submit feedback?

GRASP: This could potentially lift your portfolio if the game shows promise (even though it's not released). However, you don't actually showcase anything about the game?

Portal 2 Maps: Since these were made using PETI their Portfolio value decreases. You've got miles long articles about them, but how come one only has 87 subscribers? Why did it fall short? Are the maps the best they can be? You should really push your content in terms of quality.

Silverhawk: Not very game-related imho.

 

In the end, all this adds up to that the only real level design experience you showcase are two Portal maps made in PETI, which isn't a "true" editor. In my experience, "game designers" are rarely where they are because they could theorycraft ideas. They got there because they could deliever content (whether as artists or level designers) and ALSO were good with ideas and were allowed, at a later stage, to work more with shaping game ideas and mechanics. 

 

TLDR; you need more meat in your folio.

[selmitto]

 

Okay, my main feedback is that your portfolio is very heavy on the text, analysis and thinking and thin on content. I'm assuming 99 out of 100 game studios prefer solid content (released maps, projects, mods) way more than text detailing your design process etc. If the content is good, it speaks for itself and they assume you know your stuff.

 

Monaco QA: I'm assuming this was an unpaid position. Also, was it an actual "position" or did you simply have access to the game and submit feedback?

GRASP: This could potentially lift your portfolio if the game shows promise (even though it's not released). However, you don't actually showcase anything about the game?

Portal 2 Maps: Since these were made using PETI their Portfolio value decreases. You've got miles long articles about them, but how come one only has 87 subscribers? Why did it fall short? Are the maps the best they can be? You should really push your content in terms of quality.

Silverhawk: Not very game-related imho.

 

In the end, all this adds up to that the only real level design experience you showcase are two Portal maps made in PETI, which isn't a "true" editor. In my experience, "game designers" are rarely where they are because they could theorycraft ideas. They got there because they could deliever content (whether as artists or level designers) and ALSO were good with ideas and were allowed, at a later stage, to work more with shaping game ideas and mechanics. 

 

TLDR; you need more meat in your folio.

Thanks for the feedback, Puddy!

 

Monaco: exactly, it was unpaid (they sent me the game and a t-shirt, but still).

I made sure to talk to the game's producer and level designer and ask him how I could add to my portfolio in a way that wouldn't seem like I did more than in reality... so I stated that it was a "community contribution" as I helped them doing things that QAs usually do. I have helped many games, but with Monaco I got credited and as it's a very known game, I figured it could be a good idea to include it in my portfolio.

 

Some context: when Monaco started its closed beta, the devs selected a few players to help them out testing and providing feedback. As the levels got tested and tweaked after the other beta players and I suggest improvements, Pocketwatch Games opened the beta and started to call that first group of playtesters as "Beta VIPs". One of the differences between us and the rest of the players was that we had early versions of the game and a private section on the forum, where devs discussed things that were to be implemented later for the other beta players. For our contribution, we Beta VIPs got credited in the game.

~> Do you think it'd be better if I wrote "Unpaid position" or "Unpaid contribution" there to make things even clearer?

 

 

Grasp: I included it to show that I'm currently developing something. I'm investing all my time on this project because I too believe it'll lift my portfolio.

~> The game is not yet released. Do you think it'd be a good idea to remove it and only put it back after it gets done or I had created a trailer?

 

 

Portal 2 Maps: I totally agree. One of the maps doesn't have as much access as the other maybe because it's a lot more experimental in terms of gameplay and I didn't share it as much as the first one.

~> Hmm now I guess it'd be better if I removed Indirect Ctrl from the portfolio... ._.

 

 

Silverhawk: yep, not game related at all. I developed that to train my programming skills only.

~> ...but if it isn't adding any value, I could remove it as well. I believe the value and quality of works showcased matter a lot more than the quantity. Thoughts?

 

Thanks again

Edited August 22, 2013 by Al Anselmo~Intelect0

[Minos]

Agree with Puddy, some of that stuff could cause more harm than good imo. Anyone can beta test a game and even if you are the best beta tester in the world... you are still not a developer. In a game production environment every developer is expected to give feedback anyway, so I don't see how being a QA in an indie game could help.

 

I also think you should really decide what your ultimate goal is because that is not very clear in your portfolio. If your ultimate goal is to work at valve or develop shooters, then making a 2D game will definitely not help. Since you are investing so much time and energy into this I'd say to just go and get experience with real editors such as Cryengine, UDK, Hammer, etc.. Create a few multiplayer maps (preferably for games that people still play such as CS,TF2 etc...) or even a simple single-player campaign. Make something that a potential employer would be curious to play.

 

The tricky thing with game designer positions is that nobody will hire you if don't have any relevant titles under your belt, and what I mean by that is to actually be someone that made in impact in a project. The easier and faster way to do that imo is by being a content creator (level designer, game artist, etc...), and then slowly climb the ladder until you have enough experience to be a game designer (which is really not about having ideas but about having experience. Anyone can have ideas but very few can actually execute them).

 

Another thing that is kinda weird is to have how you perceive yourself in your portfolio (I'm talking about the main competencies section in your resume). Honestly, when we interview people here the most important thing we review is their work and their experience. If we think they are qualified for the job, then the person is invited for an interview and that's where personality comes into play. 

 

I would also be careful with "software competencies" as well, if you claim you are experienced with software A or B you have to prove it in your portfolio somewhere. (for example even though I know my way around Zbrush I don't even bother to have it on my resume, since I don't have any relevant piece created in that software).

 

Hope that helps man

[selmitto]

[gold]

 

Thank you a lot Minos, I agree with you as well.

I'm aware that I have to improve enormously and I punch myself on the face constantly for that. I'm starting to think that I should empty my online portfolio, because now it doesn't seem to add any value to me... I'm thinking about that as I write this. 

 

My professional goal is to definitely work with AAA games, with shooters being one of the genres of choice. I seriously cannot wait to create CSGO maps and a single player campaign on CryENGINE. The thing that gets me crazy is: my plan of developing the game Grasp was that this game would demonstrate my most recent skills. But, the time spent is already a lot more than I had intended. Unfortunately, Grasp's development is at a stage that if I decide to stop it and dive into the magic world of AAA, all those months spent would've been wasted, you know?

I'm close to complete it. I need to finish Grasp to make all that time worthwhile.

 

 

For future improvement: do you think I should remove the "Main competencies" section, as for what I understood that's not relevant until I get an interview?

 

 

Thanks again for the always honest and kind words. It definitely helps