Client log messages

From Wurmpedia
Jump to navigation Jump to search

Main / Technical Details / Client log messages


This page should list the various messages that the Wurm client logs to stdout and stderr. these messages are not shown by default, but you can see them by enabling the Java console in the Java plugin. Many of the messages are only for internal debugging, and are not very useful to most players, however some people may find it interesting to see what is happening in the client.

This page is for client versions 2.5 and newer. See Client Log Messages/Archive for older messages. If you find any there that still occur, feel free to copy them into this page.

Contents

Common startup messages

Time is Wed Nov 26 14:07:11 CET 2008
Running client version 2.5.2, testclient=false

This is the time the client was started (useful to make sure it's not an old console log) and the client version (useful to make sure it's not an old client) 

=== System information ===
Operating system: Windows XP (arch: x86, version: 5.1)
Java version: 1.5.0_16
Java vendor: Sun Microsystems Inc. (http://java.sun.com/)
Available CPUs: 2

Basic system info. Always useful to know which java version and which OS is at work. 

>>> Main thread exiting.
Loading character Dashiva
Loading config default
Loading props file C:\my\bin\Wurm\configs\default\gamesettings.txt
Loading props file C:\my\bin\Wurm\players\Dashiva\password.txt
>>> LoginFrame queue entry exiting.

Profile startup. It loads the most recently used character and the config associated with that character. Then it loads the settings for that config, and the password for the character. If you switch character or config, or change settings, more messages like these will appear. 

Saving props file C:\my\bin\Wurm\players\Dashiva\password.txt
Saving props file C:\my\bin\Wurm\configs\default\gamesettings.txt
Loading props file C:\my\bin\Wurm\players\Dashiva\stats.txt

Play button pressed, this causes password and settings to be saved, the stats to be loaded. 

Preparing to enable console logging.
Now logging to C:\my\bin\Wurm\console.Dashiva.log

Since you've selected a character to play with, the console log is pushed to a file. 

=== Wurm options ===
advanced_select_items = false
animation_playback_self = 1
auto_mipmaps = true
(...)

List of all game settings, and the values they had. 

>>> Game launcher thread exiting.
Starting workaround for fast running clocks

This one happens if you use the fast clock workaround setting. Which you should, on windows. 

=== OpenGL information ===
JOGL version: 1.1.1
LWJGL version: 1.1.4

Renderer library info. Only useful when it's wrong. 

OpenGL vendor: NVIDIA Corporation
OpenGL renderer: GeForce 8800 GT/PCI/SSE2
OpenGL version: 2.1.2

Graphics card and OpenGL version. Game requires 1.4 when this is being written. 

GLSL version: Not available
Colorbits: 8, 8, 8, 8
Stencilbits: 0
Depthbits: 24
Texture units: 4
AUX buffers: 4
Max GL Lights: 8
OpenGL extensions:
    GL_ARB_color_buffer_float
    (...)

Other GL info and a list of extensions supported. 

Setting up OpenAL Sound Engine
OpenAL version: 1.1
OpenAL renderer: Software
OpenAL vendor: Creative Labs Inc.
OpenAL extensions: EAX EAX2.0 EAX3.0 EAX4.0 EAX5.0 EAX3.0EMULATED EAX4.0EMULATED AL_EXT_OFFSET AL_EXT_LINEAR_DISTANCE AL_EXT_EXPONENT_DISTANCE
Generating: 16 source channels.

Sound setup. This happens if hardware (openal) sound is selected. Different messages for sonar and silent. 

Using LWJGL timer.
Showing Mojang Splash Screen
use auto mipmap generation true
use compressed textures false
use S3TC compression: false
use non power of two textures: true
Startup Phase - Setting up..

Various setup messages. 

Loading window positions from C:\my\bin\Wurm\players\Dashiva\windows_1592x866.txt
Loading props file C:\my\bin\Wurm\players\Dashiva\windows_1592x866.txt
Word filter loaded: 26
Gui initialized

Loading window positions and chat filter. 

Loaded tree texture id as 4
Startup Phase - Preparing terrain
Startup Phase - Connecting ..
Disabling Nagles

Loading textures while connecting. 

Writing to C:\my\bin\Wurm\players\Dashiva\logs\_Event.2008-11.txt
Disabling Nagles
Setting up dotXSI Model Loader
Startup message: Welcome back, Dashiva! Wurm has been waiting for you.

Loading models, successfully connected. 

Executing C:\my\bin\Wurm\configs\default\keybindings.txt
Keybindings saved.
Executing C:\my\bin\Wurm\configs\default\autorun.txt
Keybindings saved.

Loading keybinds and autorun. 

Setting up Anti-Aliasing
Setting up graphic hints
Setting up Anisotropic Texture Filtering

More GL setup. 

Starting update of login splash image...
Finished loading new login splash image!

Updating splash image for next execution. 

Using program object 3 for water

If GLSL shaders are enabled.

Exceptions

IllegalArgumentException: input == null! at javax.imageio.ImageIO.read

Failed to load material noIcon.pic from miscpack_01.jar:models/structures/cartSmall.XSI->miscpack_01.jar:models/structures/noIcon.pic
java.lang.IllegalArgumentException: input == null!
   at javax.imageio.ImageIO.read(Unknown Source)
   at class.bh.a(SourceFile:32)

The resource loader couldn't find an image referenced in a model. Non-fatal, but should be reported.

null (id 2621444) is not a House

null (id 2621444) is not a House

Non-fatal, should be ignored.

Crashes

Unable to locate server The error was: <jenn001.game.wurmonline.com>

====== CLIENT CRASH ======
Unable to locate server
java.net.UnknownHostException: jenn001.game.wurmonline.com

There may be different reasons why the client can not find the server jenn001.game.wurmonline.com

  • The DNS server does not work or DNS resolving is misconfigured
Open a windows command prompt (Win+R, cmd) and type 
nslookup jenn001.game.wurmonline.com
. This should give 194.68.222.111 as result. If you notice errors then try swithing to Googles public DNS server. [1]
  • Java uses wrong proxy settings to connect to the internet
In the Java control panel in the Windows control panel check for "Network settings". By default it's set to using the browser settings for proxies. Switch this to direct connection or browser settings, depending on what is checked for you and try to start Wurm.
  • A firewall, security suite or virus scanner is blocking Wurm from accessing the internet
Make sure you allow java (java.exe, javaw.exe, javaws.exe) to access the internet. To test if the firewall or security suite is blocking Wurm disable it temporarily and try if Wurm can connect.

Could not create window with selected width and height. The error was: <Pixel format not accelerated>

====== CLIENT CRASH ======
Could not create window with selected width and height.
org.lwjgl.LWJGLException: Pixel format not accelerated

The stock windows drivers do not support hardware accelerated OpenGL. To play Wurm you have to install the video drivers from the video card manufacturer.

java.lang.UnsatisfiedLinkError: no jogl in java.library.path : Windows

====== CLIENT CRASH ======
java.lang.UnsatisfiedLinkError: no jogl in java.library.path
   at java.lang.ClassLoader.loadLibrary(Unknown Source)
   at java.lang.Runtime.loadLibrary0(Unknown Source)
   at java.lang.System.loadLibrary(Unknown Source)

Try uninstalling Wurm, using the Sun Java WebStart Control Panel (start -> run -> 'javaws -viewer') and reinstalling.

java.lang.NoClassDefFoundError: com/dnsalias/java/timer/AdvancedTimer

====== CLIENT CRASH ======
null
java.lang.NoClassDefFoundError: com/dnsalias/java/timer/AdvancedTimer
   at class.ct.a(SourceFile:34)
   at class.fY.a(SourceFile:63)

This happens when running an outdated test client. Uninstall the test client (see previous section) and reinstall it.

java.io.IOException: An existing connection was forcibly closed by the remote host

====== CLIENT CRASH ======
java.io.IOException: An existing connection was forcibly closed by the remote host
   at sun.nio.ch.SocketDispatcher.write0(Native Method)
   at sun.nio.ch.SocketDispatcher.write(Unknown Source)
   at sun.nio.ch.IOUtil.writeFromNativeBuffer(Unknown Source)
   at sun.nio.ch.IOUtil.write(Unknown Source)

Usually a connection problem somewhere along the path from you to the server. No direct solutions.

java.lang.ArrayIndexOutOfBoundsException: 179

====== CLIENT CRASH ======
null
java.lang.ArrayIndexOutOfBoundsException: 179
   at class.bl.a(SourceFile:296)
   at class.bl.a(SourceFile:329)

Means the client is unable to use the base.jar pack, for some reason or another.

javax.media.opengl.GLException: OpenGL context not current : Mac

====== CLIENT CRASH ======
could not set up display mode
javax.media.opengl.GLException: OpenGL context not current
   at com.sun.opengl.impl.macosx.MacOSXGLContext.setSwapInterval(MacOSXGLContext.java:317)
   at com.sun.opengl.impl.GLImpl.setSwapInterval(GLImpl.java:30518)

Happens when you use LWJGL as renderer on a Mac. Switch the renderer setting to JOGL instead.

javax.media.opengl.GLException: Method "glMultiDrawArrays" not available

====== CLIENT CRASH ======
null
javax.media.opengl.GLException: Method "glMultiDrawArrays" not available
   at com.sun.opengl.impl.GLImpl.glMultiDrawArrays(GLImpl.java:13416)
   at class.eD.a(SourceFile:443)
   at class.eD.a(SourceFile:526)

Happens with Intel graphics when the drivers are too old (or the card is too old).

Retrieved from "https://www.wurmpedia.com/index.php?title=Client_log_messages&oldid=126811"