Sauerbraten release 2006-06-11 out!

by Aardappel_ on 06/12/2006 07:21, 322 messages, last message: 07/31/2007 16:33, 376083 views, last view: 11/01/2024 18:36

http://sourceforge.net/project/showfiles.php?group_id=102911

As usual, feedback SPECIFIC TO THIS RELEASE in this thread! thanks!

* scripting language: every command/block/exp can now return string values (no more use of variable "s", much cleaner code)
* scripting language: reduced allocations a great deal, should execute faster now
* scripting language: can now write X = Y instead of alias X Y for more readable code
* If sauer crashes on a non-programmer machine on Windows, it will now output a stacktrace (both in a popup and the console window) which can be copy-pasted and sent to the developers (do this before you press "OK" to close the program, from the console windows menu).
* added provisional "sendmap"/"getmap" commands for coopedit mode
* explicit sky polies are now outlined in editmode (toggled by "showsky" var)
* now shows names of entities floating in edit mode (in green, closest = red)
* any non-multiplayer games can now be paused (variable "paused", default key F1)
* fixed rockets exploding mid-air if they were aimed at a moving target
* copy/paste now work in coop-edit
* moved all mapmodels into the menus
* new SP respawning system! read "SP Respawning" in game.html
* console language macros now allow code generation (see config.html)
* added customizable file completion (via "complete" command)
* aliases and vars set in map cfgs are now sandboxed (don't persist)
* world shaders can now work with any number of textures (see "texture" command).
* support for specularity maps and glow maps on md2/md3 models (see md2.txt/md3_sauer_howto.txt)
* new "editbind" works like "bind", only the key is only available in edit mode. cleaned up keymap/default cfg files (no more bindings in keymap)
* added triggerable mapmodels (see editref.html for more info)
* removed the z-offset attribute from mapmodel info and ents and moved mapmodel ent skin attribute to mapmodel info (see editref.html)
* added support for full screen pixel shader effects (see setfullscreenshader, and the "option" menu)
* removed obsolete editheight command
* added powerful new heightmap mode! use getheightmap command [default H key] when there is a selection box to activate (see editref.html for more info)
* added selectbrush modifier [default J key] that switches between brushes defined in data/brush.cfg
* added copybrush [default K key] to use current heightmap as brush. see data/brush.cfg for more info.
* editable brushes for heightmap mode. see data/brush.cfg for more info.
* capture gameplay mode fixes
* ip address lookups now use the concurrent resolver
* added redo command [default I key]
* made importcube remip while importing to save memory
* removed some lighting/physics bottlenecks in SP mode
* removed 256 textures per map limit (is now 64k)
* fixed incorrect mapmodel shadows on Windows
* fixed invincibility bug

   Board Index   

#47: Re: ..

by kurtis84 on 06/13/2006 17:00, refers to #44

this glowing effect you see is probably just an extra alpha masked layer on the skin thats not effected by lightlevels around it...we can do that with geometry now...I assume models use the same shader methods? For example, makke could make another skin that is the same dimentions as the original, but make all areas of the skin trans, except the part he wants to glow. Then use the "decal" shader to load this second skin over the original.

reply to this message

#48: gamma

by bloo on 06/14/2006 01:02

The /gamma command does not work the same way it did in the last release for me.

As I understand the gamma range is 30 to 300. I can get the command to function from 30 to 100, but any value 101 to 300 does not change the screen. It seems to cap at 100.

I am running a G4 with an ATI card. I tried the bug command, but neither setting made a difference for gamma.

Any thoughts?

reply to this message

#49: Bug fix - z buffer

by guest57 on 06/14/2006 01:49

I note that placing a:
SDL_GL_SetAttribute( SDL_GL_DEPTH_SIZE, 32 );
just before the:
SDL_SetVideoMode(...) in main.cpp
fixes many z-buffer accuracy bugs I was having with small (or distant) textures...

- aka rpointon

OSX 10.4.6 2x2Ghz PPC, ATIx800

reply to this message

#50: Re: ..

by Aardappel_ on 06/14/2006 03:14, refers to #44

I don't see how thats different from what we do. To me, a glow map says that 1 (255) means the diffuse should not be affected by lighting (fullbright), and 0 means it should be. That's whats happening on darkplaces screenshots, and in sauer. How does sauer do the opposite?

reply to this message

#51: Map rotation patch

by eihrul on 06/14/2006 06:47

There is now map_rotation_patch.zip in the files section for this release. It is a client-side fix for map rotation, which we somehow managed to break in this release.

reply to this message

#52: Re: Map rotation patch

by eihrul on 06/14/2006 06:48, refers to #51

Forgot to add: unzip within your sauerbraten directory.

reply to this message

#53: Re: Map rotation patch

by Passa on 06/14/2006 09:47, refers to #51

Meaning it is needed for servers? What does it do? Did you bump the protocol version?

reply to this message

#54: Re: Map rotation patch

by MeatROme on 06/14/2006 13:24, refers to #53

it's just a replacement for "data/menus.cfg" ...

reply to this message

#55: curious crash command

by MeatROme on 06/14/2006 13:27

If you want to crash your engine,
simply try entering "%s" in your console at any time.

reply to this message

#56: ..

by Max of S2D [Fr] on 06/14/2006 14:46

I don't understand if the fullscreenshader is working. I type "setfullscreenshader" command, while watching the sun. I don't see differences. I'm look like an idiot, or not ? XD

And after, two thumbs up ^^ for the Sauerbraten crew :) thanks you a lot, Aardappel !

