Posted by Wilddoggie on Sat Jan 10th at 12:23am 2004
member
55 posts
36 snarkmarks
Registered: Nov 15th 2003
Location: London

Occupation: none
Posted by Wild Card on Sat Jan 10th at 12:44am 2004
There are a few door tutorials all over the place.
http://www.vlatitude.com/tutorials.php?tutID=17
First off, make sure your origin brush and your door brush are tied to the same entity. If your origin brush inst tied to the door, then the map origin (point 0,0) is used and that is why your door is flying away.![]()
Wild Card
member
2321 posts
339 snarkmarks
Registered: May 20th 2002
Location: Ontario, Canada

Occupation: IT Consultant
Posted by Gollum on Sat Jan 10th at 11:22am 2004
Wild Card has the answer - the origin brush and the solids must be the same door, not two separate doors.
A useful tip: to save compile times, learn how to do an -onlyents compile. This just updates the entities in the BSP file, so you can change things like speed and sound (and even add/delete point entities) without waiting for a long compile.
[addsig]Gollum
member
1268 posts
207 snarkmarks
Registered: Oct 26th 2001
Location: Oxford, England

Occupation: Student
Posted by Wild Card on Sat Jan 10th at 1:54pm 2004
| ? posted by Gollum |
|
A useful tip: to save compile times, learn how to do an -onlyents compile. This just updates the entities in the BSP file, so you can change things like speed and sound (and even add/delete point entities) without waiting for a long compile. |
Damn rights a usefull tip, heck I didnt know that. Does it work with solid entities though?
[addsig]Wild Card
member
2321 posts
339 snarkmarks
Registered: May 20th 2002
Location: Ontario, Canada

Occupation: IT Consultant
Posted by Gollum on Sat Jan 10th at 1:58pm 2004
Yes, it works with solid entities so long as you don't change any brushes. So you can change the properties of any solid entity, but you can't add, remove or alter ANY solids (that includes solids that are part of an entity).
Almost all the compile time of a map is due to calculations involving 3D geometry - cutting it up, splitting it into portals, calculating potentially visible sets and bouncing light around it. With an -onlyents compile, you can skip all of this because it's already been done. Note that if you accidentally change a solid, the map will fail to load in HL.
[addsig]Gollum
member
1268 posts
207 snarkmarks
Registered: Oct 26th 2001
Location: Oxford, England

Occupation: Student
Posted by Wild Card on Sat Jan 10th at 2:17pm 2004
Wild Card
member
2321 posts
339 snarkmarks
Registered: May 20th 2002
Location: Ontario, Canada

Occupation: IT Consultant
Posted by matt on Sat Jan 10th at 3:26pm 2004
matt
member
1100 posts
190 snarkmarks
Registered: Jun 26th 2002
Location: Edinburgh

Occupation: Student!
Posted by Gollum on Sat Jan 10th at 6:21pm 2004
| ? posted by Wild Card |
| And I guess all thoses .p1 .p2 etc files must not be deleted or moved right? |
Correct - leave copies of all the output files, including the BSP. I'm not sure *exactly* which ones are required, but you might as well leave them all.
[addsig]Gollum
member
1268 posts
207 snarkmarks
Registered: Oct 26th 2001
Location: Oxford, England

Occupation: Student
Posted by Cash Car Star on Sun Jan 11th at 7:15am 2004
Cash Car Star
member
1260 posts
301 snarkmarks
Registered: Apr 7th 2002
Location: Connecticut (sigh)
Occupation: post-student
Snarkpit v6.1.0 created this page in 0.0274 seconds.

