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
*something With NQuake 
Seeing how much bullshit it comes with, I'm not surprised that something like this happens. You might want to ask in the quakeworld.nu forums, as the nQuake teams hangs out there. Maybe you didn't set deathmatch 0 and there's no qwprogs.dat installed? 
 
i briefly tried it yesterday and it froze ezquake for me (on Linux). other engines were fine. aguirre's engine reported no exceeded limits. so I would suggest turning to the ezquake developers. maybe check what other qw engines do,eg zquake or fteqw. 
 
I tried it now in a clean install of ezQuake and it works fine, so i guess its a problem with some of the settings or addons for nQuake :( 
Netradiant Help Plz 
How to select entire func_?
How to flip clip plane?
How to make cloned brushes shift 
 
To select the entire func select one brush and press ctrl+alt+e. Don't know what mean about the other things. Shift cloned brushes, with alt+cursor key or what? 
 
to flip the clipping plane with 3point clipping, in sikkpin's qe3, it's ctrl+enter. it's probably something similar in netradiant. 
 
I meant how to make the cloned brushes offset when you press 'space'. 
Byte Packets 
FitzQuake - Warning: 1034 byte packet exceeds standard limit of 1024

What is this telling me that I have done wrong?

(Pulling the mothballs out of FMB-BDG) 
Overflow 
This is the more informative fitzquake version of "Packet overflow". Fitzquake itself isn't hampered by packet overflow (in single-player, at least), but it sends the warning to let you tweak things for other engines. The usual fix still applies - reducing the number of updates at once. 
Radiant And Win 7 
Is there a version of Radiant that works with Win 7? It seems like the last couple of times I've gotten the urge to make stuff for Quake, Radiant has had funky issues where I had to change my graphical settings in Windows just to get it working. 
 
All you need to do is disable visual themes (=Aero) in the compatiblity tab. Netradiant does it automatically - try if it works for you, I had some issues with it and stayed with 1.5. 
 
how do you light compile a bsp model for quoth? 
One Way 
There are lots of ways of doing it, if you know how to do it for hipnotic then that way still works. The external model supports allows for another way which I think is easier, and I'll explain that one now.

Create a new map file and build your rotating bsp model in it. Think about where you want the centre of rotation to be for your model, then move the brushes so that the centre of rotation is at the origin of the map (0, 0, 0).

Then compile your map as rot_mdl1.bsp. Return to your main map and add a point entity with classname rotate_object_point. Set the model field of this entity to maps/rot_mdl1.bsp and then compile and run the main map*. You should be able to find the rotate_object_point you just added and see the rotating model you built in fullbright.

All that remains is to open the rot_mdl1 map file in your editor and add some light entities around it, then recompile it. It's up to you to make the lighting believable, bearing in mind that your model will rotate, so keeping it fairly flat is advised.



* Question for the floor: Is maps/ the right folder for external bsp models to live, morally speaking? The guide puts it there because it's simple, where the compile process naturally puts maps. This makes it easy to compile it, check the lighting in-game and then adjust and repeat. But I think there's a case for these models to belong in another folder for released maps, either progs/ or a new folder like mapobj/. 
Thnx Preach 
I somehow forgot that you dont even need to seal the map for q1 light, unlike other games. 
Preach 
I'd say maps, even though logically it could go somewhere else - just because its the standard format that the majority of editors use. 
 
i just leave them in maps because i'm lazy. 
Also... 
id software put their item boxes in /maps 
Q3map2 Issue 
How to force q3map2 to keep samplesize at 16 on huge planar surfaces?
No, tessellating them wont help, it still bakes all them into one 128x128 lm texture. Cant make the slices non-planar (think of a square, it must be flat). Not using -meta is not an option (or other stuff wont work).
-samplesize 16 doesnt do anything either.

If its possible at all... 
 
How about tiny differences in texture alignment? Like 0.0001 unit shifts to prevent merging? 
Ikbase To Hlwad 
Using worldcraft 3.3 I'm trying to convert ikbase to hlwad but I'm getting an error saying "texture too big - shrink it".

Not sure why since none of the textures are larger than 256 pixels?

Could the fact that worldcraft has to be in the program files folder which in Vista has strict rules about creation new files? 
Metlslime 
Tried it, doesnt work. Q3map2 assigns lightmaps coordinates regardless of diffuse textures coords or names. 
 
maybe it's just a wonked out error message, and it's actually stumbling on the small 16x128 textures?

apart from that, are you trying to directly convert it from .wad to .hlwad or are you exporting then re-importing?
if you're doing one, try the other, etc...

i think hl wads, each texture is supposed to have it's own palette? not sure about that one. 
 
Thanks. Exported the textures then imported them into a wad that worldcraft was already using and the textures show up fine. Didn't have to do that in my old installation of worldcraft with ikbase... but whatever :) 
KamiKaze 
The error message it pops up typically doesn't have anything to do with the error - there's a log folder inside that tells you what really went wrong.

Lots of people have problems with that tool. 
1 post not shown on this page because it was spam
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.