reply to this message

#57: ..

by makkE on 06/14/2006 16:31

Try esc -> "Options" "Fullscreenshader"

reply to this message

#58: Re: ..

by Pxtl on 06/14/2006 16:59, refers to #57

Doesn't work on my box, but I get the "non-square textures" warning on startup which probably means my little ATI 9600 isn't really specced out for the blooming mode.

reply to this message

#59: ..

by Max of S2D [Fr] on 06/14/2006 17:32

It's the same for me, ah, DAMNED ! I was really boring while i was waiting the fss, and my graphic card isn't enough good ! -_-'

reply to this message

#60: Re: ..

by rpointon on 06/14/2006 17:37, refers to #59

I have a ATI 9600 at work and it works fine, and yes, thats with a "non-square textures" warning. I assume you have shaders turned on?

type: setfullscreenshader bloom 400, or use the menu.

reply to this message

#61: ..

by Max of S2D [Fr] on 06/14/2006 17:59

I got a lot of Win32 exceptions v_v

reply to this message

#62: Triggers in edit mode

by MeatROme on 06/14/2006 19:38

Is it a bug or a feature?

The mapmodel now also triggers when floated through during editing.

reply to this message

#63: Re: ..

by Pxtl on 06/14/2006 20:00, refers to #60

Nope, I get the "non-power-of-two textures not supported" warning, and I enable the blooming (or even try the reversing shader in the menu) and I don't see anything. I've got the normal default startup - no "-f" or anything, so presumably shaders are enabled. Any tips on why I'm not getting blooming?

reply to this message

#64: Re: ..

by Pxtl on 06/14/2006 20:11, refers to #64

Hooray for ATI.

reply to this message

#65: Nope.

by Pxtl on 06/14/2006 20:52

Just updated my drivers. My AIW 9600 still doesn't like the fullscreen shaders.

reply to this message

#66: Re: Triggers in edit mode

by MeatROme on 06/14/2006 20:59, refers to #63

well. I've been working on an SP map and it had a couple of triggers.
I replaced them with mapmodel-triggers (20060611 release) and if I fly through these during edit mode I get the same result as having touched it during normal play.
Also doors open/close for me if I fly through them in edit mode.
See sauerbraten FPS Episode #1 or door_demo (only non-triggered doors!).

Mmmh. Just did a re-check - I can't reproduce it now either. Probably some glitch occured while I was working on the map ...
... but I distinctley remember being freaked out by a door opening/closing for me in edit-mode (FPS Ep.#1) so it wasn't just on my map for sure!

reply to this message

   Board Index