Okay, this is bizarre, and maybe together we can figure out why this is happening.
Here's the deal:
Next time I loaded the client after this fix, the problem returned. Taking your advice, I added the line 'Driver3D="OpenGL";' to my client.cfg, to no avail - the problem remained. I re-opened client_default.cfg to see if there was another setting that may be causing it - saved, closed, and the problem was gone again.
So, after some experimentation, this is what I've discovered. Adding the line to client.cfg does not solve the issue.
Having the line present in client_default.cfg, in and of itself, doesn't even solve the issue.
Here's the weird part: If I open client_default.cfg, and change ANYTHING - I'm talking adding a space to one of the commented sections, not changing a setting - then save the file, THEN start the Ryzom client, the problem goes away for that instance of the Client only.
After that, if I exit and launch the client again, the issue returns.
Thoughts?
Here's the deal:
Next time I loaded the client after this fix, the problem returned. Taking your advice, I added the line 'Driver3D="OpenGL";' to my client.cfg, to no avail - the problem remained. I re-opened client_default.cfg to see if there was another setting that may be causing it - saved, closed, and the problem was gone again.
So, after some experimentation, this is what I've discovered. Adding the line to client.cfg does not solve the issue.
Having the line present in client_default.cfg, in and of itself, doesn't even solve the issue.
Here's the weird part: If I open client_default.cfg, and change ANYTHING - I'm talking adding a space to one of the commented sections, not changing a setting - then save the file, THEN start the Ryzom client, the problem goes away for that instance of the Client only.
After that, if I exit and launch the client again, the issue returns.
Thoughts?