Yep
#915 posted by ericw on 2017/08/31 04:50:59
you can just use skip
Ah, Got It.
#916 posted by damage_inc on 2017/08/31 04:56:38
But another question, hehe... sorry :(
I think this is a side effect/limitation of the QCat play here, but items or brushwork inside the "water" don't have, hrmm how to say this... correct perspective? Does that make sense. They just look strange.
I've seen this before but can't remember what it was.
#917 posted by ericw on 2017/08/31 05:23:33
I think it's a limitation of the QC; if you run it in an engine that has the swirl effect underwater like winquake, you don't get that with func_water, you only get the screen tint. I dunno if func_water is messing with the fov cvar or something?
#918 posted by Spike on 2017/08/31 09:07:41
more of an engine limitation in that the vanilla engine doesn't bother to check submodels for pointcontents, both in the physics+qc builtin as well as clientside too.
(you also need a qbsp that doesn't claim water to be solid, along with generating inwards faces.)
one of the ladders mods has something like 3 different glitches relating to said mod's ladders (breaks at certain framerates, leaves players stuck in walls, etc.
so watch out for that.
#919 posted by PRITCHARD on 2017/09/04 14:46:31
Is there any risk in using the 0.15.9 light binary with the rest of the 0.15.10 release? I've posted screenshots on the mapping help thread and github showing my reasons why.
Having all the qbsp improvements from 0.15.10 would be nice, after all... especially the func_detail fixes.
It's Safe
#920 posted by ericw on 2017/09/04 19:13:58
The only problems would be stuff like: func_detail_illusionary will always cast shadows, and func_detail_wall would cause lighting issues if it's covering world geometry.
I would go for it; the func_detail fix in .10 is worth using.
Sorry I haven't fixed this earlier, also noticed some light seams in shib1.bsp that are probably coming from 0.15.10. Fixing the code or reverting the relevant parts will be my priority for the next version!
_minlight Being Ignored?
#921 posted by PRITCHARD on 2017/09/06 05:11:56
Getting Your Christmas Jam On I See
#922 posted by Qmaster on 2017/09/06 05:26:02
That's Messed Up
#923 posted by ericw on 2017/09/06 06:34:22
let check if I can reproduce it
Weird
#924 posted by ericw on 2017/09/06 07:05:24
I couldn't reproduce it. tried both 0.15.9 and 0.15.10's light. Mind uploading a sample to github? Hopefully this should be a quick bug fix.
@ericw
#925 posted by PRITCHARD on 2017/09/06 09:14:08
Emailed you a .map and .bsp/.lit
And yes, this is for the Christmas Jam :3c
Sorry For The OT, But
#926 posted by Mugwump on 2017/09/06 12:17:41
if you look just below your pic in the first link, there's a pretty badass fan art of Vader slaughtering Ewoks.
?
#927 posted by Qmaster on 2017/09/06 20:06:17
Does _mirrorinside 1 not affect {fence textures? It's not working for me. Do I need both light and qbsp, I'm only using the qbsp from version 0.15.10
#928 posted by ericw on 2017/09/06 20:26:30
It's not in 0.15.10, I posted a dev build link in though #910
Should work on fence textures
Hrm
#929 posted by Qmaster on 2017/09/06 20:34:52
Still didn't work.
@Qmaster: Worked For Me.
#930 posted by damage_inc on 2017/09/06 20:51:46
I had func_detail_fence, skip textured all sides except for 1, which had the AD vines.
Saw them from both sides.
Pondering!!
Would it be possible to have model->geo baking like q3's misc_model(static)
#932 posted by ericw on 2017/09/06 22:21:44
I've played with that in the past, but I didn't understand QBSP as well so it didn't work very well. It's probably doable to bake in a model without converting it to brushes, but it would be illusionary only (doesn't stop bullets, no collision) so I'm not sure if it's worth the effort.
If you want collision (player / monster / bullets) qbsp needs brushes, so you can use obj2map or something to convert to .map first (turning triangles into tetrahedrons with obj2map will probably give you a bloated / inefficient bsp, though).
Wait
#933 posted by Qmaster on 2017/09/06 23:03:07
Do I need to use func_detail_fence only? I've been using func_illusionary.
Qmaster
#934 posted by ericw on 2017/09/06 23:20:40
no, I tested it with func_illusionary. I don't know why it's not working for you, check spelling? "_mirrorinside"
Build version should be "tyrutils-ericw-v0.15.10-12-gd86913a"
Func_illusionary Also Worked.
#935 posted by damage_inc on 2017/09/06 23:23:22
No, not func_detail_fence only.
When I first tested I used func_illusionary and then thought, "Oh wait, he mentioned fence!" So my brain connected dots that weren't there :(
What didn't work for me was standard func_detail and func_detail_wall
hth's
#936 posted by muk on 2017/09/07 00:40:23
"but it would be illusionary only (doesn't stop bullets, no collision) so I'm not sure if it's worth the effort. "
Still worth it, imo.
D'oh
#937 posted by PRITCHARD on 2017/09/07 02:38:53
I think I figured out my shadow bug on my trees - it was the old "intersecting brush with func_illusionary" bug.
My trees have a little solid brush in the center as a "trunk", and making it into another func_illusionary seems to fix the issue.
Still, having a fix for that bug would be nice...
Hang On
#938 posted by Qmaster on 2017/09/07 03:31:31
Turns out it wasn't compiling with the ericw qbsp at all in either version. I usually just hit yes whenever JACK warns me that prt wasnt made since I know my test map isn't sealed.
Not sure what's up. The output says almost nothing to the compile dialogue. Just says the compile path and path to file which are correct and nothing else.
Do I need any sort of compile parameter to compile 220 map format? Already tried the usual admin privileges.
Huh
#939 posted by Qmaster on 2017/09/07 04:02:44
Ya going back to tried and true txqbsp modified by mh and it compiled just fine.
?
|