Jump to content
Eternal Lands Official Forums
Debianita

I can't interact, mouse bug ? [SOLVED]

Recommended Posts

After the segmentation fault got solved, I have another problem. Like the other: this problem has came suddenly, but has came after the other. I played for 23 days without any problem and one bad day *ZAP* the game got broken or something :-) yes, it's so much strange :-) (I smile trying not to cry ;-) ). So, the problem:

 

The mouse doesn't work. But it's not fully "disabled". I can use the interface buttons, click the skills, zoom in/out and rotate the camera, etc... BUT I can't walk around, touch nothing, attack and all of that.

 

I can move the cursor (obvious) but although I click (and "activate") the touch, attack, etc... button, the cursor doesn't change. It's fixed to the walk cursor.

 

I think I have no more useful information to give. Oh, and the keyboard works perfectly.

 

Like I said on other posts, I play on linux, debain testing, and have a nvidia geforce fx 5200. And I have 3D accel thanks to the nvidia website drivers. I've tried the updated (at this moment the 100.14.11 version) and an "old" release (the 100.14.03 one). It's the same result for me. And I play on 2.6.18-4-486 , not the 2.6.21 version because of the "GPL bug" :-)

Share this post


Link to post
Share on other sites

Okay, let's first establish a few facts:

  • This happens not only with the current CVS client, but also with the official binary?
  • When the game broke, it was not because you updated the code from CVS? Did you do a system or video drivers update?
  • You say that neither of the mouse bug options in the configuration window helps. Well, the Ati thing wouldn't work anyway, but if the "mouse bug" option doesn't help you either, something funky is going on.
  • You don't have sit lock enabled? (It should print a message, but doesn't urt to ask).
  • Walking with the keyboard works.

I know you can compilke from CVS, so can you do the following:

  • turn off the mouse bug options in the configuration window and set the view to isometric
  • In the file interface.c, function get_world_x_y(), add a line
    printf ("%d, %d, %f -> %f, %f, %f\n", mouse_x, window_height-hud_y-mouse_y, mouse_z, sx, sy, sz);
    


    after the call to gluUnProject on line 99.

  • Compile, start the client from a terminal window, and click a few times around your character
  • Post the printed output here.

Edited by Grum

Share this post


Link to post
Share on other sites

I don't find the word to express the happy I am after seeing the reply to my post. I was begining to think I'll don't have any reply. Thanks a lot. You make me very happy. I'm going to do all these thinks right now and edit this answer with the results.

Okay, let's first establish a few facts:

  1. This happens not only with the current CVS client, but also with the official binary?
  2. When the game broke, it was not because you updated the code from CVS? Did you do a system or video drivers update?
  3. You say that neither of the mouse bug options in the configuration window helps. Well, the Ati thing wouldn't work anyway, but if the "mouse bug" option doesn't help you either, something funky is going on.
  4. You don't have sit lock enabled? (It should print a message, but doesn't urt to ask).
  5. Walking with the keyboard works.

  1. With the official binary (for linux) happens what I explain at bottom of this reply (so the same problem but I can walk)
  2. I think there was not a driver update because I do it manually (the nvidia drivers). Maybe was system update (with synaptic) but I surely think there wasn't any. And... I think I didn't update the cvs.
  3. No, the mouse bug options seems to do nothing for me. As I say at the bottom, on the official release it lets me walk.
  4. No, I don't.
  5. Yes, walking with the keyboard works (and sit down, etc...).

One more thing: because of my desesperating situation before going to bed yesterday I tried the "normal" version. So:

  • I renamed the $HOME/.elc dir (preventing incompatibilities or whatever)
  • Unzipped the "normal" version file to "el_install" folder (the default)
  • Run the game. Close it with [Alt]+[X] and then fix the game_data dir on $HOME/.elc/el.ini
  • Run the game again and:
    • If I check the ATI bug nothing happens.
    • If I check the mouse bug nothing happens
    • If _both_ options are unchecked (disabled or whatever) I CAN WALK AROUND but not touch, see, etc... but I can walk very well :-D

So, after doing all that things I've got:

$ ./el.x86.linux.bin 
B: 0.6
B: 1.5
B: 1.5
B: 2
B: 0.6
323, 238, 0.063128 -> -719874654.542140, 9548918.478779, 28578.687053
396, 355, 0.084144 -> -719360466.477481, 6309781.841190, 104951.241543
503, 99, 0.038159 -> -734160580.889034, 211826.505720, -263300.084461
329, 235, 0.062589 -> -720291425.345911, 9242840.769117, 20684.086302
385, 295, 0.073367 -> -720979519.722798, 6664051.413859, 45849.813714

