Grand Theft Auto : Vice City Stories

Portage 0.3.0

Portage natif de Grand Theft Auto : Vice City Stories pour macOS.

gta-vcs-recomp est un portage natif de Grand Theft Auto : Vice City Stories pour macOS, distribué en binaire dans ses releases.

Architecture

Mac OS X - macOS Mac OS X - macOS Apple Silicon Apple Silicon 64 bits 64 bits

Jeu d’origine

Grand Theft Auto : Vice City Stories Playstation Portable (PSP)

Téléchargement et liens

Historique des versions

0.3.0
Full Changelog: https://github.com/gothamor/gta-vcs-recomp/compare/v0.2.4...v0.3.0 New: macOS on Apple Silicon The game and the launcher now run on Macs with Apple Silicon (M1 and later) and macOS 13 or newer. As on Windows and Linux, you bring your own disc and the launcher builds the game on your Mac. The game draws with Metal. To install, download VCS-Recomp-0.3.0-macos-arm64.dmg, open it and drag VCSLauncher onto the Applications folder next to it, then eject the disk image. The launcher isn't signed by Apple yet, so the first time you start it macOS refuses it. Open System Settings → Privacy & Security and choose Open Anyway (you only do this once). The first start puts the game's files in your Library (Application Support → VCSRecomp) and then walks you through the same steps as on Windows. The only thing to install is Apple's free Command Line Tools: Install the Command Line Tools opens macOS's own installer. Everything else is downloaded by the build. Effects at high frame rates Above 30 fps, smoke, exhaust, tyre smoke, spray, rain splashes and dust faded far too fast, and far too many were made. At 144 fps smoke lasted a fifth as long, and fires looked thin. They now…
Changelog complet

Full Changelog: https://github.com/gothamor/gta-vcs-recomp/compare/v0.2.4...v0.3.0

New: macOS on Apple Silicon

  • The game and the launcher now run on Macs with Apple Silicon (M1 and later) and macOS 13 or newer. As on Windows and Linux, you bring your own disc and the launcher builds the game on your Mac. The game draws with Metal.
  • To install, download VCS-Recomp-0.3.0-macos-arm64.dmg, open it and drag VCSLauncher onto the Applications folder next to it, then eject the disk image.
  • The launcher isn't signed by Apple yet, so the first time you start it macOS refuses it. Open System Settings → Privacy & Security and choose Open Anyway (you only do this once).
  • The first start puts the game's files in your Library (Application Support → VCSRecomp) and then walks you through the same steps as on Windows. The only thing to install is Apple's free Command Line Tools: Install the Command Line Tools opens macOS's own installer. Everything else is downloaded by the build.

Effects at high frame rates

  • Above 30 fps, smoke, exhaust, tyre smoke, spray, rain splashes and dust faded far too fast, and far too many were made. At 144 fps smoke lasted a fifth as long, and fires looked thin. They now look and last as on the PS2 at any frame rate.
  • Lightning, clouds, camera shake and explosions also ran faster at high frame rates. Storms flickered in short bursts, clouds turned three times too fast, camera shake buzzed instead of shaking, and explosions were over sooner. They now run at the PS2's pace.
  • Above 30 fps, rain came and went in waves: a second or so of rain, then about three seconds of none, over and over for minutes. At 144 fps there was hardly any rain around you half the time. It now falls as steadily as on the PS2. Just as on the PS2, rain that has just started can come and go for a few seconds before it settles, and it still turns with the camera.
  • The light trails behind cars and street lights at night were gone above 30 fps. They're back.
  • The trails are a quarter weaker above 30 fps or above the original resolution. On a sharp, smooth picture they stood out more than they did on the PS2.
  • If you preferred the effects as they were before, the game's settings (F2) → Enhancements → Effects: Reduce Post Processing Effects puts all of this back at once. It's off by default and applies straight away.

