Hi, Thanks for your reply.
Ian Romanick wrote:
radeonUploadTexImages: ran into bound texture
I think this may be caused by a bug I found while doing some work on the texmem branch. I believe that the exported maximum texture size is too big. It may be possible that tuxracer is trying to do multitexturing with 2 maximum sized textures, and they won't both fit in on-card memory at once.
I just downloaded the Tuxracer 1.1 demo (which shows the same effect) in which one can make all kinds of video settings. I set it to the lowest quality I could (lowest detail, 16bpp, etc.). This helped slightly, but only slightly... (Still very shocky behaviour and those error messages...)You should be able to test this. If there is some way to adjust the texture detail in tuxracer, try setting it to a lower detail (i.e., use smaller textures). If that makes the problem go away, then it is probably the texture memory of over committed. If you're really adventurous, you can
I'm not experienced enough with this stuff that I can say I am really adventurous... For my own safety, I'd better not try this without some expert sitting near me! ;-)trying building and installing the texmem-0-0-1 branch. If the problem does not exist in the branch, then we'll probably want to back-port the fix to the trunk before the XFree 4.3.0 release.
Is there a way to put this fix in the Debian packages on Michel D\"anzer's site? If so, I can try that.
Thanks again!
Best regards,
Manuel Bilderbeek
-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
