So. I tried looking around for an UE3 thread and didn´t find one (With the search button broken and all it makes it kinda hard to search too).

Anyway. I´ve recently begun my journey into Ue3. A couple of years later than most but hey. Watcha gonna do eh?, Anyway, I´ve mostly been using an inhouse engine the last 1.5 years and it´s time to learn.

I didn´t get the collectors edition so i missed out on all the goodies it had. *whine*

So yeah. I was thinking this could be a Q&A / Tutorial thread perhaps. If there´s one like it already just lock this up and destroy all proof of it´s existance.

----------

First matter of business. How do you guys normally show off your models? Do you make a level and place out the mesh or do you just use the mesh viewer?

I´m still trying to find something that works for me and with being new to the program and all i have no clue about the potential.

I just maximize the quadrant and do a print screen from within the editor...but I have yet to figure out how to change the FOV for the perspective viewport in editor.

Oh and before you print screen hit "G" on the keyboard for "game mode"...it hides the lights, post-processing volume if you made one, etc...

To see if i understood it correctly, you just pull the mesh into an empty level and hide everything around it? Not the generic asset viewer itself?

Is there a way to change the background color though? Black is not the best as we know. Sorry for the nooby-level on my questions. I swear! I´m better on other things ;)

i´m not that experienced in UE3, in fact my targets were to know who to export my meshes into the ed, create their shaders and to light them porperly and a bit more, but for me the bonus DVD that comes with the collectors edition, the online reference in http://udn.epicgames.com/Three/SiteMap.html and some tips I got from this forum were a huge help to start with it.

in any case, this is a good idea if there is no post like this. the one about xnormal works pretty well and it is also a good way to keep all the information together and avoid lots of different threads about UE3.

nice one then :P

I create a quick scene (floor + walls + 1-2 small boring props maybe) with 3 point lighting, making sure the focus is solely on the asset I'm trying to show off.

If I know what angle I want and will be doing lots of tweaking, I'll set up a camera and matinee sequence so that whenever I run the level it puts me in that view. I even had a file with 3 switches that would switch cameras once - but that's really something I decide on a case by case basis if I save or lose more time by doing so.

Also set the LOD bias of all textures on the asset to -1 or whatever to make sure the model uses your highest LOD level.

Either disable the hud with Kismet or enter showhud 0 in the console.

Take the screenshot larger than what you want with "tiledshot x" (screenshot resolution = your current game resolution * x) then shrink it to whatever size you want in Photoshop (looks sharper).

Originally Posted by Notorious P.I.G

To see if i understood it correctly, you just pull the mesh into an empty level and hide everything around it? Not the generic asset viewer itself?

Is there a way to change the background color though? Black is not the best as we know. Sorry for the nooby-level on my questions. I swear! I´m better on other things ;)

Yeah you don't get much control over the mesh viewer in the generic browser...although I like orbiting control there better.

Drop in a height fog or some sort of fog plane actor if you want to quickly change background color.

Alright. Cool man. Thanks. I´ll play around with it when i get home.


EDIT: Oh anyone know a quick and easy way or tutorial to do an animated texture/effects? For example pulsating glows and what not?

Well moving textures are usually made with texture panners.

Time+sine gives you a pulsating effect
Hourences site helps a lot with such effects:
http://book.hourences.com/tutorialsu...xpressions.htm

Originally Posted by flkk

Also set the LOD bias of all textures on the asset to -1 or whatever to make sure the model uses your highest LOD level.

So if the numerical value is less than zero, is that the maximum resolution?

Is the LOD bias found in the properties of each asset (dumb question I know, had to ask it though)

E.g: -1 equals full resolution (Close LOD/Max resolution), 0 (medium LOD), and +1 (far LOD) ?

Originally Posted by flkk

Take the screenshot larger than what you want with "tiledshot x" (screenshot resolution = your current game resolution * x) then shrink it to whatever size you want in Photoshop (looks sharper).

flkk: where do you type in "tiledshot x"? A screencap from you with a red circle drawn in the area would even help, thanks! Much appreciated.

Originally Posted by A-Train

So if the numerical value is less than zero, is that the maximum resolution?

Is the LOD bias found in the properties of each asset (dumb question I know, had to ask it though)

E.g: -1 equals full resolution (Close LOD/Max resolution), 0 (medium LOD), and +1 (far LOD) ?

flkk: where do you type in "tiledshot x"? A screencap from you with a red circle drawn in the area would even help, thanks! Much appreciated.

Only with certain groups would -1 be enough to max res. In other cases you might need -2

Played around with the tips I got in here today and must say that it was a huge success. The thread is already paying off! (And I see it got stickied too! )

