xman on 23/3/2002 at 11:04
* EDITED by myself * : DON'T READ THIS !!! The problem is solved.
I've seen many people having problems with ATI Radeon, but here I'm having problems with an nVIDIA GeForce under WinXP.
Since I got the Arx Demo, I've been using the Detonator 27.30 drivers (with nvreffix). And the only graphical problem I had what the loading screen that sometimes was bilinearly filtered (OK) but most of the time, it wasn't (not OK).
Now, I've switched to the new official Detonator 28.32. I've got the second edition of the file because the first file provided at nVIDIA was buggy (no control panel). And I've got a tweaked version that supports the nvidia refresh rate fix program.
These drivers run very well : good results with 3Dmark2001se, no problems with games... except Arx !!!
Since I installed these drivers, I've been able to run Arx only ONCE (well... twice as it crashed while playing and I was able to run it again). But that was just after rebooting the PC at the end of the drivers installation. And by the way, there still was the non-filtered loading screen little problem.
Now, when I run Arx, my screen will switch the resolution to the one of the game then back to the one of the desktop and finally come back to the desktop. I won't even see the Fishtank logo, nor hear it so I guess it crashes before. And the "Arx demo 1.0" process is still running (hung though) and is visible in the task bar so I have to right click on it and choose "Close".
If all my other games were showing the same symptoms, I'd conclude that the drivers are buggy. But since only Arx has problems... I'm wondering if the problem comes from the Arx... Maybe in the video initialization process...
I'll make a few more tests to find out where the problem comes from, though...
xman on 23/3/2002 at 11:47
OK. I solved my problem. It was MY fault. Not Arx's.
I accidentally checked the box "activate nView desktop manager" while I only have 1 monitor. I unchecked the box back (it's unchecked by default) and now it works fine.
Sorry to introduce false bugs. :(
Tels on 23/3/2002 at 12:12
Well, it may help somebody else to <B>not</B> make this mistake ;)