Search results

After getting stage exports fatigue caught up with me and I was out of it for about a week. For the models, I skipped over vertex normals, textures, vertex colors and indices alpha in favor of rendering the vertexes and faces correctly. So I need to go back to .nj and start adding those in...

Schedule is posted here: https://gamesdonequick.com/schedule

You need Nodejs installed on your computer and the exe file can be downloaded from github.

You need Nodejs installed on your computer and the exe file can be downloaded from github.

For weapons, right now the easiest thing to do is use PSO version 2 as all of the weapon models are in ItemModel.afs as .nj files. For .xj files, I can parse out most of the information from the file, and have managed to get some half decent model exports, but nothing complete yet. If I can get...

I was just about to send you a message after seeing your post on Pso-World. If you need any help with extracting assets let me know. Stage models exports are still in the early stages, I'll be playing around with applying textures, and culling, so we'll see if/when I make progress on that end.

Thanks! Planning to? Short answer: no. With exporting you can skip over a lot of tiny details to export the model. Going the other way you'd need to perfectly understand everything. On top of that, there's collision and lighting, qedit stuff. So it's a pretty massive time investment. So I'm...

Good news, stage models can now be exported. Source code is here if anyone likes that stuff or anything. Basically the stage files are a list of sections with an offset. Inside each section is a list of nj files. The nj files are rendered for each scene, and then rotated and moved as a scene...

Still missing textures and a other details when it comes to processing ninja-chunks, but the source code is up on github here if anyone wants to take a look.

I finally managed to parse and render .nj thanks to Kryslin's ExMLD.Net source. I'm going to start working on textures now, but I finally got the model structure working.

I was hoping to cut corners by focusing directly on stages, but it looks like pso version 2 stages use nested nj objects and not just listed ones like in PSOBB, which means I need to go back and finish exporting nj before I can get back into stages. This is mostly to help me write out...

Well there are more client side assets that can be exported or modded if anyone wants to focus on those.

I don't think that language implementation really matters beyond preference as far as PSO private servers go. I'm mostly curious about the motivations. With well established communities and implementations like Tethealla and Sylverant, does the server really need to be ported to another language?

I've spent the last couple of days playing around with NJ. The file format is pretty simple, node, model definition, vertex list and polygon list. The node and mode definition are both static types, so reading those is super easy. The vertex list has a 8 byte header on the front...

Reggie Watts - Fuck Shit Stack

Okay added Afs_Export and Gsl_Export to NPM this morning. Source code is over on Github if anyone wants to take a look.

Okay did some npm cleaning. I removed all of the existing packages and re-published them with names that made more sense. 1. BML_Export 2. NJM_Convert 3. Ply_Motion 4. PVM_Export Also I started playing around with PVM and managed to export an archive all to png format from the command line. I...

Don't forget there's also Sylverant for comparing source code. I played around with the server a little bit, but not much. You can get Teth running on your local machine to test how it works as is. The MySQL implementation and table structure is pretty simple to get familiar with. You can write...

Okay, updated my Github page so it almost looks like a project, almost but not really. Also Soly, I'm not sure if you're using any of my poorly written source code, but you might want to look at my updated source for BML archives. PSO version 2 has 16 bytes of zeros between each file in the...

No need to argue. For me it's mostly personal preference, I'd rather be able to be able to do everything from the command line, but drag and drop is nice, and GUI's are simple and intuitive to use. That's part of why I'm trying to document everything and make my source as open and clean as...