Sauerbraten release 2006-06-11 out!

by Aardappel_ on 06/12/2006 07:21, 322 messages, last message: 07/31/2007 16:33, 376174 views, last view: 11/02/2024 00:27

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   

#208: Re: Follow-up

by MeatROme on 07/03/2006 01:38, refers to #207

@2 : as far as I understand the idea to up the difficulty is simply to place MORE monsters ;-)
... the Cube/Sauerbraten SP Games rely not on the AI for making life difficult for the player (although you can use it as a map designer) but more on their sheer numbers (see the docs, I'm sure I read something by aard about this approach somewhere).

If you're willing to wait a while I guess the capabilities of Eisenstern - respectively what we will be able to script for the NPCs (non-player characters) - will probably come close to your idea ... maybe even surpass them.

Let's see what we get ;-)

reply to this message

#209: Re: Follow-up

by TentusResurrect on 07/03/2006 07:13, refers to #208

I'm in favor of Sauer using the age-old RPG trick, where we just reskin the monsters and make them a bit tougher, but treat them as new monsters altogether, therefore allowing the mapper to add in a bit of progression. There are tons of techniques which follow this basic premise, ranging from reskinning to resizing to adding some extra meshes and effects. All let us reuse our models and same code.

Another solution would be to make "favorable" areas for monsters, in which the monster gets a little tougher, so by luring them out you could make your life easier. I can't think of a ready example, but we all know how it is (fire monsters getting extra "hit points" or whatever in a fire area, etc). A simple entity would suffice for this, by have a radius value, an alignment value (which monster it applies to), and a bonus value (plus 2 or maybe even minus 10, so that there could be "safe" areas.)

reply to this message

#210: ..

by Max of S2D [Fr] on 07/03/2006 09:21

It's weird, i've all the time the "0 score" in Sauerbraten Episode 1...
Also if i play by two different ways ; good or bad.

reply to this message

#211: Re: Gamma...

by SanHolo on 07/04/2006 00:40, refers to #204

I have to state more precisely about the gamma-issue:

I _can_ set the gamma below 100, but I _cannot_ set it to higher than 100, it will just stay at the 100-setting. This was possible in earlier versions of sauer as I am used to play with a gamma of 160.

No matter if I use shaders or hardware-occlusion or both or nothing.

I didn't touch the config.cfg, my settings are all in the autoexec-file. Any ideas?

Mac OS X 10.4.7, Radeon 9000M 64MB.

reply to this message

#212: send/getmap corrupted lightmaps

by rpointon on 07/04/2006 10:57

In using getmap I've noticed that most of the maps appear to have corrupted lightmaps, i.e. the shading it totally mad - checkboard, stripes, etc...

Then yesterday I did a send followed by a get and it came back mostly fine, but then everyone else was seeing corrupted lightmaps. I'm now wondering if it could be an Endian issue - I'm on a Mac (PPC), whereas I expect the majority of people are using x86.

reply to this message

#213: Re: Gamma...

by 2Cents on 07/04/2006 12:07, refers to #211

Even if _you_ didn't touch config.cfg (as you shouldn't, it's the auto-save-file) ,.... sometimes it gets corrupted entries.
Since it is loaded at next engine start (and written just before /really/ quitting) it might botch up your configuration.
But as aard said a couple of posts above - there might be an OS issue here ... but you keep insisting it used to work.
Just move config.sys somewhere out of the way; don't delete, just rename to "maybe_botched_config.cfg" or something.

reply to this message

#214: Let's see what we get ;-)

by Morosoph on 07/04/2006 15:24

Sounds pretty good to me.

I just like the idea of (say) an end level with two ordinary Bauuls and a tan Bauul (more skilled) that is also larger (more HP proportional to volume of the beast); somehow it just seems more interesting and fun to me than having five ordinary Bauuls.

A game mode that mixes monsters and players might also be cool; I'm just floating this one. They'd have to keep spawning, but maybe "skill" would control the rate, and they'd spawn faster when they were fewer (proportional to [1/existing_monsters])?

That said, I'm glad for whatever the devs give us. Sauerbraten is a dead cool game.

reply to this message

#215: activate fullscreen shader question

by da-old-mitaman on 07/04/2006 20:15

OK, so how do I activate full screen shaders (bloom, for example) to see all that eye candy?

I've tried from the options menu and typing in the following command at the console:

setfullscreenshader bloom

I only see the "normal" shader effect on map models.

x1300 256mg ATI vid card
newest ATI driver
directX 9.0c

Thanks in advance for any insight.

MitaMAN

reply to this message

#216: ..

by makkE on 07/04/2006 20:54

Try:
setfullscreenshader bloom 500
for a more drastic effect.

It needs a value. The bloom in the options menu is very subtle in some maps.

reply to this message

#217: Re: activate fullscreen shader question

by shadow,516 on 07/04/2006 21:36, refers to #215

minimize sauer and look in the console if it says "your card does not support texture rectangles" or something like that. Most of the ATI cards seem to have that problem. I have an X300/X550 series card with the newest drivers, and I cant get them either :/

reply to this message

#218: Re: activate fullscreen shader question

by da-old-mitaman on 07/04/2006 23:44, refers to #217

Yeah, thats it, my card does not support it. I get a "your card does not support texture rectangles, no fullscreen shaders for you" message.
Oh well, looks like a better vid card is on the horizon.
Thanks shadow,516 - MitaMAN

reply to this message

#219: Bloom costs 2/3rds of your frame rate

by Morosoph on 07/04/2006 23:52

It's cool, mind!

I've got a choice: do I run at 2048x1536, or 1600x1200 with bloom? I choose the former...

reply to this message

#220: Re: send/getmap corrupted lightmaps

by eihrul on 07/05/2006 03:40, refers to #212

Sendmap/getmap doesn't actually send the lightmaps at all (or the cfgs or anything else). That's a feature to save on bandwidth, and partly why it is coop-edit only.

Just that the surface info wasn't getting cleared properly when the stuff was sent over. Nothing to worry about and easy enough to fix.

reply to this message

#221: Re: Gamma...

by SanHolo on 07/05/2006 22:02, refers to #213

@@ 2Cent

It's not that I didn't try to delete the config.cfg, I did that several times, and even deleted the autoexec.cfg, but no go.

Setting gamma below 100 does work, setting it above doesn't work. It did so before the June-release.

Doesn't work on my 1GHz G4 with Radeon 9000 and on my old G4 350 with Rage128 (cant play there anyway, but wanted to test it – same result).

reply to this message

#222: Re: Gamma...

by absinth on 07/05/2006 23:38, refers to #221

i can confirm this, gamma > 100 is just broken at least on osx in this version, on a fresh install.

see #166 for a exactly the same problem in linux

even if "its an SDL/driver/OS thing" it's weird thats it broken for so many people in this release and worked fine in the last one ^^

reply to this message

#223: Re: Gamma...

by eihrul on 07/05/2006 23:43, refers to #222

We didn't change gamma at all, or anything with the SDL setup, and gamma still works for me and Aard. So unless anyone else can figure out what the issue is, not much that can be done.

reply to this message

#224: ..

by makkE on 07/06/2006 00:33

Gamma still working here too, winxp.

reply to this message

#225: Re: ..

by MeatROme on 07/06/2006 00:46, refers to #224

gamma 150 is my friend on Debian Sarge (linux) too :)

reply to this message

#226: Re: Gamma...

by absinth on 07/06/2006 18:57, refers to #226

hm thanks i already suspected that.

unfortunatly we need to use SDL > 1.2.9 on macosx for "Universal Binary" support (intel macs)

i also couldn't find anything to about this (to track the bug) in http://bugzilla.libsdl.org

reply to this message

#227: Re: Gamma...

by absinth on 07/06/2006 20:50, refers to #226

it's already fixed in SDL 1.2.11 so 1.2.10 is the only version to avoid...

reply to this message

   Board Index