Mac Radeon 7000 vs "Screen display mode"
Moderator: Developers
- Vincent Weylind
- Posts: 6
- Joined: Mon Aug 13, 2007 6:58 pm
Mac Radeon 7000 vs "Screen display mode"
As I read this forum, it seems I have a common problem yet I cannot fix it. When I try to log in, I get the "Unable to find requested screen display mode" message.
- I have searched the forum but there doesn’t seem to be any thread that matches my setup (I think):
Macintosh G4
OS Tiger 10.4.10 (all Apple updates made)
ATI Radeon 7000 PCI (ATI / AMD updates done)
I have tried
- different monitor resolutions and color depth
- different Options (Fullscreen / Window, Graphics quality, Color depth, Texture update, even Frame rate)
- to modify the .cfg file directly
- to both run the Illarion client from my computer and by clicking "Play Game" on the main page.
Any ideas or suggestions would be much appreciated.
- I have searched the forum but there doesn’t seem to be any thread that matches my setup (I think):
Macintosh G4
OS Tiger 10.4.10 (all Apple updates made)
ATI Radeon 7000 PCI (ATI / AMD updates done)
I have tried
- different monitor resolutions and color depth
- different Options (Fullscreen / Window, Graphics quality, Color depth, Texture update, even Frame rate)
- to modify the .cfg file directly
- to both run the Illarion client from my computer and by clicking "Play Game" on the main page.
Any ideas or suggestions would be much appreciated.
- Vincent Weylind
- Posts: 6
- Joined: Mon Aug 13, 2007 6:58 pm
I have set the monitor color depth to "thousands" and "millions" and then tried the client using 16, 24 and 32 bit, just to have gone through all options.
I have tried setting the monitor to 1024x768 (Illarion window and fullsize), as well as higher monitor resolution (1280x960).
The Radeon 7000 supports OpenGL 1.3. I ran an OpenGL test application that confirms this for the system. Could it be that Illarion requires a later version? It is a 32 mb graphics card by the way.
I have tried setting the monitor to 1024x768 (Illarion window and fullsize), as well as higher monitor resolution (1280x960).
The Radeon 7000 supports OpenGL 1.3. I ran an OpenGL test application that confirms this for the system. Could it be that Illarion requires a later version? It is a 32 mb graphics card by the way.
- Vincent Weylind
- Posts: 6
- Joined: Mon Aug 13, 2007 6:58 pm
I see, that’s the problem then.
The driver installer supports later OpenGL versions, although the 7000’s hardware cannot go beyond 1.3. The next generation of ATI cards were capable of 1.4, and the ones after that is the 2.0-generation.
When I searched this forum, I couldn’t find any other OpenGL requirements than that it had to be supported. Only version 1.1 was being mentioned as I recall.
Anyway, thank you for the assistance. Illarion seems like a great game and I hope to be able to visit it in the future.
The driver installer supports later OpenGL versions, although the 7000’s hardware cannot go beyond 1.3. The next generation of ATI cards were capable of 1.4, and the ones after that is the 2.0-generation.
When I searched this forum, I couldn’t find any other OpenGL requirements than that it had to be supported. Only version 1.1 was being mentioned as I recall.
Anyway, thank you for the assistance. Illarion seems like a great game and I hope to be able to visit it in the future.
- Vincent Weylind
- Posts: 6
- Joined: Mon Aug 13, 2007 6:58 pm
- Vincent Weylind
- Posts: 6
- Joined: Mon Aug 13, 2007 6:58 pm
I changed the line to:
debugLevel=8
When I started the Illarion client today, it downloaded again (an update?). As I try to log in, it quits with the same error message as before, but now the error log does not get updated at all. Should I try with some other debug number?
EDIT: I have now tried all numbers from 1-9 as debugLevel. Some generate the earlier error message, some leave the error log unchanged.
debugLevel=8
When I started the Illarion client today, it downloaded again (an update?). As I try to log in, it quits with the same error message as before, but now the error log does not get updated at all. Should I try with some other debug number?
EDIT: I have now tried all numbers from 1-9 as debugLevel. Some generate the earlier error message, some leave the error log unchanged.
- Vincent Weylind
- Posts: 6
- Joined: Mon Aug 13, 2007 6:58 pm