QuAdEd

[FrikaC]

Huge, obtrusive, redundant screenshot!

[Entar]

If nothing else, you can always just use CIA-1, which seems to be pretty popular, and works well.

[FrikaC]

We already went through this, it's too involved to bother for something so meaningless.

[FrikaC]

I'm starting to doubt if I should continue QuAdEd at all, it's really shoddily put together (I've been thinking about how much easier some of it would've been had I used C++, it's actually kinda object oriented already, in a weird sort of way, but it would really benefit from some added uniformity)

[frag.machine]

I'm starting to doubt if I should continue QuAdEd at all, it's really shoddily put together (I've been thinking about how much easier some of it would've been had I used C++, it's actually kinda object oriented already, in a weird sort of way, but it would really benefit from some added uniformity)

I wish I had more time and knowledge to help you on this. A model editor for Quake is a much needed tool.

[FrikaC]

It's ironic, the model editor is the part I have the most ideas for, but it's also the part I find myself working on the least. Mostly because I don't know enough 3D stuff to make it work quite the way I want - that and some difficulty with skins.

Right now the model editor loads the skins in almost raw. It's supposed to then up convert them to 24bit for texturing the models in OpenGL, but that required the program to know about the palette. I just got through implementing palette loading like last week. So that's now possible, but I'm starting to wonder if I should switch to Direct3D rather than OpenGL - it would be an almost entire recode of that part of the program.

Also wondering about plugin support. I bent over backward for farc plugin support, and it was a completely ignored aspect. That was likely due to the inadequacies of farc, however - it was bug laden and horribly unfinished.

Fimg has plugin support, I believe. There was a lot of code in there for it, I'm not certain if I went ahead and did the final steps to make it work, however, but it's interesting to note that no one even asked about plugins.

The amount of code to allow plugins in Quaded would be enourmous, just based on the sheer number of things it can do and would have to expose. However, with key things exposed to the plugin API, some pretty fantastic things could be coded for it. I may support farc plugins just for the whizzbang nature of it, because there's a ton of them already done and for formats I don't feel should be core to Quaded.

[Urre]

I've noticed some people generally seem to have a natural resentment for plugins, so one shouldn't be too surprised if no one cares about plugin support. I personally like it when the developers have such a stable and featureful plugin system that they have very few core features, if any, and just make all features be plugins that come with the program. This kind of an attitude towards editors and their development often tends to inspire others to actually make more plugins, than editors with a plugin system added in for the fun of it. I still best like it when programs just have really solid core features, no plugin system needed.

Why d3d?

[Quake Matt]

Yeah, I think Urre's right about plugins. I'm not a huge fan of them myself and often, on the rare occasions that I do use one, it's to get access to functionality that really should have been in the program in the first place.

[Up2nOgOoD[ROCK]]

FrikaC I was using Fimg a few days ago and I was dissappointed to see that there wasn't a "export all files" function for wads. Could you please add this to Quaded?

Btw great work, and hope to see some releases soon.

[FrikaC]

Export all files?

[leileilol]

aka poop out every texture from a wad file into a bunch of bmps, something wally already does

[FrikaC]

I could do it, but it's not how fimg thinks of a wad nor is it the way quaded will ultimately work. I think Quaded will use the farc 'interpretation' of a wad, ie, the correct way to think of it - as an archive containing mip & lmp files (among other things, palettes, raws etc)

Fimg's hacked on wad crap made it interpret a wad as an animated image format, which is bizarre and silly. The task you mention is "Export the first frame of every image group as a separate file using the group name as the file" in terms of a Fimg command, which is really kind of odd. Unless you want it to export .mip files, then I might be with you on that one.

[Up2nOgOoD[ROCK]]

Well, as any format. Exporting as .pcx would be easist for me, but anything will reduce the workload ultimately =)