[Bobboau]

VA those are for stepped rotation, the shivan gas miner uses it, as does the Golgotha, it's a retail feature.

I'd have to do a good bit of recoding to get multable lines in the suggestions menu, but I can probably do that eventually, as it is now what is in the menu is what will be drawn, and having the full subobject properties for a turret would be too much to cleanly fit, so I'll need to recode to have separate labels and content, but first you mentioned a few things I forgot, I'll add those.

[Bobboau]

well... because OGL does not differentiate between model and view matrix, and only has just the one, it looks like I am going to have to keep track of them myself... which means I might as well set up a full matrix stack for the model and proper set functions for the view.

I WILL have a ray picker!

hey, how do I get access to this?

[Vasudan Admiral]

A retail feature!? So that's been there the whole time, and I've never seen it. How depressing.

turret's automatically have their properties filled on load from COB/SCN if you name them to the turret naming convention

I mean for when you have a pof without that data already there, though thinking about it, that should be a pretty rare circumstance.

Anyway, I think I have a couple of new bugs to report. I'll mantis them when I know more in a few minutes.

[Bobboau]

arg, seriusly, how do I get glLoadTransposeMatrixf?
it says it's a 1.3 function, I can't tell what we even have, let alone how to change it.

[Kazan]

if it's not coming up as a defined function it means i'll have to import my gldriver - microsoft's headers only define functions for OGL 1.1, but i can use SDL to get functers for the others

[Scooby_Doo]

Ecck! Is the paths section suppose to have tons of lens flares?

[Kazan]

i didn't write the code for that

*looks at bob curiously*

[Vasudan Admiral]

Just double checking...
- That the shield and insignia sections haven't been done yet right? They currently just display the header editor.
- And also that import data is similarly not-yet-done, since the load buttons don't do anything at the moment.

And Scooby - it's quite possible that those paths are all fully correct. Just look at an Orion in path view.
However, it might be a good idea for modder sanity to have an option to only display the currently active path.

[Kazan]

bob doesn't currently plan on allowing signia editing or shield editing.... though eventually selecting the shield item should cause the ships shield mesh to be rendered

[Bobboau]

well, I wanted the non-selected paths to be visible too, the selected path should be vastly brighter than everything else. the colors for everything will be customizable soon so you can just set the unselected color for paths to black and you won't see them anymore.
does that sound good?

and yes, insig, shield, and import/export are not implemented yet, insig will probly be a while, shields will probly do nothing but display the geometry for now.

geeze all the sudden everyone is a postaholic..

[Kazan]

we're posting working builds.. and i'm sitting around waiting while raid buffs up in eq

[Vasudan Admiral]

Well....if you think about it, this is kinda the 'big thing' happening at the moment - the birth of the one modding tool to rule them all if you like.

Anyway - yeah, the selected path and it's points are brighter than the rest as well as drawing the path line itself, so that definitely works. (though the selected point becomes a solid, non transparent circle making it a little tricky to use for the moment)

[Kazan]

i don't really like those "semitranparent spheres" around it... maybe if they were much smaller and were geometry (ie lines) they would be better to show radius - ie make their actual radius the log(10) of the path point radius

[Bobboau]

well it was more, I've been waiting for activity all day, and then suddenly I tried to post and it was "warning someone else posted" like three times in a row.
thats all.

they can't be smaller the purpose is to show you what the radius is, if you make them smaller than what the radius is it'll be misleading the user and showing false data, I tried my best to make it look nice, but it is suposed to have a function, just cause it looks ugly doesn't mean you should change it to be something it isn't.

but the paths do need to be tweaked quite a bit.

[Kazan]

PCS1 didn't show the radius and people were just fine

[Scooby_Doo]

Sorry I was away....

The model was converted using PCS1.  (What state is the PCS2 converter?)

I don't mind the spheres, given that they look right.

This was the paths that I imported from:

[Kazan]

PCS2's converter works A-OK

[Scooby_Doo]

Good.. I was worried about inverted polys, etc...

[Axem]

The spheres are great, they do a better job at showing the radius than a cube.

PCS1 didn't show the radius and people were just fine

I had to use Modelview to edit anything with a radius because it didn't show up and the X mirroring for subsystems. And with that giant memory leak work never went too fast.

[Scooby_Doo]

Spheres are somewhat ok... but they need lines between to make things understandable