use 'angles' instead of 'angle' and set as a vector. 

What's the project? 

a little themed sp adventure, something to pass the time. :D 

http://g.imagehost.org/0163/vsyncorwhat.jpg
I noticed in two engines that if I look at void and move my view, the geometry tears and spasms as you can see on that screenshot (for example in tyr-glquake).
In other engines the void stays clear of the rest and there is no such tearing. (for example Fitzquake (sdl 0.80) and DP.

First I thought it was VSync disabled but vid_vsync is 0 in Fitzquake. In DP it is also disabled. Also forcing it in the video driver did not change a thing.

What is this? 

is fitzquake 0.85 one of the problem engines? if so i'd like to see your bsp to see if i can figure it out. 

Fitzquake SDL 0.80 is fine so I assume any Fitzquake is fine. For me it is any map when I look at void (eg noclip outside the map) and move/look around.

I'll try it in Windows on the weekend. 

Spirit: some sort of gl_clear issue?

Preachcros: Nice one, keep em coming! :) 

gl_clear 1 -- clear the void with a solid color
gl_clear 0 -- hall-of-mirrors effect 

The tearing appears also with gl_clear 0. It's hard to explain. Try tyr-glquake and gl_clear 1, then noclip out into the void. If it happens to you too, that's where you see it best. 

Can someone give me the item bits for the SG please. All I need to complete the coag3_start is the weapon remove hack and then we can release, but while I've found the BackpackTouch hack info, I can't find a list of item bits and the example removes everything except axe...

I'm assuming 125 should add every weapon (value of 1 for axe, value of 2 for shotgun) except SG&Axe, but I'd like some kinda confirmation for someone who's mapped for Q1 within the last 7 years... 

nm, thank god for irc 

those patterns actually look kinda cool... 

thanks for the tip on the vector and making it angles instead of angle, because i finally figured out how to do it :D [i kept adding tick-marks between the numbers :/]

and fat controller did get back to me on the e-mail today and said i can use he textures as long as i give him kreditz which will not be a problem :D

this is what i kinda looks like atm:
http://i302.photobucket.com/albums/nn113/metchsteekle/quake0005.png?t=1238886386

and yes it will be some kind of a multi-player thing map, i just dont know what yet, maybe dm/ffa 

Hi,

I just started mapping again after many years gone. I've been working on a re-mix of my Quake level "Well of Wishes" (original map was lost in a hard drive crash) and I ran across an odd thing. I uploaded a map to quaketastic to illustrate, but basically I am able to push items through solid geometry, but only from certain directions. I was trying to find a way to add items as the player progressed using the fewest possible entities/brushes, but without resorting to a custom progs.dat and When I first came up with this I didn't realize the item bounding boxes were so tall


I may not use this method because it seems like might be more of a bug in the engine than anything else, but I was wondering if anyone knew why this happens. In the map I uploaded there are 4 alcoves with nails and health in each. The wall above the alcove is low enough that the player can't pass and get to the items. In the actual level the alcove would be hidden by a func_illusionary and when triggered they would be pushed into view by the func_door.
The only engines I've tried are fitzquake085, winquake and glquake, but it does the same thing in all three. The door will push the items through only from the north and east, from south and west the items fall through the floor when they pass through the wall.

If anybody wants to check this out, the example map is here:

http://www.quaketastic.com/upload/files/misc/doortest.zip

Shoot the buttons above each alcove to trigger the pushing door.
Turn on r_showbboxes in fitzquake for a more interesting view.

Back to mapping for now. 

That's because the wall is too low - the items' bounding boxes are 64 units tall. I don't know why it works - albeit with a visible clipping glitch - on two sides but doesn't on the other two (probably related to the bottom right back corner origin thing of entities). Since you're going to use two funcs anyway, you could make the illusionary an addtional door or wall and killtarget it, or let the items drop from a closet in the ceiling or in the floor. 

OK, I can't seem to get the time stamp field to do anything in either frame groups or skin groups -- is it used at all or does the engine lock that stuff down to a specific frame rate and that's the end of the story?

I'm changing values in my model editor but it's not having any effect on the speed of either kind of group. 

Yeah, I realize why it won't work, I was just baffled as to why it ever did in the first place. It must be some quirk in the engine code. I widened the alcoves by 64 units in each direction and items still drop out in only 2 of the 4 directions, so I don't think it's bounding box related.
Anyway, it's not a big deal as I was already using ceiling doors and floor doors in other places. 

The alcoves are fine, otherwise the items would drop out right away. The openings are not high enough - raise the brush under the buttons by 16 units and you'll see that all items are pushed out correctly. 

Really could use some help here. If someone could direct me to a tutorial for arched doorways in Radiant 1.5 for Quake III Arena, that'd be great. I've tried looking myself, and the one I did find was outdated and vague besides. If anyone has a video tutorial, that's even better. Thanks in advance!

Clock 

Do you mean the value that's meant to set duration of each frame? As I recall, they work correctly in software quake, and in glquake based engines, the value in the first frame in the framegroup gets applied to the entire framegroup. Recommended setting is to set all of them to the same value so that the behaviour is the same in all engines. But you could make the framegroup-wide setting modifiable like that... 

Well, I currently have it set up where you edit them all and I guess I'll leave it like that as the file format supports it even if the engine doesn't. Heh, oh well... 

Try this:
http://www.wemakemaps.com/doorway.htm 

 

Hi !

I was just wondering, is it possible to have transperent textures in quake? By that I mean textures which contain the image which is fully visible, but areas of the texture which are not rendered. A good example of this would a fence of some sort or barbed-wire.

I did hear that quake renders texures with the color value 0 (in the 8bit quake palette) as transperent, but I think this only works for sky textures.

Any help/advie is appreciated. 

Stock Quake doesn't do transparency in any way with the sole exception of the sky (as you noted). I think more advanced engines may support textures with alpha channels but I'm not sure.