[Aardwolf]

Not sure if someone has already said this, but...

I think there should be more either built in subobject orientation detection tools, or easy tools to let the user determine the orientation of the subobjects. Like, you should be able to assign a normal vector to something by selecting a face with the same normal vector. And you should be able to select either a polygon or submodel to center the point on or in. The two might or might not have to be the same (if you select a polygon as the location).

Edit: and some easy way to flip points across planes parallel to but not identical to the three coordinate planes (i.e. the plane x = 2 instead of the yz plane, or any numerical entry); this would be particularly useful if you could do multiple points at a time.

Also, how about an "advanced clipboard" feature, where you can copy any number of points, subobjects, or what-have-you into the clipboard, and paste or remove them from the clipboard at any time. Also useful with this feature, you should be able to save clipboards, either inside their respective PMFs or as their own files.

[Scooby_Doo]

The clipboard feature has already been requested, and I'm backing it.  Ideal for duplicating turrets.


Ohhh following my suggestion about using Turret01 number just once (prev post) that should make making the clipboard easier.  Unless these some funking stuff going on in the PCS internal model/pof hierarchy i'm not aware of.

[Scooby_Doo]

Heres another feature requestion.... Kazaan already looking at me with the look of death LOL..
How about rescaling an existing model?   I could bring all my fighters to scale with Saga models without having to rebuild them and relocate the points (gun, paths, eye..etc)

[Kazan]

with PCS2 that would probably be a trivial amount of coding

[Starman01]

Is the wishlist still open ?

Not sure if it has already mentioned here (sorry, to lazy to read everything), but a really important function that we are missing for years
is a pof-resizer. It sucks to have to re-convert the model everytime I scaled it wrong.

AFAIK there was something like segeltuch in the past, but I never get this program to run like it should.

Would that be possible Kazan ?

[Kazan]

yes the wishlist is still open, i just haven't added things to the schedule for a while.. been to busy to try to think out on the road map... i think someone already requested that and with the new internal model format that wouldn't be very difficult.

conversion from COB will be 1:1 no longer 1:20 by default as well

[Starman01]

Is the factor still selectable ? I found it always quite handy that it converts 1:20. When I have to make the cob file 1:1 then I have to work on a giant model in truespace which makes it a little more difficult IMO, not to mention that navigation in truespace is a pain in the arse

[Scooby_Doo]

That would have been my request about 5 messages up 

Ok would a model thats 1km would an imported X x 3.6 x Z, switched down to X/3.6 x 1  x Z/3.6 sized up to 1000X x 10000 x 1000Z/3.6
That would be impossible to edit in truespace?!!! 

[Nuke]

its better to model fighters at 1:1, but capships i oten model at around 50:1

[Scooby_Doo]

Hmmm I never thought of it for fighters.... I'm so used to using  X/3.6 x 1 x Z/3.6.


Heres a dumb thought.... would it be possible to export the model data through a function call?  You could then write a plugin that would receive all the model data, perform it's operations and return the result back.  I'm not sure if this would work well for it or not, but it would make life in the long run easier for the wish list.  Instead of having to write everything including the kitchen sink into the program, you could write plugins that do the job.

[Nuke]

it would be cool to have some form of integration with the max plugin.

[Kazan]

no need to export the data like that... the plugin (if i write a plugin interface) could just have direct access to the internal PMF

[Scooby_Doo]

Well thats even better then :-)

I was thinking something like this:

ModifiedData = RunPlugin (OutgoingData) ;

[Kazan]

that would be terribly ineffecient.. making copies of the central data store.. oui

the plugin would simply have access to the PMF object in memory

[Scooby_Doo]

Agreed.... just pass it a reference or pointer

[Kazan]

it'll be a reference if i make the interface

[Scooby_Doo]

This might sound like a stupid suggestiong, but I just discovered I've been making a mistake for my subsystem special names...

Would it be possible (with people's suggestions/warnings) about possible errors in your pof model data.  For example in my case....
It'll warn you that you forgot to put a '$' in front of the specials name.

[Taristin]

My request is that it get made!

[Nuke]

My request is that it get made!

ditto

[Whitelight]

MOI!!  Moment of inertia? 
Have read up on this, from different threads.  There isn`t an easy fix for this, is there?

I mean, leaving the file in pof format, while fixing it isn`t possible, correct?