Please or Register to create posts and topics.

Compiling doesn't work always

Hello, i'm new to this forum and got a problem.
The compiler for the Portal 2 Authoring Tools doesn't always work.

Sometimes it compiles it correct, like it should, and sometimes, it just does this:

Code: Select all
-------------------------------------------------------------------------------
Running command: cd "c:program filessteamsteamappscommonportal 2bin"
-------------------------------------------------------------------------------

-------------------------------------------------------------------------------
Running command: "c:program filessteamsteamappscommonportal 2binvbsp.exe" -game "c:program f
ilessteamsteamappscommonportal 2portal2" "C:Program FilesSteamSteamAppscommonportal 2sdk_
contentmapstiletest.vmf"
-------------------------------------------------------------------------------

Finished. Press a key to close.

It is a nodraw box with just a player in it. Also normal maps wont do it always.
Any idea why it happens, or does someone else also have this problem?

It is really annoying, to be honest. :notwant:

Because you have a gigantic leak in your map.

Nodraw texture does not block VIS calculation. The compiler cannot do anything with your map.

At the minimum, you need a box with six sides made of solid world brushes (not brush entities), a light entity, and a player to compile.

I strongly recommend you read the basics of mapping before you start. Otherwise, you are setting yourself for tons of frustration.

He can have the box made of nodraw as long as he uses the face edit tab to texture the 6 inside faces with a non-nodraw texture.

My Maps:
[spoiler][SP] Alternate[/spoiler]
Vordwann wrote:
He can have the box made of nodraw as long as he uses the face edit tab to texture the 6 inside faces with a non-nodraw texture.

I do not think that will work. You need more than one unit of overlapping brush surface to seal a map.

I had a leak once that I textured just the inside of a glass brush with non-transparent texture, and I fixed it by texturing the entire brush.

I'm saying as long as his nodraw box is completely sealed, he only needs to texture the 6 inside faces, otherwise his compile times will be larger because he'll be rendering unseen faces.

My Maps:
[spoiler][SP] Alternate[/spoiler]

Go ahead and try that. I am just saying that may not work.

You can compile a map with leaks; I do it all the time when testing. I think the compiler has a problem if you don't have any drawn faces in a map, so texturing it might make a difference.

Vordwann wrote:
otherwise his compile times will be larger because he'll be rendering unseen faces.

Are you sure about that? Vbsp and subsequent compilers should completely ignore outside faces assuming you have no leaks (and unless you use -noopt). They still exist, but are never rendered and shouldn't contribute to compile times.

I'm talking about intermediary faces.

My Maps:
[spoiler][SP] Alternate[/spoiler]

Making a box like this:
Image

Spoiler
Image
Image is in wireframe
will make sure that no texture goes overlapped, even if it is nodraw. Also there is much less chance of the leafs being split up unnecessarily.
Medious is right to say that when you full compile that textures on the outside of the visleafs will not be drawn, however if you noclip outside the map it will.

The places where you should be fussed about putting nodraw is in places that the player cannot physically see (but looks like the map would continue in that direction) that is inside the map, and on func_detail's. Seeing as the leaf's totally ignore func_details, all their sides would be rendered. The same for faces that are connected to a func_detail that are world brushes. If you cut brushes correctly, you will also find that there is an ultimate reduction of lighting errors (especially around angled or curved brushes).

?????????????????????????????TWP Releases | My Workshop

Well, the problem is that even if I don't edit a map sometimes, it works after a time.
So I think it doesn't really have something to do with the map itself, but with the compiler...