วีดีโอ

Hi, google "kaos dos game" and you should find it easily.

Maybe some of the sound effects were used as placeholders to be replaced later in a final version that never came out. It's an interesting title, made by 3 guys, with a proprietary engine. Development started in 1995 but then things lagged behind. Eventually they released the latest build in 2003. Fun fact, at the initial stage of development the game was supposed to be a homeless simulator called Barboon :D

@@reloaded_ Very interesting. Thanks for the details.

Well, "great" compared to the DOS version (which this port is based on). It's definitely a visual improvement over that. It's indeed a rushed port: higher resolution, bilinear, and not much else... but it was exclusive for the underpowered Rage cards, where it ran abysmally, so I guess the devs didn't put much effort into it. The code was also a bit of an unoptimized mess from the start, as Wipeout on DOS struggled even on mid-range Pentiums, and exhibits many of the visual issues you can find here (some of which are exacerbated by the wrapper here). However, I think if it had been released for the Voodoo instead, running at decent speeds, it would have been a hit at the time, even if it was visually identical to this, just my two cents :D

It was the game that sold me on a 3Dfx card... such a leap in graphics and framerate... and that lens flare! :D

@@reloaded_ same thing for me with my amd k6-200 and my matrox mystique and my maxi gamer 3dfx (later replaced by a voodoo banshee then a riva tnt 1), i was blown away by the bilinear at the time ahah

It was one of the first games published directly by Sega in '95, along with Tomcat Alley and Ecco the Dolphin (with the Sega PC label).

The horse is present in all Saturn versions of Daytona USA, Circuit Edition included. In CE there's Uma (Brown horse) and Uma2 (Grey horse).

@@reloaded_ thanks for the cool info

True, we tend to forget how much PCs of the time struggled with 3D games.

I remember this game not running fast enough to play - and I really think it was a 100Mhz 486, IIRC, that I was using.

Yep, the handling is very poor, the less you steer, the better.

I'm playing in first-person/cockpit view: the game has a very "wobbly" camera, especially in 3rd person, (I've read that's an in-game bug caused by the camera being affected by the physics engine...) but the issue it's way less evident with first-person view.

It's either too fast or too slow depending on what's on the screen... it's somewhat playable with a fixed cycle count, but you still get huge slowdowns near planets or big ships, so you have to manually increase the cycles in those situations... but if you set them too high then the joystick start to drift... so it's a bit of a mess. The best way to play it is by using the unofficial patch, that basically transform the DOS version in the Windows 95 one.

No problem, be my guest.

@@reloaded_ Thanks!

Hi, I'm on vacation so I can't check, and it's been a while since I played it so I don't remember exactly, but try using OTVDM (if the installer is 16 bit). Then dgVoodoo should make it run. If I'm not mistaken you also need to limit the framerate to 30, (with Rivatuner or else) otherwise it runs too fast. Hope this helps.

@@reloaded_ Please enjoy your vacation there's no rush. It's a 32-bit application but I got the game installed, but something's still wrong. When launching it's a black screen and if I stop the A2MOVIE.DAT process it shows the main menu. But if I select start it crashes and shows both: "initlib.cpp(1014) : could not set display mode (operation is not supported)." and "pal.cpp(135) : could set entries (undefinted error condition)". If I select exit it crashes and shows: "initlib.cpp(1014) : could not set display mode (operation is not supported).". And if I Alt-Tab it crashes and shows both: "clipblit.cpp(622) : restore xvga_screen (surface was created in different mode)." and "initlib.cpp(1014) : could not set display mode (operation is not supported).". When installing it also says I require DirextX 3 and NT Service Pack 3 and that Service Pack 0 was detected.