Official forums for BZFlag.org

"pyrwall.png" works just fine, that's not the real issue.

try using mesh.png instead of pyrwall.png, maybe that will shed some light on your problem.

Here's a lua module version for 2.99.x:
http://trepan.bzflag.bz/veldrv.lua

BZFlag SVN r21252 does not use the lastScreenshot BZDB variable.

From the top of veldrv.cpp : //============================================================================// // // VELOCITY DRIVERS // // author: Dave Rodgers (a.k.a. trepan) // brief: BZFS plugin to implement velocity drivers (via physics drivers) // date: June 28, 2010 // license: LGPL v2.1 // //...

Here's a plugin for BZFlag v2.0 that implements "velocity drivers". Velocity drivers are physics drivers that change a player's linear and angular speeds when they touch them. You could use this to add mud, tar, and speed-up zones to your maps. This plugin probably only works on systems th...

you are missing the "end" for the pyramid block.

...(as it's the first movie adapted map ever)... Wrong. Crack open the following link, and find worlds/darkcity.bzg Guess what movie that's based on... Note that the file is dated 2005. http://trepan.bzflag.bz/bzmapper-g2.3-src-exe.zip For what it's worth, I don't doubt that there were movie inspir...

@ ts <-a 0 0> can probably be achieved by setting the _inertiaAngular and _inertiaLinear variables to 0. Tank hit dimensions can be adjusted using the _tankShotProximity variable. The current default value is "0.25 0.35 0.25 0.0" (xPadding yPadding posZPadding negZPadding). Shockwaves have...

Do you know if the player counts include observers?

Currently, I'm counting 78 players and 42 observers.

Of those 42 observers, it looks like the greater part
is composed of "non-active" clients (administrative
or logging observer clients, probably using bzadmin).

Or, is BZ Dying?

Thanks, fixed in SVN commit r21182.

I'll note here that I re-added the client-side lua scripts a few weeks ago. I hadn't planned to, but whatever ;) A new script has been added to the roster, LuaRules. It is much like LuaWorld except that it is capable of adjusting the state of the game by such call-ins as: ForbidShot(), ForbidJump(),...

Note that the source code that I posted here will no longer work: http://my.bzflag.org/bb/viewtopic.php?p=137273#p137273 Only BZDB variables that start with ' _ ' or ' $ ' will be accepted by bzflag clients from the server. This is to protect the client from nasty servers that want to change variabl...

Heh, that's a remarkably ironic worry.
Look at SpringRTS' history before fretting too much.

All that and a lot more can be done using the client-side Lua. Actually, all of those features have already been added to the SpringRTS game using the Lua API that I added to their engine (particles, camera shake, shell explosion distortion shaders, Xray effect, rain/snow, bloom, blur, toon, GPU-sid...

One new feature that you might want to try is: Options -> Effects -> Shot Length

Try adding #include <string.h> to the top of the file.
(fwiw, this has already been fixed in the SVN trunk code)

for lack of a better explanation on your part:

bzflag -view anaglyph

I created a bzw.jsf syntax file for the joe editor years ago...

That test currently applies to all objects, even drivethrough objects (search for COLLISIONMGR in src/bzfs/bzfs.cxx for the related code). If someone decides that they want to exclude drivethrough or passable objects in the code, they should handle link faces with care. Note that the behaviour for f...

1. Start a server with the map:
bzfs -world mapname.bzw

2. Join the server:
bzflag localhost:5154

3. Save the map in OBJ/MTL format
/saveworld -o filename

4. Import the OBJ/MTL into Wings3d


Something along those lines should do the trick.

Something that should be added to the bzw.5 manpage: MeshFace teleporter links use the drivethrough and shootthrough properties to determine the types of objects can pass through the links. A few notes about horizontal teleporters: 1. linkSrcTouch is probably the best approach (without 'passable') 2...

With SVN r20710, I've added the noRadarOutline parameter to materials (which works for both mesh face links and bases), and removed the linkSrcNoRadar mesh face parameter. This could help you clean up the look of the team bases in the radar (all those outline segments...) If you used bzfs -setforced...

If you are using BZ2 auto-converted boxes (not meshboxes), negative
values for the texsize will probably do what you want (tl;dr...)

The texautoscale material property that was added to SVN code
might also be of interest. It's similar in effect to the anti-flicker
back-port that I made for BZ2.