 News | Forum | People | FAQ | Links | Search | Register |
Log in |
|
|
Volume is pretty obvious – the volume of the sound, on a scale of 0 to 1. Attenuation basically means whether or not you want the sound to be played across the whole map, or to fade out over distance from where the sound is based.
float ATTN_NONE = 0; //no sound. float ATTN_NORM = 1; //throughout the whole level. float ATTN_IDLE = 2; //monster idle, pain. float ATTN_STATIC = 3; //diminish very rapidly with distance. put it in worldspawn.
worldspawn "_sunlight" "100" //light intension "light" "15" //minlight "_sun_mangle" "227 -57 0" //surround height 0 Sorry, the diagnostic message is misleading ("sunlight_mangle" was set to -0.126998 -0.720243 0.6681998 from commandline").. it's printing out an internal version of the mangle vector, that's different than the format it expects from the worldspawn / commandline.
Here are is the proper format from: http://ericwa.github.io/tyrutils-ericw/doc/light.html "_sunlight_mangle" "yaw pitch roll" or "_sun_mangle" "yaw pitch roll" Yaw specifies the angle around the Z-axis from 0 to 359 degrees and pitch specifies the angle from 90 (shining straight up) to -90 (shining straight down from above). Roll has no effect, so use any value (e.g. 0). Default is straight down ("0 -90 0"). Hope that fixes it! As I said, I already tried both options, from the command line and through worldspawn, and the result is the same.
If you have entered compile settings in your editor options, they may be overriding your map's worldspawn parameters.
Thank you Eric for explaining that, I see now what I have been doing wrong. It's not a lighting tool bug, it was entirely me. You would think having been mapping all these years I should have caught on to this from the start.
My embarrassing mistake was, the pitch angle was positive, not negative, so it was always shining straight up. This is what happens when you become overly frustrated, you start to make little mistakes and begin to think its something huge. Anyways, thank you again madfox and Eric, all is well. Is there a way in vanilla Quake to change where a message is printed to the player? The 'message' field on an entity normally prints to the middle of the screen, which is great for information about locked doors and things like that, but I'm looking for a way to make it print to the console/top left corner instead, like the ammo/armor/powerup messages.
Not without a custom progs.dat (QuakeC, probably items.qc) unless I am mistaken. 99% sure.
Somewhat surprising as well given the amount of things that are apparently possible through various entity hacks. Thanks for the quick reply, though.
What do you need this for, anyway? Centerprints don't exactly hinder view and Quakespasm also prints centerprints to the console.
There is a hack. Using the ammo_touch</a> as touch function in a custom info_notnull trigger, it will print "You get the" + whatever is in the netname field in the top left corner of the screen. This will not override the pickup message of the original item, so you'd have to make sure the trigger fires after picking up the item. Additional steps may be possible to hide the original message entirely.
@Mugwump
I'd had a couple ideas for making a map somewhat unique without needing its own -game switch; just small things like alternate item pickups outside of the standard gold/silver keys and ammo boxes through either stationary brush entities that are killed upon touching it or fancier, rotating brushes (cloned from a func_wall using this fantastic hack) to imitate the actual spinning keys. @negke That's fantastic, exactly what I was looking for! Getting rid of the 'You get the X' part of the message isn't a priority, as I would have ended up typing it in anyway; using ammo_touch as the touch field on a DIY-brush-entity makes a one-time trigger that not only gives you the message with your choice of 'X', but also plays the ammo pickup sound and screen flash. A little bit of fiddling shows that if you use key_touch instead, it allows you to use the noise field to play any (precached) sound you want instead, including the various key/armor pickup noises. It says Radiant now has Quake support (I know Eric made is, I tested it) but when I download it, I can't configure it for Quake. It doesn't show up in the list of supported games and there's no separate gamepack to download because the site claims it's built in.
What gives? I fail to see how centerprints moved to the top/console would relate to alternate item pickups.
As for alt keys and rotating brushes, AD can do that so you could make your map for AD instead of vanilla. So, I've been making my first map in Trenchbroom and Necro's Compiling GUI refuses to compile the map now. It gives an error message:
*** WARNING 01: No valid WAD filenames in worldmodel Processing hull 0... ---- Brush_LoadEntity ---- 371 brushes ---- CSGFaces ---- 2249 brushfaces 1974 csgfaces 1791 mergedfaces ---- SolidBSP ---- 126%************ ERROR ************ Didn't split the polygon (SubdivideFace) --------------VIS--------------- ---- vis / TyrUtils v0.15 ---- running with 4 threads testlevel = 4 ************ ERROR ************ Error opening eldertemple.bsp: No such file or directory -------------LIGHT-------------- ---- light / TyrUtils v0.15 ---- running with 4 threads ************ ERROR ************ Error opening eldertemple.bsp: No such file or directory The system cannot find the file specified. The system cannot find the file specified. 1 file(s) copied. Any ideas? Oh, and textures show up fine in the editor, plus the
Supposedly there's a weird brush somewhere or something but how would I find it? Is that even the problem? For Quake1 it's better to use the earlier versions of GtkRadiant.
Version 1.4 supports Valve half life and Quake. Version 1.5 also supports Quake. I can only create maps in it, as the links are rather queer to make. Texture files give possibility to 2 wad files, Quakewad101 and one of your own. It's a bit stubborn installing, but a very accurate editor. https://goo.gl/UyXRUJ
https://goo.gl/UyXRUJ http://celephais.net/board/view_thread.php?id=61357&start=77 Recommending any other radiant is retarded. I dropped the ball a bit, the 1.6.5 release shipped without the Q1 gamepack.
This was the game pack I prepared, just extract it in the "installs" directory with the other gamepacks and Q1 should work. https://www.dropbox.com/s/uj8iewxy2q7ozmt/Q1Pack.zip?dl=0 Oh, and textures show up fine in the editor, plus the
Supposedly there's a weird brush somewhere or something but how would I find it? Is that even the problem? I think you may have spaces in the path to your wad that TB can handle but QBSP.exe cannot. I'm guessing here... but the wad error at the top of the log is what you should correct and then see if there are further errors. I solved this (well, someone on QuakeOne did...) just now. It was because one of my brushes was weird. I can only conclude that it was something to do with the fact that I messed about with the texture scale in the wrong way.
I have three more questions. :D
First question: How would I go about building composite lifts - I.E. lifts made up of multiple brushes (such as a main platform, a thinner pillar brush below and a CLIP brush the same width and length of the platform but lower)? Because when I tried doing it normally with multiple func_doors, some of them raised back up at different times + other oddities, presumably because of their differing volumes. The second question is: Is there a "block light" brush? Yeah, that's it. The third one is: how would I go about making teleporter traps? (Where enemies teleport into the level)
|
|
| You must be logged in to post in this thread. |
|
| Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors. |