[Bobboau]

for the last month or so I've been sort of working on mt own POF editor designed to maxamise ease of use and ease of expantion, I have managed to finaly get the two main features working (the tab interface and the direct x 8.1 render window) so I'm letting you all look at it,
no, it doesn't realy do much does it?
it will only open "fighter01.POF" and load one bmp texture "Fighter01-01a.bmp" it wont save and you can't even realy edit anything, but it is a begining, and I have learned A _LOT_ about MFC and Direct X and OOP in general, all data types are read but onl a few have there interface's done and none of them are realy implemented, except maybe textures and the header,
any feedback on the basic layout of the main interface

[Goober5000]

Very good.

Maybe you could make some ModelView add-ons.

[Nico]

Originally posted by Goober5000
Very good.

Maybe you could make some ModelView add-ons.

That's what I was thinking. Modelview is already pretty efficient as it is, there's no real need for yet another pof editor, but now that you have the skills, you could probably improve it on the points it is lacking?

[SKYNET-011]

Originally posted by venom2506
That's what I was thinking. Modelview is already pretty efficient as it is, there's no real need for yet another pof editor,

Except for those of us who have problems with the Descent-Network tools.

[Ypoknons]

hmm... if it'll help any, i'm getting MFC42D.dll not found problem. Something I'm missing?

[nimroy]

Im also missing MFC42D.dll, whats that file part of?

[DTP]

jesus, you lazy slugs

http://www.google.com/search?q=MFC42D.dll&ie=UTF-8&oe=UTF-8&hl=da&btnG=Google-s%C3%B8gning&lr=

[Bobboau]

well I'm learning quite a bit, I think it's rendering prety quick considering that it's in windowed mode, so this could translate directly into super fast FS model rendering, I have just gotten it to render with diferent textures for diferent polys (it was actualy quite easy given all the work I did makeing diferent vertex buffers based on texture for each subobject),
it looks like the loading PCX files is going to be a major learning experience to say the least .

and wouldn't it be nice to have a tool who's creator is actualy still active in the comunity for once

[Solatar]

Originally posted by Bobboau
well I'm learning quite a bit, I think it's rendering prety quick considering that it's in windowed mode, so this could translate directly into super fast FS model rendering, I have just gotten it to render with diferent textures for diferent polys (it was actualy quite easy given all the work I did makeing diferent vertex buffers based on texture for each subobject),
it looks like the loading PCX files is going to be a major learning experience to say the least .

and wouldn't it be nice to have a tool who's creator is actualy still active in the comunity for once

Yeah, that would be great:nod:

[WMCoolmon]

Nice work as usual, Bobboau

[Bobboau]

another good reason for me not to work with modelview is that it is a huge massavely complex peice of code, of wich I can't open all of (says something about me not haveing a germen code file or something)

[Setekh]

Originally posted by Bobboau
well I'm learning quite a bit, I think it's rendering prety quick considering that it's in windowed mode, so this could translate directly into super fast FS model rendering

You're certainly right about it being fast, it runs like lightning (well, relatively) on my system...

Originally posted by Bobboau
and wouldn't it be nice to have a tool who's creator is actualy still active in the comunity for once

Yeah, just don't get yourself banned, okay?

[vyper]

Originally posted by Setekh




Yeah, just don't get yourself banned, okay?

Nice stuff Bob, I'll try at home later. (P.S. UNI EXAMS ARE STRANGE)

[Nico]

yeah, that's true, but that means we won't have a prog that will do everything anytime soon then. At least focus on things modelview can't do first ( like creating  engine glows and dock/path ) so I can use them both

[RandomTiger]

Originally posted by Bobboau

it looks like the loading PCX files is going to be a major learning experience to say the least .

cant you simply use the FS2 pcx code?

[EdrickV]

You might want to look at the code used by POFView. And maybe next time upload a release build rather then a debug build, getting the right debug dll for a particular system can take a few tries.

[Bobboau]

code for POF view is the same as FS (I'm assuming you are talking about the pof viewer that came with the FS2 source), it's very... compex,  the more I look into the PCX format the more I wished I didn't have to write a loader for it
seeing as I havn't even started to write the save code weather it's a debug build or not is't realy important seeing as you cant even use this for anything yet

on the up side I've plugged most of the DX releted memory leaks (there is one leak caused by the dialogs not getting deleted for some reason when you close that I havn't been able to figure out), and I have implemented basic interface for almost all normal data chunks.
soon I'll add some functionality and then the save code,
then it would be worthy of a major pimpage,
I've got some realy good ideas for some cool features that no tool available today has, copy comands, data importing, UV unwraping,
also I'm going to try and get alpha blending for the thrusters and have thrusters that render the same way that the game renderes them (rather than just a simple wire frame)
but for the moment the model only spins around in a little circle that you can't stop, I need to get that user operated too

[EdrickV]

The debug/release build thing right now only changes what DLLs it gets linked with. Some people may not have the debug DLLs so the program won't run unless they search them out and install them. (And those DLLs aren't, strictly speaking, supposed to be distributed to people without the development software I believe.) And, when you get far enough for it to matter, you will want to use tooltips. No idea what each of those buttons each thing has would do. If you haven't already, you should fix the label on the texture tab, it still says current dock. Not sure why, but I'm getting a critical error sound, with no error message, when the program quits. (And for Voodoo 3 users, change your color depth to 16-bit before running the program.)

[Bobboau]

there were some memory leaks and a few bad dealocations in that build, the critical error was becase it was trying to delete something that hadn't been alocated, there are still a few leaks but they don't seem too bad for the most part

[Bobboau]

I have updated the zip, it is a relese build, and it is much better at displaying data and user controle for the render window (right and left click on the window to rotate and zoom)
but despite what you may see it has absolutly no saveing capabilities