[diamondgeezer]

Hey... did we ever decide whether or not we were allowed to screw with the modelview code? See, I had this idea whilst hacking some POFs - would it be possible to make MV display the FOV cone for turrets? It'd be handy for making sure turret fire wouldn't clip bits of the hull, and stuff like that.

*waits for Bob to p1mp Aurora*

-------------------
Diamond Geezer is equally adept with both swords and pistols

[Bobboau]

why not use Aurora,
all hail

you can fiddle with MV if you want, but I'd rather make this addition to my editor and get it done, this will be on the top of my list for the next time I start adding things

[CP5670]

I would use Aurora more often but it has a really bad bug; it doesn't read the first parts of several of the pof chunks correctly and sets all the values to zero, so if you load a model and save it, it will screw up those parts of it.

Modelview is my favorite in terms of the basic layout but it doesn't have the functions of PCS or Aurora.

[diamondgeezer]

Aurora still has... issues. ModelView is as reliable as a two be four, so I'm sticking with it

[Bobboau]

wich parts is it forking up?

how do you people expect me to get this into a 1.0 state if you don't tell me about you'r bugs

[IceFire]

Originally posted by diamondgeezer
Aurora still has... issues. ModelView is as reliable as a two be four, so I'm sticking with it

Is it now...I've gotten it to crash, lockup, create massive swap files, and one time it even reset my computer.  Its not quite as rock solid as that but it is very good.  As good as any commercial product anyways.

[CP5670]

wich parts is it forking up?

how do you people expect me to get this into a 1.0 state if you don't tell me about you'r bugs

The main thing is what I said earlier; the program fails to load the first parts of most (possibly all) of the chunks. It also performs an illegal operation error when you close the program, but it doesn't really matter at that point, eh?

[Rampage]

Bobboau, Aurora has entered a good running start.  But if one comes to think of it, Aurora first of all should have its interface cleaned up.  When I first came to use Aurora, those buttons were alien to me (and they still are).  What I mean is that besides the obscure buttons, Aurora is not aesthetically pleasing.  Second of all, Aurora should not only support 16bit video settings but also 32bit.  Third, please correct any spelling and grammar errors in the program's resource.  The spelling errors make the program, for lack of better phrases, seem unprofessional in comparison to ModelView32.  I can understand these errors in the alpha or even beta, but if you are planning to release the 1.0 version, PLEASE correct these errors.

[Bobboau]

it's still in alpha, spelling errors are a low priority, if you feel like pointing any out, though, update and tell me about them.
and I thought I had fixed the 32/24 bit suport issue, had it basicly try every setting posable untill it found one that worked, update to the latest version (link in sig) and see if it works any better. if you have any sugestions on the interface I'd like to hear them, I tryed to get the basic layout to match the style of PCS and FSMM2 (with the exeption of the new copy/delete/keys), I have made some changes recently alowwing for the render window to be maximised, ect...