Star Wars: Dark Forces is getting another serious run on the Amiga, and this version has a very clear target: frame rate. Current development centres on getting the game moving faster across 68020, 68030, 68040 and 68060 processors, with separate attention paid to machines running with an FPU and machines running without one. It’s a broad range, especially for a 1995 PC shooter created around hardware far removed from a typical Amiga setup. This isn’t about turning Dark Forces into a different game. The goal is simpler. Cut the processing cost of each frame, make better use of each 68K CPU and get smoother play from hardware ranging from modest accelerator cards to high-end 68060 systems.
Frame rate is the main target
Dark Forces gives a 68K processor plenty to do. Its levels contain moving platforms, doors, lifts, enemies, projectiles, lighting changes and scripted events, with the engine calculating each part as the player moves through a mission. On a current PC, none of this presents much trouble. On a 68020, it’s a very different story.
A 68030 brings more speed, a 68040 moves things along again, and a 68060 sits at the upper end of classic 68K Amiga performance. Raw clock speed isn’t the only factor, either. FPU availability matters, and plenty of accelerator configurations don’t include one.
The new work takes both cases into account. Systems with floating-point hardware can use it where useful, but machines without an FPU remain part of the target. For owners of 020 and 030 accelerators in particular, this could prove one of the more interesting parts of the project.
No one expects each processor to deliver the same experience. A 68020 and a 68060 sit far apart in performance. The aim is to squeeze more from each class of machine rather than build the engine around one ideal setup.
Dark Forces asked a lot from PCs in 1995
LucasArts released Star Wars: Dark Forces for DOS in 1995, during the first big wave of first-person shooters. Doom had already set a template, but Dark Forces went its own way with the Jedi engine.
Players could crouch, jump and aim vertically. Levels used lifts, moving structures and layered spaces, including rooms placed above other rooms. Missions had objectives too, so progress involved more than finding a key and reaching an exit.
The game introduced Kyle Katarn, a former Imperial officer working for the Rebel Alliance. Its opening mission involves the Death Star plans before the story moves into the Empire’s Dark Trooper project.
Dark Forces used sprite-based enemies and objects, yet its environments asked more from a CPU than the low resolution might suggest. Rendering formed only part of the workload. Enemy behaviour, projectiles, doors, platforms and mission scripting kept the processor busy from one frame to the next.
Why the Amiga version is demanding
Dark Forces never received an official Amiga release during the 1990s. By 1995, PC games were leaning heavily on faster x86 processors, and the gap between mainstream DOS hardware and standard Amiga models had grown difficult to ignore.
The Force Engine later opened another route. It recreated the technology needed to run Dark Forces and made ports to other systems possible, using the original game data for the commercial assets.
Getting Dark Forces running on AmigaOS was one challenge. Getting it running well across several generations of Motorola hardware is another. Here’s where the optimisation work matters. Code which barely registers on a modern processor can become expensive on a 68020. A calculation suited to an FPU may need another approach on a machine without one. Memory access, rendering routines and repeated engine tasks can each take a meaningful share of frame time. Small savings add up quickly.
From 68020 to 68060
The wide CPU target gives this version a different character from an Amiga port built only for top-end hardware. A fast 68060 remains the natural place to chase the highest frame rates, but support for 020, 030 and 040 systems means optimisation has to scale across the range. For players, the idea is easy to grasp. Fewer processor cycles spent on each frame can mean more frames per second when the rest of the machine keeps pace.
Dark Forces won’t suddenly turn into a lightweight game for a stock A1200. Its engine, level design and game logic still come from a PC title released during a period of fast hardware development. A better-tuned 68K version can still make a noticeable difference across accelerated Amigas. For this project, frame rate isn’t a side benefit. It’s the main job.
MORE AMIGA & RETRO NEWS
Beyond the Motorola ceiling: can FPGA take Amiga 68K to 500 MHz?
Jedi Knight: Dark Forces II gets a native original Xbox port
Amiga and Hyperion agreement: full breakdown of AmigaOS rights
41 years of Commodore Amiga: 41 facts about the legendary computer
Copperline 0.9.0 released with major FPU and Amiga emulation accuracy improvements
Perfect Dark enters VR with new unofficial Meta Quest and PCVR port
Dark Lands for PlayStation Vita brings dark fantasy combat to Sony’s classic handheld
Amiga beyond Commodore: how outside companies built its gaming, video and software legacy
The Phase5 story: Amiga 68060 Power, PowerPC dreams and the end of an era
Amiga Bill documentary revisits the Motorola 68060 with Joe Circello
What if Dell won the Commodore auction? The Amiga’s lost future
Motorola 68000 to 68060 history: how the 68K family powered the Commodore Amiga
50 Amazing games you can play on AmigaOS 4 and AmigaOne computers
The 50 best Amiga games of all time: a nostalgic journey through the Commodore era
Star Wars: Dark Forces is getting a remaster