It feels like the editor is growing on me. There are some things i´m not happy with but that´s just because I haven´t found out how to do it yet. For example the sine-thing and get that pulsating effect (Something about invalid float samples or not being able to read it). Will study hourances page a bit.

Everything flows from right to left in the material editor. Put time on the right side of Sine just to understand how it works...now link Time into the right side of input of Sine.

To see what you are doing, check the boxes to the left of the words Sine & Time and then tick both of those little joystick looking buttons at the top of the whole window...they are to the left of the eyeball. I don't remember which is which but this is how you can see animation in your expression nodes.

What you will see is the Sine value now being taken from 1.0 down to -1.0.
Now a value of Zero is also black so that is why it looks like black is more predominately flashing than white at the moment. Make it .5 and it will be smooth...if you wish. Can play with it...

Now drop in a "Multiply" node to the left of Sine and plug it into "B". Above Sine drop in a Constant3Vector and plug it into "A". Change the Constant3Vector RGB values so you get red. Now take the output of Multiply & plug that into Emissive.

There. You just made a stop light. ;-)

Originally Posted by A-Train

flkk: where do you type in "tiledshot x"? A screencap from you with a red circle drawn in the area would even help, thanks! Much appreciated.

In the console. Try pressing Tab, ~ or F10 while ingame and look for a textarea to appear.

You can change the keys its bound with these settings:

[Engine.Console]
ConsoleKey=F10
TypeKey=Tab

in this file: My Games\Unreal Tournament 3\UTGame\Config\UTInput.ini

Try that

Thanks a bunch dude. Getting a hang of it now. Could swear i tried it before but i guess not. Figured out i would have to add a clamp after the sine to get the values into a more subtle range than on and off aswell. So... there´s some progress right there.

Next up im gonna try and see if can do something with masks and combine it with the glow to only get specific parts to be affected by the sine.



On another note. I assume it´s only possible to have one "modifier" or whatever we call it go into one of the material slots (Diffuse, Normal, etc). Or do i have to do some fancy hack or change?

Other than that. Tremendous help fellas. I´m really starting to feel it all pop into place! Guess i should post a gif of the finished result soon.

When I light my stuff, it looks great and all in the editor, but when I hit "build all", my lights turn duller. Things that were really shiny before, are now not shiny at all. Are there any tips on lighting so that what I see in the editor is actually what would happen after I build?

When I light my stuff, it looks great and all in the editor, but when I hit "build all", my lights turn duller. Things that were really shiny before, are now not shiny at all. Are there any tips on lighting so that what I see in the editor is actually what would happen after I build?

maybe "force Dynamic light" would work?(not sure though)

Originally Posted by alexk

When I light my stuff, it looks great and all in the editor, but when I hit "build all", my lights turn duller. Things that were really shiny before, are now not shiny at all. Are there any tips on lighting so that what I see in the editor is actually what would happen after I build?

What you are doing is baking a static light map when you click build all. There are a variety of things you can tweak. On the individual static mesh hit F4 to go to the properties, open the static mesh actor rollout (exact name is not coming to me at the moment). Go to the very bottom, open the rollout again, and you need to find something that says "override light map properties" or something...uncheck it. Now the light map resolution will be whatever you specify in the mesh viewer in the generic browser.

It's difficult to explain without pictures...maybe I'll do that later.

In general though, your real-time lights need to be a bit brighter for it to come thru after you build the lighting. That part is not very WYSIWYG to me. Just have to work with it.

Originally Posted by Junkie_XL

. . . not very WYSIWYG to me. Just have to work with it.

thats the longest wtf i've ever seen. . .

thanks for the lighting info, i've having bitch of a time getting good shadows across static messes, hopefully this will help me figure some things out.

P.I.G. good tread idea!

Alright guys. If you send me a bunch of cool links and resources i´ll put it in the first post. Make it nice and lovely and what not.

The tutorials that come with collectors edition UT3 are really helpful for people who are just starting out. I'm not going to get into the whole "illegal download thing" but I'm sure... if you looked... you could download them somewhere.

I've been thinking about getting Gears of War for PC... anybody have an opinion on the overall advantage or disadvantage of making a map for GOW instead of UT3?

Thanks.

True enough. Was able to borrow the bonus dvd from a workmate and took a quick peak. Seems like really good stuff. Will try to get through it all this weekend

Talbot, making a map for Gears of War would probably involve more level design theory than it would for UT3.

It also depends on if you were going to make a single player map or a multilayer map. Gears of War plays alot different than UT3... i would say that it would be easier to make a map for UT3 because of it's style... it's mostly run and gun, no need to worry about cover as much.

