Quote from Groxkiller585 on May 28, 2012, 10:50 am

Jimmy wrote:

Hello,

I made a map and I have issues with performance. There are many maps out there that are twice the size of mine and my computer can run them smoothly. My map is not even filled with anything, it's basically just empty space, but I feel like I have half the FPS that I usually have. What influences that? Is there anything I can do about that when compiling the map?

We need a bit more info than "It's a big map but runs worse".

- Do you have large masses of liquids? Many of these cause lag.
- Do you have a dynamic light lighting the big area? The sheer size can cause a significant performance drop.
- VVIS often hates large, open spaces, but in Portal 2 that has been optimized greatly (See: Enrichment Spheres) so unless your area is absolutely HUGE I can't see that being the source of lag.

Can we have a screenshot of the area where it lags the most/ a pic of the entire area so we know how large it is?

Quote from josepezdj on May 28, 2012, 11:01 am

First of all, I guess you're mapping on hammer, right? Performance issues are usually caused by a bad optimisation. I'd suggest you at least the following optimisation tips:

1. Tie all brushes that don't seal the map to func_details. If any func_detail (or whatever other func_something or entity) touches the world the compile will return an error, a leak. If this happens just go to map > load pointfile and a red line will be displayed showing you where is the entity that is touching the world.

2. Texture with the nodraw texture all the sides of your brushes that the player won't be able to see. Tipically the first ones are all the external sides of the brushes that seal the map.

3. If you have different separated chambers, I'd suggest that you make a brush at the entry, covering the whole entry from the floor to the ceiling textured with skip texture and then texture the front face of this brush with the hint texture.

That should save quite some compile time and also should make performance smoother. There are still another important optimisation element, the areaportals, but as it's more complex let me know if you already increased performance after doing the above...

Quote from Brainstone on May 28, 2012, 11:52 am

To understand how map optimization works and what you as a map creator have to do, read this HL2-guide:
http://www.optimization.interlopers.net/

And:

Quote:

2. Texture with the nodraw texture all the sides of your brushes that the player won't be able to see. Tipically the first ones are all the external sides of the brushes that seal the map

You don't need to nodraw the external sides. It is done automatically when compiling.
Also, I wouldn't tie all brsuhes which don't seal the map to func_details, only the necessary ones. (Read the guide to learn which the necessary ones are.)

Quote from Jimmy on May 28, 2012, 11:55 am

Thanks.

@josepezdj, I'll do that, and yes, mapping in Hammer.

Screens:

http://i.imgur.com/uWFq7.jpg
http://i.imgur.com/vNzpH.jpg
http://i.imgur.com/hTx1f.jpg

As you can see I have only normal lights (since I haven't learned about different ways of lighting a chamber yet). This map is not finished and I don't want to continue it when there are already performance issues that I cannot fix. It's not like I can't walk or anything, but I notice a difference to other maps. The time that it takes to compile this map is not very long.

edit: Oh and thanks Brainstone

Quote from HMW on May 28, 2012, 3:10 pm

The only reason for poor performance I can think of here, is that your map already has a leak.

If you use "noclip" and go outside your map, can you see the outside walls? If so, then you have a leak somewhere, either an actual hole or one of the props (stairs, walkways etc.) outside the map.
(It's not a problem to have part of a prop sticking through the wall, but its center must be inside the room.)

Quote from josepezdj on July 4, 2012, 6:55 am

Brainstone wrote:

To understand how map optimization works and what you as a map creator have to do, read this HL2-guide:
http://www.optimization.interlopers.net/

And:

Quote:

2. Texture with the nodraw texture all the sides of your brushes that the player won't be able to see. Tipically the first ones are all the external sides of the brushes that seal the map

You don't need to nodraw the external sides. It is done automatically when compiling.
Also, I wouldn't tie all brsuhes which don't seal the map to func_details, only the necessary ones. (Read the guide to learn which the necessary ones are.)

Only wanted to say Brainstone that I didn't know about that Optimisation guide (well, I remember I found it by accident some time ago while searching for something, but never ended up there again though), and that one was a really awesome read! I've read it all (all chapters) 2 times and learnt a damn lot, mate! Moreover, it served to me more to settle down my knowledge, to fill certain gaps about some things, and to go in depth with some others... thanks!

Quote from greykarel on July 4, 2012, 8:48 am

HMW wrote:

The only reason for poor performance I can think of here, is that your map already has a leak.

Portal 2 maps will not compile if there is a leak. Leak on VDC.
So the reason is only optimization. And that guide is realy great.

Quote from HMW on July 4, 2012, 1:06 pm

greykarel wrote:

Portal 2 maps will not compile if there is a leak.

I surely wish it wouldn't! That would save many people a lot of problems in the long run.

You are partially right though. If you pass the "-leaktest" parameter to VBSP, it will refuse to compile a leaking map. Sadly, not all of Hammer's preset compile options include that parameter. If you use the "normal" mode, it will happily compile and run a map that has a leak. Some of the "advanced" settings include -leaktest, but not all of them.

greykarel wrote:

And that guide is realy great.

Absolutely. Required reading for any serious mapper.

Quote from FelixGriffin on July 4, 2012, 1:08 pm

Really? I just use the defaults and it doesn't make a leaked BSP.