The radio

  • While you drive, the mouse wheel now changes the radio station: down is the next station, up the one before (#90). Before, the wheel did nothing in a vehicle, and the game itself can only step forwards.
  • It's part of the game's settings (F2) → Keyboard: Mouse wheel, which is on by default. If you've bound the wheel to a control, it keeps doing only that.
  • While the radio plays an announcement the game doesn't let you change the station, with the wheel or any other way.
  • Above 30 fps, getting back into a car put the station further on than it should have been. The time you'd spent on foot counted double at 60 fps and almost five times at 144 (#117). The station now picks up where it would on the PS2.

Settings

  • The game now starts in full screen (borderless, on the monitor it was last on). Alt+Enter still switches. If you never changed Window mode before, you'll get full screen too; the game's settings (F2) → Display → Window mode takes you back to a window.
  • The presets in the game's settings (F2) → Display have changed. Enhanced is gone, and Widescreen, light is now called Balanced and sets twice the original resolution. What you set with a preset before stays as it is.
  • Long setting names in the settings menu now show in full.

Missions

  • Purple Haze
    • Above 30 fps the game stayed on "Loading..." for ever after the truck rammed your van (#41). At 60 fps and up the truck didn't stop behind the van as it does at 30. It rolled on and ran over one of the two men just as he appeared behind the black screen, and the game then waited for ever for a line he could no longer say. The mission now plays through at any frame rate.
    • On a widescreen picture the haze only covered the middle and left the sides clear, and it pulled the clock and the weapon icon in from the edge of the screen (#93). It now covers the whole picture.
  • Hose the Hoes
    • Above 30 fps the fire truck's water fell far short, so the brothel's fires never went out and the girls' bar ran down (#144). The higher the frame rate, the shorter the water: it reached about 27 m at 30 fps, 14 m at 60 and 7 m at 144. It now reaches as far as on the PS2 at any frame rate, and puts a fire out just as quickly. This goes for the fire truck everywhere, including the Fire Truck side job. Locking the game to 60 fps is no longer needed.
    • The brothel's fires couldn't be hosed in a full playthrough here. The water's reach and how fast it puts out a fire were measured, so this is hoped to fix the mission.
    • The two burning cars parked outside the brothel blew up twice as soon at 144 fps, and their blasts can set rooms you've already put out alight again. They now go off when they do on the PS2.
    • With the mouse, the water drifted off the fire you were aiming at. The hose points where the camera looks, and a moment after you stopped moving the mouse the camera eased back behind the truck and took the water with it. The gamepad's right stick didn't do this. Now the camera stays where you put it while the truck sprays water, and goes back only once the water has stopped (after the delay in the game's settings (F2) → Keyboard: Car camera return, 1.5 s by default).
  • Snitch Hitch and Kill Phil
    • At 144 fps, "You are getting too far away from the jet" (or "...from the limo") gave you 1.2 seconds to turn back before the mission failed. It's 2.6 seconds again, as on the PS2. A line of dialogue in each mission also came too early.
  • Every mission
    • The kind of wait that hung Purple Haze can no longer hang any other mission: if someone dies before their line has loaded, the game carries on without it.

Fixes

  • With free aim on and a gun in hand, holding the right mouse button while sprinting made the camera stutter: it kept stopping and starting. It now turns smoothly.
  • On foot, turning the camera toward a nearby building with the mouse made it stop dead at the edge of the wall, and it stayed stuck until you turned back. It now keeps turning and moves in closer to Vic, as it always did with a gamepad.
  • Memory: the longer you played and the more of the city you drove through, the more memory the game used, and it never gave any back. Here it grew by up to 2 GB an hour, and one player's PC with 8 GB showed the game at 5.3 GB (#115). The game kept a copy of everything it had ever drawn. It now keeps only what it used recently, so its memory levels off: on the same test drive it settles between 600 and 700 MB and is still there after 40 minutes. Before, it was at 840 MB after 15 minutes and still climbing.
  • Helicopters: at high frame rates the rotor blades did their damage far too fast when they touched a wall or anything else. At 144 fps a helicopter was on fire in under a second (#102). The blades now do the same damage per second as on the PS2 at any frame rate.
  • Recording with Bandicam, or taking a Steam screenshot, filled the console with hundreds of lines and wrote picture files next to the game. F12 was also a developer key in the game (#89). The game now leaves F12 alone.
  • Laptops with two graphics cards: the game could start on the slow integrated one (#112). It now picks the dedicated card. New in the game's settings (F2) → Graphics: Graphics card lists the cards your PC has by name, the fastest first, with "(integrated)" after the one built into the processor. The first is the default. This couldn't be tried on a laptop with two cards here, so it's hoped to fix the problem. The change applies after a restart. On Linux the game already picked the dedicated card; the setting is there too.

Also

  • Windows: vcs.exe now has an icon of its own, a daytime version of the launcher's, so you can tell the two apart on the taskbar. Its version and description show in Explorer (#91).

Updating: on Windows, go to Settings → Updates → Update now in the launcher, close the launcher and start it again, then update the build. This update turns your disc into code again and builds the whole game once, so it takes as long as a first build: a fix in the tools that do this (#80) changed them, though it doesn't change how the game plays. Your saves aren't touched. You can also extract the zip into a new folder. On Linux, update from Settings in the same way, or download the new AppImage. On a Mac, this is the first release: install it from the disk image as above.

0.2.4
Full Changelog: https://github.com/gothamor/gta-vcs-recomp/compare/v0.2.3...v0.2.4 New: an Enhancements page in the game's settings (F2) A new page for options that change how the game looks or plays. Each one starts at the original game's behaviour, so nothing changes until you change it. Button prompts for keyboard, mouse and Xbox New in the game's settings (F2) → Enhancements: Button prompts (Original (PS2) by default). The game's help text and the pause menu's buttons can now show your keyboard keys and mouse buttons, Xbox buttons or PlayStation buttons instead of the PS2's (#61). Keyboard & mouse shows the keys you actually bound, so a key you changed shows up in the help text. In a vehicle it shows your driving keys, and in the pause menu Enter and Escape. Automatic follows what you played with last: pick up the gamepad and the prompts switch to its buttons, touch the keyboard and they switch back. A help box that's already on screen switches too. Original (PS2) shows the game's own text, as before. Busier streets and a longer draw distance New in the game's settings (F2) → Enhancements → World: Traffic density, Pedestrian density and Draw distance, each from 100% (the…
Changelog complet

Full Changelog: https://github.com/gothamor/gta-vcs-recomp/compare/v0.2.3...v0.2.4

New: an Enhancements page in the game's settings (F2)

  • A new page for options that change how the game looks or plays. Each one starts at the original game's behaviour, so nothing changes until you change it.

Button prompts for keyboard, mouse and Xbox

  • New in the game's settings (F2) → Enhancements: Button prompts (Original (PS2) by default). The game's help text and the pause menu's buttons can now show your keyboard keys and mouse buttons, Xbox buttons or PlayStation buttons instead of the PS2's (#61).
  • Keyboard & mouse shows the keys you actually bound, so a key you changed shows up in the help text. In a vehicle it shows your driving keys, and in the pause menu Enter and Escape.
  • Automatic follows what you played with last: pick up the gamepad and the prompts switch to its buttons, touch the keyboard and they switch back. A help box that's already on screen switches too.
  • Original (PS2) shows the game's own text, as before.

Busier streets and a longer draw distance

  • New in the game's settings (F2) → Enhancements → World: Traffic density, Pedestrian density and Draw distance, each from 100% (the original game, the default) up to 300%.
  • Missions that clear the streets still do, and missions always find room for the cars and people they need.
  • Pedestrians scale up well. Traffic only grows a little, because the places where cars can appear limit it more than the setting does.
  • With any of these above 100%, cars in front of you are no longer removed while you can see them. The game removes cars that are far away, and with a longer draw distance you could see them vanish.
  • Busier streets cost some CPU time, a longer draw distance costs GPU time.

Combat

  • New in the game's settings (F2) → Enhancements → Combat: Drive-by fire rate. People shooting at you from cars (the Scorpion in later chases) fired one shot every frame. That's a bug in the original game: 30 shots a second on the PS2, against the gun's 11, and at 60 or 144 fps it got two to five times worse, so a car was wrecked in a couple of bursts (#94).
  • As on the PS2 (the default) keeps them at the PS2's 30 shots a second at any frame rate. The gun's own rate makes them fire as fast as the gun does elsewhere (11 a second for the Scorpion), which makes chases much easier to survive.

Updating: on Windows, go to Settings → Updates → Update now in the launcher, close the launcher and start it again, then update the build. The build only compiles part of the game again and links it, so it's much quicker than a first build. Your saves aren't touched. You can also extract the zip into a new folder. On Linux, update from Settings in the same way, or download the new AppImage.

0.2.3
Full Changelog: https://github.com/gothamor/gta-vcs-recomp/compare/v0.2.2...v0.2.3 New: the pause menu works with the keyboard and mouse The mouse cursor can now be used to navigate the in-game menu. Escape now opens the pause menu. In the pause menu, Enter selects and Escape goes back. Escape on the row of tabs closes the menu. The gamepad still works in the menu just as before. Car reflections The stripes and lines that crawled over car paint as the camera moved are gone (#75). Above 1x Internal resolution, the reflections on cars are smoothed, so panels no longer flicker as you drive past. The PS2 has this flicker too, but at a higher resolution the rest of the picture is sharp, so the cars stood out. At 1x the reflections stay as on the PS2. There's no setting for this: the internal resolution picks it. Widescreen The pause menu's own Display → Widescreen option is gone. It was the PS2's mode for TVs that stretch the picture, so with the game's settings (F2) → Display: Aspect ratio set to 16:9, it squeezed and stretched everything a second time (#52). Use Aspect ratio instead. A save that had it on loads with it off. New in the game's settings (F2) → Display: Cutscene black…
Changelog complet

Full Changelog: https://github.com/gothamor/gta-vcs-recomp/compare/v0.2.2...v0.2.3

New: the pause menu works with the keyboard and mouse

  • The mouse cursor can now be used to navigate the in-game menu.
  • Escape now opens the pause menu.
  • In the pause menu, Enter selects and Escape goes back. Escape on the row of tabs closes the menu.
  • The gamepad still works in the menu just as before.

Car reflections

  • The stripes and lines that crawled over car paint as the camera moved are gone (#75).
  • Above 1x Internal resolution, the reflections on cars are smoothed, so panels no longer flicker as you drive past. The PS2 has this flicker too, but at a higher resolution the rest of the picture is sharp, so the cars stood out. At 1x the reflections stay as on the PS2. There's no setting for this: the internal resolution picks it.

Widescreen

  • The pause menu's own Display → Widescreen option is gone. It was the PS2's mode for TVs that stretch the picture, so with the game's settings (F2) → Display: Aspect ratio set to 16:9, it squeezed and stretched everything a second time (#52). Use Aspect ratio instead. A save that had it on loads with it off.
  • New in the game's settings (F2) → Display: Cutscene black bars (on by default, as on the PS2). On a screen wider than 4:3, turn it off to see the whole picture in cutscenes (#52). At 4:3 the bars are part of the original picture, so they always stay on there. Your choice still applies when you switch back to a wider aspect ratio.
  • At 16:9, the black mask around the sniper scope, the camera and the binoculars now reaches the screen edges. Before, the world showed in strips at the sides (#53).

Fixes

  • Above 1x Internal resolution, the first letter of the pause menu's tabs lost its left edge ("stats" showed a square S).

Updating: on Windows, go to Settings → Updates → Update now in the launcher, close the launcher and start it again, then update the build. The build only compiles part of the game again and links it, so it's much quicker than a first build. Your saves aren't touched. You can also extract the zip into a new folder. On Linux, update from Settings in the same way, or download the new AppImage.

Réagir sur le forum

Une question, un retour d’expérience ? Ouvrez la discussion sur le forum.

Réagir sur le forum