That single frame came out much better than the videos in the game in general do. Anyway, my plan is to make a few different approaches at deinterlacing.

In the wing commander pile I bought there's a wc4 too, which from the looks of it is the cd version.. so yeah, I guess that's next, once I've run through wc3. Assuming, of course, that it's a ddraw and not a d3d game. Considering that it shouldn't fix *anything*, I'm not surprised.

Did a quick experiment.. de-interlacing the videos in wc3: ..and yes, it's very blockyness is way more evident when the scanlines are doubled. It just might look better if I scale it down to 1/4 and output with bilinear filtering. Like I said, lots of things to do.. =), but at least it's...

Yay! Got the ddhack running (more or less), by feeding the game all the same ddraw caps the real thing gives. Still a lot to do, but no show-stoppers anymore, I hope.

Thanks, that helped. Now, here's something totally unexpected. http://www.iki.fi/sol/zip/ddwrap_wc3.zip That's a directdraw wrapper. It does nothing. Nothing at all. Simply catches the calls from the game and passes them along to the real directdraw dll. Untampered. Just.. passes them on...

I'll have to try it again on my netbook, to see if I've managed to break it for XP somehow. In other news, now that I know how wc3ks can be gotten to work on win7, I really, really would like to get ddhack to work with it - no way I'm killing explorer to play a game =) Unfortunately, it's...

By the way, if someone gets better result with older version of ddhack, please tell me. I'm assuming from the "black screen" people that all versions result in the same behavior - I haven't changed anything that should(tm) break the graphics output.

Looking at wc3 now - and it's doing some weird stuff. I get calls to my ddraw.dll, but it manages to draw to screen around it somehow. Fun. Maybe I'll have to wrap GDI too =)

Okay, new version. http://iki.fi/sol/zip/ddhack04.zip - wing commander 2 compatibility - configuration moved to ddhack.cfg file - couple new 'oldlcd' modes: subtleoldlcd and veryoldlcd. Veryoldlcd is rather trippy: Read the ddhack.txt for instructions on configuration options.

Ha, the only keys not mapped as far as I can tell are H,I,Q,U and Z. Maybe I should just ditch the keys and do a config file instead.

Sorry, no idea. Apart from the fact that these games seem tad bit buggy.

I'd rather not use combination of keys if possible.. WC2 has some busy loops with no event polling. It's amazing just how much "worse" the WC2 port is compared to WC1. This causes some issues, including the fact that the "old LCD" simulation gets a bit buggy on some screens (like the ones where...

Also notices the keys I picked for configuration overlap those of the games. Oops. Any suggestions which keys I should use instead?

Working on WC2 is irritating, as the game is unstable, crashes sometimes, audio stutters, and controls feel unresponsive. In any case, the current (0.3) version has the following issues with wc2 that I've already solved: - Alt-tabbing doesn't work (crashes on return) - Some screens are not...

That's the separate "old lcd" mode which you can toggle on and off with f8 regardless of the normal/bilinear/halfnhalf setting.

WC2 seems to crash on me on quit, regardless of whether I use the hack dll or not. Crash occurs in AcLayers.dll, which seems to have something to do with the windows compatibility modes... so, I guess I'll just rule that one out.

I'd guess the KS version has some kind of CD check, which obviously isn't in the magazine CD version..

Well, I'm stupified =) I do know that the win95 compatibility mode helps, but all graphics-related (256c mode, 640x480 mode, etc) should not affect things after the hack dll is in use. The game asks the dll to switch graphics mode, which I geefully ignore, and use the full-screen window...

That is very curious, as all graphics operations go through the DLL, and it definitely does not want a 256 color mode =)

The input lag is something I notice sometimes too, but there's little I can do about that. =(. As for half'n'half mode.. it's a bit heavy. Basically, it needs to copy a 1024x512x32bpp texture over to the graphics card each frame, which is 2 megs. Plus any overhead the graphics drivers may put...