Edited by Debianita

Share this post


Link to post
Share on other sites

Well, developer time is limited, especially if their family is visiting them to celebrate their birthday. Please realize we're all volunteers :D

 

I'm not sure what's going on here, but it almost looks like we have another depth buffer bug on our hands. The values for mouse_z (third column) should normally be somewhat less than 1, I think (0.98'ish), while your client prints a much smaller number. However, it's not a simple scaling factor as with thew Ati bug. It also doesn't explain why you can't move with the old clicker ("mouse bug" option) enabled.

 

Ehm... I don't have any brilliant insights yet. Let's see if the "old" and "new" code give the same result. In gamewin.c, make comment out lines 803-806, call both functions, and print out the results:

					/*
					if(use_old_clicker)
							get_old_world_x_y (&x, &y);
					else
							get_world_x_y (&x, &y);
					*/
					get_old_world_x_y (&x, &y);
					printf ("old: %d, %d\n", x, y);
					get_world_x_y (&x, &y);
					printf ("new: %d, %d\n", x, y);

recompile, try to move again a few times, and post results here (your character position from click on the compass would be useful too).

 

(btw, note that this effectively disables the "mouse bug" option since you always call the new clicker function afterward. But that wasn't working anyway).

Share this post


Link to post
Share on other sites
Ehm... I don't have any brilliant insights yet. Let's see if the "old" and "new" code give the same result. In gamewin.c, make comment out lines 803-806, call both functions, and print out the results:

recompile, try to move again a few times, and post results here (your character position from click on the compass would be useful too).

Oh boy. I have a problem.

Grum, you are going to love me.... (that's sarcasm btw)

 

I tried this and consistently get -32768 for both x and y, new and old.

 

I am also running Debian Testing (Lenny) with the Radeon driver for X. I'm running Xfce4 (not that that should matter) and the behaviour is the same with either Xfwm4 or Compiz Fusion (3D desktop) as my window manager.

 

I can click on and use all the 2D parts of the window, just have no detection of mouse position, "under mouse functions" (changed cursors) or click location detection in 3D space.

 

I'll try to fire up something to show mouse position coords (similar to the map editor iirc). Maybe something under -DDEBUG? I can also do the normal dumps of detected options in the client as well as glxinfo and xdpyinfo etc. if deemed helpful.

 

/edit: This is the same for all combinations of ATI and mouse bug options.

 

/edit 2: Oops, this machine is running Debian Testing (Lenny).

Edited by Torg

Share this post


Link to post
Share on other sites

Hmmmm. I'm coming up with nothing.

 

I've searched Google for a while and I can't find anything on odd OpenGL mouse things, ATI or not.

 

I'm wondering if we are doing something odd in the client? Possibly not setting a state or something which is still handled by most drivers, but not all (Radeon OSS driver), or only half (ATI bug)?

 

I've had a quick look at some of the OpenGL init examples and what we do looks mostly ok, but is far more detailed and broken up, so kinda hard to track something wrong or missing.

Share this post


Link to post
Share on other sites

Hmmmm. I'm coming up with nothing.

Same here.

I'm wondering if we are doing something odd in the client? Possibly not setting a state or something which is still handled by most drivers, but not all (Radeon OSS driver), or only half (ATI bug)?

Most likely, we're doing something wrong. Can you turn off any "experimental" features like SKY_FPV_CURSOR and see if you can get it to work.

The Ati bug was a real driver bug, btw. The value it returned from reading the depth buffer was always a factor 256 too low, and has bitten other programs as well.

I've had a quick look at some of the OpenGL init examples and what we do looks mostly ok, but is far more detailed and broken up, so kinda hard to track something wrong or missing.

Yes, and it takes only one missing glEnable() call in a routine that's supposed to only temporarily disable a certain feature, and something may get messed up in an entirely different part of the code. That's why I'd like people experiencing such problems to compile with only the most basic options, turn off any fancy extensions, and see if the problem remains.

Share this post


Link to post
Share on other sites

After the segmentation fault got solved, I have another problem. Like the other: this problem has came suddenly, but has came after the other. I played for 23 days without any problem and one bad day *ZAP* the game got broken or something :-) yes, it's so much strange :-) (I smile trying not to cry ;-) ). So, the problem:

 

The mouse doesn't work. But it's not fully "disabled". I can use the interface buttons, click the skills, zoom in/out and rotate the camera, etc... BUT I can't walk around, touch nothing, attack and all of that.

 

I can move the cursor (obvious) but although I click (and "activate") the touch, attack, etc... button, the cursor doesn't change. It's fixed to the walk cursor.

 

I think I have no more useful information to give. Oh, and the keyboard works perfectly.

 

Like I said on other posts, I play on linux, debain testing, and have a nvidia geforce fx 5200. And I have 3D accel thanks to the nvidia website drivers. I've tried the updated (at this moment the 100.14.11 version) and an "old" release (the 100.14.03 one). It's the same result for me. And I play on 2.6.18-4-486 , not the 2.6.21 version because of the "GPL bug" :-)

 

This has happened to me several times (windows version), only way to solve it is by restarting the client, i dont know what makes it happen, some of the times happened when i changed screen mode (full to window or vice-versa), but i seen it happen with a simple map change too. Can´t walk or click on stuff, can´t even see the green thingy when u click somewhere to walk.

 

The client is the officil from el site, and haven´t done any changes neither to the client nor the computer drivers.

Edited by Bahamut_Zero

Share this post


Link to post
Share on other sites
Most likely, we're doing something wrong. Can you turn off any "experimental" features like SKY_FPV_CURSOR and see if you can get it to work.

I'm not running any that I know of... only the basics expected in the new client (NEW_SOUND, CLICKABLE_CONTINENT_MAP, etc)

 

The Ati bug was a real driver bug, btw. The value it returned from reading the depth buffer was always a factor 256 too low, and has bitten other programs as well.

Hmmm, interesting. I didn't find anything about it when Googling, but at the same time I was looking for "ATI mouse bug" and such things.

 

This has happened to me several times (windows version), only way to solve it is by restarting the client, i dont know what makes it happen, some of the times happened when i changed screen mode (full to window or vice-versa), but i seen it happen with a simple map change too. Can´t walk or click on stuff, can´t even see the green thingy when u click somewhere to walk.

This definitely sounds like a glEnable (or whatever) that is not reset correctly.

 

In my specific case I actually think we have some initialisation of the window wrong because when I run glxgears (OpenGL 3D test app) under Compiz Fusion it is fine, but when I run the EL client I get odd behaviour. If I hover over the title bar/vertical scroll bar etc of a window behind EL, I get them drawn over the top of the 3D parts of the EL window and they flicker as both windows are updated (I assume).

Share this post


Link to post
Share on other sites
The Ati bug was a real driver bug, btw. The value it returned from reading the depth buffer was always a factor 256 too low, and has bitten other programs as well.

Hmmm, interesting. I didn't find anything about it when Googling, but at the same time I was looking for "ATI mouse bug" and such things.

Just for reference:

Ati bug report: http://ati.cchtml.com/show_bug.cgi?id=66

Forum threads: http://www.eternal-lands.com/forum/index.php?showtopic=11466, http://www.eternal-lands.com/forum/index.php?showtopic=13268

Share this post


Link to post
Share on other sites
Yes, and it takes only one missing glEnable() call in a routine that's supposed to only temporarily disable a certain feature, and something may get messed up in an entirely different part of the code. That's why I'd like people experiencing such problems to compile with only the most basic options, turn off any fancy extensions, and see if the problem remains.
I added -DOPENGL_TRACE for chasing down some OpenGL problems, which is probably worth using when looking for bugs... it doesn't do a lot, and is far from exhaustive, but this (with -DDEBUG) may give some hints in error_log for some problems. Of course, if anyone wants to add more to that define to catch different OpenGL problems... :) Edited by ttlanhil

Share this post


Link to post
Share on other sites

WOW!! how many replies for this post!! I'm really impressed!! Sorry for the delay to bring results but yesterday I fell ill and can't turn on the pc.

 

Here are my results: I'm on Irsis insides, at [154, 325] (inside a house in front of the store, I think...) and this is the console exit ("interface.c" indications included):

$ ./el.x86.linux.bin 
B: 0.6
B: 1.5
B: 1.5
B: 2
B: 0.6
old: -32768, -32768
338, 292, 0.072835 -> -366107651.933292, 4277904.436869, 42337.562248
new: -32768, -32768
old: -32768, -32768
308, 279, 0.070500 -> -365792674.855816, 5553051.491647, 50840.288779
new: -32768, -32768
old: -32768, -32768
366, 145, 0.046429 -> -371458661.779838, 2840996.668333, -25867.263630
new: -32768, -32768
old: -32768, -32768
289, 255, 0.066189 -> -366094231.542591, 6336195.116025, 50254.005285
new: -32768, -32768
old: -32768, -32768
314, 281, 0.070859 -> -365874737.287001, 5297091.792190, 48912.509129
new: -32768, -32768
old: -32768, -32768
269, 268, 17.542086 -> -301723100.891810, 74985782.083028, 2514842.861439
new: -32768, -32768
old: -32768, -32768
256, 240, 0.063494 -> -365770001.681177, 7737771.462642, 59341.894948
new: -32768, -32768
old: -32768, -32768
398, 84, 0.035472 -> -374173793.751118, 1364742.781512, -63291.275034
new: -32768, -32768
old: -32768, -32768
491, 101, 0.038526 -> -375890663.591412, -2624344.762528, -98474.192144
new: -32768, -32768
old: -32768, -32768
384, 400, 0.092235 -> -363791983.203592, 2459245.333366, 62653.748912
new: -32768, -32768
old: -32768, -32768
608, 206, 0.057387 -> -375393497.568356, -7513214.669756, -111069.665553
new: -32768, -32768

Share this post


Link to post
Share on other sites

Oh, one more thing: at one point of all this "problems road" :-S I updated the system via Synaptic. I've read the history os the updates and ligl1-mesa-* were updates from 7.0.1-1 to 7.0.1-2 . Maybe it doens't help because of my nvidia card and I use the nvidia drivers, but... I'd like to mention it :-) And, if there are more libraries I should look for if were updated, please tell me (I searched for libopenal, libcalm, libgl, ... ).

 

Thanks a lot for the helping and, I still hoping the time I can play EL agains arrives. "For the moment" (I'm not sure this expression is correct in english), I don't lose the hoping :-p

Share this post


Link to post
Share on other sites
I updated the system via Synaptic. I've read the history os the updates and ligl1-mesa-* were updates from 7.0.1-1 to 7.0.1-2.
Ahuh! I am also running this exact version of libgl1-mesa-dri.

 

If you can find an older version of the library you can try (my machine won't install anything else due to dependancies) that would be very helpful.

 

And, if there are more libraries I should look for if were updated, please tell me (I searched for libopenal, libcalm, libgl, ... ).
No, the problem is certainly OpenGL, the question is, is the bug in our code or theirs (the lib). I know there are quite a lot of bugs in the mesa libs, but I can't find anything about this sort of problem (yet).

 

If we can work out if an older version does in-fact work, then we might be able to help fix the mesa lib, otherwise it will be a huge amount more searching to work out what we are doing wrong in the client.

Share this post


Link to post
Share on other sites
I updated the system via Synaptic. I've read the history os the updates and ligl1-mesa-* were updates from 7.0.1-1 to 7.0.1-2.
Ahuh! I am also running this exact version of libgl1-mesa-dri.

 

If you can find an older version of the library you can try (my machine won't install anything else due to dependancies) that would be very helpful.

Mmm... I've tried to get an older version but there's no option on synaptic to do that. On the "package properties" window > Versions dont's appear any other version. Maybe because of dependencies too, or because I'm running debian _testing_ ... I don't know why.

And, if there are more libraries I should look for if were updated, please tell me (I searched for libopenal, libcalm, libgl, ... ).
No, the problem is certainly OpenGL, the question is, is the bug in our code or theirs (the lib). I know there are quite a lot of bugs in the mesa libs, but I can't find anything about this sort of problem (yet).

 

If we can work out if an older version does in-fact work, then we might be able to help fix the mesa lib, otherwise it will be a huge amount more searching to work out what we are doing wrong in the client.

Mmm... but, what I said about I'm not using the mesa libs because I'm using the nvidia ones... does it matters?? the libgl1-mesa libs are used to compile the game and it's not important the drivers I use to run the game?? I don't know very much about all of this, that's why I ask ;-)

 

Anyway, I don't know any "ugly words" in english but it's a big "putadon" for me all this stuff (I don't know if stuff is correct here) :-) Yes, I know this is not happy for you too, but my addiction for Eternal Lands hurts me :-p Seems I'm losing the hope. Any ideas??

Share this post


Link to post
Share on other sites

To find out which libraries EL is using, you can use ldd. On my system:

host:/extra/Software/EL/elc % ldd ./el.x86.linux.bin
	libSDL-1.2.so.0 => /usr/lib/libSDL-1.2.so.0 (0x00002ba4cc52a000)
	libpthread.so.0 => /lib/libpthread.so.0 (0x00002ba4cc68e000)
	libxml2.so.2 => /usr/lib/libxml2.so.2 (0x00002ba4cc7a8000)
	libz.so.1 => /lib/libz.so.1 (0x00002ba4cc9e6000)
	libm.so.6 => /lib/libm.so.6 (0x00002ba4ccafa000)
	libSDL_net-1.2.so.0 => /usr/lib/libSDL_net-1.2.so.0 (0x00002ba4ccc52000)
	libSDL_image-1.2.so.0 => /usr/lib/libSDL_image-1.2.so.0 (0x00002ba4ccd57000)
	libopenal.so.0 => /usr/lib/libopenal.so.0 (0x00002ba4cce73000)
	libGL.so.1 => //usr/lib64/opengl/nvidia/lib/libGL.so.1 (0x00002ba4cd018000)
	libGLU.so.1 => /usr/lib/libGLU.so.1 (0x00002ba4cd1d6000)
	libcal3d.so.12 => /usr/lib/libcal3d.so.12 (0x00002ba4cd353000)
	libalut.so.0 => /usr/lib/libalut.so.0 (0x00002ba4cd4de000)
	libpng12.so.0 => /usr/lib/libpng12.so.0 (0x00002ba4cd5e6000)
	libvorbis.so.0 => /usr/lib/libvorbis.so.0 (0x00002ba4cd70a000)
	libvorbisfile.so.3 => /usr/lib/libvorbisfile.so.3 (0x00002ba4cd834000)
	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002ba4cd93c000)
	libc.so.6 => /lib/libc.so.6 (0x00002ba4cda47000)
	libdl.so.2 => /lib/libdl.so.2 (0x00002ba4cdc82000)
	libX11.so.6 => /usr/lib/libX11.so.6 (0x00002ba4cdd87000)
	libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.6/libstdc++.so.6 (0x00002ba4cdf92000)
	libXext.so.6 => /usr/lib/libXext.so.6 (0x00002ba4ce182000)
	libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0x00002ba4ce294000)
	libXrender.so.1 => /usr/lib/libXrender.so.1 (0x00002ba4ce397000)
	/lib64/ld-linux-x86-64.so.2 (0x00002ba4cc40e000)
	libasound.so.2 => /usr/lib/libasound.so.2 (0x00002ba4ce4a1000)
	libsmpeg-0.4.so.0 => /usr/lib/libsmpeg-0.4.so.0 (0x00002ba4ce669000)
	libGLcore.so.1 => //usr/lib64/opengl/nvidia/lib/libGLcore.so.1 (0x00002ba4ce7c5000)
	libnvidia-tls.so.1 => //usr/lib64/opengl/nvidia/lib/libnvidia-tls.so.1 (0x00002ba4cf0fa000)
	libogg.so.0 => /usr/lib/libogg.so.0 (0x00002ba4cf1fb000)
	libXau.so.6 => /usr/lib/libXau.so.6 (0x00002ba4cf301000)
	libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00002ba4cf404000)

Share this post


Link to post
Share on other sites

Ok, this is mine:

$ ldd ./el.x86.linux.bin
	linux-gate.so.1 =>  (0xffffe000)
	libSDL-1.2.so.0 => /usr/lib/libSDL-1.2.so.0 (0xb7e20000)
	libxml2.so.2 => /usr/lib/libxml2.so.2 (0xb7d03000)
	libSDL_net-1.2.so.0 => /usr/lib/libSDL_net-1.2.so.0 (0xb7cff000)
	libSDL_image-1.2.so.0 => /usr/lib/libSDL_image-1.2.so.0 (0xb7ce4000)
	libopenal.so.0 => /usr/lib/libopenal.so.0 (0xb7ca8000)
	libGL.so.1 => /usr/lib/libGL.so.1 (0xb7c13000)
	libGLU.so.1 => /usr/lib/libGLU.so.1 (0xb7b92000)
	libcal3d.so.12 => /usr/lib/libcal3d.so.12 (0xb7b14000)
	libm.so.6 => /lib/libm.so.6 (0xb7aee000)
	libalut.so.0 => /usr/lib/libalut.so.0 (0xb7ae6000)
	libpng12.so.0 => /usr/lib/libpng12.so.0 (0xb7ac3000)
	libvorbis.so.0 => /usr/lib/libvorbis.so.0 (0xb7a9b000)
	libvorbisfile.so.3 => /usr/lib/libvorbisfile.so.3 (0xb7a92000)
	libz.so.1 => /usr/lib/libz.so.1 (0xb7a7d000)
	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb7a72000)
	libc.so.6 => /lib/libc.so.6 (0xb792a000)
	libX11.so.6 => /usr/lib/libX11.so.6 (0xb783e000)
	libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb7753000)
	libasound.so.2 => /usr/lib/libasound.so.2 (0xb768c000)
	libdl.so.2 => /lib/libdl.so.2 (0xb7688000)
	libdirectfb-0.9.so.25 => /usr/lib/libdirectfb-0.9.so.25 (0xb7632000)
	libfusion-0.9.so.25 => /usr/lib/libfusion-0.9.so.25 (0xb762c000)
	libdirect-0.9.so.25 => /usr/lib/libdirect-0.9.so.25 (0xb761d000)
	libvga.so.1 => /usr/lib/libvga.so.1 (0xb75bd000)
	libpthread.so.0 => /lib/libpthread.so.0 (0xb75a5000)
	libGLcore.so.1 => /usr/lib/libGLcore.so.1 (0xb6c0d000)
	libnvidia-tls.so.1 => /usr/lib/tls/libnvidia-tls.so.1 (0xb6c0b000)
	libXext.so.6 => /usr/lib/libXext.so.6 (0xb6bfd000)
	/lib/ld-linux.so.2 (0xb7ef0000)
	libogg.so.0 => /usr/lib/libogg.so.0 (0xb6bf8000)
	libXau.so.6 => /usr/lib/libXau.so.6 (0xb6bf4000)
	libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb6bef000)

