activeworlds

Active Worlds Release Notes

This is a compilation of Active Worlds release notes (originally up to build 246, compiled on May 7, 1998 by NetGuy, where Mauz took it from there, and Eep then added it to this wiki). It is hoped that it may serve as a sort of history of the evolution of the AW browser.

Some releases are still missing, so if you have any old release notes lying around or know the dates of certain releases, please add them to this wiki. Thanks!

Depending on how old the release is, the notes were contained in a file named either "bugs.txt", "readme.txt" or "readme.html" in your Active Worlds program directory.

In particular, release notes are missing from builds 1-45,51,55,57-63,78,87,89,119,120,131,132,178,199-227.

Active Worlds 4.1

Build 940?

Active Worlds 3.6

Build 567


Build 566


Build 565


Build 564

Fixed random crashes when closing the browser.


Build 563

Fixed a sporadically occuring memory leak when switching worlds.


Build 562

Fixed tags from 32 to 42 for avatars.


Build 561

internal build


Build 560

Installer for build 559 had an issue; increased to build 560.


Build 559

Fixed opacity for avatars again.


Build 558


Build 557


Build 556

Fixed an issue where the browser could eventually crash if an urls exceeds a length of 255 characters.


Build 555


Build 554

Fixed an issue with WinXP SP2, where the download window would flash and fixed the user list to be displayed and updated correctly.


Build 553

Fixed an issue where it could happen that new incoming telegrams would not notify in the chat log and would not display in the telegrams tab properly during universe logon.


Build 552

Fixed IME character sets for Windows XP.


Build 551 (7/6/04) - Release

Changes:


Build 550 (6/29/04)

Fixes:


Build 549 (6/21/04)

Changes:

Fixes:


Build 548 (6/16/04)

Changes:

Fixes:


Build 547 (6/14/04)

New features:

Changes:

Fixes:


Build 546 (6/7/04)

Changes:

Fixes:

Notes:


Build 545 (6/3/04)

New features:


Build 544 (5/17/04)

New features:

Changes:

Fixes:


Build 543 (5/11/04)

Help is online.

New features:

Changes:

Fixes:


Build 542 (4/30/04)

Features included:

How to use: Use the 'create media' or 'activate media' action command followed by the url or path, on any sign object.

Example:

create sign; activate media url=mms://66.231.226.12/womb.video.wm.80 osd=on

Optional parameters: 

   On-screen display: osd=on
   default: off
   valid values: on, off, true, false, yes, no

   Audio volume: vol=-600
   default: 0
   valid values from 0 to -100000
   (-100 equals -1dB, -6dB is half of the nominal volume)

   Video resolution: res=128
   default: 256
   valid values: 64, 128, 256, 512
   (take care to use the lowest possible resolution, some users on older systems may suffer if you over-do it!)

   Play in loop: loop=2
   default: 0
   valid values: positive integer, 0 to some millions...

   Play in external window: ext=on
   default: off
   valid values: on, off, true, false, yes, no
   (window is resizeable and can be set to background; if external window is closed, it will close the running media too)

Notes:

a) The create command only works, if 'Create Url' is enabled in the world features settings. To pass urls or local paths with blanks in their names to the create media or active media use: 

   activate media "C:\Program Files\cat.mpeg" osd=on res=512

b) If you want to define a text for the sign differnt to the description when using the create media command, the url= parameter must be used and the url must not contain blanks: 

   create media "Sign Text" bcolor=red url=C:\myfile.avi

All video and and audio formats supported by Windows Media Player™ work, unless the expected codec is not installed on your machine. Playlists are not supported at that time.

Enjoy!

Active Worlds 3.5

Build 525 (12/2/04)


Build 524 (1/29/04)

This is the first public beta release of Activeworlds 3.5. Again, please send bug reports to Beta@activeworlds.com.

The following bugs have been reported and will be fixed in the next release:


Build 520 (11/6/03)


Build 519 (11/3/03)


Build 514 (10/1/03)

Build 513 (9/26/03)


Build 510 (8/13/03)


Build 509 (8/11/03)


Build 508 (8/6/03)


Build 507 (8/4/03)


Build 506 (8/1/03)


Build 505 (7/31/03)


Build 504 (7/30/03)


Build 503 (7/28/03)


Build 502 (7/25/03)

1. /whisper username, message - users may whisper to another user without using the whisper box. Just type /whisper, followed by the target's name, followed by a comma, and then your message.
2. /join [citnumber] - Type /join followed by the citizen number to send a join request to that user.
3. /teleport location - just enter /teleport followed by the location you wish to go. For example, "/teleport aw 1n 0w" or "/teleport 100s 223n 10a" Any valid teleport location should work.
4. /me emote - enter /me followed by an action to have that shown in the chat window. For example, if your username is "Bob" and you enter "/me waves goodbye", then the chat window will display "Bob waves goodbye".

NOTE: These chat commands may be removed or changed during testing.

In addition, any of the toolbar button commands list below can be used as a /slash command. For example, /world_features will cause the world features dialog to open. This option was added during testing and is not likely to remain as a feature in 3.5. More info on the toolbar.cfg file

The new toolbar will load the toolbar_image.bmp from the /default directory. This image is divided into 32x32 images to be used as toolbar buttons. The buttons are numbered horizontally starting with 0 on the left. The image file is divided into four rows as follows:

Row 1: Image of button in its normal, unpressed state.
Row 2: Image of button pressed
Row 3: Image of button in its normal, unpressed state with mouseover.
Row 4: Image of button pressed, with mouseover

Open the toolbar_image.bmp to see how this works.

Each line in the toolbar.cfg file will define a button on the toolbar. Each line has the following format:

exit
forward
back
home
teleport_set_home
remember
look_up
look_down
look_level
first_person
third_person
world_features
world_rights
world_ejections
show_downloads
show_tabs
show_gestures
show_web
show_whisper
show_cell_grid
login_citizen
login_tourist
privileges
web_back
web_forward
web_stop
web_refresh
help
about
options_controls
camera_locked
camera_chase
camera_front
contacts_tab
worlds_tab
users_tab
telegrams_tab
teleports_tab
help_tab
search_tab
afk
mouse_move
sdk_event


Active Worlds 3.4

Welcome to Active Worlds 3.4

Welcome to the Active Worlds 3.4 user guide.

The latest release version of the Active Worlds browser, server, and administration software are now available for download at http://www.activeworlds.com/products/download.asp.

Many of the new Active Worlds browser features are specifically designed to take advantage of new World Server features, and may not work the same in worlds running on older world servers.

Active Worlds 3.4 includes the following new features and changes:

New World Options:

Active Worlds 3.4 offers many new features for world owners. In fact, the number of available world options has more than doubled from what it was in 3.3. World owners should upgrade to the latest world server as soon as possible in order to take advantage of this new functionality. The new world options are:

New Browser Features

Other changes

1. Animation designers no longer need to worry about how "fast" the animation is. This was often very difficult to match to the movement of the character in world.
2. The same walk sequence can be used on avatars of any size. Under the old system, a sequence that worked right for a normal avatar would be much too slow for a short avatar, and far too fast for a giant. Now the feet should more or less "stick" to the ground regardless of size.
3. Animations can now play in reverse when the avatar is walking backward.
4. Existing sequences will be fixed. Many of the (too slow) sequences that have spread throughout the universe should now perform properly if combined with this option.

To use this feature, simply place the word "autowalk" on a line by itself after the "name=" or "geometry=" line in the avatars.dat.


Build 493 (6/13/03)

World Server Build 53 for Windows - New Installer Test Notes (06/10/03)


Build 492 (6/10/03)


Build 491 (6/5/03)

o 1053 Precise Movement
o 1054 Enable browser referrer


Build 490 (6/3/03)


Build 489 (5/29/03)


Build 488 (5/28/03)


Build 487 (5/20/03)


Build 486 (5/9/03)


Build 485 (5/6/03)


Build 484 (5/6/03)


Build 483 (5/2/03)


Build 482 (5/1/03)


World Server Linux Build 53 (4/28/03)


World Server Build 53 Windows Installer Test (4/28/03)


World Server Windows Build 53 (4/25/03)


Build 481 (4/24/03)


Build 480 (4/22/03)


World Server Windows Build 52 (4/16/03)


Build 479 (4/14/03)


Build 478 (4/10/03)


Build 477 (4/9/03)


Build 476 (4/8/03)


Build 475 (4/8/03)


Build 474 (4/7/03)


Build 473 (4/4/03)


Build 472 (4/3/03)


Build 471 (4/1/03)

Idle seq is re-instated using a different method that will hopefully avoid the crashes experienced in previous builds.


Build 470 (3/26/03)


Build 469 (3/21/03)


Build 468 (3/20/03)


Build 467 (3/17/03)


Build 466 (3/14/03)


Build 465 (3/13/03)


World Server Build 51 (3/7/03)


Build 464 (3/7/03)


Build 463 (3/6/03)


Build 462 (3/5/03)


Build 461 (3/3/03)

Fixed bug where visibility and the clipping plane would be messed up if the start world did not have fog


Build 460 (3/3/03)


Build 459 (2/27/03)


Build 458 (2/25/03)


Build 457 (2/14/03)


Build 456 (2/11/03)


Build 455 (1/30/03)


Build 453 (1/22/03)


Build 452 (1/3/03)


Build 451 (12/27/02)


Build 450 (12/24/02)

Many aspects of the movement code were changed or re-written in order to fix the slow movement issues experienced by some users.


Build 449 (12/13/02)


Build 448 (12/5/02)


Build 447 (12/3/02)


Build 446 (11/27/02)


Build 445 (11/26/02)

1. Animation designers no longer need to worry about how "fast" the animation is. This was often very difficult to match to the movement of the character in-world.
2. The same walk sequence can be used on avatars of any size. Under the old system, a sequence that worked right for a normal avatar would be much too slow for a short avatar, and far too fast for a giant. Now the feet should more or less "stick" to the ground regardless of size.
3. Animations can now play in reverse when the avatar is walking backward.
4. Existing sequences will be fixed. Many of the (too slow) sequences that have spread throughout the universe should now perform properly if combined with this option.
To use this feature, simply place the word "autowalk" on a line by itself after the "name=" or "geometry=" line in the avatars.dat.

Build 442 (11/5/02)


Build 441 (11/4/02)


Build 440 (11/1/02)


Build 439 (10/31/02)

Also, many users have requested information on what all the separate event sounds are. The sounds are stored under your ActiveWorlds directory under /default/sounds. Here is a list of the sounds, and when they are played:

1. delete.wav - object is deleted.
2. odrop.wav - object de-selected.
3. omove.wav - object is moved.
4. opick.wav - object is selected.
5. oturn.wav - object is rotated.
6. read.wav - user clicks on a telegram.
7. tdrop.wav - terrain is de-selected.
8. telegram.wav - new telegram arrives.
9. tmove.wav - terrain height is adjusted.
10. tpick.wav - terrain is selected.
11. tturn.wav - terrain texture is rotated.


Build 438 (10/28/02)

NOTE: In the last build we stated that we at "release candidate", which usually indicates that the new features are done, and all further builds will be bugfixes until the public release. However, It was decided that there were several new features that could not wait for 3.5 and needed to go in now. Those features are in this release, and so we are once again marking this build as a release candidate.


Build 437 (10/24/02)


Build 436 (10/23/02)


Build 435 (10/10/02)


Build 434 (9/30/02)


Build 433 (9/24/02)


Build 432 (9/19/02)


Build 431 (9/16/02)


Build 430 (8/21/02)


Build 429 (8/13/02)


Build 428 (7/29/02)


Build 427 (7/1/02)


Build 426 (6/28/02)


Active Worlds 3.3

Welcome to Active Worlds 3.3 and beyond!

Version 3.3 introduced several useful new enhancements and features to the Active Worlds technology platform. We hope that the new features and changes added in version 3.3 increase your enjoyment of Active Worlds more than ever before!

As of version 3.3, the user guide is now searchable!

Active Worlds 3.3 contains the following new features and changes:


Build 417 (6/11/02)


Build 416 (5/28/02)


Build 415 (5/21/02)

This build fixes the following bugs:


Build 414 (5/17/02)

This build contains a possible fix for bug #7 (random crash bug.) Since this bug is so hard to reproduce there's no way to know for sure whether it is truly fixed. Please be sure to report any crash bugs to the beta newsgroup and include crash details.


Build 413 (5/15/02)

This build fixes the following bugs:


Build 412 (5/14/02)

This build fixes the following bugs:

Changes in this build will require all cached objects to be re-downloaded. This process will happen automatically.


Build 411 (5/9/02)

This build fixes bug #1 - objects with the "visible off" sometimes remained visible after first download. This bug also affected your own avatar while in first person mode.


Build 410 (5/9/02)

This is the first beta build of Active Worlds 3.3. All new changes and features are listed here.


Active Worlds 3.2

Welcome to Active Worlds 3.2 and beyond!

