| 1 | Ports on computers can be disastrous either due to older computer systems lacking certain capabilities that consoles or arcade machines have, developers undermining the higher-end capabilities of newer ones, or simply not bothering to program the game in question to run properly on a computer. |
| 2 | |
| 3 | '''A Administrivia/{{No Recent Examples|please}} rule applies to this trope'''. Examples shouldn't be added until '''six months''' after the ported program is released, to avoid any knee-jerk reactions. However, examples may still be added even if the port was fixed during the six-month period, so long as the port had clear issues on its initial release. |
| 4 | |
| 5 | %% |
| 6 | %% No nitpicking examples. |
| 7 | %% Make sure the program really, really stands out as a disaster. |
| 8 | %% If you have any doubt, leave it out. |
| 9 | %% Just because it's "not as pretty" doesn't make it a disaster. |
| 10 | %% |
| 11 | %% (Games played on a sub-spec machine aren't candidates.) |
| 12 | %% |
| 13 | |
| 14 | [[foldercontrol]] |
| 15 | [[folder:Apple II]] |
| 16 | * ''VideoGame/BubbleBobble'' on the Apple II suffered from some rather inconsistent HitBoxDissonance. Sometimes the player can jump through walls they shouldn't be able to. Sometimes Bub can be right next to an enemy and yet the CollisionDamage won't trigger while other times just looking at an enemy will count as a hit. It only gets worse when the [[DemonicSpiders Monstas/Belugas]] start appearing. |
| 17 | [[/folder]] |
| 18 | [[folder:Commodore 64]] |
| 19 | * ''VideoGame/BionicCommando1987'' had two [=C64=] versions -- one by Capcom USA and one by Software Creations UK, both based on the arcade version. The Software Creations version is a [[ArcadePerfectPort glorious aversion]] of this trope, pretty much porting the game as well as the C64 would allow, and sporting a superb remix of the soundtrack by Tim Follin. The Capcom version is astoundingly half-assed. There's only one music track, much blockier graphics, jerkier scrolling, sluggish movement, and absolutely no swing physics. |
| 20 | * ''Cisco Heat'' features a truly abysmal framerate, ugly and non-transparent sprites for the AI cars, a near-total lack of collision detection, and generic backgrounds that look nothing like San Francisco. For proof that racing games can be more gracefully converted from sprite-scaling triple-16-bit-CPU arcade hardware to the relatively puny 8-bit [=C64=], see ''VideoGame/PowerDrift'' and ''Buggy Boy''. |
| 21 | * ''VideoGame/EnduroRacer'' has graphics that would be acceptable but for choppy and inconsistent scrolling: The player bike and the roadside stripes move at a decent rate, unlike everything else on the road. |
| 22 | * ''Hard Drivin''' wasn't designed for the hardware it was being ported to and is often noted as the worst port of the game in existence. It moves at a snail's pace in both framerate and actual driving speed and the controls often had you skidding across the road during even the slightest turns. The incredibly butchered physics engine, the very short draw distance, and the relatively inaccurate drawing scheme and monochrome nature of the 3D engine itself didn't help matters. |
| 23 | * ''VideoGame/JetSetWilly'', a port of a Platform/ZXSpectrum game, tried to stretch the levels and jumping distance to fit the C64's higher graphical resolution. The result was oddly asymmetric JumpPhysics and HundredPercentCompletion being impossible. You could still technically reach the ending sequence, except that the porting team didn't program that in. |
| 24 | * ''VideoGame/TheLegendOfKage'' suffered massive graphical and audio downgrades when it was ported from the arcade to many home consoles and computers. The [=C64=] version is largely considered the worst port out of them all. |
| 25 | * ''R-Type'' has a serious problem on tape: Even if you only survived for a minute, you still had to rewind the tape and wait five minutes for the game to reload. |
| 26 | * ''VideoGame/{{Rastan}}'' was a port of the arcade version. While they did a decent job of the music, the gameplay was destroyed: |
| 27 | ** Enemies would constantly spawn if you stood in the right spots, summoning swarms of enemies that you would likely be unable to pass without damage. |
| 28 | ** The hit detection was also broken, often causing you to die from enemies that were "attacking" with melee strikes that were out of reach. |
| 29 | ** The bosses had no visible markers if you were hitting them properly, nor was there any way to dodge their attacks reliably. |
| 30 | ** The weapons (with the exception of the golden sword) offered no change from your standard blade, so no throwing axe, no extending mace, no reason to bother with any weapon aside from that golden blade. |
| 31 | ** Last, the landscape was altered slightly, [[UnintentionallyUnwinnable causing one of the jumps in a late-game level to be impossible to clear]]. |
| 32 | * ''Renegade III The Final Chapter'', an already terrible ZX Spectrum game was made even worse by a draining health bar that you regenerate killing enemies, which is a chore with the awful collision detection. |
| 33 | * ''VideoGame/TeenageMutantNinjaTurtles1989'' was a port of the NES version. The reduction of the audio quality, the password CopyProtection, the likelihood that more than five sprites on-screen would cause severe flicker... all these might be forgivable. But the biggest problem was that they attempted to emulate the NES controls on a joystick. With only one fire button available, they decided to assign both tasks to that button. To attack, you would ''very'' briefly tap the fire button, while jumping required you to hold it down instead. This made it nearly impossible to defeat the mini-boss of the first stage (Bebop), much less completing the game, as holding the button for any length of time longer than that brief period would result in a tiny hop instead. Combined with the short-range weapons of this game... |
| 34 | * ''VideoGame/UltimaVI'' was butchered horribly on the C64. Because the C64 system was so immensely popular, Origin kept porting their Ultima games to the system even after the hardware couldn't handle them anymore. While ''Ultima V'' was a complete port that lacked only music (and had even that -- and very good, too -- on the Commodore 128 in native mode), ''Ultima VI'' was designed for the much more powerful computers then available, so a ''lot'' had to go. |
| 35 | [[/folder]] |
| 36 | |
| 37 | [[folder:ZX Spectrum]] |
| 38 | * The ZX Spectrum version of ''WesternAnimation/CountDuckula II'' is hideously ugly, especially considering its 1992 release date. The Platform/Commodore64 version is actually quite colorful, but on the Spectrum everything that moves in the main PlatformGame section is black on solid white backgrounds, even the tomato juice that can be fired into enemies' faces. While such graphical compromises were typical of the system, in this case they don't really make things move more smoothly. Instead, the already sluggish gameplay becomes a flickering nightmare, with the jack-in-the-boxes actually skipping some of their animation frames. |
| 39 | * ''VideoGame/KungFuMaster'' has backgrounds about as well detailed as those in the Commodore 64 version, but given the ZX Spectrum's graphical limitations, this comes at a horrible cost: The game moves along at a snail's pace, and kicking and punching enemies results in nasty flickering as the differently colored sprites come into contact. |
| 40 | * ''VideoGame/{{Sqij}}'' was [[http://www.gb64.com/game.php?id=7274 originally]] an undistinguished ShootEmUp written for the Commodore 64. The [[http://www.worldofspectrum.net/infoseekid.cgi?id=0004793 ZX Spectrum version]] is far, far worse. It starts by locking the Spectrum into Caps Lock and then only checking for lower-case letters; the only way to move is to "poke" the game[[note]]break into the source code - in other words, ''hack it''[[/note]] and disable the caps lock. It runs far more slowly than the Commodore version because it's mostly written in BASIC. Not only that, but [[https://www.youtube.com/watch?v=Xc3D5GEwWY8 until 2016]], there was thought to be only one room in the game; without killing both enemies, going left leads to nowhere, while going right crashes the game. Unlike most ports, this trope was {{Invoked|Trope}}--The port was made this bad out of spite as the publisher was [[TheScrooge too cheap]] to give the programmer a copy of the C64 version. Said programmer promptly gave them a port so bad that it would be rejected...[[SpringtimeForHitler only for the publisher to release it instead]]. '''''Twice'''''. |
| 41 | * ''VideoGame/{{Tiger Road}}'s'' port was so bad ''[[ExaggeratedTrope it actually led to a lawsuit]]''! Gaming magazine ''Your Sinclair'' took the game's publishers to court over it being {{Unwinnable}}[[note]] This after using an infinite lives cheat to try to get to the end, only to find out that it still wasn't possible to beat [[/note]] and '''won''', forcing the developers to make bugfixed copies of the game. |
| 42 | [[/folder]] |
| 43 | |
| 44 | [[folder:Amstrad CPC]] |
| 45 | * With varying degrees of awfulness, the scourge of "[[http://www.cpcwiki.eu/index.php/Speccy_Port Speccy ports]]" must be mentioned first. Due to certain hardware similarities, it was easy to port games from the ZX Spectrum to the CPC. But as the CPC was a less popular system (at least in the UK), most developers didn't bother touching up the graphics to use its superior capabilities. So there was a multitude of games that looked no better than those running on that far weaker machine. |
| 46 | * ''VideoGame/GhostsNGoblins'' received an ''absolutely horrible'' CPC port. As if the game wasn't hard enough already, the Amstrad version ups the ante by removing the armour. Yep, in this version of the game Arthur is a OneHitPointWonder, touching ''any'' baddie will kill you instantly. Also, the zombies respawn at a ridiculously fast and constant rate, and the version of the music is enough to induce nightmares. [[https://www.youtube.com/watch?v=GQ5QdHLOhIk Check it out here]], but make sure you swig some brain bleach afterwards. |
| 47 | * ''VideoGame/OutRun'' had its CPC port handled by Probe Software. The programmers really had no excuse, as far better driving games had already been available on the CPC for years. How bad was it? Well... |
| 48 | ** The graphics gave no sense of acceleration or speed, and mostly looked like cars and unidentifiable roadside objects blinking into existence and jerking erratically towards you. |
| 49 | ** The crash animations were gone; your car just made a quiet "barp" noise and came to a dead stop. |
| 50 | ** The ''only'' other sound effect was a generic "boop-boop-boop" noise that - given that it usually happened when cornering -- was probably supposed to be squealing tires. |
| 51 | ** The catchy in-game music was missing. The original release did at least come with a cassette tape of the arcade tunes, but anyone buying a budget/compilation re-release was presumably out of luck. |
| 52 | *** There was an expanded version for computers with 128K of memory. This had passable (though inexplicably [[SuspiciouslySimilarSong mangled]]) in-game music and improved sound effects. Crashes now sounded like maracas being thrown out of a window. |
| 53 | ** When you completed a stage, you were punished with a long, boring wait while the next stage [[LoadsAndLoadsOfLoading loaded separately from cassette or disk]]. |
| 54 | ** [[AWinnerIsYou The funny end-game sequences no longer existed. You just got a message reading "Congratulations. You have completed OutRun. Now try a different route."]] |
| 55 | ** Oh, and the game would [[GameBreakingBug crash at random moments]], which was especially frustrating if you'd bought the [[LoadsAndLoadsOfLoading cassette version]]. |
| 56 | ** To sum up, it screwed up ''every single thing'' that made the arcade version awesomely cool. And, as if to mock the purchaser even further, the manual began: |
| 57 | --->[[BlatantLies Taking nine months for numerous programmers to develop the graphic design and gameplay, OUT RUN must surely be one of the greatest, if not the greatest, home computer arcade versions of all time. The computer game reproduces as faithfully as possible all of the exciting elements of the OUT RUN arcade machine.]] |
| 58 | ** Probe (the company who did the Amstrad conversion for U.S. Gold) did the Atari ST and Commodore Amiga versions as well- both of which were also panned. |
| 59 | * ''VideoGame/PsychoSoldier'' on the Amstrad had graphics like the Platform/{{Commodore 64}} version (though slightly brighter). The gameplay, however, was unbearably slow and choppy, even with the replacement of continuous scrolling with FlipScreenScrolling. |
| 60 | * ''Count Duckula 2'' takes the already awful ZX Spectrum conversion, keeps all of that version's issues and turns it into something that makes ''VideoGame/ETTheExtraTerrestrial'' and ''VideoGame/{{Superman|64}}'' look like ''VideoGame/ChronoTrigger''. For no good reason, the Amstrad version [[CeilingBanger disallows jumping above the top of the screen]], which makes it impossible to get past the game's second screen using only your normal moves. Stuart Ashen took a look at it in the book ''Terrible Old Games You've Probably Never Heard Of''. |
| 61 | * ''Zynaps'': The Amstrad CPC conversion may be superficially good-looking, but the vertical resolution of the gameplay window is somehow ''less'' than that of the ZX Spectrum version, despite the fact the ZX Spectrum's native display resolution has 8 fewer pixels vertically. This results in less maneuvering room for the player's ship, aggravated by its having a larger collision box which makes the final stage unwinnable without cheating. |
| 62 | * The Amstrad conversion of ''Los Angeles SWAT'', an urban ''VideoGame/CommandoCapcom''-like game which originated on Platform/Atari8BitComputers, is notably incompetent even by the low-budget standard of Mastertronic (who released this game under their Entertainment USA label). The continuous upward scrolling slows gameplay to a crawl, the controls are stiff, sound is outright nonexistent, and shooting one type of person can crash the game. |
| 63 | [[/folder]] |
| 64 | |
| 65 | [[folder:MSX]] |
| 66 | * ''VideoGame/FantasyZone'' was a port of the Master System version of the game, except worse in just about every conceivable way. Garish graphics, slow, stuttery gameplay, badly ported music, and inexplicably altered bosses (the boss of world 7, which even the Master System portrayed as splitting apart and reforming while trying to crush you, was turned into a generic "move around and shoot projectiles" boss no different from any of the others) are among the major flaws. |
| 67 | * ''[[VideoGame/RushNAttack Green Beret]]'', a port of the side-scrolling action game by Konami, plays incredibly slowly and stiffly in its MSX version. Konami UK was responsible for this port, which was never released in Japan. |
| 68 | [[/folder]] |
| 69 | |
| 70 | [[folder:Atari 400/800/XL/XE]] |
| 71 | * ''[[https://www.youtube.com/watch?v=R4shac02_ks BROS]]'', a peculiar [[FollowTheLeader knockoff]] of ''VideoGame/SuperMarioBros1'' for Atari 8-bit computers, suffers from very stiff jump physics that make it hard to time jumps and dodge obstacles ([[DamnYouMuscleMemory not helping you press up on a joystick to jump and move, even if you try to do a diagonal jump]]), and Mario has no weight or momentum when moving (but a bit of mid-air direction control, oddly), which, combined with bad collision detection (apparently from loading the digitized sound effects each time a coin is grabbed, making you clearly pass through other ones when you fall) results in a platformer rife with FakeDifficulty. |
| 72 | * ''VideoGame/JetSetWilly'', despite coming out on 8-bit Atari systems three years after the Spectrum original, was actually inferior with a "worst of both worlds" approach to graphics, poor animation and bugs that meant the game couldn't be completed. Although the new music from Rob Hubbard was praised, it wasn't enough to save the game from the critical panning it received. |
| 73 | [[/folder]] |
| 74 | |
| 75 | [[folder:MS-DOS]] |
| 76 | * ''VideoGame/BadDudes'' had EGA graphics, tiny characters, and no clock speed adjustment, which means the game is unplayably fast on computers made just a few years after its release. |
| 77 | * The port of ''VideoGame/CastlevaniaI'' done by USI had garish 16-color EGA graphics, choppy controls/gameplay, and terrible one-channel PC speaker audio. Not only did it lose many helpful mechanics from the NES original (for example, the holy water did not stun enemies, losing its strategic advantage), but it introduced new problems as well: for example, the timer still counts down when you pick up the orb after defeating a boss, so [[KaizoTrap it's possible to die from running out of time during the victory fanfare]]. |
| 78 | * ''VideoGame/{{Contra}}'' had CGA graphics, PC speaker sound effects, and (the kicker) completely unresponsive controls. |
| 79 | * ''VideoGame/MegaManX1'' had a pretty spotty PC port, having lower-grade music and sounds than the SNES original, as well as removing the various Ride Armors, despite being on CD-ROM and not limited by cartridge space. It also came with a gamepad modelled after a Sega Genesis 6-Button controller for whatever reason. The ''X3'' PC port thankfully avoided these problems, not to mention had high-quality remixed music. The original did have a Windows port, but it was released only in Japan. |
| 80 | ** The gamepad (which also came with a PC port of ''Super Street Fighter II'') was especially bizarre. Only the bottom row of buttons seems to actually work with the game. Try changing the controls to use any of the top three buttons and they're totally unresponsive. The same goes for other DOS games. Basically, you got a 3-button gamepad that looks like a 6-button gamepad. |
| 81 | ** The music is especially bad because the person responsible for writing the MIDI versions apparently didn't know how to use the drum channel, resulting in all the drums being random thumping on various melodic instruments. This, in turn, causes a bizarre situation where the music actually gets worse the better your soundcard is. The real reason for this is technically caused by lazy porting and hardware limitations of the PC: The SNES' [=SPC700=] is a wavetable synthesizer, while most PC sound cards only had an [=OPL2=]-based FM synthesizer (similar to that of a Sega Genesis, but much more limited in that a Genesis also has a PSG for percussion -- which the PC doesn't have, and could also use the [=OPL2=] for digital audio -- which the PC can't). Combine that with the fact that some games are optimized for the [=AdLib=] sound card (which has an even more crippling limitation of not being able to handle percussion well) and you have an audio-centered porting disaster in the making. Yes, there were better sound cards on the market (and even wavetable synth cards) when that game came out. For some reason, though, many PC game developers and porting houses just didn't care until the mid-'90s. |
| 82 | * ''VideoGame/NinjaGaiden II'' has the same problems as ''VideoGame/BadDudes'' on PC. |
| 83 | * ''VideoGame/StreetFighterI'' got a DOS port... the less said about it, the better. The characters were rendered at an approximate height of twelve pixels, Ken was replaced with a palette swap of Ryu, only a single punch and a single kick button were available, and [[SecretAIMoves while the computer could use special moves, the player couldn't]]. |
| 84 | * ''VideoGame/TeenageMutantNinjaTurtles1989'' wasn't exactly excellent on the NES, but its PC port featured broken controls (e.g. making it nearly impossible to jump precisely), jumpy framerates, cheap enemy placement, etc., and was, in fact, {{unwinnable}} without the use of cheat codes due to a design flaw in the sewers of Area 3 (there's a jump that's too wide with too low a ceiling). Also, despite what the manual said, you'll never find a single Boomerang or Shuriken in this port. |
| 85 | * ''VideoGame/TeenageMutantNinjaTurtlesTheArcadeGame'' also suffered on PC, with only one single tune playing through the entire game, awkward controls and enemies that can cheaply wail on you when they're not supposed to. Let [[http://www.scary-crayon.com/games/tmnt12pc/ Scary-Crayon elaborate on both games]]. |
| 86 | * ''Oscar'', as with the SNES port of the game, was a port of the Commodore Amiga version (like so many games from the time). [[https://www.youtube.com/watch?v=wdkhNi3RwUY It itself had features cut]], as this opening video from the Amiga version shows us. Hear! Stereo sounds that put [=AdLib=] and [=SoundBlaster=] audio[[note]]The most common audio cards[[/note]] to shame [[note]]Granted, a later model [=SoundBlaster=] could actually do better and had the potential of sounding close to the Amiga version, but the PC version seemed to only be optimized for the [=AdLib=] music card.[[/note]]. See! Fluid smooth background animation along with an animated title logo! Despair! As you realize that the PC version had mediocre sound and a barely passable 16-bit static title logo. Also, like the SNES version, the title screen music was a rewritten horrible sounding MIDI train wreck instead of that awesome-o piece on the Amiga version. |
| 87 | * The PC version of ''VideoGame/UnchartedWatersNewHorizons'' technically got the shortest stick of all the ports of the game, with a crippled MIDI track that's only optimized for the [=AdLib=] music card, inability to support Sound Font enabled cards like the Gravis Ultrasound or [=SoundBlaster AWE32=] for instrument samples even though both cards were already released when the game came out (which could've made the game music sound just as good, if not better than, the SNES port if the game supported it and the PC has the card installed), and not only had the least amount of graphical effects of all the ports, it even failed at simple graphical effects like smooth screen scrolling. Additionally, the game used only EGA colors instead of VGA color, causing less colors to be available to the game and resulting in duller graphics. For a game that came out in late 1994 when VGA was common and EGA was already on the way out, and the common sound card was the marginally better, music-wise, OPL-3-based [=SoundBlaster 16=] (which supported stereo MIDI and enhanced percussion compared to the OPL-2-based original [=Soundblaster=] and [=AdLib=]), the game has "lazy port" written all over it. And on that topic, the Windows version released in 2017 is even more of a lazy port than the DOS one: it’s basically the PC-98 build of the game sandwiched in an emulator. It doesn’t get any lazier than this. |
| 88 | * ''VideoGame/Rayman1'', while playable, is missing many graphical effects from the console versions, has more limited palettes, removes some frames from the sprites' animations, remaps crouching to an unintuitive and awkward key combination, has a jerky framerate on the [=FMVs=], and handles the music awkwardly: whereas previously, each world tended to have multiple level [=BGMs=] that were spread across its multiple stages, the PC version had one per world that combined all tracks into one, starting the next one when the current one finishes playing. Even worse, some of those tracks had totally different moods one from another, so now you have the forest music which changes from a cheery theme to a urgent-sounding track for no reason. An enhanced version called ''Rayman Gold'' that included an ExpansionPack with extra levels was released later, but it removed the [=FMVs=], and some versions lack the music altogether. Yet another enhanced version, Rayman Forever, followed, but the [=FMVs=] were still missing, and many music tracks were removed to make space in the disc. As if that wasn't bad enough, the game's code wasn't altered to reflect this, so now some areas in the game lack BGM, while others plays the wrong track; for instance the forest levels use the cave music now! Even the GOG.com version of ''Rayman Forever'' suffers from these problems despite being officially labeled [[BlatantLies ‘the definitive version of the first Rayman game']] by the GOG.com website. Fortunately, fan patches like "Rayman Plus" restore nearly all the music and FMV sequences of the original, while adding a few extra touches like modernized screen resolutions and filtering to make the game look like the animated painting it was meant to be. |
| 89 | * The PC port of the ''Franchise/{{Robocop}}'' arcade game was a mess. The graphics were massively simplified and animations were cut: Robocop was unable to draw and sheath his gun, his melee attack was changed from a one-two punch to what looked like an attempted handshake while his pistol hovered in front of him, not moving. Enemies faced similar animation limitations. The music and voice clips from the arcade machine were entirely cut out and replaced with weak audio. Hit detection was quite glitchy, especially with the Cobra Gun: its shots would frequently fail to properly hit enemies or vanish partway across the screen. Of particular note was the enemy who held a hostage: you were supposed to wait until he pulled her back to shoot, but often your shots would somehow still kill the hostage without harming the enemy. Finally, enemy grenades were supposed to roll across the floor in a straight line but would instead home in on you if you jumped over them. Considering that they also rolled faster than you could run, they were effectively impossible to dodge. |
| 90 | * ''VideoGame/{{Karnov}}'' was released on PC in 1989, and most [=PCs=] of the time just didn't have the graphics hardware to draw a smooth side-scrolling background. If you had multiple enemies on-screen and it was scrolling, the game would slow to 1/2 to 1/3 of its normal speed unless you had a top-of-the-line computer. This ended up greatly reducing your needed reaction time, making the game trivial to complete. |
| 91 | * ''VideoGame/BubbleBobble'' had EGA graphics and [=AdLib=] music[[note]]Although setting up the game to run with [=AdLib=] music was a case of GuideDangIt since it doesn't come with a configuration program like other DOS programs of the era does. Many who've gotten the game without a manual were stuck with PC speaker sound since this was before the internet had become widely available[[/note]], which were fine for the time, but the game-breaker here is that faster [=PCs=] actually had an ''opposite'' effect on the game speed: the faster the PC, the ''slower'' the game. On a 166 [=MHz=] Pentium, the game would run at an unplayable ''one frame per second''. Comparatively, the game ran perfectly on a 12 [=MHz=] 80286. The bug appears to manifest if you use a CPU faster than a 486DX-33. A fan-made patch to fix the issue exists however. |
| 92 | * ''VideoGame/MadDogMcCree'' featured poor controls (mouse clicking was no substitute for pointing a light gun) and FMV scenes that were nothing to write home about. When ALG finally released the PC Gamegun, its accuracy was horrible. All the PC ports of other American Laser Games titles suffer from the same issues. |
| 93 | * ''VideoGame/TombRaiderI'' was originally developed for the Platform/SegaSaturn and [=PlayStation=]. When it was ported to PC, the quality of the pre-rendered cutscenes was severely decreased, the reflection effect on Golden Lara was removed, and worst of all, '''all of the game's music was removed''' except for the title screen theme and cutscene dialogue (which was stored as CD audio). Ambient sound was added to the levels as a compromise, but an entire game published without its music was ridiculous. This was made even worse when the Sold Out Software version of the game was released, some copies of which were missing the few remaining CD audio tracks. So, during cutscenes, gamers would be "treated" to the characters silently bobbing their heads at each other. This was remedied by a patch that not only restores the missing tracks, but also all the tracks from the [=PS1=] and Sega Saturn versions of the game. Justice has finally been served! |
| 94 | * ''VideoGame/TwistedMetal'' lacks transparency on PC, and increases the resolution but in turn, scales down the UI to a microscopic size. The almost unknown PC port of ''Twisted Metal 1'' did replace a single weapon to make one of the characters viable, though. |
| 95 | * ''VideoGame/{{Wipeout}}'' loses the light effects on PC, which wouldn't be so terrible if they weren't what made it such a graphically awesome title in '95. It also acquired a peculiar kind of flickering track bug. Lastly, the opening cinematic had a random probability of locking up certain [=PCs=] while playing... |
| 96 | * ''[[VideoGame/MetalGear1 Metal Gear]]'' received a DOS port, based on the NES version, which is apparently impossible to complete without cheating (the level 7 key card can't be obtained in normal gameplay). It also features ear-stabbing music, dubious AI, one-time-only item pickups, and a possible oversight that allows you to bail out of the final boss fight. |
| 97 | * Interplay's ''[[VideoGame/TheBardsTaleTrilogy The Bard's Tale Trilogy]]'' games were all originally written for the 8-bit Apple [=IIe=], and subsequently ported to various 8-bit and 16-bit platforms, in the latter case with much-improved graphics. There were a few teething issues, especially with the Amiga versions, but otherwise the porting for the first two games was pretty competent... and then came the notoriously terrible 16-bit versions of ''The Bard's Tale III''. Some of the MS-DOS port's more egregious problems: |
| 98 | ** The playing interface was extremely awkward compared to the other games. You couldn't speed up message scrolling speed, meaning you had to either wait several seconds or hit Enter after every single combat message (of which there could be dozens or hundreds). The movement keys inexplicably wouldn't let you move through doors; you needed to press a special command key, forcing you to use two hands for navigation instead of one. The status window wasn't always cleared properly after certain messages, meaning you couldn't be sure which status messages were actually current and which were not. Finally, the spell-casting interface was just painful. In previous games you could either select the spell by name from a list (which took longer but allowed you to see the available spells), or type a four-letter spell code, which required you to know the code but allowed for very quick casting. Here, however, you were given the worst of both methods: you ''always'' had to select the spell from a list... but the list only showed the four-letter spell codes! This meant you were not only required to know all of the spell codes but you ''still'' had to scroll through a long list every single time you cast a spell (and the list of cryptic spell codes meant it took longer to find the right one). |
| 99 | ** The frequency of random combat encounters was ''insanely'' high compared to the previous games (and 8-bit versions of this game), and ''any'' action could trigger one, such as turning around or even ending a previous encounter. It wasn't uncommon to move to a new dungeon square and get hit with two or three consecutive fights before your next move! Multiply that by every square of every dungeon, and the result was that many people just found the game unplayable. |
| 100 | ** On the flip side, many monsters were completely unable to use their (supposed) special attacks, or in some cases to even attack at all, making them hilariously ineffectual; this even applied to some of the major boss fights. |
| 101 | ** Many of the items in the game simply didn't work at all. |
| 102 | ** Bard songs only lasted a single combat round and weren't cumulative – thus severely breaking one of the game's signature features. |
| 103 | ** Anti-magic zones would extinguish light (which they shouldn't), but for some reason didn't prevent spell-casting (as they should); various other special zones didn't behave as they were supposed to either. |
| 104 | ** The entire game would crash if too many characters were created in the Refugee Camp. |
| 105 | ** The Amiga version (the only other 16-bit port) reportedly also shared many of these bugs. When the trilogy was re-released years later, emulated versions of the 16-bit ports were used for the first two games, but the original 8-bit Apple [=IIe=] version was used for ''The Bard's Tale III'', despite its inferior graphics; evidently the publishers concluded that the 16-bit version was broken beyond redemption. |
| 106 | * Kyodai's obscure 1989 DOS port of the first ''[[VideoGame/YsIAncientYsVanishedOmen Ys]]'' game, retitled ''Ancient Land of Ys'', is hands down its worst conversion, with muddy graphics that only supported CGA (when EGA and VGA was already in the market), an unbearably jerky framerate on par with the NES version of ''VideoGame/{{Hydlide}}'', and no soundcard support, restricting the sound and the previously iconic music to the ear-grating PC speaker. |
| 107 | * The PC port of VideoGame/TestDrive 2, while otherwise somewhat solid, had two glaring issues: firstly, it only supported EGA graphics when VGA was already a thing. Secondly, it had no sound card support and only utilized the PC speaker for music and sound effects when the Game Blaster, [=AdLib=] and original [=SoundBlaster=] were already in the market, which made it look and sound inferior compared to even the Atari ST version (which was pushing tracker music through the modest PSG). |
| 108 | [[/folder]] |
| 109 | |
| 110 | [[folder:Amiga]] |
| 111 | * ''VideoGame/SmashTV'' has badly redrawn graphics, nearly all of the music cut out of the game, and horribly muffled sound effects. |
| 112 | * ''VideoGame/TestDrive'' didn't do justice to the Amiga's graphical capabilities, had the engines sounding more like 8-bit jets than cars, and there are few other sound effects to speak of. By comparison, the technologically less advanced Commodore 64 managed to pull it off a lot better. As with ''Defender of the Crown'', the inferiority of the Amiga version is likely attributable to inexperience and [[ChristmasRushed ludicrous deadlines]]. |
| 113 | * ''[[VideoGame/{{Outrun}} Turbo Outrun]]'' was a turkey of epic proportions, with abysmal frame rates and utterly failing to give any sense of movement or speed - the road and scenery seemed to move around your car rather than vice-versa. The ineptitude of the conversion was emphasised both by the fact that the concurrent and similar ''Lotus'' series of racing games on the same platform was light years ahead in quality and that reviewers who'd played the Platform/Commodore64 version as well ranked it ''higher'' despite it being a full generation behind in power and graphical ability. The Atari ST version suffered from the same issues. |
| 114 | * Creator/{{Sierra}} was a serial offender in its heyday. The company's Amiga ports of its classic games were notorious for failing to take advantage of the machine's graphics and sound capabilities. To wit, A lot of the games were straight ports of the PC version with the music and sound effects ported from the ''PC Speaker'' code base instead of the marginally better PC Jr. PSG, Game Blaster or even the [=AdLib=] code base, causing them to completely misrepresent the true audio capability of an Amiga. Although some games would later receive updates to have better audio on said port (for example, Space Quest III, which started out sounding like the PC Speaker version but later received an upgrade to improve the music to use 4 channel polyphony with MT-32 samples), it would have been too late and the reputation of the port would have already been tarnished. Additionally, they used the EGA graphics code, which means the EGA palette limitation was retained, instead of seeing a higher resolution palette befitting the Amiga's graphical chipset. This is in contrast to their Platform/AppleII GS and Platform/AppleMacintosh ports, which are often ''rewrites'' that can take advantage of the system's enhanced capabilities instead. Lastly, a lot of the ports are written with NTSC Amigas in mind and do not offer a PAL mode, meaning these games actually run ''slower'' on PAL Amigas. While the Atari ST version shared the weaknesses of the graphics and integrated sound, it had the saving grace of being able to spit out better quality music through the ST's integrated MIDI out ports, meaning if you have a Roland MT-32 hooked up, the music is just as good as the PC version with the same sound device. The Amiga, lacking integrated MIDI ports, does not offer this luxury. Additionally, PAL Atari [=STs=] do not exhibit any slowdown playing Sierra games that PAL Amigas do[[note]]Although NTSC titles do stutter when the machine is busy loading scenes from disk on PAL machines, this can be fixed by installing the game to a hard drive[[/note]]. |
| 115 | [[/folder]] |
| 116 | |
| 117 | [[folder:Microsoft Windows]] |
| 118 | * ''[[VideoGame/{{Suguri}} Acceleration of SUGURI X-Edition HD]]'' by Rockin' Android, which is a port of the [=PlayStation=] 3 version that was, in turn, a port of the original PC version and its expansion pack, was rushed to Indie Royale followed by Steam and the numerous bugs at launch shows. The game had issues with crashing frequently, online multiplayer that barely worked, compatibility problems with Windows 8/8.1, screen flickering problems in fullscreen mode, broken Steam Achievements, and the game still used the outdated [=DirectInput=] API for controllers which was a problem for modern [=XInput=] controllers. Rockin' Android later released a patch in 2014, but only for the Steam release (DRM-free releases did not get any patches whatsoever), which fixed a few of these issues, however, it introduced [[LoadsAndLoadsOfLoading longer and frequent loading times]] between matches instead, which wasn't present in the DRM-free release of the HD version found in select Indie Royale bundles or even the original 2006 version of the game, and abandoned supporting the game soon after. When you compare it to its sequel ''[[VideoGame/{{Sora}} acceleration of SUGURI 2]]'' and how that was handled (which was done by a different publisher who not only gave it several quality-of-life features, but also keeps supporting it to this day), you know there's no excuse. |
| 119 | * ''VideoGame/AssassinsCreedII'' has extremely clunky copy protection; users who legitimately bought the game and then used the crack to get rid of it anyway consistently report that the game runs ''exponentially'' better, going from a chugging slideshow at low or medium detail settings to completely smooth while maxed out and running at 1080p. Those who simply pirated the game get a product that is not only less annoying but actually ''works better'' than those who paid for it. The online-only DRM was later removed from the game, but it still suffered from poor mouse control due to aggressive acceleration, and controller support for the newer [=XInput=] gamepads was shoddy and required a third-party fix to function correctly. |
| 120 | * ''VideoGame/AssassinsCreedUnity'' has become notorious for its poor optimization, alarmingly high system requirements ([=GeForce=] GTX 680 is the minimum video card requirement) which will bring high-end machines to their knees, and many game-breaking bugs. The port also suffers from a bad LOD system, and the profile for machines running SLI is broken. Add this, to stuttering even on machines with the recommended requirements, and Ubisoft still hasn't fixed these issues even after updates. While the console version doesn't run well by any stretch, the PC port is unplayable. |
| 121 | * In a wider sense, the PC version of every major ''Franchise/AssassinsCreed'' title since ''[[VideoGame/AssassinsCreedIVBlackFlag Black Flag]]'' onward suffers from an issue that makes the game incapable of progressing past the opening splash screen if not installed to the C: drive, which in the following years has caused complaints from users with custom PC builds that use smaller, more expensive [=SSDs=] as their native OS drives for a speed boost. Closer examination shows that the cause of this apparently [[http://archive.is/aIhld lies with the sound files]], and can be overcome by hosting only them on C: and creating symbolic links to them in an external install location. However, Ubisoft support seems to be completely unaware or uncaring about this, since every time the issue is brought up they seem to be in the dark about it, and useful advice on the matter can only be obtained from other users. |
| 122 | * ''VideoGame/AtelierSophieTheAlchemistOfTheMysteriousBook'' on PC suffers from a single glaring flaw: complete abhorrence for keyboard support (which is the way that most PC players play video games). You can use any controller you like, but the keyboard setup is unintuitive, [[SomeDexterityRequired takes three hands to use properly]], and worse, can't be remapped in any way. |
| 123 | * ''VideoGame/AzureStrikerGunvolt''[='=]s PC port, despite initially giving players a version of the game with a faithful localization and the fully-voiced dialogue intact up until the ''[[PolishedPort Striker Pack]]'' for Switch and [=PlayStation=] 4 and the [=3DS=] version eventually had its English localization revised ([[NoExportForYou for the North American version anyway]]), the PC version is a mediocre port that [[https://steamcommunity.com/sharedfiles/filedetails/?id=828598756 looked]] as though Inti Creates was emulating the [=3DS=] version on PC. The PC version also lacked remappable keys, assumes players are using Nintendo-styled controllers despite being ported to a platform that commonly uses Xbox 360 (or similar) controllers with the reversed A/B buttons for menus, was locked to 30 FPS like in the [=3DS=] version, enabling its V-sync causing performance issues, its broken Steam DRM prevents the game from even booting if Steam is in Offline Mode, and sometimes the game doesn't close properly and its process is left running even after exiting the game. A patch was later released on May 11, 2018 that makes the PC version somewhat comparable to the Switch and [=PlayStation=] 4 ports and added partially rebindable keys. However, they didn't bother to update the menu control scheme for Xbox 360 controllers, much less update the low-res art assets still present in the PC version or fix the broken Steam DRM. The Skill Activation keys are also inconveniently hard-coded to [=F1=] through [=F4=] and can't be remapped. Its latest patch also inexplicably introduced another problem that renders the Speedrun and Other Modes inaccessible due to a "Memory Shortage Error" regardless how much RAM the user's PC has, and despite supporting multiple languages, some languages are still using the cut-down version of the game by 8-4 rather than using the revised in-house localization. |
| 124 | * ''VideoGame/BatmanArkhamCity'' had its PC versions delayed for well over an ''entire month'', and had little to show for it upon release. It had ridiculously unoptimized graphical settings, forces [=Direct=] 11 despite its infamous bugginess, contains crippling DRM and sometimes has problems with connecting to Games for Windows Live for absolutely no reason. The latter two were finally removed entirely in a 2013 patch that coincided with their removal from its predecessor ''Arkham Asylum''. Also, there's an issue with the Game Of The Year edition that prevents the disc from running ''at all'', citing an [=AppID=] issue. It's unclear whether this was a humongous error of judgment or a backhanded way of driving people to Steam. |
| 125 | * ''VideoGame/BatmanArkhamKnight'': The PC port had even more problems than the aforementioned ''Arkham City'' at launch, with widely reported optimization problems, frame rates capped at 30 and regularly dipping as low as 10, and missing graphics options compared to the console versions. Many angered customers left negative reviews on Steam and Metacritic, and not only was Steam's then-new refund option for digitally purchased games put through its paces, but services like Green Man Gaming that previously had no refund policy made a special exception to allow players to return ''Arkham Knight''. The response was so bad that WB Games [[https://community.wbgames.com/t5/Support-for-PC/June-24-Update-on-PC-Version-of-Arkham-Knight/m-p/575332 suspended the game's sale]] ''less than 2 days after release'' to buy themselves time to fix the game. Subsequent patches added some missing graphical features and reportedly ameliorated the problems for some, made them worse for others, and had no appreciable effect for the majority. When rereleased on October 28, 2015, [[http://arstechnica.com/gaming/2015/11/warner-issues-refunds-for-broken-batman-arkham-knight-again/ the game still had technical issues for many players]]. WB Games offered no-questions-asked refunds to anyone who purchased the game or its season pass through the end of 2015. Reportedly the sorry state of the game was [[http://www.gamespot.com/articles/batman-arkham-knight-pc-problems-were-known-for-mo/1100-6428577/ known well in advance]] of its initial PC release and the suspended sale period did almost nothing to help it. ''Arkham Knight'' also used [=nVidia=]'s proprietary Gameworks technology, making the game run slowly or not at all on AMD cards. The game was supposedly fixed in 2016, but several minor and major issues are still there. |
| 126 | * ''Videogame/BattlestationsPacific'' uses GFWL in an otherwise pretty good port and unlike most other games in Steam, it wasn't patched out as of 2019. While being dormant might be a non-issue, installing it in Windows 10 might just didn't work, except the GFWL is bypassed in a way that the client isn't actually used. |
| 127 | * ''VideoGame/BillyHatcherAndTheGiantEgg'''s PC port, released in 2006 (three years after its original Platform/NintendoGameCube release), suffers from poor optimization, which causes framerate issues on many video cards, severe screen-tearing problems (due to having no V-Sync) and very limited controller support. The sound mixing is also inferior to the [=GameCube=] version of the game due to using different audio code. The launcher's settings are too basic, the only graphics settings to change the framerate to 30 FPS or 60 FPS, resolution and a clipping option which doesn't seem to do anything. Most controllers are incompatible with the game, as it doesn't support analog triggers and many analog pads. For example, the Xbox 360 controller's analog triggers will not work. There are also missing visual effects from the original release. For instance, the fog that obscures the player's view in a few of the later levels is absent which makes the level too easy. |
| 128 | * ''VideoGame/BioShock2'' is another game that was plagued with both Games for Windows LIVE and [=SecuROM=] (2K claimed the latter was only programmed to prevent preordered copies from being playable before the official release, but that doesn't mean it won't ever have technical issues), but it was a badly coded port to begin with. It eats up 100% of the available CPU clock cycles at all times, ''even when it's idling in the menu screen'', and there's flagrant texture pop-in if you're using a GPU without a lot of video memory -- both problems that the first game, which runs on the same engine, didn't have. Apparently, the whole thing was ported from scratch by a different team than the first game. Also, some of the default key bindings are different from the first game for no discernable reason (Use is F instead of E, despite E not being used for anything, for example), attempting to rebind any keys used in the hacking minigame (like ''F'') caused the minigame to not work at all, and the game didn't even have controller support despite being a port of a console game! Those issues, at least, were finally ironed out in a 2013 patch that also removed the DRM and switched the multiplayer system to Steam, as well as unlocking all the multiplayer DLC free of charge ''and'' giving existing players ''Minerva's Den'' as well since they had no way of knowing who had already bought it and who hadn't. Oh, and also the vending machines didn't talk and still don't, but a lot of users consider that one a {{good|BadBug}} thing. |
| 129 | ** All of this was eventually not so much fixed as abandoned via the release of remasters of the first two games in 2016. The remaster of ''[=BioShock=] 2'' irons out all of the above glitches (even the vending machine voices!) and includes all the DLC (though multiplayer isn't included, it was long dead by the time of the remaster's release). Ironically, the remaster of the first game was a PortingDisaster in its own right, with the 2007 original generally considered the superior version. |
| 130 | * The Steam version of ''VideoGame/BlazBlueCalamityTrigger'' lacks an online multiplayer. It also suffers from numerous bugs, like music not playing in some parts of the story mode, characters disappearing after alt-tabbing, and randomly running at 30 FPS, all of this despite being released several years after its fully functional console versions. Fortunately, ports of later games are equal to their console counterparts. |
| 131 | * On its initial launch, the Platform/{{Steam}} version of ''[[VideoGame/BloonsTowerDefense Bloons Tower Defense 6]]'' was a clear example of hastily rushed port. It hosted a multitude of bugs, ranging from [[GoodBadBugs good]] (such as the multiple heroes glitch, as the developers forgot to accommodate that the shift key, which lets you place down multiple towers at the same time, also done the same to heroes and you can only normally place one of them down per game) to [[GameBreakingBug bad]] (like the game failing to load beyond the title screen unless you delete the game folder inside your Steam user data folder) and design issues, such as how the UI for the game isn't designed in mind for [=PCs=], has a [[{{Microtransactions}} micro-transaction]] for double cash mode that costs ''$18''[[note]](which, to be fair, is the same as in the mobile version, but that doesn't excuse its insanely high price that's almost twice the price of it)[[/note]], among other complaints. Thankfully, the developers have patched them out and it's much on par with its mobile version. |
| 132 | * ''[[VideoGame/{{Caladrius}} Caladrius Blaze]]'' got an incredibly lazy PC port thanks to H2 Interactive. The PC version is locked to 720p for no good reason while the [=PlayStation=] 4 supports up to 1080p, has absolutely no graphics setting other than toggling Windowed or Fullscreen Mode, barebones keyboard support with strict preset keys that can be used, and for Steam users, the game requires a constant internet connection to even play the game, nor can it be launched in Steam's Offline Mode due to the implementation of its online leaderboards (the GOG.com however has no such issue and can be played offline, although its leaderboards are different from Steam's). |
| 133 | * ''VideoGame/CallOfDutyBlackOps'' is infamous for the disastrous launch of its PC version. On release, a line in the servers' config file that hadn't been set properly caused ''every'' online game played to lag terribly. This was fixed after a few days, but the game still had some obvious problems with its renderer (not present in any of the previous current-gen titles that use the same engine) that cause ridiculous framerate drop when shadows are enabled and when sounds are played for the first time. Still, the game was much more playable, especially if you were willing to live without shadows. A few days after that patch, a second patch was released that was supposed to improve server browser functionality and fix several bugs with the browser. The patch did this... but also reintroduced all the problems the first patch fixed. |
| 134 | ** The 2013 installment ''VideoGame/CallOfDutyGhosts'' has suffered similar problems. Framerate issues, narrow field of view (a fan-made tool was made, but was promptly taken down by Activision), and using way too much CPU power than it should (its minimum requirement lists 6 gigs of RAM when fans have found out the game itself would probably only need 2 or 3 for itself at minimum). |
| 135 | ** ''VideoGame/CallOfDutyBlackOpsIII'' also has serious issues: even on high-end machines, the framerate can dip into the twenties or teens for no apparent reason, and the switch between 30 FPS in cutscenes and 60 FPS in gameplay is downright jarring. |
| 136 | * ''WesternAnimation/Cars2: The Video Game'' is this on the PC. While the models of the characters were okay, the scenery was terribly downgraded so that some of the features were missing or just simplified. |
| 137 | ** Similarly, the PC port of the first ''VideoGame/{{Cars}}'' tie-in game is based on the last-gen Playstation 2/Gamecube versions of the game as opposed to the much nicer looking Xbox 360 port. Worse, the Steam release is prone to save file corruption and reportedly won't run on certain graphics cards without convoluted workarounds. |
| 138 | * ''VideoGame/ChaosLegion''[='=]s PC port suffered from botched copy protection that rendered the game virtually unplayable to most players after the initial installation (unless they cracked their own game), which caused Capcom to recall the game and reprint it with the DRM issues patched out. Even after that fiasco, players that were able to play the game beyond the copy protection ran into problems the original [=PlayStation=] 2 release didn't have, such as frequent crashes between loading screens, low-quality DepthOfField effects that make the game look pixelated from a distance, limited graphics settings, performance issues, and corrupted or mismatched textures when played on Windows 7 or later. |
| 139 | * ''VideoGame/CommandAndConquer the First Decade'' is a lot of nasty. ''[[VideoGame/CommandAndConquerTiberianSun Tiberian Sun]]'' often ''fails to install outright'', and ''[[VideoGame/CommandAndConquerRedAlert2 Red Alert 2/Yuri's Revenge]]'' [[ItOnlyWorksOnce only launch one time]]. The whole disc often fails to install more than once, and no, this isn't because of DRM. The only way around these issues? Copypasting the disc onto an alternate file layout. After this little bit of Tech-Heresy, all games are Version 1.0, meaning all of them chug like steam engines on a bar crawl. |
| 140 | * ''[[VideoGame/FantasticNightDreamsCotton Cotton Reboot!]]''[='=]s PC port on Steam originally suffered from the same inconvenient issues of the developer's other PC games (''VideoGame/TroubleWitches ORIGIN'' and ''Hurricane of the Varstray'') with no PC-related options, is locked to 720p while the console versions of ''Cotton Reboot!'' can run at 1080p, uses a pre-defined keyboard layout that can barely be changed, [=PlayStation=] prompts with a few Switch ones used all over the place when most PC games support Xbox controllers, and there's no way to quit the software without using Alt+F4 or closing the game in windowed mode. The kicker? The PC version costs $45 whereas the Switch and [=PlayStation=] 4 versions costs $40 ''digitally''. A March 2022 update at least brought it to parity with the console versions by adding 1080p support, proper controller support and an exit button, although it's still more expensive than the console releases. |
| 141 | * ''VideoGame/DarkSector'' was actually a fan-made PC port that got adopted by the publisher and sold for cash on Steam. It definitely shows. The graphics are usually off if you run the game in widescreen or on anything other than the default resolution, and if you use custom key bindings the quick-time prompts still give you the WASD prompts. |
| 142 | * The ''VideoGame/DarkSouls'' trilogy has a storied history of this: |
| 143 | ** ''VideoGame/DarkSoulsI'' had its long-anticipated ''Prepare to Die Edition'' PC port developed by Creator/FromSoftware. The problem: they had never done so in-house before (the earlier port of ''VideoGame/NinjaBlade'' had been farmed out to a third-party porting house), and they openly admitted to having significant issues with the port about a month before release. In short, the release was basically the Xbox 360 version with an expansion. The frame rate is locked tightly at 30 FPS, and even then slight framerate lag is notable; the provided keyboard controls are particularly atrocious, designed to have two hands on the keys at all times--having an Xbox 360 pad is a '''must'''; mouse control (what there is of it) is skittish, the buttons can't be rebound, the sensitivity can't be adjusted, and the camera vertical range is shorter than if you were using a controller's thumbstick. |
| 144 | *** The resolution is locked to 1024×720, same as the console versions--even though the game has higher resolution support, running it at 720p or higher simply upscales the image to fit; multiplayer is a crapshoot, with summons failing for unexplained reasons and summon markers popping in and out of the world at random; and despite being sold on Steam from day one, the game relied on the controversial Games For Windows Live DRM for achievements and multiplayer sessions. This reliance on Games for Windows Live has also proven to lead to problematic installations, leaving some users unable to even launch the game, let alone experience any gameplay. This could be considered a game-breaking bug but the game doesn't start to begin with for some people. However, in December 2014, an update came out for the Steam version that ports the multiplayer components and achievements to Steamworks, thankfully removing the reliance on Games for Windows Live for multiplayer sessions and getting rid of any quirks related to it. Owners of the retail and GFWL digital editions were also allowed to redeem their original serial codes on Steam. It should also be noted someone made a ''fantastic'' fanpatch that fixed almost all of the above issues, but it's a bitter pill to swallow that a fan had to fix the port for the developers. |
| 145 | *** Fortunately, nearly all of these issues were fixed from the outset with the port of ''Dark Souls: Remastered '', which is overall a PolishedPort. |
| 146 | ** ''VideoGame/DarkSoulsII'' has a much more improved port compared to the first game, but it too had its own host of issues at launch, including poor mouse controls. Also, because it's running at 60 FPS, it has a ''horrible'' PC-exclusive bug that caused weapon degradation speed to double, as it was tied to the frame rate for some illogical reason. A year later the game was remastered for the next gen consoles, and because these versions also ran at 60 FPS and presented the same bug, Creator/FromSoftware was finally prompted to patch the game on all platforms. |
| 147 | ** The PC port of ''VideoGame/DarkSoulsIII'' on launch also had significant technical issues, particularly the infamous "bonfire crash", and compatibility issues leading to poor performance. It didn't help that the game's anti-cheat system was utterly broken, sometimes banning players from online play simply for ''switching between online and offline mode''. Now, on the other hand, the port is actually pretty good, as all the technical problems were patched out by the start of 2017, and is a marked improvement over the first two games. |
| 148 | * ''VideoGame/DCUniverseOnline'' |
| 149 | ** The game has one egregious issue on Windows: If you're planning to play the game with a gamepad, you'd better have an Xbox 360 controller. Have anything else (like one of those cheap USB [=DualShock=] 2-controller look-alikes or even a [=PlayStation=] 2-to-USB controller adapter?) You may find that the camera is stuck looking up, because the right nub is handled differently from Xbox 360 controllers on these controllers. No thanks to the fact that the game does not provide a way to remap controller buttons and axes. |
| 150 | ** You can still work around that problem with a 360 controller emulator, although since this is an online game it might be seen as a cheating tool. But then you consider the fact that the only other platform the game came out for is the [=PlayStation=] 3, whose controller is similar to the [=DualShock=] 2 save for the L2 and R2 buttons being [[PressureSensitiveInterface pressure-sensitive triggers]]. Also, if they see gamepads as a cheating tool, wouldn't it be a better idea to not allow gamepads at all (and while at it, force the players of the [=PS3=] version of the game to use a USB mouse and keyboard too?) |
| 151 | ** A later version of the game attempted to fix this issue. The good news is, these controllers are treated like the [=DualShock=] controllers they are and the screen no longer sticks to the floor looking up anymore. The bad news is, it has a minor glitch that fails to read the right nub correctly-- the camera now pans in a spiral motion due to being still reliant on [=XInput=] and thus not able to see the axis properly. This is fine if your character doesn't have the power of flight. Otherwise, you'll find yourself returning to the mouse and keyboard pretty often. |
| 152 | ** And this was also the case with numerous other games, too, as they now make use of the [=XInput=] [[MediaNotes/ApplicationProgrammingInterface API]]. Especially the ones released alongside the Xbox 360 versions. |
| 153 | * ''VideoGame/DeadRising2'' requires Games for Windows Live on PC. Most Games for Windows Live titles run fine and players who don't care about GFWL see it as a minor annoyance. ''Dead Rising 2'', however, often has problems talking to the GFWL wrapper; it may not even realize it's there, in which case, the most you can do is play the game ''without saves''. Also, if your computer just met the minimum requirements to play the game, you'd be lucky to get 10-15 FPS. Anyone who was playing the game with more... questionable methods reported that they had no such slowdowns on the same hardware. GFWL strikes again. But hey, at least you got achievements! |
| 154 | ** Note that GFWL on ''Dead Rising 2'' and ''Off the Record'' has since been disabled in favor of [[Platform/{{Steam}} Steamworks]]. However, you still cannot change (or even look at) key bindings (except when combination attack cards and tutorials were shown). |
| 155 | ** Even after the Steamworks change, there are still glaring issues, especially if one tries to play online. Dead Rising 2 is extremely picky and will crash on start-up every time unless the system's sound settings are just right. Even if that's set up the way it wants it, Terror is Reality will still consistently crash during the final round, rendering it pointless as best. Off the Record somehow manages to be even worse, though. The Proto Man costume that's supposed to be obtained for achieving a Bronze Medal on all single-player challenges isn't, as due to a bug it never unlocks and co-op is incredibly unstable, as loading a save is pretty much guaranteed to disconnect the client provided they don't crash as soon as they join in anyway, and with no justification whatsoever, the game will blatantly ignore what you ask it to do, as trying to match into story mode may get you thrown into Sandbox Mode anyway, and vice versa. At least playing offline works. |
| 156 | * The original ''VideoGame/DeadSpace1'' is notrious for having several game-breaking problems which are caused by having an uncapped framerate. These include extremely slow aiming, randomly getting killed in the zero gravity sections, and [[UnintentionallyUnwinnable broken scripted sequences that completely prevent you from progressing]]. The PC port of ''VideoGame/DeadSpace2'' is far more functional, but it has an infamous bug that prevents you from unlocking the [[InfinityPlusOneSword Handcannon]] for beating hardcore mode unless you ''do it in a single sitting''. |
| 157 | * Sadly the case for ''VideoGame/DeadlyPremonition'', which was a particularly lazy port in the first place (lacking graphic options and even controller support for a game originally designed with controllers in mind) with game crashes aplenty and numerous issues with various graphic cards cropping up. It was so bad that the lead designer, Hidetaka “[=Swery65=]" Suehiro, offered a BackhandedApology via Twitter. Thankfully, however, the gaming community has come up with fixes and mods to make the game playable as it seems an official patch is unlikely at this point. |
| 158 | * The first PC port of ''VideoGame/DeathSmiles'' by Degica Games is often regarded as the worst port of Cave's main trio on Steam. Despite restoring the slowdown that Aksys removed from the Xbox 360 version, the entirety of Mega Black Label has no slowdown whatsoever, making half of the game not only broken, but also impossible to beat without dying and continuing over and over. Despite Cave and Degica addressing some other issues from the port, the lack of slowdown in Mega Black Label was never addressed. |
| 159 | * The developers of the mobile game ''VideoGame/DeusExTheFall'' showed only a minimal amount of effort with the PC port. Even before starting the game, one will notice that the awkwardly-placed keys are unreliable and that the graphics cannot be adjusted save for anti-aliasing and resolution. In the game itself, almost every playable level is filled with low-res textures, constant screen-tearing, and LoadsAndLoadsOfLoading. The player can also forget about smooth gameplay, with horrible FOV issues (such as firing a gun causing the camera to ''zoom in and out''), bizarre and inconsistent mouse sensitivity, and frequent AI glitches and issues with guards and other [=NPCs=]. Moreover, when engaged in a conversation, lip-syncing is weak and some [=NPCs=] don't move their mouths at all. [[Creator/TheCynicalBrit TotalBiscuit]] [[https://www.youtube.com/watch?v=rEpfTfgzWp0&list=UUy1Ms_5qBTawC-k7PVjHXKQ takes a look at the port.]] After several months with no word, the devs did release a patch to allow rebindable keys. |
| 160 | * The 2006 Windows port of ''VideoGame/DevilMayCry3DantesAwakening'' from console to PC, thanks to Creator/{{Capcom}} outsourcing the porting job to [=SourceNext=] (one of the notable problems is missing crucial cutscenes). Thankfully, Capcom learned their lesson after ''Devil May Cry 3'' and ''VideoGame/ResidentEvil4'', resulting in the PolishedPort of ''VideoGame/DevilMayCry4'' as they ported that game in-house. |
| 161 | * ''VideoGame/DisneyInfinity 3.0'' (pre-Gold Edition): Other than the game being released on Steam as an AllegedlyFreeGame with almost $900 worth of DLC at launch (which was rectified immediately after and the total DLC cost was reduced to a more manageable $130), it was also ''not'' kind to lower-end [=PCs=] despite its simplistic graphics. Unlike most games at the time, the latter problem couldn't be remedied by lowering the texture settings or the resolution (which is locked at 16:9), because the game didn't even let you do that. |
| 162 | * The Windows port of ''[[VideoGame/DonPachi DoDonPachi]] [=DaiFukkatsu=]'' is missing all of the intentional slowdowns from the Arrange A mode that is present in the Xbox 360 version, significantly [[FakeDifficulty inflating the mode's difficulty]]. The Black Label ArrangeMode was hit with the opposite problem (''too much'' slowdown, enough to be a detriment to most players), but was patched, while Arrange A still forces players to brave the BulletHell patterns with no speed reduction whatsoever. |
| 163 | * In April of 2023, ''VideoGame/DragonBallLegends'' was chosen as one of the many mobile games playable on PC through Google's Play Games desktop app. The main problem that kills this version is that the game is very much still designed with touchscreen in mind, with no way to properly bind any action to controller or keyboard commands without using some roundabout third-party app method. Combine the lack of true widescreen support with very awkward forced mouse controls and you have a port of a fighting game with all of its issues exasperated to no end. |
| 164 | * ''VideoGame/DungeonsAndDragonsChroniclesOfMystara'' was re-released on Steam, and they did try to make DropInDropOutMultiplayer a selling point, but the problems with the port were so great that almost nobody wants to mess with it. For one thing, there's no support for local multiplayer and no support for gamepads, but more damningly, the majority of the keybindings are set. You can't change the movement buttons from the arrow keys to WASD, and even if you change the action buttons, you can't change the buttons you use to confirm or cancel on the main menu. Furthermore, the graphics are worse than the graphics from pre-existing arcade emulators, making many wonder why they even bothered with porting it. |
| 165 | * The PC version of ''VideoGame/EldenRing'' is the least stable version of the game. Aside from not supporting PC exclusive features like ultra-widescreen or framerates above 60 FPS, many players had various problems like heavy frame drops, issues playing with a keyboard and mouse, and various graphical glitches not found in console versions. The day one patch addressed some of the problems, but introduced new ones as well. Unfortunately, due to the addition of Easy Anti-Cheat, using mods to fix these issues will prevent you from using any online functionality. |
| 166 | * ''VideoGame/FinalFantasyVII'' had ''several'' issues when the PC port came out in 1998. The music was all converted into MIDI format, making the instruments sound worse than the SNES version of ''VideoGame/FinalFantasyVI'' (the most jarring result is that "One-Winged Angel" doesn't have lyrics unless your sound card is from a particular wavetable sound card family -- namely, either the [=SoundBlaster AWE32 or AWE64=] line. People who don’t own a wavetable card, or even if they owned wavetable cards from other companies, were pretty much screwed out of the experience). The pre-rendered cutscenes -- which didn't always sync properly with the in-game sprites in sequences where they overlapped -- needed a special Windows 95 codec to run, and yet this codec isn't on the install disc. The game itself had rather high system requirements for something meant for a Windows 95 machine (Windows 98 would be another matter, except the game wasn't made for it). It only gets worse from there: On more modern systems, there are game-code/OS compatibility issues, crashes (before/after [=FMVs=], on quitting...), speed and graphic artifact/rendering issues, and basically the whole thing is a mess unless you use a handful of fan-created mods. These issues normally wouldn't be held against a game of its age, except that it was being sold in this format as part of the EA Classics line even as late as 2010.\ |
| 167 | Much of this falls at the blame of being ScrewedByTheNetwork: when Square initially contracted to have the port done, they demanded it be a straight port with nothing added or enhanced. This already meant by default the game wouldn't look or play any better than it originally did, so the game would still be stuck with its original low-res backgrounds, and rather than being able to use the original master FMV recordings, they had to settle for converting the PSX files to a new format for the PC, putting even greater degradation on already modest quality. The use of a third party FMV renderer instead of [=DirectX=] had wildly varied results, from glitched playback to outright ''[[GameBreakingBug crashing the system]]'' (which the only solution Eidos offered was a save file past the crash point, but say goodbye to hours of progress if it came down to that). Furthermore, the game in its originally released state ''wasn't compatible with AMD or Cyrix processors'', something Eidos refused to service for quite some time, and due to PC graphics architecture not being built to handle the multiple tricks and tactics the PSX used (such as multiple color depths employed at once), the game dragged down many of even the highest end users at the time too. It's quite telling that emulating the game in 1998 might have actually been a better experience than playing this port. |
| 168 | ** The 2012 digital re-release also has its share of issues. Occasionally, the game doesn't detect saves, several users had trouble with activating the game, and the music is ''still MIDI-quality'', despite being released fourteen years later and space not being an issue. Fortunately, the latter is relatively easy to fix, but it makes one wonder why Square Enix didn't do ''anything'' about it. |
| 169 | ** It also had rare but noticeable problems with certain textures and models. The textures used for the ''Break'' spell may sometimes glitch out and the models for JENOVA Synthesis and Bizarro Sephiroth may glitch out to the point where you have two models overlapping with each other and when you kill them, only one of the models goes through its proper death animations while the "extra" model is left alone. |
| 170 | ** The game was also released a year later in July 2013 on Steam, except it's the ''same version'' as Square Enix's 2012 re-release, which includes the low-quality MIDI music and other glitches. It wasn't until October 2013 that the original soundtrack was finally added in a patch. |
| 171 | * ''VideoGame/FinalFantasyVIII'' ironed out most of the problems with the PC port of the previous game, but there are still two issues: firstly, the game does not work with video cards newer than a Radeon 9000 or [=GeForce=] 6800 in hardware acceleration mode, which means most modern hardware. Secondly, like ''VII'', the game also has unusually high requirements for something meant for a Windows 98 machine (requiring a 233 [=MHz=] Pentium MMX with 64 MB of RAM minimum and a 300 [=MHz=] Pentium II with 128 MB for optimum performance). The biggest problem was that like ''VII'', it was being sold on store shelves as an EA Classics title even as late as 2010. Most of the problems are corrected with a fan-made launcher, which also allows you to play the game with custom resolutions. Coupled with the fact that the PC port featured much better quality character models, the game ends up looking ''much'' better than the original, although it still needs a relatively high-end system. |
| 172 | ** This game, ''Final Fantasy VII'', and ''VideoGame/FinalFantasyIX'' all have a major aesthetic flaw; the CG-rendered backgrounds (which make up 95% of the games' areas), very much a selling point of all three games and which have aged fairly well even today on the console versions, were not re-rendered for higher resolutions. They'll still 640×480 (at best), and for ''VII'' and ''VIII'', the backgrounds all looked extremely pixelated and lacking in detail on what would be a large monitor at the time of release. Playing them today on a monitor with an even higher native resolution will make the problem exponentially more pronounced. Even ''IX'', which unlike its older brothers didn't have an earlier PC port to draw from, falls prey. It also makes a jarring contrast with the 3D models rendered over them. You might think that Square Enix would at least go through the trouble of implementing a filter to address this issue in the digital releases, but alas... |
| 173 | ** Square Enix also quietly launched a Steam port of ''Final Fantasy VIII'' towards the end of 2013. Aside from the fact that it was launched with absolutely no marketing at all, it still required the user to activate the software with Square Enix like ''Final Fantasy VII'' above. And oh, it ''still'' used MIDI music and the background graphics are ''still'' 640×480. Worst of all is that the cutscenes and videos that play in the background are still at 15 FPS, but the other assets are at 60 FPS, causing certain areas to feel weird. This was eventually fixed in ''Final Fantasy VIII Remastered''. |
| 174 | ** The original PC version was also released without any way to quit the game from within. The only way to close it was to alt-tab out or alt-f4, and if you didn't know about either of those (not a far stretch of the imagination for the late '90s for everyday PC users to not know it) then your only option was to turn off the computer. |
| 175 | * ''VideoGame/FinalFantasyX'': The PC Remaster version of the game comes with a few bugs, the most annoying one being the green screen you get instead of the full motion videos. This very well-known bug has never been fixed ever since the game's release. There are also cases of the game not proceeding as it should, such as when Tidus is fighting one-on-one in the lost ruins where you can get stuck in a never ending fight, unable to enter inputs, when Rikku is supposed to appear and help you. Finally, the game can crash, though it seems to be rare. Such issues are absent from the console versions. |
| 176 | * ''VideoGame/FinalFantasyXIII'' has a Steam release that takes up an alarming amount of space (60 gigabytes, which was ''twice'' what was considered a ridiculous amount of space in 2014), has no graphical settings whatsoever, is locked at 720p, barely has rebindable keys at all, and pressing Esc exits to desktop while in fullscreen (pressing Esc while windowed brings up a confirmation menu), which you're expected to know this already. On top of all this, all of the game's logic runs on a single thread, meaning the game doesn't take advantage of multi-core [=CPUs=] that are ubiquitous in [=PCs=], which combined with other issues ([[DarthWiki/IdiotProgramming such as the HUD being unoptimized to the point where having the minimap open can cause the framerate to tank]]) means it runs abysmally on most hardware configurations. And the Asian release has one extra gotcha - it's only available in Japanese in the region when the [=PS3=] version was available in English in the region. |
| 177 | ** A patch released in October 2014 fixed the "pressing Esc at full-screen exits without confirmation" issue, and a patch in December added a scarce few graphics options including custom resolutions, but the other issues remain unresolved. All of the said graphics options were things that modders had managed to add soon after the initial release, and they don't even work as well as said mods; Playing in any resolution other than 720p causes enemy descriptions to not appear during scans, making the game harder. |
| 178 | ** ''VideoGame/FinalFantasyXIII2'' has shown to have similar issues ''XIII'' had, only having the graphics options that came with ''XIII'''s patch. For some people, it actually runs ''worse'' than ''XIII''. |
| 179 | ** As of 2020, there is a mod, [[https://github.com/rebtd7/FF13Fix FF13Fix]], that alleviates most of the egregious performance issues with ''XIII'' and ''XIII-2'', making them considerably more playable. |
| 180 | * ''VideoGame/FromDust'' shipped with the same maligned DRM scheme as other contemporary Ubisoft PC games, even after the developers had previously announced that it wouldn't, deleting and rephrasing their original announcement on the game's own forum. Coupled with minimal visual options (no choice for anti-aliasing or any way to disable the 30 FPS limit on the display) and some baffling performance issues and {{Game Breaking Bug}}s (one level is very nearly UnintentionallyUnwinnable because the tides change much faster than on the console version), the PC release was a public relations disaster for Ubisoft, with Steam giving out refunds to disgruntled players for the first time since ''VideoGame/GrandTheftAutoIV''. |
| 181 | * ''VideoGame/GearsOfWar''[='=]s PC port had one horrible, horrible flaw. Occasionally, players' saved games would disappear, never to be seen again. The developers, Epic Games, also forgot to renew the certificate on the game's copy protection, leading everyone's copy to declare that the game was pirated and refuse to boot on January 28, 2009. This was fixed just over a week later, on February 6. During that time, ''[[{{Irony}} only pirated installations of the game could still play]]!'' |
| 182 | * ''VideoGame/GhostbustersTheVideoGame'''s PC version has no multiplayer. While that can be ignored (espcially since the PC version launched at a lower price to compensate), what can't be ignored is the horrid mouse acceleration that makes it unplayable unless you use a controller (or use 3rd party fixes, fixes that assume you have a Logitech-brand mouse). The PC version also has no achievements, unlike the other Realistic versions. |
| 183 | * ''VideoGame/GhostReconFutureSoldier'', already suffering from weird and inconsistent issues on consoles [[TroubledProduction due to its delayed development]], had a PC port that was delayed several further times in part because it was actually cancelled in December 2011 (with the free-to-play ''[[VideoGame/GhostReconOnline Ghost Recon Phantoms]]'' envisioned as the "PC version" of ''Future Soldier'') only for them to change their minds a month later, leaving them scrambling to catch back up with the console versions' development. Despite the long development time, it has laziness written all over it. The launch-day problems are so numerous that a necessary list includes but is not limited to: |
| 184 | ** Limited graphical settings. |
| 185 | ** Poor, crash-prone performance, even on high-end [=PCs=], sometimes with a nice memory leak to destabilize any system it's installed on for good measure. |
| 186 | ** [[LoadsAndLoadsOfLoading Insanely long load times]]. |
| 187 | ** There's no way to change settings in-game at all without having to quit to the main menu (resulting in even more agonizing load times). At the very least, this is a problem in the console versions too -- its "in-game manual" feature, despite being advertised as "more convenient" than leaving your spot in front of the TV to look things up in the manual, forces you to quit back to the main menu to access it. |
| 188 | ** If you have a controller plugged in (or in worse cases, simply have its driver installed), then the mouse -- which was working perfectly in the menus -- refuses to work in-game. |
| 189 | ** Control remapping is broken beyond belief. As in, trying to rebind an action ''[[DarthWiki/IdiotProgramming causes an unrelated action to be unbound]]'', to say nothing of the reports of the game ''not saving the keybindings at all''. |
| 190 | ** Even if you get the mouse to work in-game, it's handled poorly, with a weird sort of negative acceleration (e.g. slow mouse movement translates to very fast aim adjustment and vice-versa) and additional mouse buttons, or even the mouse wheel button, not working in-game. |
| 191 | ** Instead of fixing any of the mentioned issues with the 1.2 patch, not only was performance actually worse, ''it forced lower resolutions'' in the configuration file. And for a decent percentage of its players, with each further patch [[FromBadToWorse it somehow kept getting worse]]. At one point they even had to change things so that the weapons unlocked for the campaign through playing Guerilla mode on consoles were just added to your list of rewards for finishing specific missions because they were somehow completely incapable of fixing the PC version's issues with tracking these achievements - quite an accomplishment given that, even on the platforms the devs actually cared about, updates frequently failed to fix bugs at best and introduced new ones at worst. |
| 192 | ** XP users who preordered the game were screwed over even worse -- until the game had actually been released (and even for several months afterwards, if your source was anywhere other than Platform/{{Steam}}), there was absolutely no word that the game required Vista or above to run, leaving the aforementioned users paying [[BribingYourWayToVictory at least]] 50 bucks for a terrible port that ''they couldn't even play at all''. Ubisoft promised a patch that would allow the game to run on Windows XP for three weeks after release, but like everything else about the game's development ScheduleSlip quickly set in and the patch ended up taking almost an entire year. |
| 193 | * ''VideoGame/GrandiaII'' has cutscene encoding problems similar to the [=PS2=] version (needlessly duplicated frames, creating the illusion of "hanging" attack cutscenes), badly downsampled and compressed cutscenes (resolution somewhere around 256×192 or similar, with countless artifacts), and on top of that, requires an obscure codec to play them. |
| 194 | ** ''Grandia II Anniversary Edition'', while more or less decent for a port, has several glaring flaws. The game is full of bugs and glitches, some of which are game-breaking, such as [[spoiler:Millenia's first boss battle being impossible to end due to a looping bug preventing her from performing the attack that's supposed to signal the end of the battle]]. The music during battles cuts out completely after a ''single'' loop. Finally, the much-touted addition of the original Japanese audio isn't at all synced with the onscreen text's autoscrolling, which was designed with the English dialogue in mind, meaning many conversations end up being cut off abruptly, making it almost impossible to keep up with the dialogue. |
| 195 | * ''VideoGame/GrandTheftAutoIV'' is a particularly infamous PC port. At release, it not only had noticeable performance issues and a clumsy mouse and keyboard interface, but Rockstar also decided to package the game with an extra piece of software known as the Rockstar Social Club, a utility created to handle the game's multiplayer connectivity, which in its original iteration would run on top of the game (along with [=SecuROM=] ''and'' the infamous Games for Windows Live) and nag you to log into it not only whenever you wanted to play, but on startup as well. The controls couldn't be changed (a feature that has been standard even in the DOS era). It was so bad that Platform/{{Steam}} gave out ''refunds''[[note]]To clarify, Steam '''never''' gave out refunds before June 2015, where they allowed anything to be refunded if it's been owned for less than two weeks and played for less than two hours. Before then, they only did so five times including here - twice for other games that were the epitome of this trope like ''From Dust'' and ''Ghost Recon: Future Soldier'', and twice for games that were advertised entirely on BlatantLies like ''The War Z'' and the "remake" of ''VideoGame/ColinMcRaeRally'' (which turned out to be a port of the ''[=iOS=] game'').[[/note]] to angry gamers. Since the game's launch in December 2008, many of the game's performance issues have now been ironed out, and Rockstar Social Club has been integrated into the game software itself... almost a year and a half after launch. |
| 196 | ** Version 1.0.4.0 ran at an acceptable framerate and is generally recommended by most gamers on low-end systems (at the cost of not being able to sign in to multiplayer, which went down in 2014 with Games for Windows Live anyway). This wasn't the case with 1.0.6.0 and 1.0.7.0 -- despite Rockstar's claims about the shadow mapping system being "less memory-intensive", it actually has ''worse'' performance than the previous versions. A lot of mods for the game are also incompatible with anything after 1.0.4.0. |
| 197 | ** And even to this day, ''GTA IV'' still couldn't run fluently on all but the high end [=PC=]s made in the past few years. Getting it to run at 1080p 60 FPS or more apparently calls for a GTX 1060 and a high-end Core i5 or a Core i7-6700K - both of which came about at least ''seven years'' after ''GTAIV'' - which is ironic considering how games released almost ten years after ''GTA IV'' look and perform even better. |
| 198 | * ''VideoGame/GuitarHero III'' was touted to be playable on laptops, for the first portable ''Guitar Hero'' experience (until the DS version). Too bad that, on some computers, the game chugs down to unplayable speeds, apparently unrelated to the computer's specs. The CopyProtection seems to at least be partially responsible, too. ''Guitar Hero: Aerosmith'', which runs under the same gameplay engine as ''III'', is just as bad, and ''World Tour'', the final ''GH'' game to get a PC port, was prone to crashing a lot for seemingly no reason, requiring the fan-made Definitive Edition mod in order for it to run properly as Aspyr apparently couldn't be bothered to release a patch themselves. The lack of compatibility with modern systems does nothing to help these issues. |
| 199 | * In a bizarre case of a port to the ''same'' platform having problems, the ''VideoGame/HalfLife'' expansions were rereleased on Steam with the original soundtracks missing and mysteriously replaced with the same tracks from the original game. No explanation was ever made as to why, but apparently it wasn't irreconcilable because Valve finally got around to patching them back in... in ''2013'', when it was submitted as a bug report on the [=GitHub=] they had set up to track bugs with their new Linux ports, and the staffer basically said "Huh. Dunno why that was. Here you go." [[YourPrincessIsInAnotherCastle All was not right with the world, however]], as said port somehow [[GameBreakingBug broke the ability to actually finish]] ''Opposing Force'' -- the player is supposed to be teleported to the finale when the final boss dies, but that didn't happen, and then ''that'' had to be remedied. |
| 200 | * Compared to the PC port of the first game (which only lost the co-op mode and has minor visual bugs regarding shadows, but gained a new weapon in multiplayer and a free demo that people are ''still'' playing two decades later), the PC version of ''VideoGame/Halo2'' by Microsoft Games Studios was damn poor. Many keys couldn't be bound to commands because they were pre-reserved by Games for Windows Live functionality (almost a big "screw you" to all non-WASD keymap users), and network connectivity was patchy (another big thank-you for Games for Windows Live). Worst of all, the game could ''only'' be played on Windows Vista, and even though Windows 7 and up are technically able to run it, they still require the same sorts of workarounds as XP needed since Microsoft quickly dropped support for this game and the concurrent ''VideoGame/{{Shadowrun}}'' before those [=OSes=] released. The most infuriating part is that this being a port of a 2004 game that uses a much older version of [=DirectX=] than Windows Vista offers, ''nothing'' in the game code requires Vista to run except for one small line in the installer that prevents people from installing and running the game on any other OS. To compound the issue, the "Halo 2 Editing Kit" was extremely gimped. The ability to modify vehicles, weapons and tons of other functionality were removed, including creating custom tags. This means it's impossible to use the official tools to make new single-player content, and greatly reduces the amount of map modification possible; one of the few reasons why you might prefer the PC version of a game over a console version. Oh, and it's terribly optimized. This port was so badly botched it's probably the primary reason it took a solid ''decade'' for any main-line ''Franchise/{{Halo}}'' games to make it to PC again, with the only offerings on the platform between the 2007 port of ''Halo 2'' and the 2018 remaster of ''VideoGame/HaloWars'' being [[VideoGame/HaloSpartanAssault ports of mobile games]]. The ironic contrast here was that ''Halo 2''[='=]s PC release, alongside the cross-play-compatible 2007 ''Shadowrun'', was intended to headline ''increased'' support for PC gaming from Microsoft, but both performed so badly (whether in and of themselves or because they required Vista in its early, heavily-buggy days) that it instead resulted in the opposite situation, with first-party Microsoft-published games remaining exclusive to the Xbox until nearly a decade later, with the advent of Windows 10 and the Platform/XboxOne, and even then the fact that several first-party Xbox One games are also available on PC through the Windows Store is [[InvisibleAdvertising never actually brought up]] unless they sell through Steam as well (compare the almost-unadvertised PC releases of the ''Halo Wars'' remaster and its sequel to the hype surrounding the PC port of ''The Master Chief Collection''). |
| 201 | * ''VideoGame/HomefrontTheRevolution'' had many bugs and performance issues on all platforms at launch. The PC version was no exception with constant framerate drops. |
| 202 | * ''VideoGame/{{Interstate 76}}'s'' UpdatedReRelease on Platform/GOGDotCom came with a plethora of issues due to the game's update from Windows 95 not being particularly good; the game was originally designed to run on the "Glide" video wrapper (versus [=DirectX or OpenGL=]), which was last updated more than a decade before the GOG version's release - instead, the GOG version runs without any wrapper by default. TechnologyMarchesOn causes the game to run in what is essentially turbo mode on modern [=CPUs=] to the point where everything from physics to the AI breaks: jumps are impossible, flame weapons [[VideoGameFlamethrowersSuck have absolutely no range]], and NPC characters drive at 10mph while their wheels spaz out. It's (mostly) playable with a [[http://www.gog.com/forum/interstate_series/updated_new_i76_arsenal_launcher_with_automatic_workarounds_2_versions/page1 fan-made launcher]] designed to counter the issues. |
| 203 | * ''VideoGame/IronMan1'', an [[TheProblemWithLicensedGames already mediocre game]] to begin with, was based on the [=PS2=] version rather than the superior Xbox 360 or [=PS3=] ones, just for starters. |
| 204 | * ''VideoGame/JustCause1''. Not only is it a glitch-ridden, crash-prone mess, but it's also based on the original Xbox version—so it lacks the far superior lighting system from the Xbox 360 version. A [[https://www.youtube.com/watch?v=cSCX8kVAwlA side by side comparison]] is just humiliating. |
| 205 | * ''VideoGame/TheLastOfUs [[UpdatedRerelease Part 1]]'''s PC version takes one of the most beloved games of the 2010s and gives it a launching disaster on par with ''VideoGame/Cyberpunk2077''. Helmed by Iron Galaxy, the same studio responsible for the botched PC port of ''VideoGame/BatmanArkhamKnight'', the port is ripe with horrible optimization, a plethora of performance issues, and infrequent crashing that can render the game borderline unplayable without heavily modifying your settings. Worse yet, Steam Deck users reported the game spending literal hours loading the shaders used. The issues were so bad that not only was the game predictably [[InternetCounterattack review-bombed by users]], but even professional critics panned it, earning the game a 56 on Metacritic (technically becoming Creator/NaughtyDog's first game to get such a low rating). While subsequent patches addressed many of the issues, the damage was done. |
| 206 | * ''VideoGame/LANoire'' is a lagfest when running the PC port on certain setups with the default multithreaded renderer on. Adding the -str command line argument on launch cures the problem somewhat, but it still doesn't eliminate all the issues from the game, adding to the fact that it was locked at 30 frames per second, citing limitations with the game's facial animation system. |
| 207 | * ''VideoGame/Left4Dead2'', specifically the "No Mercy" campaign from [[VideoGame/Left4Dead the original]], which Valve had problems porting. The third map in the campaign has a shutter door that can [[DoorToBefore only be opened from the inside of the building]] so that any survivors that get yanked outside can go through the door without having to climb up to the rooftop again. While a Tank can bust the door down, survivors were able to do the same thing with melee weapons, allowing them to bypass the crescendo event. It took Valve several patches to fully squash the problem, but the Grenade Launcher can still destroy the door. Thankfully, this is not a problem in Vs. mode since survivors can't carry over weapons from the previous map and the Grenade Launcher never spawns before the event on this map. |
| 208 | ** The elevator from the fourth map regularly causes players to fall through the floor randomly (can mostly happen if a player goes idle) even today despite several attempts by Valve to fix it. Considering that most issues in the first game got fixed very quickly or were not even present, that looks rather pathetic. |
| 209 | ** There are also issues with the ports of the ''[=L4D1=]'' survivors into ''[=L4D2=]''. |
| 210 | *** The character models were directly ported over, so they received no graphical upgrades, which isn't a problem, but they use skeletons/animations from the '[=L4D2=]'' survivors instead of their own. This means Louis is now suddenly taller than he used to be while Zoey seems to have shrunk and often suddenly grows two heads when taking out some of the new weapons. The survivors' hands also clip into the models of the pistols and they don't hold items like pills and bombs properly. On top of this, the survivors also have no lines for the elevator scene in No Mercy and have no reactions when being torn up by a Hunter, despite that there are actual sound files for these events present in the game's files. This makes the port of the old characters look like a rush job. |
| 211 | *** Originally, The Sacrifice DLC was only going to be for the original Left 4 Dead, but Valve decided at the last minute to give the DLC to ''Left 4 Dead 2'' players as well with No Mercy as a bonus. This caused the porting to be rushed out with almost zero bug testing. |
| 212 | *** In one of the updates, Zoey (and apparently only Zoey) regained her original animations - and lost ''all'' of her animations she uses in The Passing as an NPC. |
| 213 | *** Valve has at least attempted to remedy the survivor dialogue issues regarding ''Left 4 Dead 2'' content such as being attacked by the new special infected and when they use adrenaline shots. |
| 214 | ** There are also other audio issues related to The Passing. When it comes to a line from Louis, saying "That was for Bill!" after killing a Tank, the game seems to be unable to differentiate between that campaign, where Louis is an NPC and Bill is dead, and the other campaigns ported from the first game, where Louis and Bill are both playable and likely to be alive. |
| 215 | ** As part of the Cold Stream DLC, Valve planned to release all of the ''Left 4 Dead'' campaigns into ''Left 4 Dead 2''. As with No Mercy, the campaigns had numerous issues when they were released to the PC gaming public as a beta. Nearly all the maps had item density problems, which meant that instead of items spawning randomly by the AI Director, the game wound up spawning items at every single spot that they could appear in. This was fixed over time. |
| 216 | * ''VideoGame/MafiaIII'' ended up being a disaster on the PC, with irate players complaining about the game being locked to 30 FPS. On top of that, lower-end systems which can run games that are just as graphically intensive as Mafia III are unable to maintain a stable framerate even with the settings turned down to a minimum -- forget about playing it on a G3258 or a similar dual-core chip, the game simply goes down to a crawl in city areas, yet in the bayou areas, the game seems to run more or less fine. Very soon after release, the framerate cap was removed in a patch (which lead to many players wondering why it was even there in the first place). Other patches also resolved many issues, but there are still some glitches and performance problems that are waiting to be fixed. |
| 217 | * Years after the release of the excellent PC port of the first ''VideoGame/MarySkelter'' by Ghostlight, the company released a port of the second game alongside the first game's remake. Unlike the first game, the PC port of ''Mary Skelter 2'' was released as a broken, unplayable mess at launch. Barebones graphical settings, framerate and audio issues and the worst of all, constant crashes. On top of that, the PC port had its purification minigame removed, just like the Platform/PlayStation4 version. This censorship generated enough backlash that Ghostlight would later release a separate patch to uncensor the game on their own website. As for the port, it did get a few updates to fix the aforementioned issues, but Ghostlight would later abandon the port, still leaving it in a broken state. To this day, the port is still plagued with crashes, and there are no workarounds to fix them. Creator/IdeaFactory would later ditch Ghostlight and release ''Mary Skelter Finale'' on PC by themselves. |
| 218 | * ''VideoGame/{{Mass Effect|1}}'': |
| 219 | ** The game was originally released exclusively on the Xbox 360, but was ported to the PC about half a year later (and also to the [[Platform/PlayStation3 PS3]] about ''four more years'' after that). While there were actual gameplay improvements, such as ten hotkeys for abilities over the 360's three, and generally better controls, rumor has it that the game was tested on one graphics card and one sound driver. The released game was exceptionally buggy, with sound effects and background music dropping out and the game regularly crashing between the transitions of unskippable cutscenes (which were made unskippable because skipping them also crashed the game). It took over a year and a combination of game and driver patches before the game was stable. It also had rather high system requirements for an Xbox 360 port, although [[TechnologyMarchesOn most PCs you can buy or build today]] will run it fine. |
| 220 | ** The PC version of the game's first DLC, ''Bring Down the Sky'', was released for free, but for some reason still required a CD key. To get the key, one would merely have to register on the Mass Effect website, on a page dedicated to giving out [=BDtS=] CD keys... a website that stopped existing by the time ''Mass Effect 2'' was announced. For a long time, players new to the series had to e-mail EA tech support to get a CD key for the DLC. Fortunately, they eventually fixed it with a [[https://help.ea.com/article/mass-effect-bring-down-the-sky-dlc-redemption new downloadable file]] for the DLC that doesn't require a key. |
| 221 | ** An extremely obscure design feature of some [=CPUs=] that have come out since the game was released causes the graphics to glitch out in certain areas and make the game near-unplayable. Specifically, the section in Port 15 during the Noveria portion of the story campaign uses a form of software lighting to take a load off the GPU; presumably, it's a concession left over from the Xbox 360 version of the game, where the framerate was already unstable. This uses an ancient instruction set known as [[http://en.wikipedia.org/wiki/3DNow! 3DNow!]], which very few games other than ''Mass Effect'' use. Because of this, AMD dropped support for 3DNow! in 2010 and every processor they've made since then does 3DNow! through SSE emulation. This, unfortunately, means that the lighting in the scene is rendered improperly, resulting in characters [[http://i470.photobucket.com/albums/rr69/SnuffThePunkz/Gaming%20Crap/MassEffect_2012_01_10_15_49_21_512.jpg not being lit at all]]. Of course, pre-2010 AMD processors have native support for 3DNow! and don't require emulation through SSE, so the scene is lit properly. However, even more perplexing is that Intel [=CPUs=] never supported 3DNow!, and yet they're subject to the same issues -- pre-2010 Intel [=CPUs=] light the scene properly, post-2010 ones don't. |
| 222 | * ''VideoGame/MegaManX7'' was ported from [=PlayStation=] 2 to PC by the (defunct) South Korean-based Multi-Enterprise, who did absolutely ''nothing'' to properly program the game for [=PCs=] and ported it as is. The result was a shoddy PC port with ugly low-res visuals, jagged polygonal models, missing shadows and visual effects, and there's no way to fix that. They don't even include an option to exit the game, you have to close the game by Alt+F4 or Task Manager. The kicker? It has one of the most horrendously awkward control schemes for a semi-2D platformer/3D third-person shooter while ''forcing'' you to use keys they want to use and the game does not support gamepads at all! The game even flat-out fails to run on modern Windows operating systems. |
| 223 | * ''VideoGame/MightyGunvolt''[='=]s PC version is a barebones, sub-par port that suffers from input lag and frame-rate problems due to its V-sync implementation, no rebindable keys, very few PC settings to speak of, and playing the game at a resolution higher than the default 960x540 forces a smoothing filter that can't be turned off. For AMD graphics card users, the game is virtually unplayable as the game can't render enemies at all. |
| 224 | ** ''Mighty Gunvolt Burst'' on PC also has its issues, especially for AMD graphics card users. The game sometimes renders itself on a 4:3 aspect-ratio in fullscreen despite being made for widescreen, resulting in a substantial part of the game screen cut off, especially for those with 4K displays, and the game fails to render the lighting effects from the Switch/[=PlayStation=] 4 version on AMD graphics cards. |
| 225 | * ''VideoGame/MortalKombatX'' had a disastrous launch on Steam. It used a 'streaming installer', which in theory, was supposed to allow you to play the game's content as it came in, instead of waiting for the whole game to install. What actually happened was that on launch, the only assets that were made available was the main menu. The rest of the game didn't even start streaming out until ''12 '''hours after''' launch''. Add to that, you had no control over what assets were installed in what order, and no idea what would be in each pack. So if you wanted to kill time playing single matches with your favorite character, you had to hope he was in one of the first couple of packs, or else you might be waiting a while. |
| 226 | * ''VideoGame/NierAutomata'' was a complete disaster at launch: the game crashed frequently depending on the hardware, the displayed resolution was locked to 1600x900[[note]]the game rendered at the resolution set, but scaled it before displaying it[[/note]], the performance was poor[[note]]with the biggest culprit being the global illumination, which was set to a ridiculously high level and cannot be tweaked[[/note]], pre-rendered cutscenes stuttered heavily... Mods were essential for an acceptable experience. It took 4 years[[note]]and a Microsoft Store version that added only a few unimportant graphics options[[/note]] for a patch to arrive that fixed all the above problems. While the game is now in a much better state, there are still problems: the mouse and keyboard are still terrible[[note]]in particular, the dodge is bound to double-tapping the directional keys, with no way to change it. Nothing else in the game works like this: the porting team went out of their way to make the dodge bad, as if keyboards were starving for buttons[[/note]], the game is still capped at 60 FPS, and there are LOD issues that weren't there before. |
| 227 | * The PC version of the ''VideoGame/NinjaGaiden Master Collection'' has a complete lack of mouse and keyboard support, and at launch, lacked ''any'' form of PC-related settings (e.g. resolution options, graphics settings, display modes). |
| 228 | * It would be generous to even call the Windows version of ''VideoGame/{{Nightfire}}'' a "port" at all, as it was rebuilt completely from the ground up using the ''Half-Life'' engine. While in theory this at least means better lighting, Gearbox was unable to figure out how to add drivable vehicles and instead just removed all the driving levels entirely, which is close to half the game. And the rest of the game [[https://www.youtube.com/watch?v=shEz4vs2elI barely works either]]. Odd considering this was the same studio behind the excellent Windows port of ''VideoGame/HaloCombatEvolved''. |
| 229 | * The 2023 Steam release of ''VideoGame/O2Jam'' by Valofe. Rather than being a remastered version of the PC original, [[FirstInstallmentWins which is seen as the best game in the series]], it's a port of their mobile version, which itself is seen as not particularly remarkable due to its gameplay having little to do with the original game and not being standout compared to other mobile rhythm games. And the developers couldn't even get ''that'' right; the game's audio tends to distort randomly, sometimes the game may just softlock when loading songs and be stuck at a specific percentage indefinitely, and some of the timing judgements don't exist. Perhaps worst of all is the pricing for the VIP subscription: While it costs 1 USD per month on mobile, in this version it's ''12.99 USD'', which is already bad enough...but rather than being a monthly charge as advertised, the 12.99 USD is charged ''[[GameBreakingBug every single day]]'', for a total of about ''400 USD per month!!'' |
| 230 | * ''VideoGame/{{Oddworld}}: Munch's Oddysee'' and ''Stranger's Wrath'' are horribly unoptimized for the PC, despite being released at least five years after the original Platform/{{Xbox}} versions, to the point where people with competent gaming [=PCs=] (ones that can run ''VideoGame/{{Crysis}}'' smoothly at high graphic settings) regularly get less than 30 FPS -- and the actual graphics are unchanged. ''Stranger's Wrath'' has no visual customization options apart from the resolution settings, ranging from "Low" to "Medium", to "High", and "Ultra", with the latter three being 1024×768, 1280×1024, and 1600×1200, respectively. Both games also have noticeable issues with the Xbox 360 controller, which is the default recommended joypad for both: In ''Munch'', the left stick changes the direction that the character faces, but ''doesn't actually move the character'' -- the arrow keys on the keyboard are apparently still needed for that. In ''Stranger'', the game completely fails to recognize the right thumbstick's button press, which is supposed to toggle the switch between first and third-person -- a ''[[ForcedTutorial mandatory step in the in-game tutorial]]''. Both games are also ridiculously crash-prone: You'd have to be ''very'' lucky to even get to the second stage in ''Munch'', and as of the first week after release, only a third of the player base had managed to pass the tutorial in ''Stranger''. And keep in mind, the Xbox itself already has very similar hardware to an IBM-based PC, so you have to be ''incredibly'' lazy to botch a port this badly. |
| 231 | ** ''Stranger's Wrath'' is now fixed, as of the 1.1 patch. Performance is nigh-flawless on a Q6600[=/=]8800 GT[=/=]Windows 7 64-bit system at 1600×1200, like it should have been from the start for a five-year-old Xbox port, and you can now select which controller you want and rebind it through an .ini file. Unfortunately, wireless Platform/{{Xbox 360}} gamepads are not configured properly by default (which is baffling when the game clearly shows Xbox 360 gamepad controls), and in-game control configuration is still not present. Still, a hell of a lot better than the state it was in at release, and actually quite playable. |
| 232 | * ''VideoGame/PrinceOfPersiaTheSandsOfTime'' is reasonably well-optimized and doesn't lack any features, but it is ''notoriously'' glitchy and crash-prone, in addition to being a pain in the ass to run. The [[https://www.youtube.com/watch?v=spw8wfcL7vo infamously ill-fated]] run of the game at [[WebVideo/GamesDoneQuick SGDQ 2015]] highlights just how buggy it is. |
| 233 | * ''VideoGame/{{Prototype}}'' is very picky about what qualifies as "recommended system specifications". It struggles with maintaining a double-digit frame rate on the ''menus'', not to mention in actual gameplay. There were also issues with audio sounding exceptionally muffled and other issues. Definitely not one of the best ports out there. |
| 234 | ** The [[VideoGame/{{Prototype 2}} sequel's port]] is also plagued with issues. Some systems would run it just fine, others which greatly ''exceed'' the listed requirements would somehow result in a chugging mess, and some would just not run at all. One very common syndrome appears to be a memory leak affecting AMD drivers, due to an unmentioned incompatibility with Catalyst AI, which would cause the game to degenerate into a slide show. Being a 32-bit program, [=PCs=] with at least 4 GB of excess memory to spare (builds with 6 to 8 GB or more) might escape the slowdown even as a ton of memory is consumed, but there are also other game-breaking bugs, such as a very early mission refusing to progress unless all CPU cores except for one are disabled for the game (on some machines). Additional problems reported include mouse sensitivity being tied to the frame rate; certain fast performing machines would have the mouse look go crazy even on minimum sensitivity. |
| 235 | * Not only did the original Windows port of ''VideoGame/QuantumBreak'' require the divisive Windows 10 to run due to running in [=DirectX=] 12, it performed terribly even on very high-end systems, especially with NVIDIA cards.[[note]]In fairness to the developers, this was as much NVIDIA's own fault, as the then-ubiquitous [=GeForce=] 900-series had an incomplete implementation of [=DirectX=] 12, meaning that games which were developed with the [=PS4=] and Xbox One in mind tended to suffer performance issues on those cards.[[/note]] [=PCs=] with AMD graphics cards would run the game better, but the performance still isn't great by any stretch. Also, any efforts on part of users to mitigate them were hampered due to how restrictive the Universal Windows Platform, or Games for Windows - Live 2.0 as some would derisively call it, is. The developers eventually gave up on UWP and released a new port on Steam, this time built around [=DirectX11=] and so compatible with older versions of Windows, with considerably better results. |
| 236 | * The Windows 95 port of ''VideoGame/{{Ray|Series}}Force'' (''Layer Section'' in other regions) has some glaring problems, some of them have gotten worse over time. The game is played on a 4:3 aspect ratio but the game screen is crunched to a square box. This results in giving the player less viewing area to anticipate enemies or lock-on to them as efficiently as the arcade and the other home ports. Effects from the arcade and home versions are also missing. Some tracks of the game don't play at all, such as the Game Over music, and if you don't have the game disc inserted in your CD drive, then the game will not play since the game will only read them from the disc. The game's frame rate is also unstable and runs at an unplayable speed, but the .dll files on the disc can fix this issue. The game forces fullscreen mode and its scaling doesn't work properly on newer Windows operating systems, resulting in a smaller game screen despite running in 640×480, and the only way around this is through third-party [=DirectX=] wrappers such as DXGL or [=DxWnd=]. |
| 237 | * ''VideoGame/RedFaction: Guerrilla'' ran far too fast on Windows 7 computers (which rather quickly replaced Vista as the go-to modern Microsoft OS), which forced players to use a third-party hacking program to slow down the game's refresh rate. Furthermore, the game carried an infamous bug where Games for Windows Live informed the player that a patch was available and was mandatory for online gameplay (even if the game itself was already up to date). Every time without fail, should the player have accepted the patch download, the game's framerate was reduced to a crawl (in the '''main menu''', mind you) and eventually froze. Even Volition's release of a manual patch to fix this didn't work for many, making online multiplayer completely unplayable. On the other hand, the Steam re-release published by Nordic Games, the new owner of the Red Faction IP, doesn't have the aforementioned issues, no longer requires Games for Windows Live, and is overall PolishedPort instead. |
| 238 | * The Xplosiv version of ''VideoGame/ResidentEvil3Nemesis'', which was made mainly for Windows XP, is a mess. The port has new and unique glitches, such as the background clipping out, Jill walking in the air and the game freezing at random intervals; the game sometimes flatly refuses to start; and worst of all, programming errors accidentally removed both the Mercenaries bonus mini-game (making it impossible to get the infinite weapons and the infinite bullets for every weapon) and the NewGamePlus save system (which means that you can't unlock any of the epilogues, due to the game not detecting a completed save). |
| 239 | * The 2007 Windows port of ''VideoGame/ResidentEvil4'' was touted to feature [=GameCube=]-quality graphics with the extra content of the [=PS2=] version, something that wouldn't happen until the Wii version. Instead, [=SourceNext=] (whom Capcom commissioned to develop the PC version, along with the PC ports of ''VideoGame/Onimusha3DemonSiege'' and ''VideoGame/DevilMayCry3DantesAwakening'') ported the [=PS2=] version of the game as it was, with grainy pre-rendered cutscenes and all, but [[https://www.youtube.com/playlist?list=PLMyoprrqVo6DnDskwr5CJNf634P6LX2Qn without the shading and lighting]], meaning every environment in the game was lit at 100% brightness with no shadows, thus no atmosphere, and had to have that patched (note that this was the ''only'' patch the game received). The game's controls were gimped to boot, to the point where the game could be played on a keyboard and ''only'' the keyboard, without mouselook like most PC shooters. Quick-time events were near-impossible to complete if you weren't using a gamepad because the button prompts were limited to "button 3" and "button 4" instead of the actual keys on the keyboard, and to add insult to injury, they accidentally switched the icons for button 3 and button 4 around, so following the on-screen prompts would actually get you killed. For added irony: The same company also released [[UpdatedRerelease improved]] (and Japanese-only) PC-DVD ports of ''Resident Evil 2'' and ''3'' that are fully capable of running on modern Windows operating systems (Windows XP and above) no problem. Fortunately, the devoted mod community of the PC version of ''Resident Evil 4'' has not only patched all these but released mods that up the graphics above and beyond any other version of the game, give the game proper mouse aiming, and change the quick-time event prompts to match up with most commonly used gamepads such as the Xbox 360 one. |
| 240 | ** The ''Ultimate HD Edition'' of the game released on Steam in 2014, while obviously leagues better than the older one, also has several problems of its own. Not all the new textures are truly in high definition, so if you select the new set the results are uneven. It misses some graphical effects that were already missing in the Xbox 360 port (which this version is based on), but a modder managed to put them back in within a few hours. Gradients and lighting are not set up correctly, so compared to the Nintendo and Xbox 360 versions, you get excessive dithering and blinding lens flares. Mouse calibration is imperfect to the point of being unplayable for some, and only the bare minimum of keys are rebindable from the Options menu; to rebind keys such as the ones used in quick-time events (X and C by default), requires going to the .ini files and editing settings from there, [[GuideDangIt with little-to-no help]] on rebinding other keys on the keyboard, and some keys cannot be remapped at all. Some of the issues were addressed through patches, but other lingering issues such as the forced mouse acceleration, the broken fire filter effect carried over from the Xbox 360 port, doubled [=QTE=] requirements while playing at 60 and many other issues remained unaddressed. Thankfully the re4_tweaks mod can resolve many of the issues still present in the ''Ultimate Edition Edition'' while adding new quality-of-life enhancements. |
| 241 | * ''VideoGame/ResidentEvilVillage'', while praised for its gameplay, setting, and variety, was nevertheless criticized for its downright terrible performance on the Windows version, as the game suffers from stuttering and frame rate dips even on systems that exceed the recommended hardware requirements. This would eventually be blamed on both Denuvo--itself already reviled by critics as an excessively draconian form of DRM--and on what appears to be a botched implementation of Capcom's own anti-tamper mechanism in an attempt to further deter pirates. Adding insult to injury was that a cracked release of the game by an independent cracker who goes by the alias EMPRESS ran ''far better'' than the original version, as shown by [[https://www.dsogaming.com/news/resident-evil-village-crack-completely-fixes-its-stuttering-issues/ [=DSOGaming=]]] and [=YouTuber=] [[https://www.youtube.com/watch?v=-ig4dqozB1I Modern Vintage Gamer]]. |
| 242 | * It's ultimately generous of Blizzard to release several of their old games for free on Windows, but the ''VideoGame/RockNRollRacing'' release was a major mess up, period. The classic songs were removed and replaced with a generic grunge metal soundtrack, and to make things worse, it was actually the ''SNES'' version of the game patched to disable the songs and then run on a modified emulator that also provided the grunge soundtrack on its own[[note]]loading the ROM into a proper emulator resulted in the game missing its music, but sound effects are intact[[/note]]. This also meant that the game had one long soundtrack that doesn't change through the game and gets annoying quickly enough. Another thing to note is that the game is a demo version. While the free releases of ''VideoGame/{{Blackthorne}}'' and ''VideoGame/TheLostVikings'' were the full games, for ''Rock 'n' Roll Racing'' the people at Blizzard decided to give out a severely cut-down version that, after just three races, unceremoniously dumps you back to the title screen, with no fanfare or anything. |
| 243 | * The PC port of ''VideoGame/SaintsRow2'', handled by Creator/{{CD Projekt|RED}}'s Localisation Centre rather than Creator/{{Volition}} themselves, was so bad that Volition essentially fired them from the port and washed their hands of it, declaring it hopeless (thus the PC version never got the DLC). The on-foot sequences basically worked, but driving was essentially impossible thanks to an internal game clock that did not know how to adapt for CPU speeds other than 3.2 [=GHz=], which was the clock speed of the Xbox 360, the platform the game was originally developed for. Thankfully, the game has a fantastic community that has not only brought the game back to its intended speed and fixed thousands of other bugs but also added plenty of neat content to boot. [[http://idolninja.com/ You can check out the Gentlemen of the Row supermod here]]. With the fan patch, it still isn't perfect, but it is far more playable. |
| 244 | ** The one thing that can't be fixed is the sound; all of the sound files are compressed to cassette tape quality and mono. Luckily, there is a [[https://www.saintsrowmods.com/forum/threads/high-quality-radio-mod.9515/ huge fan-made patch]] that fixes the radio back to its intended high-quality sound from the console versions. |
| 245 | ** The Steam release of the PC version also displays a bizarre issue where, unless both the client and the game are installed to the C: drive, the game will run, but only show the opening titles and not progress past the loading screen that comes immediately afterwards, which would ordinarily lead to the main menu. Oddly enough, years later the Steam release of ''VideoGame/SaintsRowIV'', a ''vastly'' superior port, would suffer from the same issue; the Platform/GOGDotCom version works on any drive with another, vastly more minor problem instead: graphics settings will revert to default upon the next launch if the game is installed on the C drive, probably because of a protected write area. |
| 246 | * ''VideoGame/{{Shadowrun}}'' was a port of the Xbox 360 game released around the same time as the above ''Halo 2'', also required Windows Vista just to install, and again only checked a single line of code. Especially egregious as the game was released before Vista Service Pack 1, when the OS was still ridiculously buggy and ''expensive'', and was multiplayer-only. This and the advantage keyboard and mouse controls gave PC players over 360 players ended up killing the idea of cross-platform multiplayer that was touted as one of its main features - it's been almost a full decade before anyone started trying again, and even then it's almost entirely limited to indie devs. |
| 247 | * ''VideoGame/SilentHill2'': |
| 248 | ** The game has what appears to be a horrible, horrible memory leak in the [=GameTap=] version. After about 40 minutes of play, almost like clockwork, the game will slow to an absolute crawl. You will take a step, wait five minutes, and then be able to take another step. This even applies when bringing up menus, so that if you don't save and quit '''immediately''' after the effect starts, it can take nearly thirty minutes to quit the game! |
| 249 | ** ''Silent Hill 2'' has other problems on the PC. On Radeon 9000 series graphic cards (which were the ones produced by ATI when the game was released and were very common), the flashlight doesn't work; turning it on means watching many textures disappear, making it ''harder'' to see. The solution could be downgrading to older drivers or adding some lines to a file dedicated to graphic devices, which are equivalent to a hack, for getting what should be a normal feature. In another glitch, you could get CG movies that play all in acid green and violet palette (and no way around it), and out-of-sync speech during some scripted sequences. There was also the "skipping music" glitch, although there was a patch to fix this -- but that patch did not fix anything outside of removing the game's [=SecuROM=] DRM. Unpacking the patch executable reveals exactly nothing. [[ShapedLikeItself The entirety of the patch's size is its own .exe.]] |
| 250 | *** Other glitches include not being able to run two code events at once, leading to an interesting bouquet of issues if you keep a piece of text on screen, say, by autosaving constantly to bring up the 'save complete' text. If you do this, cutscenes won't trigger, enemies won't spawn, and you can even ''walk out of some cutscenes entirely and unload the area they're set in'' by crashing the code that keeps you from moving during them. |
| 251 | *** Thankfully a group of talented programmers and modders has banded together to develop the ''Enhanced Edition'' project, which effectively turns the PC port of ''Silent Hill 2'' [[PolishedPort the opposite of this trope]] while remaining faithful to the game's original vision. |
| 252 | * ''VideoGame/SilentHillHomecoming'' features a lot of random crashing on the PC. A lot worse when it will always happen if you simply want to change the resolution. Want to play it with a gamepad? Good luck, because like the Silent Hill town itself, it has a mind of its own. There are the out-of-sync cutscenes. Finally, the game is locked to 30 FPS, when even low-cost budget PC monitors run at a much smoother 60 Hz. |
| 253 | * ''VideoGame/{{Skylanders}}: Spyro's Adventure'' received a hasty port to the PC. The options menu does not allow you to change any graphics settings. The worse problem, however, is, that sound often completely cuts out at certain pre-rendered cutscenes, and to make it worse, there were no subtitles feature for these scenes, so you end up with Eon simply mouthing at you or Kaos and Glumshanks mouthing at each other with the player having no idea what's going on. There were also random crashes at various places, such as the beach levels. Possibly due to this, the sequel, ''Skylanders: Giants'', had its PC version cancelled, and none of the rest of the sequels were announced for the PC. |
| 254 | * While still a fully playable game, the Steam version of ''[[VideoGame/SegaSuperstars Sonic & Sega All-Stars Racing]]'' has no exclusive characters, DLC support, achievement support, or even online multiplayer when the console versions each have some or all of those features. Thankfully, the Steam version of ''Sonic & All-Stars Racing Transformed'' amended this by including DLC support, achievements, online play, and an exclusive character from ''VideoGame/TeamFortress2''. |
| 255 | * The resolution problems the 2010 Steam port of ''VideoGame/SonicAdventure DX'' (see [[PortingDisaster/{{Multiplatform}} Disastrous Multiplatform Ports]]) had been also repeated in the Steam releases of ''VideoGame/SonicTheHedgehog4: Episodes I & II'' as well--the game's native resolution for both titles was ''always'' fixed at 1280x720p, and when the user selected a higher or lower resolution, the game's native resolution was actually upscaled or downscaled to the set resolution, rather than rendering the game at the set resolution. It was especially bad in the case of these titles as unlike the SA:DX 2010 port, both games were made with HD resolutions and graphics in mind (the [=PS3=] and 360 versions of these games can run at 1080p with no issue), ''and'' they even lacked anti-aliasing options, resulting in the games looking like a very jaggy mess of graphics. It came to a head when the complaints concerning the resolution problems in ''Episode II'' [[http://forums.sega.com/showthread.php?411044-I-have-come-to-request-a-refund-for-this-awful-and-lazy-port were raised in the official Sega Forums]] when the game was released, upon which the PR manager for the game claimed that a fix to allow the game to properly display the game at different resolutions would not be possible due to the image "breaking down" if forced to a higher resolution. [[TemptingFate Within hours of that statement]], a fan made and presented a patch that showed that not only ''could'' the game be run at a higher resolution than its intended native resolution, but the result also looked '''much''' better than the original upscaling method. ''And all he did was change a single line of code to do it.'' Another fan similarly made their own patch that allowed the game to support anti-aliasing features based on the user's local graphics cards. Needless to say, an official patch for ''Episode II'' was soon released that addressed the former issue not long afterwards. |
| 256 | * The PC release of ''[[Franchise/SonicTheHedgehog Sonic Origins]]'' turned out to be a disappointment in comparison to the otherwise [[SoOkayItsAverage mediocre]] at worst console versions. Performance issues and slowdown are more rampant on the PC version than the Nintendo Switch version, even on hardware technically surpassing the Switch, most in part due to [[MediaNotes/DigitalRightsManagement Denuvo]]. A bilinear filter smears the image poorly (in comparison to the sharper console versions and the razor-sharp ''VideoGame/SonicMania''). And lastly, the PC version also has no HDR support which the console versions (but the Platform/NintendoSwitch) do. |
| 257 | * ''VideoGame/SpaceChannel5 Part 2'' has gorgeous graphics on the PC, but the music often goes out of synch, making the game absolutely unplayable unless you edit a few settings to fix it[[note]]turning on a triple buffer and Vertical Sync in your graphic card's settings[[/note]]. |
| 258 | * ''VideoGame/SplinterCellConviction'' was another port brought down by Ubisoft's CopyProtection system. If either you or Ubisoft's Internet connection is anything less than perfect for more than a single second, you are automatically kicked out of the game and must return to the previous checkpoint upon recovery. As always with copy protection, the pirates had it cracked within - well, okay, it took a month, but the method should patch through to crack every future Ubisoft game using the same tech within a day or two. It also had an issue that affected players who installed the game on anything other than the C: drive. Launching the game from that location would result in just a black screen, while the sound played as normal. Apparently, Ubisoft didn't foresee this kind of situation. |
| 259 | * ''VideoGame/SplinterCellDoubleAgent'' had a PC version that, while technically not a port, was clearly based on the Xbox 360 version. Considering that the game was based on the MediaNotes/UnrealEngine, that Ubisoft had released plenty of PC games before (including every other ''VideoGame/SplinterCell'' game before then, no less, with no issues inherent to the games themselves on systems back then), ''and'' that it was a pretty high-profile game, you'd think it would've gone fairly smoothly. Wrong. There are so many problems with this port that a list is necessary. |
| 260 | ** The menus are a confusing mess, and you can't use the mouse on the in-game "laptop" menus (even though you could in the previous games); you need to stupidly press the keys mapped to "use" and "crouch". This wasn't a problem in earlier ''Splinter Cell'' PC games. Entering codes for keypad-locked doors likewise requires using the movement and use keys to select and punch in the numbers, rather than using your keyboard's Numpad as in ''[[VideoGame/SplinterCellPandoraTomorrow Pandora Tomorrow]]'' onward or even simply clicking them with the mouse like in ''every'' prior ''Splinter Cell'' game on PC. |
| 261 | ** The saved games are arranged in what appears to be completely random order. Not alphabetical, not by mission, not by date or time. Also, checkpoints occasionally overwrite saved games and vice-versa. |
| 262 | ** There is no gamepad support except for the Xbox 360 gamepad. This isn't new to the ''Splinter Cell'' PC series, and it uses a mouse wheel-driven "acceleration" scheme to compensate for the lack of an analog stick. This causes problems, however: the new safe-cracking sequences are affected by the analog stick in a way Ubisoft apparently didn't foresee, and so if you sneak up to a safe at minimum acceleration (the best way to sneak, obviously) on the PC version and try to crack it, you're inexplicably unable to do anything with the safe until you scroll the mouse wheel back up to "re-accelerate". Again, this wasn't a problem with the similar lockpicking sequences in earlier ''Splinter Cell'' PC games, or even in ''this'' game. |
| 263 | ** The game supports a pathetically low selection of resolutions, not even including full HD or 16:10 resolutions. This is remedied by editing the game's .ini file. Ubisoft's entire team of programmers apparently couldn't figure this out; that or, as some allege, the PC version is prohibited from maximum graphical detail to make the 360 version appear better, as editing the .ini files can also result in improved graphics. Until a patch, it was not even possible to enable anti-aliasing (mind you, that's ''all'' that patch did). |
| 264 | ** The "Kinshasa, Part 2" mission is almost guaranteed to crash every time you load a saved game, so you'd better be good at it. [[https://steamcommunity.com/app/13580/discussions/0/2949168687317629728/ According to]] the guy behind the widescreen-fix patches for the series, this is apparently the fault of the optional minimap, which causes so many problems that loading a saved game after having used it at any point during that mission guarantees a crash. |
| 265 | ** The game would even freeze for no evident reason when viewing some of the training videos for the Versus multiplayer. |
| 266 | * The first two ''VideoGame/SplinterCell'' games [[TechnologyMarchesOn eventually]] became this. They were directly ported from the original Xbox version, and as such were optimized for some contemporary [=NVidia=] cards that supported a form of shadow mapping called "shadow buffers", first supported on the [=GeForce 3=] and the [=NV2A=] GPU used on the console. While it did work on most hardware at the time, later graphics cards, driver versions and [=DirectX=] [=APIs=] broke functionality for said buffers, causing spotlights and other projected shadows to no longer work. As lighting and shadows are key elements of the gameplay, playing the original ''VideoGame/SplinterCell1'' and ''Pandora Tomorrow'' would be an ugly and unpleasant ordeal with a lot of trial-and-error. Fortunately, the first game does have a fallback mode for systems incapable of rendering shadow buffers, but ''Pandora Tomorrow'' lacks it, which may account for why it is the only ''Splinter Cell'' game unavailable through digital distribution. [[http://www.jiri-dvorak.cz/scellpt/ However, there is now a fan-made fix for both of those games]]. |
| 267 | * ''VideoGame/StarTrekLegacy'' lags badly on the lowest settings even on the ''menu screen'', even with a good graphics card. None of the controls can be remapped -- in fact, there isn't even an in-game guide to the controls. This is horrible because the default control setup forces an {{JustForFun/egregious}} use of the mouse in situations where buttons should be (and in the 360 version, were) used. |
| 268 | * ''Franchise/StarWars: VideoGame/TheForceUnleashed'' had a long-awaited/delayed Windows version that was inexplicably over 30 gigabytes, and has very few options for scaling the game down. It runs fine on a fairly decent rig, but there are no options to tone down the graphics for older machines. The game isn't very well optimized, so while a decent computer will run it with few problems, a mid-range system will choke. The keyboard and mouse controls are also extremely clunky and cumbersome, and the only gamepad supported is the Xbox 360 controller. |
| 269 | ** The game did allow you to rebind the keyboard and mouse controls, so you could pick a more logical setup. However, the game wouldn't update the on-screen prompts for quick time events from the default bindings. Good luck trying to remember what you rebound 'F' to before you die. |
| 270 | * ''VideoGame/TalesOfSymphonia'': The PC port on Steam has the internal resolution locked at 720p, the framerate locked at 30 FPS (when the Gamecube version released ''over a decade before'' ran at 60 FPS), the game crashes often or doesn't start, lagged at the options, config and save menus, has new typos, has the wrong fonts and broken or missing text when selecting languages other than English, and had incorrect button displays for the controls showing [=PlayStation=] 3 prompts. A slew of new glitches were also present in this port. The port also had additional [=VMProtect=] DRM software and had only six save slots on launch, though some of these problems were patched out and [=VMProtect=] was removed entirely while the latter has been fixed. |
| 271 | * The PC release of ''WesternAnimation/{{Tangled}}'' was left with a half-assed co-op mode where for some strange reason, ''only the second player'' can use a controller while player one is forced to make do with a keyboard. Pity the poor little girl whose dexterity is not that refined enough to play as Rapunzel using the WASD keyboard control scheme (you can, however, adjust the default keyboard mapping, though), as what Steam reviews from disgruntled parents can attest--apparently, the porting house responsible for the Windows conversion forgot to note that the game's target audience is ''small children'', not first-person shooter players. And to add insult to injury, the Windows release was left unpatched at 1.0, effectively abandoning it soon after release. Sure, it is a tie-in game, but they shouldn't have released it on Steam at all if they left it in such a sorry state. Though if there is any consolation, a rudimentary online co-op mode is available on the Steam release of the game via Steam Remote Play Together, and best of all, it doesn't require the second player to own a copy of the game, either. |
| 272 | * ''VideoGame/{{Toukiden}}: Kiwami'''s PC port has been met with heavy backlash. Video options are sparse (e.g. cannot go beyond 1080p, no 16:10 resolutions) and does little to make the game look any better. The game is locked at 30 FPS, and if you try to unlock the frame rate, the game becomes unplayable as the animations and physics are tied to the frame rate so the game runs faster than it should, nor does its Steam page warn customers about this. The game is poorly optimized with demanding system requirements (an [=i7=] for both minimum ''and'' recommended) and will sometimes slow down in certain areas even if your machine meets the ''recommended'' system requirements. Certain video cards and Windows 8/8.1 combinations cannot run the game at all and crash if you try to play it. Keyboard controls are poorly implemented, using the mouse will sometimes freeze the game when there's no mouse support at all, and despite recommending a gamepad and using Xbox 360 prompts, only a few are supported and analog sticks don't work properly. |
| 273 | * The Windows 95 port of ''VideoGame/ToyStory'', on top of already missing many of the graphical effects and the level "Really Inside the Claw Machine", has heavily mangled controls compared to the console versions, with Woody's jumping being much more floaty and less realistic than the console counterparts. His whip also has extremely strict collision detection, making it very hard to actually aim at enemies and adding a ton of FakeDifficulty to an already NintendoHard game, and making the bosses nearly unplayable. By far, though, the biggest offender has to go to the RC stages -- they were already notorious enough for being difficult due to being hard to control in the console versions, but they are outright ''unplayable'' in the PC port, with the controls being so overly sensitive that it's impossible to aim at anything. It ''does'' get a red book soundtrack on the plus side, but that's far from enough reason to pull it out of this territory. |
| 274 | * The PC version of ''WesternAnimation/ToyStory3'' was for whatever reason based on the cut-down Wii port of the Xbox 360 and [=PS3=] versions. Some levels and cutscenes were omitted, and that's even when a low-end family computer could shrug off those removed levels at low settings anyway. |
| 275 | * ''VideoGame/VirtualOn: Operation Moongate'' was a decent port but it unfortunately became this over time due to a horrible game-breaking bug where the game crushes after getting a Game Over with any Virtuaroid other than Fei-Yen for some reason and ending a match on Versus Mode due compatibility issues on Windows Vista and later. |
| 276 | * ''VideoGame/VivaPinata'' has a PC version notorious for slowness and occasional crashes. The worst part of the game is that the coveted Chewnicorn, the game's rare Unicorn Piñata, is colored incorrectly and, due to a lighting glitch, ''glows black'' every three seconds. |
| 277 | * Games running with [[MediaNotes/UnrealEngine Unreal Engine 4 & 5]] are criticized for stuttering issues, even with high end machines such as ''[[VideoGame/FinalFantasyVIIRemake Final Fantasy VII Remake Intergrade]]'' (it was priced at $70), ''[[https://www.youtube.com/watch?v=tkspRdejBSM Sackboy: A Big Adventure]]'', ''VideoGame/EvilWest'' and ''VideoGame/HogwartsLegacy'', mainly due to the shader compilation for not enough to precompile enough to all shaders in the draw distance with certain builds. It is matter worse when any GPU driver updates requires to reprecompile the shaders for restuttering process. |
| 278 | ** ''VideoGame/TheCallistoProtocol'' has come under heavy fire for having severe lag, compounded with the required use of the performance zapping anti-piracy DRM tool, Denuvo. These issues cause users to leave very negative reviews on Steam. |
| 279 | ** ''VideoGame/StarWarsJediSurvivor'' suffers from [[https://www.youtube.com/watch?v=uI6eAVvvmg0&t=0s significant frame stuttering, lag, and graphics dips]] to the point of being nigh unplayable on PC, even with the option to run the game in "performance mode". The cutscenes also suffer audio issues and often break entirely. Even on Patch 7.5 which fixes most of the problems and the [=GPU=] driver upgrades, the game still have issues with performance to concern unoptimized (compare to the console versions). |
| 280 | * ''VideoGame/WatchDogs'' on PC was purposely made to run on [=nVidia=] hardware, and [=nVidia=] hardware only.[[note]]The 8th-gen console versions were optimized for AMD hardware since that's what they have.[[/note]] If you don't have [=nVidia=] hardware, then you're screwed. You will experience framerate drops and crashing/freezing galore, even if you have a computer that can run contemporary games on their highest setting flawlessly. Also, like many other Ubisoft games since 2012 or so, [[ArsonMurderAndJaywalking the game requires the use of UPlay regardless of where you buy it from]]. Another problem is that modders found that the coding for the absolutely ''amazing'' graphics configuration settings shown in the E3 demo were in the game and performed absolutely fine if they were added back into the game, leading to backlash and widespread allegations that the quality was tuned down so [=PCs=] didn't overtake the Xbox One and [=PS4=] in graphics fidelity. While [[VideoGame/WatchDogs2 the sequel]] had a slightly better port, it has one major flaw - with some graphics card and processor combinations, the game would ''refuse to load''. |
| 281 | * ''[[VideoGame/{{Wipeout}} Wipeout 2097]]'' lacks a speed limiter in PC versions, causing the game to run out of control on top of the line [=PCs=] back in '97, never mind today (this can be fixed with a CPU-killer program, but then you will find out the hard way that Windows Vista/7 require a lot more CPU to run properly than the game). The game also has a different soundtrack that's nowhere near as good as the original. |
| 282 | * ''VideoGame/WolfensteinIITheNewColossus'' was clobbered with negative user reviews on Steam, most complaining about technical issues: poor performance even on high-end machines, constant crashes, save data getting corrupted, and so on. |
| 283 | * The 2020 remaster of ''VideoGame/{{XIII}}'' is a dumpster fire in pretty much all aspects save the level design and that's only because the levels were copied wholesale. The distinctive cel-shaded art style is gone in favor of a bland ''Fortnite''-looking style. Controls sometimes don't work or get stuck. Enemy AI is braindead, sometimes not noticing the player standing out in the open and not reacting when getting shot or bashed. Weapons have no weight when firing. Enemy ragdolls are janky, drop frames when falling, and fall into a rigid neutral pose. Sound effects don't always play. The remaster gives no incentive to buy it at its asking price when a regular port of the 2003 original is available at a fraction of that. |
| 284 | * ''[[VideoGame/{{Warcraft}} Warcraft III: Reforged]]'' promised to be a high fidelity remaster of one of Blizzard's most beloved games, and instead became a [[ObviousBeta broken, buggy, bloated disaster]]. [[TrailersAlwaysLie The marketing promised]] new cinematics, a revamped UI, and an enhanced storyline to better fit the lore of ''VideoGame/WorldOfWarcraft''. Upon release, none of these new features were included, and several essential features from the original (Ladders and Clans, Custom Campaigns[[note]]not to mention the intellectual property issue on user-made content in a likely attempt to avoid another DOTA[[/note]], etc) were totally gone. Instead of being a new game, it was a mandatory patch for the digital version of the original game and mandatory for the disc version if you wanted to continue using Battle.net for multiplayer. This massively bloated the file size and doubled the system requirements. As of this writing, [[GeorgeLucasAlteredVersion Reforged is the only "official" version of the game you can play.]] Even stuff as simple as the game's menu system was made more cumbersome and buggy. The game is so glitchy that the first and only tournament was ruined by connection issues. Despite promising to fix everything in patches, only incremental updates were released until development stopped entirely and the team behind it was dissolved. An internal company report revealed that the project's budget was cut midway through development and outlined why it ended up as it is. |
| 285 | * ''VideoGame/YsVIIILacrimosaOfDana'' was released 6 months later than the [=PS4=] port it was based on, and even then, after multiple delays, it was still a lousy mess of a PC port. The resolution of the game is locked internally at 1800p regardless of the resolution chosen, bringing older systems to their knees, the framerate is known to be inconsistent with random stuttering, the background music is prone to distortion upon booting the game, the KB&M controls are generally poor, the controller support isn't great with the game failing to detect buttons on occasion along with button remapping glitches, the game only uses 8-way movement despite every other version supporting the full directional movement, the game crashes frequently, the lighting model and effects are more washed out compared to the [=PS4=] release, there are numerous typos and punctuation errors in in-game text and the shadows are semi-broken. Add it all together and you have one of the worst PC ports of 2018, at a time when ports like these were meant to have been a thing of the past. Then again it was ported by Creator/NipponIchi Software America instead of Creator/XSEEDGames[[note]]As it turns out, NIS has no porting expertise of their own and normally outsource their ports to a budget porting company called ''Entertainment Support Inc.''[[/note]]. The backlash from this was so great that NIS actually contracted [=PH3 GmbH=], the company co-founded by legendary software porter Durante after his contract with XSEED ended, to ''re-do'' the port, and the result was a [[AvertedTrope complete 180]] of the trope and a really solid PC port of the game. This also cemented NIS as one of [=PH3=]'s clients soon after, as it was later announced that future ports of Falcom games to the PC from NIS will be done by [=PH3=]. |
| 286 | * The PC version of ''VideoGame/ZombiU'', titled ''Zombi''. Despite coming out 3 years later, it somehow manages to have more bugs than the [[ObviousBeta Wii U version did at launch]]. |
| 287 | [[/folder]] |
| 288 | |
| 289 | [[folder:Macintosh]] |
| 290 | * ''VideoGame/HeroesOfMightAndMagic IV'' had its AI lobotomized at some point during the porting process from the PC, and the computer would send out one day's worth of troops to try to kill a horde of mid-to-high level monsters. This was somewhat amusing in maps where you weren't tasked with the defeat of a specific hero, but when you ''were''... well, you just had to hope that said hero wasn't allowed to move from his starting position, because you didn't get credit for the kill if you weren't involved in the fight. |
| 291 | * ''VideoGame/MafiaII'', ported by Feral Interactive was just as disastrous as the Platform/PlayStation3 version, not because of the lack of grass and blood but because it was ill-optimized compared to the PC version, churning out 15-20 FPS even on a reasonably powerful Macintosh. |
| 292 | * ''VideoGame/SimCity 3000'' was not made in-house by Maxis, and its quality reflects this. It was ported by a Ukrainian company that left the entire PC interface (such as the file hierarchy system) intact, all while leaving out other features (such as the Building Architect Tool). |
| 293 | * ''VideoGame/SimCity 4'' was also outsourced and was released months after the PC version. It was terribly slow to the point of unplayability, left off the official tools that PC users got, and exhibited behaviors that PC gamers would only get if they had a plug-in conflict. In fact, for owners of Intel-based Macs, running the Windows version via a compatibility layer such as Wine or Crossover Games is preferable in every way. |
| 294 | * The OS X version of ''VideoGame/ThePinballArcade'' was apparently a direct port from the [=iPad=] version. This means it has an interface meant for touch screens for a keyboard instead, as well as the [=iPad=]'s resolution. While some of the issues (but not all) have been fixed, a few specific tables would also exhibit strange behavior--for instance, if one App Store review is to be believed, the ball will occasionally fly right off the ''Pinball/WhiteWater'' table, never to return. |
| 295 | * The Steam version of ''VideoGame/RollerCoasterTycoon'' Classic is considered inferior not only to the second game that it uses the engine from but even the mobile version. It's actually impossible to quit through conventional means - you have to either press Cmd + Q or minimize the program and do it there. It's impossible to zoom in/out unless if you happen to use your mouse's wheel (good luck if you're only using a laptop). Importing scenarios/rides is impossible to do the "conventional" way because it still uses the instructions from the mobile version. You have to actually go in the actual folder of the game and manually drop them from there - and even then, the game recognizes it as a "suspicious file" (although you can still play the imported content normally) and constantly reminds you to reinstall it. |
| 296 | * [[https://youtu.be/pFqKj5bbuFo The Mac version of]] ''[[VideoGame/TestDrive The Duel: Test Drive II]]'' had only black & white graphics support despite the first Color Macintosh being out for over a year by the time of its release, a barely playable framerate even on faster machines, and atrociously lo-quality audio reminiscent of listening through a blown-out speaker. |
| 297 | [[/folder]] |
| 298 | |
| 299 | |
| 300 | [[folder:Linux]] |
| 301 | * In general, Linux ports released in response to Steam announcing support for it tend to be optimized for the latest version of Ubuntu at the time, and no other distro/version of Ubuntu. The further you get from that Ubuntu version, the better it would be to just run the Windows version via MediaNotes/{{WINE}} or gaming-optimized forks of it like Proton. |
| 302 | * The Linux release of ''VideoGame/QuakeIV'' requires a CD Key, as well as an existing installation of the Windows version of the game. If that's not inane enough for you, there's another catch: the GOG release does not come with a CD Key. Basically, if you have the GOG release, you're stuck playing in Wine. Thankfully, you already have the game installed in Wine because this port was developed by monkeys. |
| 303 | * Sega Genesis & Mega Drive Classics on Linux has a nasty bug on some computers where the ROM's video completely cuts out when put in fullscreen, forcing you to play with the smaller Game Room TV. Potentially infuriating but otherwise playable if you meet the recommended specs, but if you only meet the minimum, games played this way can develop severe input delay that worsens as you go, almost immediately rendering most of the games unplayable. |
| 304 | * The Linux port of ''VideoGame/Borderlands2'' initially averted this by being on par with the Windows version in terms of content and superior to the Windows version in terms of optimization that the game ran smoothly on lower powered hardware compared to the Windows version. However it eventually devolved into this as Gearbox chose to tear up their contract with Aspyr, barring them from further updating the Linux version of the game, while in the meantime adding a new free DLC to the Windows version and changing the version number so Linux users no longer have cross-platform play with their Windows counterpart. At this point, those wanting to enjoy the final DLC or continue playing with their Windows counterparts had no choice but to install the Windows version and play using Proton. |
| 305 | * The port of ''VideoGame/{{Civilization}} VI'' is... bad, to say the least. The good news is that it doesn't crash or have a GameBreakingBug, but it's all but mitigated since turn times took 50% longer compared to Windows on release, which increased to a whopping ''three times longer'' when the DLC ''Gathering Storm'' came out - and that's not even considering general sluggishness just panning and moving units around on the map. All in all, the performance issues making it feel like you're playing the game on an old machine from the 2000s makes the game nearly unplayable. |
http://tvtropes.org/pmwiki/context.php
FollowingContext PortingDisaster / Computers
Go To
- Show Spoilers
- Night Vision
- Sticky Header
- Wide Load
