Uru

Still riding the wave of their recent sucess, the new International Hood is busy preparing for their next event! Combining a Summer Music Fest and Cavcon Awareness party, this event has been dubbed D'niPalooza 2013!

Here's what the sponsors of IHP has to say about the event:

Spring is here, and we have many reasons to celebrate! On Friday the 17th of May, the Female Hood is putting on a music and dance party, chaperoned by none other than Mimi Bot, with special guests Yeesha, the Bahro, and Jeff Zandi! All explorers are welcome, there's something for everyone.

At 13:00 KI time, (3:00 PM in New York, 9:00 PM in Western Europe), send a private message to Mimi Bot with the single word, link, and you will be transported directly to the party in Eder Delin.

Haven't done this before? Just add Mimi Bot as a buddy. Use her KI number by typing /addbuddy 21420380. You can then send Mimi a private message to transport you to the party; click on Mimi Bot in your buddy list and then type link without any punctuation.

More details to come as next week progresses.Lire la suite

Another month, another All Guilds Meeting. This time, Doobes was on a well-deserved vacation, so Lyrositor took over moderating duties for this month. As usual, both cleansed and raw logs are available for your viewing pleasures, as well as the customary summary of the event:

Christian Walther

Christian was our first speaker and summed up the recent series of events concerning the licensing problems with Bink, which interrupted the normal flow of development and testing. To be concise, a portion of Uru's code was discovered by RAD Game Tools (makers of the Bink video codec) to contain copyrighted code from their Software Development Kit (SDK). They demanded that the code be removed from all CWE repositories, an arduous task to say the least. Developers promptly began the process of rewriting repository history to remove these files. Most of the work has been acheived by now, fortunately, and only a few tasks remain, and H'uru has already resumed its normal development pace.Lire la suite

To all Uru players, there is a chance that your Uru Live installation(s) will cease working because of a problem with MOUL's physics engine, PhysX. If this happens to you, don't worry, it's an easy fix which will require downloading a different driver, as outlined in this post.

Indeed, as a user on the OpenUru.org forums discovered recently, MOULa users (and users of most MOUL-based shards) that get an update to PhysX through the NVIDIA Update Service or perform an install of PhysX at version 9.12.1031 or later, either from the NVIDIA website or a supplied driver CD, should also run the optional legacy installer. This is not necessary if PhysX version 9.12.0613 or earlier is installed. Lire la suite

This is an emergency post following an announcement by Cyan Worlds, Inc..

An emergency situation has arisen quite rapidly over the last 24 hours. In short, three files in the CWE sources are in violation of licensed code by RAD Game Tools: Plasma20/Sources/Plasma/FeatureLib/pfSurface/plLayerBink.cpp, Sources/Tools/MaxPlasmaMtls/plBinkMipmap.cpp and Sources/Plasma/PubUtilLib/plPipeline/plBinkPlayer.cpp. You absolutely have to delete these files from any cloned repository you might have - completely. This means that you must perform a complete rebase removing these files from the initial source release, so that they never appear ever again. As a first measure, make a commit removing those files from your fork. They contain code belonging to RAD Game Tools, and were accidentally released by Cyan as they were unaware of its origin at the time..

Complete discussion: http://forums.openuru.org/viewtopic.php?f=91&t=848#p7522

This affects all known forks and branches, including H'uru.

Failure to so could result in prosecution of Cyan Worlds by RAD Game Tools for releasing copyrighted code, which would be A Bad Thing(TM).

If you need help removing these files, please contact one of the developers (including me) for instructions on how to proceed. Speed is essential in removing these files.

Note: your client will probably no longer compile if you remove this file. A fix will be distributed once it has been found.

If removing this file is too time-consuming and/or difficult, simply delete your fork or make it private until the original code is ususable once more, following which you can clone it anew.