Same here. This is an old, long standing bug. I can't say if the bug is with Ryzom or with the intel drivers.
I believe most of the code development and bug fixing actually happens on the open source fork of the NeL engine (the code that runs Ryzom). The project's web page can be entered here: http://ryzomcore.org/
Last year (or was it two years ago) dfighter started to work on the Shaders as a Google Summer of Code project. He's again a GSoC contributor this year. Maybe some of the work around what he's doing is or will eventually address this problem as well.
If you find a bug which you can identify to be a real code bug, then your best bet is to address this on the issues tracker on the ryzomcore project. Eventually, from time to time (read: rarely, but they do), the Ryzom (this paid game) developer(s) merge code from the open source project into the paid game (they also contributed back in the past).
However all actual game data (mission texts, NPC behaviour and such) can only be resolved by contacting support in the Ryzom game.
I believe most of the code development and bug fixing actually happens on the open source fork of the NeL engine (the code that runs Ryzom). The project's web page can be entered here: http://ryzomcore.org/
Last year (or was it two years ago) dfighter started to work on the Shaders as a Google Summer of Code project. He's again a GSoC contributor this year. Maybe some of the work around what he's doing is or will eventually address this problem as well.
If you find a bug which you can identify to be a real code bug, then your best bet is to address this on the issues tracker on the ryzomcore project. Eventually, from time to time (read: rarely, but they do), the Ryzom (this paid game) developer(s) merge code from the open source project into the paid game (they also contributed back in the past).
However all actual game data (mission texts, NPC behaviour and such) can only be resolved by contacting support in the Ryzom game.