Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.

Warning for game developers: PCGamingWiki staff members will only ever reach out to you using the official press@pcgamingwiki.com mail address.
Be aware of scammers claiming to be representatives or affiliates of PCGamingWiki who promise a PCGW page for a game key.

Topic on User talk:Osprey

This is a permanent link to the first version of this post. You can view later versions on the post history page.

Spending probably too much time researching and testing fixes for classic and obscure games? You and me both, hah! Anyway, I figured out what my problem with dgVoodoo was (and why I didn't see the forced AA/AF). Either dgVoodooCpl.exe or dgVoodoo.conf has to be present in the game directory (alongside the wrapper dlls). I assumed that it would be enough to run the Cpl from its own directory, and that its config file (once created) is later read at the game's launch. Nope! The documentation for the wrapper, as detailed as it is, doesn't mention it, either.

About JKDF2.com, I believe these fixes still hold true, however, they are specifically meant for the original CD release. Also, your experience running JK/MotS "out-of-the-box" seeems to run contrary to mine. Were you able to run these games without any fixes? For me, the CD version (1.00 and 1.01) would always crash at launch. Adding the -windowgui let me lauch the game, but it would still give me an error when I tried to start a new game. That issue was remedied by using the AMD driver fix. An alternative solution was to use dgVoodoo, this time without the switch.

The GOG version ran from the get-go, albeit in software mode by default. Both versions would crash on startup as soon as I applied the unofficial patch. Again, using the switch+driver fix combo or dgVoodoo+no switch did the trick. BTW, I'm on Win7, with FX-8300 and HD7970. I eventually was able to run the game with all the graphic and music improvements installed; in fact I recently finished my playthru of JK to conclude that every fix works as intended.

As a side note, I figured out IMO the best way to determine whether forcing AA/AF works. Run the game in its lowest resolution (the differences are more pronounced then), take a screenshot at a static location in the game by creating a save point (has to be one where you can actually see AA/AF at work), and then compare the two screenies by switching between them while viewing. Since the effect of using AA/AF is generally hard to notice in normal gameplay, I thought it best to compare static screens.

Right. May the Force be with you, bro!