Brendane,
this is very strange. As I told you I had the same problem, and they totally went away by installing new drivers.
But beware! on laptops like mine (and yours?) you have to be very careful to install the right drivers. Mine's a Dell, and after consulting our Sysad I had to go to the Dell side and download drivers there, and nowhere else. So you might doublecheck this.
That said, I can imagine on the other hand that the GUI uses some exotic DX thing that simply isn't implemented in a very efficient way on the nVidia2go chips (or yours, whatever that is). So maybe there is a way to check whether the GUI component gets an extra overhaul.
Oh, and by the way - windowed or fullscreen doesn't make a difference on my machine. I am sure that this is a matter of what of the DX specs are implemented how. And this is a matter of the chip and it's drivers.
Regards,
Dirk
this is very strange. As I told you I had the same problem, and they totally went away by installing new drivers.
But beware! on laptops like mine (and yours?) you have to be very careful to install the right drivers. Mine's a Dell, and after consulting our Sysad I had to go to the Dell side and download drivers there, and nowhere else. So you might doublecheck this.
That said, I can imagine on the other hand that the GUI uses some exotic DX thing that simply isn't implemented in a very efficient way on the nVidia2go chips (or yours, whatever that is). So maybe there is a way to check whether the GUI component gets an extra overhaul.
Oh, and by the way - windowed or fullscreen doesn't make a difference on my machine. I am sure that this is a matter of what of the DX specs are implemented how. And this is a matter of the chip and it's drivers.
Regards,
Dirk