Just thought I'd say that again. 

Be interested in implementing support for 'proper' rotatings code?

Essentially it's true collision on rotating objects, without dicking about with multiple entities all over the place.

We had it implemeted in RMQ and it works like a charm. Obviously a way to mark the pivot (info_notnull) is still needed, but the rest is just making the brushes and configuring them.

Basically takes the pain out of making rotating objects.

Haven't got time just now but I can dig out the specs if anyone is interested. 

Also, consider the dynamic light bottleneck fix! 

proper rotating objects 

Is anyone seriously going to say no? :) 

requires a custom progs.dat, naturally, like hiprotate does. 

I would point out, i don't think the word "proper" should be used here -- doesn't it just rotate the hulls? (Sure it makes the mapper's life easier but) collision hulls are not equal on all axes -- the player is taller than he is fat, so collision hulls have more height added than they do width. Probably the results are fine as long as you only rotate on the Z axis. But if you tip an object onto its side (like a drawbridge) it will look funny when you try to walk over it. 

Been playing around with the Rubicon2 entities and all that rotating stuff. Why is the texture alignment on, say a hatch that only opens 90 degrees, totally screwed?
and setting up those func_movewalls for collision is elaborate(to be honest a pain in the ass..)
Sorry for the wrong thread, just had to let it out:) 

the texture alignment on rotators is a compiler bug, i hope someone fixes that someday.

and yes, func_movewalls are annoying to set up. Though they don't really take that much time, it bothers me more how limited they are in functionality. 

oh, if you are asking about why the texture alignments are messed up in the .map files for rubicon2, that is to correct for the compiler bug. I had to make them look wrong in the editor so they would look right in the game. 

So this is at offset 0 0 0 i guess?
Confusing.. 

yes, my technique is to move the model so to 0 0 0, fix all the texture alignment, then (with texture lock disabled in the editor) move the brushes back to the correct location in the world. 

Center of model at map origin?
Or the lower left corner of the bbox put at origin? (Like when path_cornering?) 

lower left corner (i'm pretty sure) 

Will try out, thanks!

Is there a chance a compiler(like BJPs Tools)
could be fixed, so that this setup is irrelevant?

Just curious. 

But we're capable of improving what is there, the reason I'm asking.

Props go to Gb for writing the original qc frontend.

Easier for the mapper means we'll see more rotating things in maps, and I can't see how that could be bad (disclaimer).

I'll implement the code from RMQ in RRP for now.


If you don't build it, then it's not built. 

they're solid_bsp. 

It causes an intermittent 'pop' when looping sounds wrap around - this has been driving me crazy for years!

omg THANK YOU. I hated that pop! 

Ok - Since no-one's reported sound niggles, Eric's sound loop fix is committed.

ijed: [mouse] Is still locked in top left corner if I alt-tab out, from the menu, console or otherwise.

Hmm - i'll have to test it in windows sometime. It works acceptably for me on linux, but if it's broke on OSX/windows it may have to be reverted. My change was just a hack-and-see.

Re other changes - i can't say. I guess if people feel strongly, patches are welcome, but main focus is to fix things, not break them ;> 

I can't tab out of the engine, but I can put it into windowed (alt+enter) and then hit ESC to show the menu, which will release the mouse pointer. 

Well i guess we'll have to remove the hack.
Maybe there's some other SDL befuddlery to get it going... 

How about a patch to remove the 4096 +/- limitation? 

Isn't that limit there to stop floating point hilarity with large world coordinates? 

Isn't that limit there to stop floating point hilarity with large world coordinates?

Sort of - the hardest limit on coordinates comes from the standard network protocol, where entity coordinates are sent as a 16 bit integer (so fixed precision at 1/8th of a unit). Even with a less bandwidth efficient netcode, server-side locations are recorded in floating point. Before you could make truly huge maps you'd need to consider upping that to doubles for precision of small movements (and then deal with how QC can't handle doubles). 

So it's not just an arbitrary limit then.

Ok, will make stuff fit instead.