Het forum

GOG.com - Starship Titanic

Now it's only impossible to complete

Auteur Antwoorden
curtinparloe Vrijdag 8 Juli 2016 om 19:20
curtinparloeAnonymous

Wine version: 1.8
Distribution: Mac
Distribution version: 4.2.10
Graphics card: Intel Iris Pro
Graphics card driver: Using El Capitan
Comments:

Starship Titanic is a technological marvel. And it cannot possibly go wrong.

Seconds into its maiden voyage it crashes into hyperspace, vanishes… and collides with your house.

A ridiculously difficult Myst-style game by Douglas Adams.

 

Well, this was a nightmare to get working! At first, a regular manual install has a few issues - the mouse pointer flickers, there's some juddering, and when Fentible the Doorbot comes down the ramp, he's replaced by a black square, and you can't get any further.

I tried different Windows versions with no change (currently on Vista).

I managed to fix the juddering with the following display settings:

GLSL Support - enabled

Direct Draw Renderer - GDI

Video Memory size - 256

Off-Screen rendering mode - fbo

Render target mode lock - readdraw

Multisampling - enabled

Strict Draw Ordering - enabled

 

I suspect Strict Draw Ordering is the only one which fixes the judder, but I'm not changing them back now...

 

The other problem is one of codecs. Every reference to ST on the internet is about the Cinepak drivers, which GOG have addressed in their release. However, inspecting the assets folder revealed that everything you see is run from video clips, and some of them use Indeo 4.1.

I installed the older Indeo codecs from here: https://www.moviecodec.com/download-codec-packs/indeo-codecs-legacy-package-31/

This seemed to crash when it started searching for Nescape Navigator, so I did a custom install and switched off internet codecs. After that it installed perfectly.

 

Now it works! I'm so happy I'm not even bothered about getting a cabin upgrade...

Aangepast door curtinparloe

curtinparloe Zondag 10 Juli 2016 om 23:54
curtinparloeAnonymous

Spoke too soon, getting this in a particular location:

err:seh:setup_exception_record stack overflow 816 bytes in thread 0009 eip 004471ed esp 00241000 stack 0x240000-0x241000-0x340000

Still, got further than I had before...