[Bobboau]

put the editors on the other side, make the window of an adjustable size, it'll be fine

[Kazan]

i tried putting it on the other side.. didn't like the appearance

allowing resizing the edges off those [relative to each other] windows = RPITA

-----

Once I get everything working I can put in a "layout preference" that will have it setup to haave this default view, this without the tree, the and the GL canvas sammiched between the tree and the editor.

how about that?

[Bobboau]

if I will be able to use the tree to select stuff, fine.

[Kazan]

to select stuff automatically up in the editor?

[Bobboau]

yeah, if I select one of the thruster arrays in 'Engines' the editor window will display the properties of that array, if I select one of the points in the array the editor will have  the radius, position, and normal of that point

you don't remember the big huge argument we (you me and everyone else) had and what we finaly agreed upon on what would be best? it's were the whole tree controle thing came from. the tree selects what your editing and a second editor window has all the editors, the editors are minimalist to what you have selected makeing the best use of limited space.

[Kazan]

eh no i don't remember that.. but showing _only_ the pertinant sections of the editor window will be insane - i can show the appropriate editor window with the appropriate data already selected

[Bobboau]

I'm not sure why that would be insain, but I guess what you say would be good enough

[MetalDestroyer]

After using several times PCS 1.3 this last 4 days, I think you have to represent the engine location when we put coordinates.

And other trouble in it, when I put turrets/guns or missiles the red/yellow/green line is mix with the background color (black).
I can't see where I put my turret/gun/missile into the model :/


About this PCS 2.0, I try it, but, i'm wondering, if it's normal I can't see any texture ?

[Kazan]

metal have you setup your texture paths

[MetalDestroyer]

Yep, I give it the same path as the previous PCS (1.3) I use actually and it doesn't work :/
I use generally the default path "c:\games\Freespace2" I try to add this path "...\data\maps" but, doesn't work neither.

[Kazan]

if you give it "c:\games\freespace2" [default] it searches

"c:\games\freespace2\*.vp" vps for textures and
"c:\games\freespace2\data\maps\*" for textures

what format are your textures in.. and which build are you using? the last one?

[MetalDestroyer]

I used the last one, and the textures are in .pcx only and dds for some.

[Kazan]

you need to set your path to "c:\games\freespace2"

NOT c:\games\freespace2\data\maps\

it automatically appends the \data\maps\

[Bobboau]

it looks in 'c:\games\freespace2' first though, right?

[MetalDestroyer]

It didn't work :/

[Kazan]

no it doesn't bobboau - i thinks in VPs in c:\games\freespace2

i'm going to modify the code later to check the roots too

right now it only looks at

[path]\*.vp vps
[paths]\data\maps\* raw files

metaldestroyer: then i don't know, you've set something wrong, or your ship has all DDS textures and DevIL's ability to read .DDS is flakey

[Bobboau]

sence you can put in multable texture paths, why not just have each path check [path]\* and [path]\*.vp, and by default set it up to c:\games\freespace2
and
c:\games\freespace2\data\maps

and it would probly be a good idea to have it check the folder were the model was loaded from first, or makeing an opption for it.

[Kazan]

i was going to make it check
[path]\*
[path]\data\maps\*
[path]\*.vp

[TrashMan]

Hey KAz, I thought o a neat feature that might be very usefull - SCALING!

You have a scale bottun and you just imput the modifier by which to scale the model. Of you want a model  75% the size of the original one you imput0.75. If you want a 50% larger one you imput 1.5.

What PCS should do is scale hte pof itself and them go trough the engine glows coordinates (and radius), docking points, subsystems coordinates(and radius), turret fire points, path coordiantes (but shouldn't touch the radius there), and eventually glows and insignias and multiply each value by the modifier and save it..


Do you think it's doable?

[WMCoolmon]

How about rotating? (See MetalDestroyer's thread)

Edit: Just thought of what might be a nice feature, some X/Y/Z arrows that could be toggled on/off so you could make sure that the model is aligned properly.