obsidian wrote:So does this mean you will soon post a new record time for Quake Done Quick, one in which your computer does all the work?

Hopefully

For future reference, you should type all that into the video description, so people watching your video don't have to watch 8 minutes of you typing with 1 minute of actual demo. :offended: Sorry, that is pretty derpy... Interesting concept, though I think you also need to keep in mind that real pl...

Forgot to post this here. Comes with an overview of what I'm doing at the beginning - note you should watch it in 720p for more legible text. I'd like to actually turn this thing into something that can be included with Radiant and produce a demo map showing how to use it, but the amount of engineer...

It looks to me like what is going on in the Forsaken video is the same movement as the spectator in Q3, only with a slight rotation when you start to strafe. I would search through the code to see how the spectator's view is being handled. As you note, you can access YAW PITCH and ROLL so you should...

obsidian wrote:There is a bug in GtkRadiant where the colour values aren't properly being converted by the colour picker, so choosing a 50% value would result in a normalized value of 0.49609... or 0.50196... because of some dodgy math and failing to increment.

Is that on the issue list somewhere?

^misantropia^ wrote:inolen, how's the project coming along? I confess to being a teensy weensy intrigued.

Kaz, is https://github.com/freemancw/Q3Plan your project? I'm guessing yes.

Yessir

edit: don't judge potentially crap code

Ahh, yes, the engine uses the entity number as part of the int32 sort key for the draw surfaces. You could fiddle with removing some bits used by the shader number (SHADERNUM_BITS is 14) and adding them to ENTITYNUM_BITS (which is 10). 16384 shaders sounds rather generous. Thx for the suggestion......

The localents are stored in one big pre-alloced linked list, the max is defined at the top of cg_localents.c - pretty easy to up it seems. I don't think there is a restriction on their resulting refents. I upped the localent limit to 4096, but then I hit the overall entity limit and get an error me...

Actually here's a better shot of what's happening - unfortunately I hit the entity limit almost immediately :(. Is there any easy way of upping the max entities, or is that going to be the pain in the ass I think it is? Edit: I think I just just add polygons directly to the scene instead of creating...

Eraser: doesn't Steam have similar functionality to IndieCity? why not use that? I want to be able to approximate the time it takes a player to move between pairs of locations in a level. That way, you can report timings for pairs of items, or even display the "time reachable set" for a gi...

Working on putting some different motion planning algorithms into Q3 - here Sarge randomly hops around...

inolen: Should do D3 in browser next!

[lvlshot]http://cs.unc.edu/~freeman/junk/naiveplanning.jpg[/lvlshot]

Most of this is not really useful from a LD perspective, but may be worthwhile if you want to know what's going on...
http://www.kbs.twi.tudelft.nl/docs/MSc/ ... thesis.pdf

- phpbb's primitive like button

:up: Seems like it'd be a huge undertaking to port all of that to JS, but neat nonetheless! Wish I had time to do stuff like that >:( I spent last weekend playing around with Bullet and Awesomium - something inherently great about having jQuery UI in an OpenGL app. Here are some flying Utah teapots....

As we talked about on IRC the rendering geometry definitely isn't getting chopped by split planes. However, intermediate geometry is actually chopped up during compilation, which seems like a point of confusion (for me at least). Hint planes are split planes with a higher priority for selection. Tha...

AEon wrote:Yes, that is what I thought.

Okay I see... didn't read the question correctly. Hint planes should be chopping geometry in half, they're just regular split planes with higher priority (AFAICT).

I agree about the fluting on the plasma thing. Something more uniform like straight with rounded corners would make more sense/look better. Or maybe multiple windows into the blue plasma, each straight with rounded corners, but the outer ones having a shorter length (if that makes sense).

I always thought that hint brush planes actually cut up structural geometry when they are extended into e.g. walls. But after some though that does not seem to happen, only the "empty" space in the map gets cut up, right? I probably knew about this, only forgot, and was adding hint brushe...

I wonder how consistent local hint is - I would guess there are some weird cases where the local hint gets selected as the split plane higher up in the tree than the containing room?

Doors don't have collision against level geometry on them so you don't actually have to make slots for them

I think it'd help alot if you can do something to make it less dark / more contrast / more colorful lighting. Lava pit + blue teleporter lighting is good --> expand on that?

+1 for egypt

@MuffinMan: Euclidean distance is just standard straight-line distance