Dashiva

The stacktrace makes no sense unless your mouse has zero buttons, and in that case it should have nothing to do with the village tab... Did you experience this before the 3044 release? Does anyone else experience this problem?

As indicated by the warning the system clock is unstable, and the stable client doesn't properly handle time going backwards. This has been fixed in unstable, so you could try that. Alternatively, the nano timer might be more stable on your system.

With Mac you have to use JOGL instead of LWJGL in the stable client (game settings).

Does this happen every time, or just that once? If it still happens, please enable the java console window (in java control panel -> advanced -> console) and see if anything appears when you click the link.

Changes in 2.7.5f * Broken release, ignore. Changes in 2.7.5g * Backported client data collection so we can get data from people who can't (or just don't) use the unstable client as well.

Wollschaf: Hint, it's not cave-related. This is most likely a proxy messing up the content-length header. We'll have to add handling for that, I guess.

Color picking is a method for detecting the object underneath the mouse. It's needed because some drivers are dropping support for the old built-in API. Eventually color picking may be the only option, so we should try to figure out why it misbehaves in your case. Could you post a console.log for later analysis?

The input thing is nasty, it goes all the way to the native code in windows. Can someone please check if non-Latin text (russian, hebrew, arabic, japanese, chinese, etc) works on mac and linux?

Not all settings can be changed ingame. The console shows details for now, eventually those options will be disabled in the settings window.

The capability detection wasn't enough, there's another crasher inside the intel driver. Back to manual setting of the compatibility options.

If it only happens when the mouse is over the world, you could try disabling color picking in the compatibility tab.

@Mongori I have a hypothesis. If I'm right, the next client (not this one) will be faster again. Changes in 3.0.0-2900 * Celebrated too early, the Intel drivers found a second way to crash. Added back the big scary warning.

If the update actually fails, please click the 'show error log' button and copy the contents here.

Changes in 3.0.0-2896 * New capability detection code. This one should actually work, which is good news for Intel users. The client will ask to reset the compat settings (again). It should be safe this time, so go for it.

http://www.wurmonline.com/client/wurmclient_unstable.jnlp It's linked in the city hall client release threads.

Unstable client 3.0.0-2896 should solve this problem once and for all. Please give it a try (and accept the settings reset).

While it is a shame you crashed, this could be awesome news. The notice about changes being reverted was based on the fact that VBO used to cause crash-to-desktop. In this case the settings would never be saved. However, it looks like they now crash with a crash window. This means the settings do get saved, but it's a huge usability improvement. We might even be able to detect the crash before it happens and avoid it. To restore your client, you might have to disable one or more of VBO, occlusion queries and multidraw.

Does it happen in both stable and unstable clients?

Does it happen in both stable and unstable clients? Also please give more details about the light issues, exactly what happens and when it happens.

This is now available as unstable client.

As in fire or fog or both?

There is a uservoice forum for Wurm at http://wurmonline.uservoice.com/ The forum remains the best place for discussion, but uservoice can be used to track the relative popularity of suggestions. That is all.

Changes in 3.0.0-2876 * Less smoke in caves. * Client will now submit anonymized game settings and general system info to the server so we can get more reliable info than low-response, unrepresentative forum polls. The client will ask before submitting, but we hope as many as possible will say yes.

It's worse than that. We can tell that the card supports NPOT because it claims to (and it does). The driver just goes crazy if you use it.