Search results

Great work!

Nah, I'm not bothered. I have been very busy, though; I just moved into a new apartment and still have a bunch of stuff to unpack. Apart from that, I've been working on some modifications to clang to support my feature proposal, and of course there's always my day job. I honestly expected to...

Correct. The only other way would be to add new resource IDs for the new files, and then make a new version of the executable that referenced those IDs. Which is doable, but not something I have a lot of time for right now (otherwise, I'd be doing more wcdx work).

Trust me on this one: It's install.dat. I've spent considerable time going through the code to create wcdx. I wasn't aware that the DOS version did things differently, but KS definitely uses install.dat as a resource manifest, not just for installation.

The files are referenced in install.dat. Each 16 bytes in that file comprise a reference to a resource file: Bytes 0-12: File name Byte 13: disk (as in, which floppy disk the file originally shipped on) Byte 14: Not sure Byte 15: Resource ID The resource IDs can either be 0xFF, in which case...

Your best approach is to: 1) Install Kilrathi Saga. This can be as simple as unzipping the files from the PC Gamer distribution. 2) Apply my patch. My patcher will only run if the target EXE has a known hash value. 3) Edit the EXE as desired.

I'm definitely planning to add her. Y'know, once I get back to having the time to work on this...

Apologies if that came across as sardonic; that's not the way I meant it. I just think it's neat that the game had the achievements concept long before anyone else had really thought of it. Note that I'm not talking about medals. I'm talking about the ribbons that appear above the medals...

Wing Commander 1 already has achievements. They're called ribbons...

Boy, that brings me back... For me, the best ship I could use was the Ferret. Unfortunately, I seem to recall that at some point you go up against something that requires torpedoes, so the Ferret couldn't actually win.

More to come...

This is a great idea; I'll be sure to use this as I continue working on wcdx!

One of these days I should try testing my software before distributing it...

What operating system are you using? Edit: Never mind, I found the issue; I was unwittingly using CLSID_WICImagingFactory2, which was introduced Windows 8. I only needed CLSID_WICImagingFactory1, which is available in XP SP2. I've rebuilt the image program and attached it to this post.

It's doable, and certainly a lot easier for KS than for the DOS version, but I'm prioritizing the basic functionality of the games above any enhancements. I'd prefer to get each of the games (including WC2 and WC3) fully operational before moving on to this sort of thing.

Since nobody has posted any new issues with the beta, I've gone ahead and rebranded it as 1.2. There are still a number of issues that need to be addressed, but I think 1.2 is in a good stable place right now. The next release will be 1.2.1, somewhere down the road. I have a number of non-WC...

Ah, I see; that makes a lot more sense. You are correct; the mouse isn't moving. I removed the calls to SetCursorPos for two reasons: If you're playing the game in a window, or if you've temporarily switched to another application, having the game wrench the cursor away from where you...

Glad to hear it! I'm a bit surprised that you're encountering mouse issues immediately after launching. I've been alternating between using keyboard and a gamepad and haven't had that happen yet. Are you moving the mouse around somehow? Nudging it, maybe?

I've just released 1.2-beta4, which addresses a number of issues: I've reworked mouse handling in Wing1 to work the same way as it does in SM1 and SM2; let me know if this fixes your issue. This should be fixed now. This should be fixed now. Additional changes: Fixed crash on minimize...

That's my bad for not being clear. The image executable works on image sets that have already been extracted from the resource archives. The briefing.vga file is a resource archive, not an image set. Before you can extract any images, you'll need to extract the resources from the archive...