:-)

Share this post


Link to post
Share on other sites

Found it!

 

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=441071

 

They have discovered a serious bug in Mesa 7.0.1-2 that causes gluUnProject to not work properly. This has been fixed upstream and will be fixed in 7.0.2. In the mean time, it is recommended to downgrade your package to 7.0.1-1 which can be found here: http://snapshot.debian.net/archive/2007/08...ol/main/m/mesa/.

 

I haven't tried this myself yet, but shall do once I finish posting this.

 

As for why this affects you Debianita when you are using and linking to the Nvidia drivers, I have no idea. It seems you are linked to all kinds of things that are GL and GLU related. Maybe there is some deeper linking in other libs (which I'd be a little worried about).

 

Anyways, worth trying to downgrade the drivers and see if that fixes things for you.

 

 

/edit: WOW!! If you check through the various bug reports eventually you find a link to the commit that breaks things. Check this out for a mess!!

Edited by Torg

Share this post


Link to post
Share on other sites

Nice work, Torg!

Told you it there was something weird going on with gluUnproject :P

 

And I think libGLU on Debianita's system is from mesa, not from the nvidia drivers. At least on my ubuntu box, libGL is from nvidia, but libGLU isn't. Since I'm a newbie to Ubuntu, I'm still trying to figure out how to get dpkg/apt/whatever to give me more information :blush:

secretly wishing "equery belongs /usr/lib/libGL*" would simply work on Ubuntu

 

EDIT:

/edit: WOW!! If you check through the various bug reports eventually you find a link to the commit that breaks things. Check this out for a mess!!

Actually, the new code with all the multiplications) is at first glance pretty similar to the inversion routine we've had in the client. I did check that one, but it took me approx. 1.5 hours to check all the indices, so I'm not going to hunt for the bug in this one :D

Edited by Grum

Share this post


Link to post
Share on other sites

So.... it has been a very very very hard time for me. I'm very addicted to eternal lands and I've been "logging in" only to speak with my friends without moving or anything. But... I can say.... THE PROBLEM HAS FIXED !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

 

I cant's express how much happy I am and how much I thank you for all the help, and the patience. All of you are wonderful guys :-) Sincerely: thank you very very much. I think I'¡m gonna cry :-p

 

Oh: what I've done has been downgrade _all_ the packages with *-mesa-*-7.0.1-2 to 7.0.1-1 version. But the ones have done it works have been the libglu1 ones ;-) I think the thread is solved and I'm very very very happy so I can play EL again :-D

 

YUUUUUUUUHUUUUUUUU !!!! :-D

Share this post


Link to post
Share on other sites

After installing libglu1-mesa all is fine now thanks a lot. :blush:

 

edit: that is libglu1-mesa version 7.0.1-1 of course

Edited by Mortek

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

×