ToME: the Tales of Maj'Eyal

I have been unable to go down below level 4 in Amon Sul. Every time I use the stairs the program closes without saving. I am using a Nandor Archer. I tried clearing out some other dungeons first and then returning but it still happens. Luckily, I saved first this time.

I should also mention that I haven't been this excited about a new release since Angband 2.4 Frog-knows. Thank you very much!

I have the same problem, it is probably an error with the new unique glow effect implemented in the last beta:

My last output lines are OS is Ubuntu 10.04, AMD 780G integrated graphics.

Two other bugs: When trying to buy or sell in the stores, when it prompts for "Quantity?", I am unable to backspace or delete the number listed. Whatever number I enter comes after the number listed. For example, if it prompts "Quantity: 14" and I type in a "1", it then says "Quantity: 141".

When stacking arrows of a similar wood type, the arrows take the attributes of the stacked group. For example, if I am wearing some yew arrows (35-39 power, 10 apr) and I w(ear) some yew arrows (26-29 power, 10 apr), then all of the arrows become yew arrows (35-39 power, 10 apr).

I have the same stais problem on a Vista machine (Radeon X1200 Adapter),
game crashes on climbing to level 5 of Amon Sul.

The latter arrow stacking effect is a feature; they are stored last in first out (whether it is a misfeature is another question, but DG has said that is intentional).

I just came across the same problem with my Nandor Archmage with the exact same lines in my stdout file as Massimiliano Marangio. I was using Windows 7 with integrated Radeon 3200 graphics.

EDIT: I switch the graphics mode to ASCII before I went down the stairs and the bug did not occur. If you do this make sure you go back up the stairs before you exit and try to reload, as my save from the fifth level of Amon Sul now doesn't want to load.

I took a look at this and... there doesn't seem to be anything wrong with the shader.

In fact, the one thing that it could be means it would also crash with water effects, and the other thing means it would crash for EVERYONE, not just a select few. Interesting that its all ATI cards with that problem...

I'll have to do some more research.

As a quick fix, I modified the shader to not have noise. I kinda don't have time to test, so it might still crash, but if the crashes affect you it SHOULD work:
Unzip the attached file into:
/game/modules/tome/data/gfx/shaders/

Should still give you a glow effect this way, but removes the noise glow.

EDIT: Ug, whats with the forum file attachment?

Try: http://drop.io/n4kmlqt ?

Thanks Antagonist, the fix worked for me. My archmage is alive and well again.

Also, I can only see file attachments on the forum if I am only viewing as a guest and not logged in...

Dr Who wrote:Also, I can only see file attachments on the forum if I am only viewing as a guest and not logged in...

This quick fix didn't help me.
Going down to level5 still closes the game.

f_i_r_s_t, I need the relevant parts of your stdout.txt

The first error and a few lines before and after should do.

Hopefully these are the correct lines:

[MOVE] actor moved without a starting position The Shade of Angmar 25 48
[SHADER] making shader from unique_glow into unique_glow[]
[SHADER] Loading from /data/gfx/shaders/unique_glow.lua
New GL Shader program 3
New GL Shader 4 of type 35632
[SHADER] created fragment shader from /data/gfx/shaders/unique_glow.frag
OPENGL ERROR: Program link ErrorFragment shader(s) failed to link, no vertex shader(s) defined.
Fragment Shader not supported by HW

Curious, I'll likely need to know what GPU you have, and glewinfo information.

FIRST... find and update your GPU drivers. Alot of issues with shaders so far has been solved just by simply doing that.

If it still does not work, I need GPU details and preferably also your glewinfo information:
http://forum.t-o-m-e.net/viewtopic.php?p=85488#p85488

This is needed because your hardware doesn't support something we use, but we need to know what it is so we can properly query for it and disable those code paths.

Hope this will help

..and I updated to latest somewhat compatible ati-drivers (9.11) but that didn't help.
I cannot have later drivers 'cause I've got a laptop with ati x700 and 9.11-> drivers aren't supported (I think)