pyxlz

Set up the ip and port in the config file. You'll need to connect to a server that allows vie clients though.

try connecting to a server

The network code is probably 95% complete. All the standard subspace protocol is implemented. Continuum specific packets are not in. I've been playing on local servers for continuum 0.37/0.38 (there is a problem with level checksums right now, so it'll kick you out in a few minutes). If there's been any updates since then it probably won't work. On that note, if anyone has do!@#$%^&*entation on protocol updates, a reference would be nice. www.openal.org I've included a slightly updated version of the client. The zip includes openal32.dll subdemo_11_11_2005.zip

On my computer...?

You need to extract it in the continuum directory. It depends on the graphics and sounds from continuum. Alternatively, you could copy all of the graphics and sounds into the program directory. There should definitely be better error messages and handling of this though. You're right, I should OpenAL, were there any other dll's that were missing?

!@#$%^&*o everyone, I've seen a bunch of activity regarding a new subspace client. I skimmed the past few topics, but was wondering if there's an "official" status report on the new client. Specifically, is there any kind of prioritized feature list or timeline for development? Especially interesting would be a list of suggested additions to the game/client. I also worked on a subspace client clone about 1-1.5 years ago, and have recently found some time to work on this old project. The latest version is attached. Just extract into your continuum directory and set up the config file. I've been testing against an old version of the continuum server (whatever version worked with 0.37, maybe 0.38?). Let me know if you have any questions, problems, or suggestions. (I've included my todo list to give you some idea of what's still not working) Enjoy. subdemo_11_6_2005.zip subspace_todo.txt

Well, I have a more or less complete client (minus prize synchronization and continuum encryption), but I haven't decided where to go from there. As far as cross-platform compatability, there's only a couple pieces of windows-specific code. Timers and threading is all I can think of offhand. The graphics are openGL and the sound is openAL. Granted there's still plenty of polishing to be done, but without anymore immediately interesting technical problems, the project has fallen a bit on my priorities.

That's what I thought too...until I got banned.

Having my own zone up works fine for small scale testing, but you miss things that crop up using a larger population.

Are there any zones out there, with population ~10+, that allow the vie subspace clients (even as a spectator only)? I seem to have gotten myself banned from every subspace network in the process of testing subspace clients.

After doing some work recently, I was wondering how someone else might design a client. Given any design goal, simplicity, academic, practical, extensibility, etc. - what would your architectural model look like? I'm more refering to code structure, but given free reign how, if at all, would you improve/redesign a subspace client (e.g. change the Hud layout)? I've attached the model (note that it is not exhaustive by any means) I've been using and welcome any comments/feedback. I'm really curious, though, as to how someone else would have done it.

hex and stuff....hmm... I suppose I thought cracking typically involved decompiling, and trudging through !@#$%^&*embly and memory - not my idea of a good time . Like I said before though, if you have any references or want to provide code or algorithms, please feel free.

well the only stuff I'm missing is the stuff that I'd have to fool around with the !@#$%^&*embly to get, so door sync, cont encryption, that's about all I can think of offhand. And I have some stuff that doesn't exist in the continuum client. Snrrrub may have code for the door synch. Shrap is also sync'd. ctmenc is tough. you need to write a virtual machine to rip it, whether starting from a deadlisting or reading the code in memory (which is my fav apprch) Cracking was never really my area of expertise, so it's on the bottom of my priorities now. But if anyone wants to make a contribution, I'm more than open to that.

well the only stuff I'm missing is the stuff that I'd have to fool around with the !@#$%^&*embly to get, so door sync, cont encryption, that's about all I can think of offhand. And I have some stuff that doesn't exist in the continuum client.

a bunch