Getting Closer
#14100 posted by bennett93 on 2014/07/14 20:39:17
now it says opened log bspc.log no files found
#14101 posted by bennett93 on 2014/07/14 20:53:34
ok now the in program gtkradiant aas conversion worked, how do i make the bots do something after they teleport to another room? and thank you all for your help
Also
#14102 posted by bennett93 on 2014/07/16 01:59:21
do you guys know how to make a open map "outside" i want to replicate q3dm17 and be able to kill whoever jumps/goes "off" the map
#14103 posted by necros on 2014/07/16 04:35:05
those maps are not really outside. they just have the entire main structure floating inside a box with the sky texture on it, then they put a trigger_hurt (or the q3 equivalent) with a super high damage on it above the bottom of the box.
What Necos Said
#14104 posted by quaketree on 2014/07/16 05:49:06
And
#14105 posted by Rick on 2014/07/16 08:23:20
as best as I remember, without going and looking at a map, you also need a trigger to play the Player death scream sound and another to remove the weapon they drop.
Open The Editor
#14106 posted by ijed on 2014/07/17 15:35:57
And do it. Come back when you have more solid ideas about what you want to achieve.
If you try to build on the idea too much before putting brushes together you'll get frustrated once you get to that stage.
<smiley face>
Wtf Light
#14107 posted by - on 2014/07/24 23:26:18
I have a weird lighting issue in my jam map in a single corner... it's a dark shadow along a seam that only occurs when the map is vis'd. If the map is unvis'd, the seam doesn't show.
Any ideas how to clean this up so there is no seam? The light from that light fixture is a upward spotlight, delay 3, and a small delay 2 light. Using the latest tyrlite. All my other corners set up exactly the same don't have this issue :_(
Try moving the lights extremely slightly. Or if you're using trenchbroom try using snap to grid on the geometry. :P
Tinkering a bit tends to work out for me. I get loads of weird lighting bugs all the time
Light After Vis
#14109 posted by mfx on 2014/07/25 00:14:43
#14110 posted by - on 2014/07/25 00:25:43
er... well, I took vis out of the equation completely and it still lights funny... I should've really specified "the seam only appeared when the map was sealed", rather than vis being the culprit, since I'm sure vis itself isn't doing anything to the faces that would effect lighting.
Brushes are absolutely and completely on an 8 unit grid. I use Radiant, so there's no need to guess if I making a mess. I guess I'll poke the light positions a little and see if that helps... but not hopeful there.
I Wonder
#14111 posted by mfx on 2014/07/25 00:38:47
maybe the brushes join in an other way as the others corners?
But i guess you checked, hmmm.
Do you have skybrushes behind that geometry?
i found light sometimes leaks through, when dabbling with commandline parameters :)
Is the texture scaled?
I have no clue.
#14112 posted by JneeraZ on 2014/07/25 00:59:04
"Light After Vis"
What difference does that make?
I find that I get different results depending on whether the map is sealed or not. I try to work with a sealed map just so I know it's working right.
#14114 posted by metlslime on 2014/07/25 01:10:08
"Light After Vis"
What difference does that make?
Shouldn't make any, it seems that Scampie really meant sealed vs. unsealed.
Sealed maps have additional surface splitting/BSP optimizing steps in them, so i can see why it would affect lighting.
Afaik
#14115 posted by ijed on 2014/07/25 01:23:55
It depends on how the geometry gets flattened to UV to create the light map.
The problem occurs most with diagonals, depending on the resolution of the light map. So setting extra4 will help it a bit, but still leave a shadow.
Either way, only try and fix it once the map is finished, since all additional world brushes will cause the light map to be recoordinated - which is why a leaking map is ok, because then light doesn't try to optimize the UV space. Meaning you also get poorer resolution shadows.
Well... I Fixed It
#14116 posted by - on 2014/07/25 01:30:47
After eating some dinner and thinking about it, I decided to split the brushes, and shifted their texture alignment 1 pixel horizontally (not noticeable) to force qbsp to make them each different faces.
Here's r_showtris of the bad lighting and the fixed lighting.
Looks like the lesson is "Throw more polygons at it until it looks good"
#14117 posted by - on 2014/07/25 01:32:56
ijed: yeah, that sounds about right and why my fix worked.
(as an aside, I was compiling with -extra4 -soft - gate 10... mainly because my compile still is reasonably quick)
#14118 posted by mfx on 2014/07/25 01:39:42
"Light After Vis"
What difference does that make?
I made a switchable light setup once, which was spawnflag 1 (start turned off) , lit and vised the map in that order, and the light was turned on... All the time.
So i lit it again, and the switchable light behaved like it should.
I Have A Problem
#14119 posted by mfx on 2014/07/25 02:03:13
with some trigger_relays (3), which are all triggered by a trigger_once.
They have different delays (instant, 0.2, 0.1).
When running this map in the rubiconmod from ijed, everythings fine. Even in quoth this works.
But in vanilla progs only the first relay gets activated, the other two not? Is my progs.dat corrupted or what is going on?
Its late..
Do You Believe
#14120 posted by RickyT33 on 2014/07/25 03:04:20
in light after vis?
Should Make No Difference, Or..?
#14121 posted by mfx on 2014/07/25 03:10:24
What i believe is something else.
Different Progs!?
#14122 posted by ijed on 2014/07/25 03:40:18
Don't jump ship! I'm sure the other map will be finished soon...
And looking at the code everything seems fine - I can't see any particular thing labelled as a fix.
I didn't apply any changes to the triger system apart from is_waiting, which won't affect SUB_UseTargets. But bear in mind this is code inherited from various sources.
I have seen the bug you describe in 1.06 so I assume someone did make a fix, but didn't comment it as such.
I could do a diff, but I don't have any diff software installed on this machine.
Mfx
#14123 posted by Preach on 2014/07/25 06:10:25
Can you e-mail a copy of this map to me? I'd like to investigate but it's hard to reproduce the specific issue you're encountering.
I posted a series of blog posts about how Quoth does triggers, but it's certainly very different code to the original, and contains behaviour changes. If you are running into a very specific bug in the original progs there's a good chance it's not present in Quoth simply because the code is so different, rather than a deliberate targetted fix.
If it's a behaviour change which avoids the bug, then I can't see which one it can be. One of the things that's changed is that multiple target, targetname and killtarget fields are supported, but that shouldn't affect a vanilla-built map. Another change is that an entity in Quoth can have a killtarget and still fire targets afterwards - in vanilla the code skips target if killtarget is set. But that doesn't explain why one would fire and not the other two...
Scampie
#14124 posted by necros on 2014/07/26 17:31:18
an alternative would be to put a skip texture on the offending world face and make a func_illusionary with the same brush without skip on the face. i've done that a few times and it seems to work fairly well.
|