Gears of War is all about cover, you have to integrate props that act as cover nodes, and then you have to place your cover spots all over the map... so it's a bit more time consuming, but it will make you use your brain a bunch more.

Another great resource is the Epic Games Forum. Go to the modding/level creating section for the specific game you are making a map for.

Some advice for people who are making maps for UT3 or GOW and are thinking about posting it on the epic forum. Make sure that you understand the community that goes to that forum. They are very different from the people here. People there are looking for gameplay when it comes down to it. Yes a different environment from the shipped levels is appealing to them... but they won't like the map unless it is fun.

So here is a basic timeline of the posts you have on the epic forum when you are sharing a map. This may seem stupid to some people... like "do you really need to follow this?". My response is that it isn't necessary... but it something to think about. Devoted Testers are hard to come by and if you overload them with releases... they won't bother downloading them and putting time into playing it, getting an opinion, and posting their thoughts.

First post: Post your Alpha release. This should be not much more than a BSP. No static meshes are necessary here. Test it with bots and make sure there are no clitches and that someone else will have fun playing it. With that said, if you have a friend that is willing to play it for a little while... send it to them. That can be really helpful so that you know that you aren't the only person who enjoys the map before sharing it with the internet.

Second post(s): Listen to what people give you for gameplay feedback. Make sure you don't post another version of your map within a week after your first release. Chances are that you aren't going to get too many devoted testers who are going to want to test every little change. Posting a new version everytime you change something like elevator speeds will make them not want to download the new version. Then when you release the final... nobody will see it.

Third Post: Post a Beta. Your beta should take a sometime to nail that core gameplay. You should have listened to everything people said about your map and really act on what they said. If someone sees that you didn't address what they said needed work... well... you probably just lost a tester. Make sure that your beta really nailed that key gameplay element that makes your map special. Your Beta should also have some life. Even though you want to wait a little bit before posting your beta... I personally think that your beta shouldn't include all of your custom assets... this would take longer than you want and people will forget about the map. The gameplay should be considered done. Now I'm not saying that your Beta should be the default checkered material. Take sometime looking through the assets that come with the game to give it some spice. After your beta... the only thing left to do are the custom assets and ART... yes ART. If you are a polycounter, chances are art is very important to you. Make sure that after you post your beta you start working on your assets. It's going to take a long time to create all new assets and you should get started as soon as you feel comforatable with the layout. I would suggest starting with assets that are going to be in a section of the map that is unlikely to need tweaking. This way you don't waste your time making assets that don't end up getting used.

Fourth Post(s): Same as the Second Post(s), just listen to what people have to say. If you don't get any gameplay critiques then just keep working on the assets. But if you do get a lot of critiques that aren't necessarily "minor problems", consider releasing a second beta (BETA2/B2) that address's those problems.

Fifth Post: Post your final release. Like I said above, this might not be your 5th post... but it is the fifth step in my mind. There is going to be a pretty big gap between the Beta and the final due to all the custom assets you have to make. In that time you should start a thread here and to get art critiques if you haven't already made a thread. There really isn't much to say about your final release... except that it shouldn't be rushed... especially considering you will be doing, what I hope, is your true passion... art.

So that's all I have to say. I know this might not be a perfect workflow but I think it will help get the most out of the people there. Oh and please don't think that I'm classifying them negatively... I'm just saying that the people here (on polycount) are focused on art while the people on the epic forums are less focused on art and more focused on gameplay.

There are a lot of people on this forum that have more experience than me so maybe some people could add to what I wrote.

I also don't know if this is the best place to post this but it seemed like a good idea while writing it. :P

Hope this is helpful to some people.

Originally Posted by Junkie_XL

What you are doing is baking a static light map when you click build all. There are a variety of things you can tweak. On the individual static mesh hit F4 to go to the properties, open the static mesh actor rollout (exact name is not coming to me at the moment). Go to the very bottom, open the rollout again, and you need to find something that says "override light map properties" or something...uncheck it. Now the light map resolution will be whatever you specify in the mesh viewer in the generic browser.

It's difficult to explain without pictures...maybe I'll do that later.

In general though, your real-time lights need to be a bit brighter for it to come thru after you build the lighting. That part is not very WYSIWYG to me. Just have to work with it.

I found a tutorial for this, thanks. It's helped increase my lightmap resolution, but yah the lighting, guess I have to crank up the brightness on those.

Okay another lighting question: Is there a way for me to have different light setups in the editor (not the build). Like say, I have 2 lights, one is blue, one is red. But I want to be able to just flip them both to full white, and then back to the blue and red. I want this because I want white lights when I work on my textures, but be able to flip to the colors to see how my texture is like with colored light, and then flip back to white so I can continue working.