[Kazan]

out of all the 2.1 features it will probably be the most time consuming to implement

[blowfish]

Its a frakking XML file.  Unless there is a lot of infrastructure that needs to be implemented before DAE import can be done, than I fail to see why it should take so much longer than everything else.

Note that I'm not saying that this should be easy to implement, I'm just surprised that it is the most time-consuming of all of the features (there is some stuff that I would have thought would be much harder).

[Kazan]

Its a frakking XML file.  Unless there is a lot of infrastructure that needs to be implemented before DAE import can be done, than I fail to see why it should take so much longer than everything else.

Note that I'm not saying that this should be easy to implement, I'm just surprised that it is the most time-consuming of all of the features (there is some stuff that I would have thought would be much harder).

because obviously XML is easy as hell to implement and parse, which explains why it's such an ancient standard and has been in use for 30 years.. yup


writing xml may be simple, handling it's parsed DOM tree contents is not

[Bobboau]

you want to write a UI cheat sheet?

Yes. A lot of users would find it helpful. Would it be possible for pictures (icons) as well as text? html?

yeah, I actually think there is a prebuilt HTML viewer in wxwidgets, but short of that if it wasn't too long I could recreate just about anything you could want in some sort of help window. and there is always the option of simply having the documentation in HTML and having the OS handle it (ie have it show up in firefox or (ugh) internet explorer)

also on the subject of XML, there is a saying:
there comes a time in every coders life when they have a problem and think "Ah! I know I'll use XML", now they have two problems.

not saying it's a bad idea, I just always thought that was funny.

[chief1983]

also on the subject of XML, there is a saying:
there comes a time in every coders life when they have a problem and think "Ah! I know I'll use XML", now they have two problems.

That's made of win.  I'll have to share that some of the other coders I know.

[blowfish]

Maybe I'm just too used to Apple's automated parse APIs...

[Water]

yeah, I actually think there is a prebuilt HTML viewer in wxwidgets, but short of that if it wasn't too long I could recreate just about anything you could want in some sort of help window. and there is always the option of simply having the documentation in HTML and having the OS handle it (ie have it show up in firefox or (ugh) internet explorer)

Ok - I'll see how minimal I can get it.

[Water]

Minimal Help Text
------------------------

View:
L Mouse
R Mouse - Rotate view along Z (long) axis
Shift + L Mouse - Pan view

Zoom:
Shift + R Mouse - Zoom Fast
Mouse Wheel - Zoom Slow

Move:
Ctrl + L Mouse - Move item around in blue plain (dual axis)
Ctrl + R Mouse - Move item along red axis (single axis)



-------------------------------------------------------------------------------

Using these icons to replace the existing ones makes the help file easier to explain, and allows you to drop the X, Y and Z axis lock icons. So instead of 3x3 button variations. Just three are all that is needed for both dual and single axis use.

[Bobboau]

ok, had a free moment to work on this, and CVS got unbroken, so I was able to get this half way implemented, if you want anything about it changed tell me, I'm thinking about implementing a transparency slider on the bottom and makeing the window always on top, not sure if that would be worth the effort though. it's currently modless so it can be up while you use pcs2, but it will be pushed to the background while you use the graphics window. I expect you will want to make changes to the help file as I only made a minimal html file for it, no frills at all.

[Water]

I expect you will want to make changes to the help file as I only made a minimal html file for it, no frills at all.

I though the adding special points, paths etc seemed to not need any sort of help section so any alterations would depend on feedback from others.

[Scooby_Doo]

Any chance of having a turrets automatically setup their up and forward angles?

[blowfish]

Has this already been mentioned?  It would be nice if you could use autogen for specific paths.  Sometimes I have new paths I need to generate but I don't want to destroy the old ones.

[Kazan]

just import those paths.. selective autogen would not make you happy.. trust me

[blowfish]

just import those paths.. selective autogen would not make you happy.. trust me

Why not?  (If there is a good reason, I'd like to know)

[Kazan]

just import those paths.. selective autogen would not make you happy.. trust me

Why not?  (If there is a good reason, I'd like to know)

do you want 20 million prompts when loading a model?

[blowfish]

I don't get it.

[Talon 1024]

I'd just like to make a useful feature request: Transferring data from one file to another.

This could be very useful because...  Let's say you import a model once with PCS2, you have it hardpointed, glowpointed, subsystems, the etc. and then you decide you aren't happy with the mesh the way it is.  So you decide to go back into your modelling program and add LODs, debris, the etc. and you're finally happy with that one and you decide to re-import the model, but you want it to have the same glowpoints, weapon hardpoints, etc. as the old one.  Well I'm not sure many people would want to go through the trouble of transferring this data manually...

[Colonol Dekker]

Would it be possible to implement a project style view where you can import cobs as you sub-models of existing Pofs?

[Kazan]

Would it be possible to implement a project style view where you can import cobs as you sub-models of existing Pofs?

*facepalm*

feature.. already..present

[Colonol Dekker]

Animation preview then?