News | Forum | People | FAQ | Links | Search | Register | Log in
Mapping Help
This is the place to ask about mapping problems, techniques, and bug fixing, and pretty much anything else you want to do in the level editor.

For questions about coding, check out the Coding Help thread: https://www.celephais.net/board/view_thread.php?id=60097
First | Previous | Next | Last
What's Better ? 
when you make a room out of a cube, to make it hollow outwards (-) or inwards (+) ?
I would think outwards would be better because the inside of your cube would be lined to the grid. (?) 
Repent Sinner, Repent !! 
Never use hollow maker: this is blasphemy !!! 
Why Not ? 
Really, I've always used it ... 
When You Build A Box.. 
..with the amount of clipping you then have to do to 'open it up', you're probably no better off than had you laid it down brush by brush

i only use hollow for misc entity boxes out in the void (teleporting monsters, spikeshooters etc) 
There Are Good Reasons.... 
... not to use Hollow makers: check #1461 and after.... since this time I never used again Hollow maker, believe me: it is safer !!!

Blasphemy !! Heresy !! You'll all burn in Hell !! 
 
Guys, he said he was hollowing out a cube. If you're using an editor that can't successfully hollow out an axis aligned cube, it's time to find a new editor. 
 
Guys, he said he was hollowing out a cube. If you're using an editor that can't successfully hollow out an axis aligned cube, it's time to find a new editor.

i'm not sure how you deduced that from what i wrote?

ron: to answer your question, if you hollow inwards (at least in WC) it should still align to the grid as it goes by the thickness of the walls, so it makes little difference. but it's generally better practice to construct rooms brush-by-brush in most cases, partly because it gives you more control but mainly because it helps discourage the old boxroom-corridor-boxroom syndrome :P ..although it is still useful for throwing testmaps together and the likes 
 
I don't see how you figured I was replying specifically to you. 
 
because it was only JPL and me who responded to the question, and 'guys' clearly indicates a plural? 
Rj 
...it's generally better practice to construct rooms brush-by-brush in most cases, partly because it gives you more control but mainly because it helps discourage the old boxroom-corridor-boxroom syndrome :P

I fully concur with you ! Thqt is exactely the point... hats-off... 
Rj 
Willem would have sent you a mail if the reply was for you only. Don't be so selfish and egocentric.


Ok, enough. :-P 
 
"because it was only JPL and me who responded to the question, and 'guys' clearly indicates a plural?"

FFS. 
Mindless Pedantry Or A Point To Be Taken? 
you decide. 
But Back On The Subject Of Mapping Help.. 
..does anyone have any insight into why all switchable lights would fail when compiling a full map? they work fine when compiling each section individually (it's split into about 6-7 'areas' in the form of visgroups) but can only display at full brightness when the whole thing is done, whether the 'start off' spawnflag is on or off. no errors in the light log or anything..

it's a bit of a limitbusting map if that counts for anything, breaks just about all of them... 
 
have you checked if you're getting any 'too many lightstyles' errors?

also, i've accidentally ticked the 'not in xskill' box on a light and not have it toggle because it wasn't present in that particular skill level.

if it's 'limit busting', it's possible you have run out of lightstyles.

you get 64 total light styles, the first 10 (not including 0) are for flickering lights, and the compilers only assign 32-64 (or 32-63?). so in actuality, you only get 32 light styles; 32 seperate switchable lights. i'm not sure if light.exe will collapse multiple lights with the same targetname into the same lightstyle or not, although it should otherwise even stock quake maps would have 'too many lightstyles' errors. 
Hollow 
Some editors will, when "hollow" is used on a cube to create a square room, make a nice square room of six brushes...but the brushes will all still stretch to the extents of the original cube, and will overlap.

Will a decent compiler usually clean this up and toss out the overlapping bits? Yes, usually, but it will still be messy in the editor, and potentially confusing.

Nothing wrong with hollow as long as you do any necessary clean up the result afterward. 
 
"on" the result, rather... 
Thanks For All The Replies 
What I usually do (in Worldcraft) is
- make a cube the size of your room to be.
- make it hollow outwards
- ungroup the thing,so your left with 6 brushes
- copy and paste (special, to same location) a brush 4 times and then shape them to fit a door in, 1 for the door, 1 for the left of the door, and for the right and one for above the door.

It does work that way.
I don't know if it's smart or handy though.
The thing with mapping is that you basically have to learn how to do it yourself.
The tutorials only show you the basics.
I still find it very difficult to find efficient ways to achieve things.
That's why I love this website ... ;) 
Hey... 
You know that combat music in Star Trek when Captain Kirk is battling a Klingon in the arena (with pick axe, spear, and shovel), well that music was playing in my head a few posts up.

I was thinking, HollowMaker sounds like an excellent stand-alone program that could work this way. First you make a cube in any of the editors available. Next, export the cube. Now, import the cube into HollowMaker. It has just 1 button, Hollow_out ! Now export and import into your favorite map editor. Voila ! So easy, and you'll want to do it over and over again.

I feel so hollow... Hey wait! HollowMaker hollowed out my brain.

Where is it?

It's in Quark? But I use BSP...

Spock, help get my brain back!
...my next map title... 
Sounds Like You Need UEd 
 
 
have you checked if you're getting any 'too many lightstyles' errors?

hrm, i compiled again to check, and this time it worked okay.. bizarre.

it is something where just because it works correctly one time it doesn't mean it will work all the time? or can i assume that it either compiled correctly or it didn't? 
 
did you run a -onlyents? remember to run a -onlyents on both bsp and (aguire's) light to reconnect lightstyles with the entities.
-onlyents on bsp breaks that connection (probably cause it can change the order of entities). 
Ahh 
that would be the problem :)

didn't realise there was an onlyents light option.. thanks. will have to add it to your compiler gui 8) 
 
cool, glad it's been useful! ^_^ 
Quake Sounds And Sample Rate... 
what's the deal with quake sounds?

I thought they had to be 11kHz 8bit mono, but i just made a 44kHz 16bit mono sound and it loaded in both fitzquake and winquake... so is that okay? Is dosquake the only quake that needs 11kHz 8bit sounds? 
First | Previous | Next | Last
You must be logged in to post in this thread.
Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors.