Note: LucasForums Archive Project
The content here was reconstructed by scraping the Wayback Machine in an effort to restore some of what was lost when LF went down. The LucasForums Archive Project claims no ownership over the content or assets that were archived on archive.org.

This project is meant for research purposes only.

Compile issues...

Page: 1 of 1
 fattysbox
12-04-2003, 3:50 PM
#1
Sometimes when I compile my map I see old brushes and textures from previous saves that I have already deleted.

Another problem is when created some brushes as detail, when I compiled the map and loaded it, Everything that was detailed just disappeared.


What compile type can I use that actually draws what I have in my map?

Thanks
 _PerfectAgent_
12-05-2003, 12:57 AM
#2
1. I think the map is not compiling due to an error. Look at the little white box at the bottom of the screen and scroll up, it's probably a leak or a max_build_sides or something. The compile stops when it finds such an error. It's annoying, I know... You might have been able to compile before, but then you might have added something in the map that causes an error and stops compiling, so it simply uses the previous update to your map.

2. Hmmm... I don't know about that... Maybe you used a shader that makes any brushes textured with it invisible?

3. All compile modes display brushes.
 zeimi
12-05-2003, 1:29 PM
#3
Just remember to always compile with an option that has "BSP" in it.

About brush disappearing: Are you sure that you haven't pressed CTRL-D in accident? That hides detail brushes. Pressing it again shows them again.
 gotcha8903
12-05-2003, 9:17 PM
#4
i am also having toruble with compiling, and keep getting a BSP monitoring error. strangely, when i do each part of the complie by itself, it works fine
 _PerfectAgent_
12-05-2003, 10:34 PM
#5
Just don't turn on BSP monitoring, it is evil and messes stuff up.
 Druid Bremen
12-10-2003, 8:12 AM
#6
BSP Monitoring does not mess up JA for me, it messes up itself. The map itself is okay. I set it to run the engine after compile, and it ran the engine. Then, after I quit JA, and minimized GTK, there were white patches on it, like it was still loading or something. I waited for a reeeeaaaaly long time, and it still was there. In the end, I learned to restart Radiant after I finished my testing. :D
 WadeV1589
12-10-2003, 12:26 PM
#7
I just leave it open and minimise it, launch JA, set its process priority to low and leave it running as I map, compiles are short enough it makes sense to do thi when I'm workin on a new complex area and need to keep testing.

And what is the BSP monitoring error gotcha?
Page: 1 of 1