Active Worlds 3.2 brought several useful new enhancements and features to the Active Worlds technology platform. We hope that the new features and changes in version 3.2 increase your enjoyment of Active Worlds more than ever!

Some of the more significant improvements introduced in version 3.2 include:


Build 389 (9/4/01)

The following bugs are fixed in this update:

This build adds a new RWX command randomuvs. This command causes a pair of random UV texture coordinates between 0 and 1 to be assigned to each vertex in the object that does not have a UV specified. This allows emulation in 3.2 of the "random texture" effect that was possible in AW 3.0 and 3.1 by applying a texture to an object that had no UV coordinates specified.

This build contains a change to fix floating point rounding errors that could occur when calculating vertex normals on certain very small objects. These errors could cause the object to be lit incorrectly when illuminated by a light source.

The RWX sphere and hemisphere primitives are now assigned "reasonable" UV coordinates so that they can be textured (Bug #5).

This build also contains a change to the way masked textures are cached. If the 3D video card supports them, alternate texture formats will be used that are more efficient for storing textures with an alpha (i.e. transparency) channel. This should help to reduce some of the banding and color quality reduction that can occur when using grayscale masks.

Changes in this build will require all cached objects and textures to be re-downloaded. This process will happen automatically.


Build 388 (8/28/01)

The following bugs are fixed in this update:

This build also contains a small change to the download priority algorithm to give models and textures a higher download priority over sounds and avatar sequences.

In addition to cubes and cylinders in the last version, the RWX cone and disc primitives are now assigned "reasonable" UV coordinates so that they can be textured (Bug #5).


Build 387 (8/24/01)

The following bugs are fixed in this update:

The minimum visibility that can be set from the Visibility menu, the performance options, and the world features has been reduced to 30 meters. However, it should be noted that any worlds that have had their world features already modified by a 3.2 browser will have had their minimum visibility set at 40 meters (the old default), which will override your browser settings, until the value has been reset to 30 by the world owner (if they choose to do so.)

Changes in this build will require all cached objects to be re-downloaded (but not textures). This process will happen automatically.

Build 386 (8/20/01)


Active Worlds 3.1

Welcome to the Active Worlds 3.1 introductory help page!

As you've come to expect from each new version of Active Worlds, the upgrade to version 3.1 brought a great collection of new features, as well as enhancements of existing features, to increase your enjoyment of Active Worlds more than ever!

Some of the more significant improvements in 3.1 include:


Build 370 (2/12/01) Final Beta

Build 370 is a final beta, meaning if no further significant bugs are found, it will be released shortly to all users.

The following bugs are fixed in this update:


Build 369 (2/10/01) Final Beta

Build 369 is a final beta, meaning if no further significant bugs are found, it will be released shortly to all users.

The following bugs are fixed in this update:


Build 368 (2/9/01) Final Beta

Build 368 is a final beta, meaning if no further significant bugs are found, it will be released shortly to all users. This update contains a slightly modified version of the new splash screen for 3.1.

The following bugs are fixed in this update:


Build 367 (2/7/01) Final Beta

Build 367 is a final beta, meaning if no further significant bugs are found, it will be released shortly to all users. This update contains the new splash screen for 3.1.

The following bugs are fixed in this update:


Build 366 (1/30/01)

The following bugs are fixed in this update:

This update also fixes an obscure problem with the chat window (not on the bug list) where clicking in the chat window after bringing up the user right-click menu could sometimes cause the chat window to stop scrolling.


Build 365 (1/26/01)

The following bugs are fixed in this update:

Negative lights (i.e. lights with negative values specified for the brightness= argument) are no longer supported with this upgrade. This is because we've learned negative lights won't be supported in future versions of RenderWare.

Also, this update contains a small optimization to the way certain types of RWX files are loaded. This shouldn't cause any problems, but you never know (that code is very complex.) Keep an eye out for any new problems with RWX files, particularly with avatar animations.


Build 364 (1/18/01)

The following bugs are fixed in this update:

This version also prints a useful message rather than "reason 79" when trying to login as a tourist or non-beta user.

Note that changes in this build will require all cached objects to be re-downloaded (but not textures). This process will happen automatically.


Build 363 (1/12/01)

This build fixes bug #18 - Timed rotates were not defaulting to "nosync".


Build 362 (1/12/01)

The following bugs are fixed in this update:


Build 361 (1/8/01)

This is the first beta build of Active Worlds 3.1. All new changes and features are listed here.


Active Worlds 3.0

Welcome to Active Worlds 3.0!

We are extremely proud of the advances brought to you in this version of the Active Worlds software. Over a year of effort went into version 3.0, bringing you a major revision through a very ambitious effort. Version 3.0 brought entirely new levels of performance and realism to the online 3D virtual world experience, to increase your enjoyment of Active Worlds more than ever!

The most significant new feature of Active Worlds 3.0 is native support for 3D hardware accelerators. In fact, many aspects of Active Worlds were completely redesigned "from the ground up" to support 3D hardware. This new design gives Active Worlds a significant performance boost, especially when run on the latest generation of 3D video cards. It also provides access to a whole new set of 3D graphical effects that were not previously available. It is important for users who are upgrading from a version before 3.0 to note that support for 3D hardware has also changed the system requirements for the Active Worlds browser.

Some of the more significant improvements in 3.0 include:


Build 351 (10/25/00) Final Beta


Build 350 (9/11/00) Final Beta


Build 349 (8/24/00)


Build 348 (8/9/00)


Build 347 (7/20/00)


Build 346 (7/14/00)


Build 345 (7/5/00)


Build 344 (6/22/00)


Build 343 (5/29/00)


Build 342 (5/24/00)


Build 341 (5/24/00)


Build 340 (5/3/00)


Build 339 (4/21/00)


Build 338 (4/19/00)


Build 337 (4/12/00)

Build 336 (4/3/00)

This is the first beta build of Active Worlds 3.0. All new changes and features are listed here.


Active Worlds 2.2

The Active Worlds development team has a strong commitment to continually improving the features and functionality of Active Worlds with each new version. Many new features and changes in version 2.2 were added in the hopes of increasing your enjoyment of Active Worlds more than ever!

Some of the more significant improvements added in version 2.2 include:


Build 298

Welcome to the first build of Active Worlds 2.2! All of the new changes 2.2 are described in detail in the beta help files under the "What's New in Version 2.2?" section. They are also summarized here:

In addition to the above features, several small bugs and problems have also been addressed:


Active Worlds 2.1

Build 302 Final Beta

This build fixes an obscure bug where the browser would reveal the names of all avatars right away if it was run on a machine that had been up and running continuously for more than about 25 days (not likely under Windows 95/98, but possible under Windows NT.)


Build 301 Final Beta


Build 300


Build 299


Build 295 Final Beta


Build 294 Final Beta

This update fixes a crash bug that could occur after a manual log in to a beta account at startup when a new beta version was available.


Build 293 Final Beta

This update fixes a bug in build 292 that could cause a new install of the browser to hang up at the splash screen.


Build 292 Final Beta

This is a minor upgrade that includes fixes for the following bugs:


Build 291 Final Beta

This update includes another minor fix to the registration process.


Build 290 Final Beta


Build 289 Final Beta


Build 288 Final Beta


Build 287


Build 286


Build 285

Oops! Build 284 broke whispers. They should be working now. Sorry about that.


Build 284


Build 283


Build 282


Build 281

A mousewheel diagnostic message accidentally left in build 280 has been removed.


Build 280


Build 279


Build 278

Thanks for all the great feedback we have received already! These bugs have been found and fixed:


Build 277

Active Worlds 2.1 is finally here! All of the new changes 2.1 are described in detail in the beta help files under the "What's New in Active Worlds 2.1?" section. They are also summarized here:

For people who like to browse the help files offline, we will be providing a separate download containing all of the help documentation which you can place on your hard disk.


Active Worlds 2.0

Build 261 Final Beta


Build 260 Final Beta


Build 259 Final Beta


Build 258 Final Beta


Build 257 Final Beta


Build 256 Final Beta


Build 255 Final Beta

This update fixes a crash bug that occured in certain cases when the "animate" command was used with a texture name ended with a "." By the way, the trick of appending a "." to the texture name in an animation in order to suppress the trailing digit was never intentionally supported, it only worked because of a bug in the browser. It is supported now only because so many people started using it before we discovered the problem, so fixing the "bug" would break a lot of existing content.


Build 254 Final Beta


Build 253 Final Beta


Build 252 Final Beta


Build 251 Final Beta

This upgrade fixes a cache problem that occured if a world was upgraded to 2.0 from 1.3 while you were in it.


Build 250 Final Beta


Build 249 Final Beta


Build 248

This upgrade fixes a bug in builds 246 and build 247 that prevented AW from detecting that there was a new beta upgrade available on startup.


Build 247


Build 246 (~May 6/98)

Persistant problems with the code that handles recovery from modem disconnects and other losses of network traffic has sent us back to the drawing board somewhat. This upgrade contains some new mechanisms for handling connection loss more robustly. Hopefully this will mean fewer "reason 212" errors among other things.


Build 245


Build 244


Build 243


Build 242


Build 241


Build 239,240

Various attempts to fix the teleport problem.


Build 238


Build 237


Build 236


Build 235


Build 234


Build 233


Build 232

The crash on startup under 8-bit mode should be fixed.


Build 231


**Missing Build 230**

**Missing Build 229**

Build 228

All of the initial changes in 2.0 are documented under the What's new in 2.0? section of the integrated HTML help. Please refer to this section for a complete description of all the new changes and features in Active Worlds 2.0.


Active Worlds 2.0 Beta

Welcome to Active Worlds 2.0!

Before getting into the details of 2.0, one thing needs to be made very clear: the vast majority of new features in Active Worlds 2.0 will NOT WORK in 1.3 worlds! If you enter a 1.3 world with a 2.0 browser, it will revert to the old 1.3 functionality in virtually all respects. Currently we have a single 2.0 world called Beta running in the Active Worlds Universe for the sole purpose of testing 2.0. The Beta world contains an exact duplicate of the AlphaWorld ground zero area out to about 40N/S/E/W, and is open for public building out to 100N/S/E/W. Only 2.0 browsers can enter this world (1.3 users will not be allowed in, even though the world shows as a green light on the world list). Beta users are welcome to build all they want in Beta, although you should be aware that it will be shut down after the 2.0 beta testing period is over.

Many beta users who are also world owners have expressed interest in running the 2.0 world server. If you are willing to accept the restriction that only beta users will be able to enter your world (until 2.0 is released to everyone of course) then you are welcome to test the 2.0 world server. For information on installing and running the 2.0 world server, click here.

Once the 2.0 browser is released, we will then make the 2.0 world server available to all world owners, and then hopefully the entire Active Worlds universe will migrate to 2.0 as quickly as possible. Once everyone is up to 2.0 and all is running well, 1.3 worlds and 1.3 browsers will be disabled and the whole universe will be running with the new 2.0 architecture only.

Please, before sending a bug report about a 2.0 feature not working, remember to stop and check to make sure that you were not in a 1.3 world when you tried it. Again, except where noted below, none of the new 2.0 world features will work in 1.3 worlds.

Please post your bug reports to the newsgroup news://news.activeworlds.com/beta. Alternatively you can email bug reports to roland@activeworlds.com.

Please don't send bug reports via telegram!

When sending a bug report, be sure to include your current build number. The current build number is displayed in the About Box.

New features and changes for 2.0

Note that this is not intended to be a parental lock-out mechanism.
Also note that the sound options have been moved to this "General" settings tab as well. The "Sound" tab has been removed.
You can set a welcome message in a 1.3 world but only 2.0 browsers will display it. 1.3 browsers will continue to display the old default message.
These options will actually work in 1.3 worlds since they are implemented solely in the browser. However they will only affect users running the 2.0 browser.
World caretakers are immune to the effects of these settings.


**Missing Builds 199-227**

Build 198 (~Jan 14/98)

The change in build 196 apparently broke object downloading from certain web servers; this update should fix the problem.


Build 197 (~Jan 13/98)

This update contains a workaround for a problem that has shown up on some of the new AGP video cards based on the nVidia chipset. Previously, AW would only run in 8-bit color on these video cards. With this update AW should now run in full 16-bit color and the MMX driver should load properly on Pentium II systems which use this card.


Build 196 (~Jan 9/98)


Build 195


Build 194 (~Dec 22/97)


Active Worlds 1.32

Build 193 (~Dec 16/97)


Build 192 (~Dec 10/97)


Build 191

This fixes a new problem with the web browser component, where it enabled itself on startup even if you had previously disabled it.


Build 190 (~Nov 26/97)

This fixes a new problem where AW did not exit properly sometimes, causing problems when it was next startup up.


Build 189 (~Nov 26/97)

This fixes a crash bug introduced in 188


Build 188 (~Nov 26/97)


Build 187 (~Nov 11/97)


Build 186


Build 185 (~Nov 11/97)

   news://news.activeworlds.com/discussion - General Active Worlds discussion, all topics
   news://news.activeworlds.com/worldbuilders - Discussion for world owners and builders
These newsgroups are provided as a service to our users; they are intended to be a forum for users to exchange tips and ideas, and to ask and answer questions. They are currently unmoderated but may become moderated in the future. We are also considering adding some new newsgroups later on.


Build 184 (~Nov 6/97)

This upgrade should fix the mysterious teleport bug, where sometimes you would try to enter one world and wind up getting bumped into different world (often the one you just came from) after a few seconds.


Build 183

Your responses to the survey are anonymous and private. We will be using this data only for the purposes of seeking advertisement revenue for Active Worlds and for better marketing the product.
   create animate tag=200 me 3 3 400
Remember that if you use the "tag=" argument before this version is released, the animation will only work for other beta users.


Active Worlds 1.31

Build 182 (~Oct 29/97)


Build 181 (~Oct 21/97)


Build 180 (~Oct 20/97)


Build 179 (~Oct 13/97)

This upgrade contains a few minor bug fixes, as well as more documentation improvements. The help files now include an "Active Worlds Server" section with some basic information about installing and hosting your own world. The new registration system is also discussed in more detail.


**Missing Build 178**

Build 177 (~Oct 2/97)


Build 176


Build 175


Active Worlds 1.3

Build 174


Build 173 (~Sep 3/97)


Build 172 (~Sep 1/97)


Build 171 (~Aug 28/97)

This update introduces a substantial modification of the "Telegram" feature. Telegrams are now downloaded automatically when you get them and stored in the new "Telegram" window (you will notice a new fourth tab on the left called "Telegram" in there with Contacts, Worlds, and Help). The telegram button in the toolbar is gone. To read your telegrams, simply click on the Telegram tab, and then click on any telegram you want to read. It will be printed in the chat window like before. Telegrams are saved so you can read them again later. You can delete a telegram or telegrams by selecting and then right-clicking and selecting "Delete". You can also reply directly to a telegram by right-clicking on it and selecting "Reply". A red star next to the telegram indicates telegrams you have not read yet. The telegram list can be sorted by name or by date. Also, if you are use multiple identities in AW, the telegrams received for each identity are kept separately, so as you switch from one identity to another, the telegram window only shows the telegrams sent to the identity you are currently using.


Build 170 (~Aug 25/97)


Build 168-169 (~Aug 23/97)


Build 168 (~Aug 23/97)

This build contains another "lockup" bug fix.


Build 167 (~Aug 22/97)


Build 166 (~Aug 21/97)

Build 166 has only one change: another attempt to fix the texture striping bug. If you are currently seeing striped or otherwise corrupted textures in Active Worlds, please delete the "cache" folder in your Active Worlds directory and restart AW. If after deleting your entire cache, if you are still seeing striped textures please let us know. Thanks!


Build 165 (~Aug 20/97)


Build 164


Build 163 (~Aug 17/97)


Active Worlds 1.21

Build 162 (~Jun 2/97)

A few minor bug fixes and a new help file for you. If there are no serious problems this version will be going out to all users shortly.


Build 161 (~May 29/97)

All of your saved teleports are stored in a simple text file on disk called "teleport.txt". If you want you can exchange your favorite teleports with your friends by exchanging all or parts of this file.


Active Worlds 1.2

Build 160

This version contains an optimzation to the avatar code which should give about a 15% improvement to the frame rate in crowded areas such as the Gate and AlphaWorld ground zero.


Build 159 (~May 9/97)


Build 158 (~May 8/9)

This upgrade contains a new updated help file. It also has a few more small bug fixes. If there are no problems with build 158 it will be going out to all users shortly.


Build 157 (~May 2/97)

One small crash bug fixed.


Build 156 (~May 1/97)

This upgrade contains a fix to a crash bug in the new debug logging code (oops!). It also has a fix for a new building bug that crept into to build 155 which made it difficult sometimes to delete objects.


Build 155 (~Apr 30/97)


Build 154

But, just because we had to go straight to release with this build doesn't mean I don't still want to hear about bugs! Please treat build 154 as a new beta as far as bug reporting goes, perhaps with the added urgency that if you are having a problem with it, so are probably hundreds of non-beta users...
Probably the second biggest change is that we are no longer going to be using the immigration number email-back mechanism for immigration (too many new users were having trouble with it and giving up). To immigrate, you simply need to pick a unique name and password; you still need to provide an email address, but no immigration number will be emailed to you. Passwords are now encrypted before getting stored in the .ini file, for a little added security.
The old immigration dialog box has been replaced with a (hopefully) simpler dialog box. New users see a "Welcome to Active Worlds" dialog box which lets them pick a name and come right in as a tourist. This dialog also has an immigrate button for people who want to immigrate right away. Users who have already immigrated are logged-in automatically automatically.
Finally, within the browser there is now a "Citizen" menu. From this menu you can change to a different identity, including a tourist, on the fly. Of course, if you are in a world that has a restricted enter list, and you change your identity to someone who is not allowed into that world, you will get booted out in the process. You can also optionally change your name, password, and/or email address from this menu.


Active Worlds 1.1

Build 153 (~Apr 11/97)

For obvious reasons, the "keep rwx" setting is ignored for models that have been password protected, so that the .rwx file never exists on the user's hard disk. Also, you should probably avoid putting this new feature into heavy use in an open world until this beta has become the new release version. Otherwise, only other beta users will be able to see your locked objects!


Build 152 (~Apr 8/97)


Build 151 (General Release) (~Apr 1/97)

Build 150 (~Jan 10/97)

This upgrade fixes a fatal crash (typically occuring in the RWL20.DLL library) that occured if you had run the browser under different display depths (e.g. if you ran AW after just switching your display to 8 bits, and you had previous been running the same copy of AW under 16 bits, you would most likely crash).

This is a serious bug that has been affecting a lot of users, so build 150 will most likely be going out to the general population very shortly.


Build 149 (~Jan 10/97)

   c:\Program Files\Active Worlds\Browser\

all file names will already be 40 characters long before the browser even started tacking on its various additional cache folder names and such. This would significantly increase the possiblity of this bug vs. someone who is running AW out of, say, "c:\aworld".


Build 148 (~Jan 8/97)

Since Worlds Inc. is not in the business of censoring its users, an alternative approach to the pornography problem is warranted. Suggestions are welcome. It would seem that any anti-pornography policy or enforcement would have to be a community-run effort, where the AlphaWorld community itself decides what is appropriate and what is not, and enforces it perhaps through "elected" officials. Also, the focus of any such effort should also be on "public" displays; what you put on the inside walls of your own home should be your own business. Again, suggestions are welcome.
If anyone has access to or is using one of the many commercial programs now available which block out web downloads from known pornographic web sites, I would be curious to hear about whether they work with Active Worlds, and if so, how well. We may offer that as a suggestion to users (presumably parents) who complain about the pornography problem.


Build 147 (General Release)

Whoops, one teensy bug snuck into 146.


Build 146 (~Dec 20/96)


Build 145 (~Dec 19/96)


Build 144 (~Dec 18/96)


Build 143 (~Dec 17/96)

Yet more small fixes. Also, there is one functional change: the old [network] section in the world.ini file is no longer used. The browser now looks for an entry called "world" in a new section called [start] to determine which world it should start out in. If there is no [start] section, then it defaults to the world "aw" (AlphaWorld). So, for example, if you would like to start out in the Gate each time instead of AlphaWorld, you can add the following to your aworld.ini: 

 [start]
 world=gate

There is no host or port entry anymore. The browser determines these values automatically from the world name. Note that this change is probably going to be only the first step in an eventual transition to a full-blown "hotspots" (or "favorites") feature.


Build 142 (~Dec 13/96)

Whoops, forgot to add a tooltip for the new toolbar button in 141.


Build 141 (~Dec 13/96)


Build 139-140 (~Dec 11/96)

Many more bugs found and fixed, thanks to the excellent bug reports we've been getting from the beta users. Keep it up folks, and we'll be ready for a release in no time!


Build 139 (~Dec 10/96)

Two more crash bugs found and fixed, thanks to the excellent bug reports we've been getting from the beta users. Keep it up folks, and we'll be ready for a release in no time!


Build 138


Build 137


Build 136

Fixed a major problem in the new sound code that was causing a significant portion of the crashes and assertions people have been experiencing in 1.1.


Build 134-135

Fixed some crashes and other small problems


Build 133

 picture <url> [update=<seconds>] [name=<name>]
<url> can be any URL, either absolute or relative, to any JPEG image on the Web. Relative URLs come off of the current world's object path. JPEGs specified with no path information at all come out of "textures". The optional "update" argument is for images that are changing frequently on the web (e.g. output from a digital camera somewhere) and specifies how often the client should attempt to reload the image (it will only actually reload it if the image has changed on the web). Use this argument with caution; it should not be used with any picture that is not changing regularly, and short update intervals (i.e. less than 60 seconds) can cause people to needless pound whatever web site is serving the image. Finally, the "name" argument allows you to specifiy another named object in the scene to be the recipient of the picture (allowing you to, for example, create a TV screen that shows different pictures depending on which button is clicked on a panel elsewhere in the room).
Example usages of the picture command:
 create picture www.my_isp.com/~myname/mypicture.jpg
 bump picture /pictures/portrait.jpg
 activate picture surprise.jpg name=hidden_panel
 create picture theghetto.mit.edu/livepic.jpg update=30
We are in the process of creating some new picture objects for AlphaWorld, they should be showing up soon. In the meantime, people running their own servers are free to experiment with creating original picture .rwx objects.


Active Worlds 1.0

**Missing Build 132**

**Missing Build 131**

Build 130

 "teleport 205.153.208.51 0n 0w"
This is useful for those of you running your own trial server on machines that do not necessarily have domain names assigned to them. (Note: it was possible to use raw address in pre-130 builds, but you had to put them in double-quotes.)


Build 129


Build 128


Build 127

By popular demand, we've decided to bend the rules a bit and introduce a new feature into version 1.0: avatar censoring. Now you can right-click on an avatar and get a little pop-up menu that let's you "censor" another citizen. If a citizen is censored, their chat messages will not show up in your chat window, and you will see "name: <censored>" over their heads when they talk. This is useful to block out offensive, pestering, or otherwise irritating citizens who you don't want to hear from anymore. You can only censor someone who has already spoken (you will not get a menu if you click on someone who is still anonymous). Also, the "censored list" only persists for a single session; if you quit and restart everyone becomes un-censored again. Note: if you censor someone, they don't know about it (unless you tell them.)


Build 126

This upgrade removes the temporary port number override that was directing everyone to The Gate, so most of you will be returning to AlphaWorld on startup. It also fixes a few more small bugs.


Build 125

Build 125 contains a fix to better handle the case where a world's download folder name has been changed, and the case when a world's database has been rebuilt on the server. Both of these events may have caused some cache synchronization problems in the past.


Build 124 (~Oct 31/96)

Today (10/31/96) we brought down the AlphaWorld property server in order to port the world data over to a new, improved server design. Unfortunately, this process will take several days, during which time building will not work and you will receive no cache updates in AlphaWorld (note that all other worlds should still function normally). In order to avoid some of the confusion that will result, we have decided to release this upgrade which temporarily changes the default starting world to the The Gate instead of AlphaWorld. In The Gate there will be a large sign that informs arriving users about the current downtime in Alphaworld. This is build 124 because the non-beta users will also be getting an upgrade to build 123, which the same thing.


Build 123 (General Release) (~Oct 31/96)

Build 122

A few more small bug fixes, and one new feature: public speakers are now presented with three additional avatars in the avatar menu: Special1, Special2, and Special3 (regardless of whether or not that particular world actually has those avatars). This allows a world to have special avatars that can only be used by public speakers.


Build 121


**Missing Build 120**

**Missing Build 119**

Build 118 (General Release) (~Oct 14/96)

This is it! The official 1.0 release. There are no functional changes between 117 and 118. The patch is large because it includes the new updated help file. We would like to thank all the beta users for all of their extremely useful testing and feedback over the past several months. We would not be where we are today, with a robust, well-tested, (not to mention useful and fun!) product that we can call "ready", without your continued evaluation and support. Thank you for all of your time and energy. And rest assured, although 1.0 is an exciting milestone for us, it is by no means a stopping point. We will continue to charge ahead, adding new features and functionalities as quickly as we can. We have many exciting new things planned for Active Worlds in the months ahead. The beta program will continue on in full force, with the beta users continuing to receive the latest features first.

Again, thanks to all of you from all of us at Worlds, Inc.


Beta Build 117


Beta Build 116


Beta Build 115


Beta Build 114


Beta Build 113


Beta Build 112


Beta Build 111


Active Worlds Explorer .8

Beta Build 110

Beta Build 109


Beta Build 108

Yet more tweaks and mods to the disk space manager algorithm


Beta Build 107

Several problems with the new disk space manager in 106 have been fixed.


Beta Build 106


Build 105

This is general release 105 to get the fix in 104 out to everyone.


Beta Build 104

This version fixes a memory leak.


Build 103

Whoops! The "visible" command was broken in 102. It is fixed in this version, which will most likely become a release version shortly.


Build 102

Beta Build 101


Beta Build 100


Version .99

This is a new general release that will be going out to all the users. There are no funtional differences between .99 and .98 beta, although this upgrade installed an updated help file.


Beta Version .98

This version contains some minor adjustments to the implementation of the new "sign" command. In particular, since many signs are turning out to have the same text as the "description" of the object, the text is now an optional argument of the sign command. If you do not specify any text for the sign, it uses the object's description field as the text.


Beta Version .97


Beta Version .96

 sign "<sign text>" color=<text color> bcolor=<background color>
<sign text> is the text you want to appear on your sign. It must be enclosed in double quotes. The "color" and "bcolor" arguments are both optional; the default sign is white text on a blue background. The color arguments can take the name of any common color, or a raw 6-digit hex value giving the reg/green/blue components of the color. The colors you can specifiy by name are: aquamarine, black, blue, brass, bronze, brown, copper, cyan, forestgreen, gold, green, grey, magenta, maroon, navyblue, orange, orangered, orchid, pink, red, salmon, scarlet, silver, skyblue, tan, turquoise, violet, white, yellow. The most common way to specifiy a sign is with the "create" trigger, although the sign command can be used with the other triggers as well (such as "activate"). Example:
 create sign "This sign is red on white" color=red bcolor=white
At the moment the four objects that can have text put on them are: sign1.rwx, sign2.rwx, news1.rwx, and tport1.rwx (a new teleporter object). (For those of you creating your own objects in other worlds: look at those four objects for examples of how to do it. Signs are applied to all quads in a model that are tagged with the value 100. At the moment, the quads MUST be oriented vertically, which means you cannot create a horizontal roof or ground piece and try to apply a sign to it.)
Also, as you create new sign objects rememember that until this feature goes out to the public in a later version, no one but other beta users can see your signs.


Version .95

This is release version .95 which will be released to the general public shortly after it goes out to the beta users. A crash bug in the new avatar animation code has been fixed, and some debugging code removed.


Beta Version .94


AlphaWorld

Beta Version .93


Beta Version .92


Beta Version .91

This upgrade fixes a few problems in .90


Beta Version .90 (~July 17/96)


**Missing Version .89**

Beta Version .88


**Missing Version .87 (Jun 19/96)**

Beta Version .86


Beta Version .85


Beta Version .84


Beta Version .83


Beta Version .82

This version fixes a crash that sometimes occured during a teleport from one community to another.


Beta Version .81


Beta Version .80


Version .79 (General Release) (~Apr 23/96)

**Missing Version .78**

Beta Version .77 (~Apr 11/96)

This version should fix a few problems people were having with some forms of the teleport command.


Beta Version .76


Beta Version .75


Beta Version .74

This version fixes a bug introduced in version .73 which caused build requests to get delayed for up to 30 seconds.


Beta Version .73

Beta Version .72

This version fixes a crash that could occur when the AlphaWorld window was minimized.


Beta Version .71


Beta Version .70 (~Mar 6/96)

WARNING WARNING WARNING

Starting With beta .70, AlphaWorld became a 32-bit application. This means that AlphaWorld will not run under Win 3.1 unless you have Win32s installed. Repeat, you MUST HAVE Win32s installed on your machine, or preferably, be running Windows 95, in order to continue using AlphaWorld!


Beta Version .69 (~Mar 5/96)

WARNING WARNING WARNING

With beta .69, AlphaWorld is now a 32-bit application. This means that AlphaWorld will not run under Win 3.1 unless you have Win32s installed. Repeat, you MUST HAVE Win32s installed on your machine, or preferably, be running Windows 95, in order to continue using AlphaWorld!

This beta is actually a major new release with some important changes. They are:


Version .68 (General Release) (~Feb 21/96)

Beta Version .67


Beta Version .66

Also, we quickly learned that spaces are a no-no in URLs, so we had to change the syntax for web-based teleport to:

http://www.worlds.net/cgi-bin/teleport?123N_456W

instead of

http://www.worlds.net/cgi-bin/teleport 123N 456W


Beta Version .64/.65

This release features a few new models and some changes to existing models. It also has one new avatar ("dredd"). It also contains fixes for many of the .mid files that were not working correctly under Windows95.

Win95 users also reported that music was only coming out of one ear. This was traced to a bug in Windows95 itself (honestly!) and so to work around it we have disabled distance/directional volume control of midi music for Windows 95 users. This means music will play at whatever previous volume you have set for midi, regardless of where the local musical object is in relation to you.

This version has an experimental new feature: web-based teleport. You should be able to associate "teleport" commands with a URL and have netscape invoke AlphaWorld with that teleport command. So for example, if you would like your friends to come directly to your house at 1234N 5678W from your web page, use the URL

http://www.worlds.net/cgi-bin/teleport 1234N 5678W

You will have to teach Netscape to run aworld.exe on the response. For the moment, "teleport" is the only behavior command that works in this manner. If AlphaWorld is already running, you will still be teleported to the requested coordinates, but you will be requested to confirm the teleport before it occurs. The confirmation is to protect people from unsolicited teleports that pranksters could implant in the world; extra credit for the first beta user that figures out how to do this (it's not hard).

Please experiment with web-based teleport and report any problems you have with it. In general, if you encounter any GPFs, stack faults, or other crashes, please email the relavent addresses (and a stack trace if available, that is always VERY useful), and a description of what you were doing at the time, to roland@worlds.net.

KNOWN BUGS

Below is a list of known bugs in this beta copy of the AlphaWorld client. Please review this list before reporting any problems you have with it.

Bug # Description

FIXED BUGS

Bug # Description


**missing Versions .57-.63**

Beta Version .56 (~Jan 24/96)

Today (1/24/96) we started experiencing mysterious and prolonged property server outages. Beta .56 has some changes we have made to the client in an effort to address this problem. The problem will probably not go away until we actually release .56 as a new general release and everyone is using the new clients, but at least we can make sure there are not any new problems as a result of the changes.

You may notice a new message "waiting for server" appearing in your title bar. This will be the common mechanism by which the client reports timeouts or other network problems while trying to communicate with the property server. In general, if you see the message "waiting for server" it means something is wrong, either at your end, or at the server end. If you don't see it, things should be functioning normally.

However, until some changes to the server are put into place within the next couple of days, you will see this message appearing briefly in your title bar from time to time. Do not be alarmed.  :-)

One aspect of these changes that is sure to appreciated is that, barring catostrophic server failure, no build requests should EVER get lost. This is because the client now queues build requests (propery adds, changes, and deletes) and holds on to them indefinitely until they are acknowledged by the server. If any request should fail (other than for a valid reason like encroachment) the client will attempt to retransmit the request until it succeeds.

Again, please email problems with this beta to roland@worlds.net ASAP. We want to go live quickly so we can resolve this new problem.

KNOWN BUGS

Below is a list of known bugs in this beta copy of the AlphaWorld client. Please review this list before reporting any problems you have with it.

Bug # Description

FIXED BUGS

Bug # Description


**missing Version .55**

Beta Version .54 (~Jan 18/96)

What!?! A MENU bar? Amazingly, we now have a menu bar in AlphaWorld. You can't do much from it yet, though. But you can now choose your appearance from amongst 8 different avatars. If you change your appearance, other beta users will be able to see your new avatar; the rest of the world will be able to see you when this version becomes the new release.

We have also made yet another change to the mouse logic in attempt to fix the mouse pointer problems a lot of people have been experiencing under Windows 95.

This beta version also has the new art that went out with version .52 but which beta .50 did not have (sorry about that). It also has a lot of new sound files that were not available before.

KNOWN BUGS

Below is a list of known bugs in this beta copy of the AlphaWorld client. Please review this list before reporting any problems you have with it.

Bug # Description

FIXED BUGS

Bug # Description


Beta Version .53 (~Jan 11/96)

The primary purpose for this beta upgrade is to make the new art that went out to the general users with version .52 available to the beta users (sorry about that!).

KNOWN BUGS

Below is a list of known bugs in this beta copy of the AlphaWorld client. Please review this list before reporting any problems you have with it.

Bug # Description

FIXED BUGS

Bug # Description


Version .52 (General Release)

**missing Version .51**

Beta Version .50 (~Dec 18/95)

This version only has a couple of minor tweaks in it. It should be our last beta before a new general release.

KNOWN BUGS

Below is a list of known bugs in this beta copy of the AlphaWorld client. Please review this list before reporting any problems you have with it.

Bug # Description

FIXED BUGS

Bug # Description


AlphaWorld Beta Version 49 (~Dec 14/95)

We are trying to port the AlphaWorld servers to a new machine in order to move them off of overloaded hardware. There is still some work to be done, but when the transition occurs, there will probably be some AW downtime on the order of two hours or so. Please be patient when this time arrives.

Version 49 has one new feature: warp and teleport now can take relative coordinates. Put a + or a - in front of the numeric arguments to make them relative (and leave off the N/S/E/W part if you do).

This version should also stop cycling the system beep sound if it can't find the real sound file.

Also, some people were reporting that builds were sometimes failing silenetly in version .48. At least one case of silent failure has been fixed in .49 (you get an error message box now).

KNOWN BUGS

Below is a list of known bugs in this beta copy of the AlphaWorld client. Please review this list before reporting any problems you have with it.

Bug # Description

FIXED BUGS

Bug # Description


Beta Version 48 (~Dec 8/95)

ATTENTION

The AlphaWorld user load has effectively doubled in the last couple of weeks. This new load is causing severe problems with the property server, which is in turn disrupting service for many AlphaWorld uers. Building is difficult, if not impossible, during peak usage, and many users are now getting various types of network failures at a regular rate (usually accompanied by an error number in the 100xx range). We are working hard to determine the cause of the delays and we will be trying to restore normal, responsive service as soon as possible. Thanks for your patience!

This version should (hopefully) fix a mouse pointer problem some people started experiencing with version 47 under Windows 95.

The most significant change in this release is that mulitple objects may share the same "name" now, and named behaviors (e.g. "visible mydoor off") will affect all objects in the scene with that name, not just the first one. A side effect of this change is that bug #5 should now be fixed.

Bug #1 is fixed, where going off the edge of the world (at 32767 and beyond) caused a GPF. It has been fixed by preventing motion beyond 32767 in any direction.

We are homing in on another regular release, folks. We need to get behaviors out to the general public, as well as the many minor fixes that are in the beta. If people are having problems with the beta versions (other than the obvious server issues mentioned above) we need to know about them! Thanks! -Roland

KNOWN BUGS

Below is a list of known bugs in this beta copy of the AlphaWorld client. Please review this list before reporting any problems you have with it.

Bug # Description

FIXED BUGS

Bug # Description


Beta Version 47 (~Dec 6/95)

This version features directional bumping. This change should have little or no effect on regular collision detection. It does mean that those of you who have been experimenting with invisble trigger walls will have to make sure that your walls are either "double sided" (one polygon on each side) if you want a two-way trigger, or pointing in the right direction if you want a one-way trigger.

Bug #2, where triggering a URL action w/o Netscape running put you into build mode, has been fixed. In general the mouse pointer handling has been improved a bit. If you are switched into another application while AlphaWorld is running, you should get your mouse pointer back while using the other application.

Bug #3, where "warps" and "teleports" could get stuck on a wall, has also been fixed.

Other changes:

The network timeout mechanism has been improved, but this should not really change anything, although across the board all network timeouts have been increased to 45 seconds (some operations were timing out after 30 seconds).

KNOWN BUGS

Below is a list of known bugs in this beta copy of the AlphaWorld client. Please review this list before reporting any problems you have with it.

Bug # Description

FIXED BUGS

Bug # Description


Beta Version 46 (~Dec 5/95)

This client should have the "stuck property update" bug fixed, which causes some people on slow connections to stop receiving property updates until they restart AlphaWorld.

Special note to you script hackers: very shortly, bump triggers will become DIRECTIONAL. Currently, an object's "bump" behavior is triggered regardless of which way you were going when you hit it. This is about to be changed so that the "bump" is only triggered if you hit a surface coming from the "outside" (the direction the polygon's normal is pointing). This will allow the creation of "one-way" invisible trigger walls. If you want a two-way wall, you simply have to create two polygons in the object, one facing each way, as you do now when you want to create a normal wall that is visible from both directions. Please keep this in mind if you are creating new bump-triggered behavior for AlphaWorld.

KNOWN BUGS

Below is a list of known bugs in this beta copy of the AlphaWorld client. Please review this list before reporting any problems you have with it.

With version 46 I am also introducing an informal bug numbering scheme. Future copies of this file will also list known bugs that have been fixed.

Thank you for participating in the AlphaWorld beta program!

-Roland

Bug # Description


Older

Nothing prior to version 46; please add anything you have. Any notes older than version 66 would be called "bugs.txt" instead of "readme.txt".

**Missing Version 38 (~Oct 12/95)**

**Missing Version 30 (~Aug 30/95)**

Other

Mar 12/95: Jumanji special release related to the motion picture