[SHIFT] key = Walk!

[Ring_of_Fire]

Hi, does anyone know why I can't run, but walk in Vice City when in Windows XP compatibility mode? I could always do so in Windows 98/ME mode. Why? I think this problem should be added to the Bug Fix list...

 

By the way, the ReadMe file for Vice City clearly states that it supports Windows XP.

 

* Also, I am not able to skip the cutscenes for that key anymore nor blow my horn! Thanks anyway, but I fixed the problem already.

 

 

EDIT: Well, I thought at first changing the 'Sprint' key to a different assignment was what cause it to work. But it seems that it was the gta_vc.set file.

Edited April 15, 2007 by Ring_of_Fire

[Justin]

Are you running on Vista then?

[Ring_of_Fire]

I'm using XP, not Vista. "Restore Defaults" in Controller Setup made it work since it reinitialized my gta_vc.set file for use with the gta-vc.exe in Windows XP compatibility mode. The only problem I am having now is that textures take too long to load in places like Little Haiti/Havana or in Washington Beach during "The Driver" mission when Hilary dies through a bridge, so I had to switch back the gta-vc.exe to Windows 98 compatibility mode. It's like Vice City was meant to be played on Windows 98/Me only. It's seems buggy in Windows XP mode -> turning on frame limiter, even tweaking around in Catalyst Control Center, and upping the draw distance didn't help.

Edited April 16, 2007 by Ring_of_Fire

[Justin]

I'm using XP, not Vista.

Well then it's just Windows XP, not Windows XP compatibility mode...

 

Does Restore Defaults actually edit the SET file? I would have thought not. Deleting it might be worth a shot just in case it doesn't.

[Ring_of_Fire]

I tried to run, and I realized I couldn't. Restore Defaults -> everything works like a charm.

 

 

Does Restore Defaults actually edit the SET file? I would have thought not. Deleting it might be worth a shot just in case it doesn't.

Well, seeing as though no settings can be changed and saved without the gta_vc.set file, I'd think yes. The game has to edit the [.set] file if you change anything in the "Options" menu as that's where the game keeps it's configuration settings. I thought you knew that? So by clicking on 'Restore Defaults', the game communicates with the file and makes changes to it. This is another way of having to not delete the [.set] file.

[Justin]

Does Restore Defaults actually edit the SET file? I would have thought not. Deleting it might be worth a shot just in case it doesn't.

Well, seeing as though no settings can be changed and saved without the gta_vc.set file, I'd think yes. The game has to edit the [.set] file if you change anything in the "Options" menu as that's where the game keeps it's configuration settings. I thought you knew that?

I know that.

 

But I thought Restore Defaults was a Windows command, restoring the default "open this file type with" and the like. I'm still sceptical that it actually restores the defaults of installed programs such as the VC setting file. In fact, I find it highly unlikely and would think that your game now works for some reason other than an editing of the SET file.

[Heihachi_73]

The cars falling through the bridge isn't a compatibility mode bug, it sounds like an onboard graphics chipset bug.

 

By rights, you shouldn't need to touch compatibility mode at all for any of the modern GTA series.

 

I was using my onboard SiS chipset for ages and it was driving me up the wall in Vice City (don't even get me started on GTA3!). Since I bought a Radeon 9550 (256MB) and upgraded to 512MB RAM I have never had a single problem with any GTA, including San Andreas, which refused to run at all before (the SiS chipset stole 32MB for the graphics, leaving the PC with only 224MB usable).

Edited April 16, 2007 by Heihachi_73

[Ring_of_Fire]

T2-Support said that it was actually an issue with high-end grqphics card. When Hilary falls through a bridge -> it means that the textures weren't loaded on the road he drove on, thus, he then falls through Blue Hell and dies. This problem happens when people crank up anti-aliasing and anisotropic filtering, and so it takes more time for textures to load up as a result of indirect fps loss. For IGP chipsets, the only workaround is to lower down the resolution so that the GPU doesn't have to work as hard. T2-Support didn't mention this because they assumed that people could easily run Vice City at their current resolution. They didn't realize that the in-game res. and draw distance also impacts performance, not necessarily the settings in Catalyst or ForceWare.

 

For a bit of test: I think if we were to set the game to be run in Windows 98 compatibility, turned on the frame limiter, and maxed out the resolution/draw distance/AA-AF, then texture performance would be just as worse when run without compatibility mode turned on.