83 replies to this topic

[English learner]

Don't wanna let you down,but I am sure it doesn't work(2CD Version) on my X64.I wonder if there is someone else who have tested it on win7x64.
In fact,it doesn't matter as Ion(Nvidia 9400M) doesn't cause much compatible trouble during playing.

[WDeranged]

I've just got myself a Radeon 5970 and was pretty blown away to find that PST works without any of the graphical issues that plagued me with my Geforce, the only issue I'm getting is slowdown when lots of NPC's are on screen, has anyone found a workaround for this?

I'm on Windows 7 by the way, I tried the compatibility toolkit but performance is almost identical

The d3dwindower will probably fix your problems.

I didn't like the d3dwindower/shiftwindow method, it felt a bit sluggish so after a bit of digging I found another method for Windows 7, download and install the DirectX SDK from Microsoft and run dxcpl.exe (*install folder*\Utilities\bin\x86), this allows you to disable Directdraw hardware acceleration.

The only downside is mouse trails and no vsync, not a perfect solution but the the game is at least running full speed and glitch free

[ghostdog]

I had issues with mainly the cursor trails. I tried to use the windower along with that other program to make it full screen with the fixed cursor.

But for some odd reason no matter the resolution I put on the window it always runs it full screen and I still ave the trails.

If you have trails it means that you've disabled direct draw acceleration and that may cause the problem, since d3dwindower probably needs ddraw enabled in order to emulate it. Re-enable it and try again.

[ghostdog]

The mouse trails appear only when you've turned hardware acceleration off, as far as I know.

[Creb]

Don't wanna let you down,but I am sure it doesn't work(2CD Version) on my X64.I wonder if there is someone else who have tested it on win7x64.
In fact,it doesn't matter as Ion(Nvidia 9400M) doesn't cause much compatible trouble during playing.

I run windower and Torment just fine on win7x64.

Anyways, just wanted to thank Ghostdog for this. Playing Torment again after a decade or so was unbearable without this fix.

Also, I use autohotkey to remove the window border/title so you don't have to play around with the resolution to accommodate your taskbar. Aka 'full screen windowed mode' as found in modern games. The script is:

^f::
WinSet, Style, -0xC40000, A
WinMove, A, , 0, 0, 1920, 1200
;WinActivate, A
return

Once you load it, pressing cntrl + f will work the magic. Replace 1920, 1200 with whatever your desktop resolution is.

Now, the only issue(s) I've had are a few crashes when the game goes to load a cutscene. Sometimes it'll work if I delete the cache and restart the game with the last autosave, though I had one instance when you are leaving the the alley where your body was found to go to the lower ward where the cutscene trigger crashed about 10 times in a row before I gave up and ran it without windower. Coincidentally or not, I had no problem loading the cutscene. Of course I returned to using windower after this workaround so I could use spell effects without wanting to kill myself. ;p I have no idea if that was related to windower, but it was a strange, seemingly coincidental workaround, so I thought I'd mention it.

The other minor problem I have which is not related to windower at all (happens regardless of using it or not), is the rare and seemingly random crashing on zoning. Restarting and reloading one's last autosave works, though I had one incident in which I could reproduce this almost 100% of the time. If I zoned into the midwife's hut (after I had already zoned in and out once successfully; so basically every time I returned to turn in a quest), it would crash. However, one of those crashes didn't occur till a few seconds after successfully zoning. In that instance, I clicked on the midwife to initiate dialog and she ignored me. Several seconds later, it crashed. Whether this sheds any light on the cause of these zoning-related crashes, I don't know. I have read that crashes tend to be associated with the widescreen mod, but my understanding is that those are related to not starting a new game, which is not the case here. I'm assuming something gets corrupted randomly. Thank goodness for all the autosaving on zoning so you loose nothing.

Again, ghostdog, thanks for all your work!

[ghostdog]

Hello, I tried to use this fix on my GOG copy of planescape Torment, but as soon as I start it up the screen goes black, I get a blue screen and a forcereboot... worst this is that the third time around it blue-screened without even booting the game. This could mean hardware problems, but im on my OSX partition now and everything seems fine... help? Im on Win7x64, I istalled all the GOG recommended patches plus the nvidiafix.

The fixes in this thread are considered obsolete since aqrit created the DDraw fix. This is stated clearly in the first post. Have a look at this pinned thread.