Difference between revisions of "Common bugs and solutions"

From Wurmpedia
Jump to navigation Jump to search
m (Breadcrumbs)
 
(19 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 +
[[CDB|Main]] / [[:Category:Technical Details|Technical Details]] / '''{{PAGENAME}}'''
 +
 +
 
[[Image:LogicBug.jpg|50px|right|"It has been just so in all of my inventions. The first step is an intuition, and comes with a burst, then difficulties arise—this thing gives out and [it is] then that "Bugs"—as such little faults and difficulties are called—show themselves and months of intense watching, study and labor are requisite before commercial success or failure is certainly reached..." -Thomas Edison.]]
 
[[Image:LogicBug.jpg|50px|right|"It has been just so in all of my inventions. The first step is an intuition, and comes with a burst, then difficulties arise—this thing gives out and [it is] then that "Bugs"—as such little faults and difficulties are called—show themselves and months of intense watching, study and labor are requisite before commercial success or failure is certainly reached..." -Thomas Edison.]]
  
Line 54: Line 57:
 
Read the crash message at the top of the window (the part inside <brackets>).
 
Read the crash message at the top of the window (the part inside <brackets>).
  
* Make sure maximum texture size for megatextures (advanced graphics) is more than 256.
+
* Check [[Client Log Messages]] if the message and a solution is listed.
* Make sure automatic mipmap generation (compatibility) is not disabled.
 
* Make sure your Java version is up to date.
 
* If the crash message mentions jogl.library.path, [[reinstall]] the client.
 
  
 
=== The game crashes without a crash window ===
 
=== The game crashes without a crash window ===
Line 78: Line 78:
 
==== If it still fails ====
 
==== If it still fails ====
  
Post a log file with description of the problem by Forum PM to a GM and wait for developer or GM assistance.
+
Post your log file with description of the problem in the technical issues forums, and wait for developer, GM or other assistance.
  
DO NOT POST YOUR LOG ON THE OPEN FORUM.
+
  Link : http://forum.wurmonline.com/index.php?/forum/26-technical-issues/
  
 
Mention that you used this page, and that your problem wasn't listed.
 
Mention that you used this page, and that your problem wasn't listed.
 +
 +
== Other technical issues ==
 +
 +
=== 64bit Java ===
 +
 +
If you're running a 64bit Windows you should run 64bit Java too. This will allow you to use more of the available system memory and it avoids certain crashes that may occur with 32bit Java.
 +
 +
When you visit the Java download site with a 32bit web browser you will get the 32bit Java download by default. Visit the [http://java.com/en/download/manual.jsp Java download site] to download the 64bit version.
 +
 +
If you don't need the 32bit version of Java you should uninstall Java completely and install only the 64bit version. This will prevent problems where the 32bit version is automaticly selected to run Wurm.
 +
 +
Once you have the 64bit Java installed you can create a shortcut to start the Wurm client. Paste one of the following command lines as target for the shortcut.
 +
 +
'''Stable client'''
 +
 +
"%SystemRoot%\System32\javaws.exe" http://www.wurmonline.com/client/wurmclient.jnlp
 +
 +
'''Unstable client'''
 +
 +
"%SystemRoot%\System32\javaws.exe" http://www.wurmonline.com/client/wurmclient_unstable.jnlp
 +
 +
=== Texture problems on turkish computers ===
 +
 +
The turkish language settings performs upper and lowercase conversion of the letters ''i'' and ''I'' differently than most languages. As a consequence the client can't find some textures and models and just display a red "x" on white ground instead.
 +
 +
You can either change the language setting of your computer to a different language (eg. english) [http://forum.wurmonline.com/index.php?/topic/72252-strange-texture-issues-since-3-months/#entry715617] or
 +
start Wurm with an option to run with a different language setting [http://forum.wurmonline.com/index.php?/topic/93625-graphics-problem/#entry939516]:
 +
 +
Create a shortcut with the following command or run the command from the command prompt (Windows+R):
 +
 +
C:\Windows\System32\javaws.exe -J-Duser.country=us -J-Duser.language=en http://www.wurmonline.com/client/wurmclient.jnlp
 +
 +
=== Solutions in the forums ===
 +
* Out of memory errors: [http://forum.wurmonline.com/index.php?/topic/75790-how-do-i-fix-this-problem/#entry749327]
 +
* nVidia Optimus systems: [http://forum.wurmonline.com/index.php?/topic/71698-2fps-and-crashing/#entry708815]
  
 
== Gameplay problems ==
 
== Gameplay problems ==
  
=== Wurm runs, but doesn't accept keyboard or mouse input/gain window focus after login (Linux) ===
 
 
Try a combination of switching the renderer between JOGL and LWJGL, and also experiment with <tt>'Release OpenGL context each frame'</tt> in the advanced options menu. For Nvidia users the 877x series of drivers are recommended, unless you are using X.org 7.0 or higher. You should also check that you are using the official Sun JRE 1.5, instead of [[http://www.blackdown.org/ Blackdown Java-Linux]] 1.4.2-02 (as included by default with many 'fully GPL' distros), as it is known to cause problems.
 
  
 
[[Category:Technical Details]]
 
[[Category:Technical Details]]
 
[[Category:Babel/C]]
 
[[Category:Babel/C]]

Latest revision as of 22:06, 4 August 2023

Main / Technical Details / Common bugs and solutions


"It has been just so in all of my inventions. The first step is an intuition, and comes with a burst, then difficulties arise—this thing gives out and [it is] then that "Bugs"—as such little faults and difficulties are called—show themselves and months of intense watching, study and labor are requisite before commercial success or failure is certainly reached..." -Thomas Edison.

Note: This is made by the players of Wurm, not someone from the development team so there may be errors, don't just fully rely on this, just check this first, attempt it then post.

Have a look at Client Log Messages for more common errors and solutions.

Problems before pressing the play button

The game crashes before the login screen

  • Make sure you are running an up to date client version.
  • Make sure your Java version is up to date.

The play button is grayed out

  • Have you entered your character name correctly?
  • Have you entered your password?
  • Have you read and accepted the EULA?
  • Has the pack update completed successfully?

If the button remains greyed out, post a thread in the bug forum and ask for help.

The pack update has failed

(In version 2.7.0 or newer only) Press the 'show error log' button and post the log in the bug forum.

Download-icon.gif Attempt to download the packs manually.

The packs can be downloaded using these links (Right click & then Save Target/Link As):

Then, place the downloaded .jar files in the wurm/packs/ folder.

Do not attempt to unzip the files.

Make sure ALL files are downloaded and installed.

If it still doesn't work:

Make a post in the bug forum and wait for dev or GM assistance.

Problems after pressing play, before actually playing

Grey game window when using a Macintosh

Make sure you are using the JOGL+AWT renderer in game settings.

Turn on 'Use nanoTime' timer in the compatibility tab in the settings.

The game crashes with a crash window

Read the crash message at the top of the window (the part inside <brackets>).

The game crashes without a crash window

Locate the HS_ERR_PID crash log. It is usually on the desktop, but can be placed in other locations too.

For Intel users

  • Disable VBO (compatibility tab)
  • If it still crashes, disable multidraw (compatibility tab)

For ATI users

  • Make sure you are using Catalyst 9.12 or newer.
    • If your card is too old, use Catalyst 9.3 or older.
    • Catalyst 9.4 through 9.11 have OpenGL memory leaks.
  • Disable Catalyst AI
  • Set antialiasing (AA) and anisotropic filtering (AF) to game-controlled.

If it still fails

Post your log file with description of the problem in the technical issues forums, and wait for developer, GM or other assistance.

 Link : http://forum.wurmonline.com/index.php?/forum/26-technical-issues/

Mention that you used this page, and that your problem wasn't listed.

Other technical issues

64bit Java

If you're running a 64bit Windows you should run 64bit Java too. This will allow you to use more of the available system memory and it avoids certain crashes that may occur with 32bit Java.

When you visit the Java download site with a 32bit web browser you will get the 32bit Java download by default. Visit the Java download site to download the 64bit version.

If you don't need the 32bit version of Java you should uninstall Java completely and install only the 64bit version. This will prevent problems where the 32bit version is automaticly selected to run Wurm.

Once you have the 64bit Java installed you can create a shortcut to start the Wurm client. Paste one of the following command lines as target for the shortcut.

Stable client

"%SystemRoot%\System32\javaws.exe" http://www.wurmonline.com/client/wurmclient.jnlp

Unstable client

"%SystemRoot%\System32\javaws.exe" http://www.wurmonline.com/client/wurmclient_unstable.jnlp

Texture problems on turkish computers

The turkish language settings performs upper and lowercase conversion of the letters i and I differently than most languages. As a consequence the client can't find some textures and models and just display a red "x" on white ground instead.

You can either change the language setting of your computer to a different language (eg. english) [1] or start Wurm with an option to run with a different language setting [2]:

Create a shortcut with the following command or run the command from the command prompt (Windows+R):

C:\Windows\System32\javaws.exe -J-Duser.country=us -J-Duser.language=en http://www.wurmonline.com/client/wurmclient.jnlp

Solutions in the forums

  • Out of memory errors: [3]
  • nVidia Optimus systems: [4]

Gameplay problems