[Kazan]

properties are already a multiline isn't it?

if not it's trivial to make it multiline - and it's probably a standard two character windows \r\n carage return+new line

[ARSPR]

Either I'm really dumb, (never discard that possibility), or Properties is not multiline at all.

OK, I would really love your tech explanation about "windows \r\n carage return+new line" if I had understood it  But, how do I insert that thing in the middle of the text?

[Kazan]

you can't without a multiline edit box... it should be trivial enough to change

[Bobboau]

special point properties is not multi-line, and honestly I had never considered it, the only things I've ever seen in it was the subsystem thing and split, I didn't realize (and none of any of the other coders who have worked on POF editors for the last ten years have either) there could be anything else there.

I'll look into this and if your right I'll fix it.

[Bobboau]

wow, it is, heh... fix committed

[ARSPR]

Could you post a new RC build please?

[Vasudan Admiral]

Just a quick request - could one of you stick in a 'Length' 'Width' and 'Height' measure for the open pof in both the header and subobject pannels? (ie, for the model as a whole and the currently selected subobject) I know we get the bounding box min and max positions, and so can work it out through pre-school math, but it's just so much nicer to be able to get that info at a glance.

[Bobboau]

I guess I could do that, just as a read only display, though I try to minimise things like that so things don't get too cluttered.

[Bobboau]

uploading a new build that has a number of small improvements and one big one I redid the way subobjects are drawn to take advantage of vertex buffers as best I could (don't know what the hell kaz was thinking when he decided to define geometry as a bunch of vertex arrays, as opposed to a single vertex array with a bunch of index arrays but that's going to have to wait until post 1.0) so all the htl models should render smooth as silk now. this turned out to be a much bigger pain in the ass than I was expecting it to be, but I got it done in not too huge an amount of time.
I'm expecting some compatibility issues, so tell me if it doesn't work.


I might be tempted to implement some sort of real render of thruster/glow point effects, I'll need to figure out how that'll work with the current omnipoint code (probably just leave it to people to turn the colors down real dark)

[Kazan]

what the hell i was doing was making it easily editable for future geometry/uv manipulation.

make sure you put a hook in to allow other parts of the code to force a rebuild of the VBO

and since we're making VBOs can you see if you can make it generate .ibx files to go with the POFs

[edit]
oh.. and not using VBO's = less coding work (it's only one model, we don't need the performance advantage of VBOs) + more compatible

[Vasudan Admiral]

Major display glitches with the changes Bob;







Small ships like the uly and dragon etc seem to be largely unaffected, so it's not a global thing. It might be something to do with subobjects?

[Bobboau]

well that is very very weird, because some of those ther the very models I spent a lot of time testing with.
looks like UV coordinates are getting borked in a very peculiar way, it's especaly weird how the glowmaps are working but the base map is messed up.

[Bobboau]

gees you make the tinniest of mistakes and OGL rips your guts out, found what was causing that, I made one extremely small mistake right before I compiled/uploaded, I am now uploading a new version. that should have that fixed, it was literally one line.

[Vasudan Admiral]

Awesome, yeah that fixed it. And wow - the renderer really is a lot faster. Sweet.

Also, one other thing - in PCS1 in the paths tab there was a 'Turret' section where you specified turrets and then the subobject number of that turret in the object list.
As far as I know it has absolutely no effect in-game, but any models that do have a turret defined cause a non-fatal 'Warning: Couldn't fix up turret indices in spline path.....' message upon load into fred.

This stuff wasn't included in the PCS2 path editor so I assume you are aware of it already, but would it be possible to get PCS2 to remove any data on existing pofs in that field upon save? So rather than going through all the problem [v] ships one by one in PCS1 manually removing any defined turrets, we could just open and save them in PCS2.

[ARSPR]

Well, with the newest build texture location is not shown. (The magenta triangle outlines are missing).

Also when you select a model, that piece isn't outlined either. I think you should revise general rendering...

[ARSPR]

OTOH, I think there's something wrong with PCS.

Because of the Shivan Comm Node Mantis report I've run FS debug three times. I've just started the game and gone to F3 lab, then I've selected Shivan Comm Node LOD0 and I've exited (actually the game crashes because of a unknown known bug which Taylor knows about). Then I've read fs2_open.log.

When I use retail (from sparky_fs2.vp) Comm2s-01.pof I get the following warnings:

Code: [Select]

Warning: Ignoring unrecognized subsystem piece1a, believed to be in ship Comm2S-01.pof
Warning: Ignoring unrecognized subsystem piece2a, believed to be in ship Comm2S-01.pof
Warning: Ignoring unrecognized subsystem piece3a, believed to be in ship Comm2S-01.pof
Warning: Ignoring unrecognized subsystem piece4a, believed to be in ship Comm2S-01.pof
Warning: Ignoring unrecognized subsystem piece5a, believed to be in ship Comm2S-01.pof
Warning: Ignoring unrecognized subsystem core, believed to be in ship Comm2S-01.pof

When I use new Mediavps 3.6.10. Comm2s-01.pof:

Code: [Select]

Warning: Ignoring unrecognized subsystem piece1a, believed to be in ship Comm2S-01.pof
Warning: Ignoring unrecognized subsystem piece2a, believed to be in ship Comm2S-01.pof
Warning: Ignoring unrecognized subsystem piece3a, believed to be in ship Comm2S-01.pof
Warning: Ignoring unrecognized subsystem piece4a, believed to be in ship Comm2S-01.pof
Warning: Ignoring unrecognized subsystem piece5a, believed to be in ship Comm2S-01.pof
See how subsystem core one is missing probably due to the Mantised issue, as core isn't likely a valid subsystem. The Mantised in-game warnings aren't shown when you just open the model in F3 Lab.

Then I open Mediavps 3.6.10. Comm2s-01.pof with PCS 2 (your latest build from 0112 at 22:50), I insert an Enter in the middle of the conflictive line and I save. Then I get:

Code: [Select]

WARNING: "Inverted bounding box on submodel 'debris01' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
WARNING: "Inverted bounding box on submodel 'debris02' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
WARNING: "Inverted bounding box on submodel 'debris07' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
WARNING: "Inverted bounding box on submodel 'debris03' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
WARNING: "Inverted bounding box on submodel 'debris04' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
WARNING: "Inverted bounding box on submodel 'debris05' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
WARNING: "Inverted bounding box on submodel 'debris06' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
WARNING: "Inverted bounding box on submodel 'shcomma' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
WARNING: "Inverted bounding box on submodel 'piece1a' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
Warning: Ignoring unrecognized subsystem piece1a, believed to be in ship Comm2S-01.pof
WARNING: "Inverted bounding box on submodel 'piece1a-destroyed' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
WARNING: "Inverted bounding box on submodel 'piece2a' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
Warning: Ignoring unrecognized subsystem piece2a, believed to be in ship Comm2S-01.pof
WARNING: "Inverted bounding box on submodel 'piece3a' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
Warning: Ignoring unrecognized subsystem piece3a, believed to be in ship Comm2S-01.pof
WARNING: "Inverted bounding box on submodel 'piece3a-destroyed' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
WARNING: "Inverted bounding box on submodel 'piece4a' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
Warning: Ignoring unrecognized subsystem piece4a, believed to be in ship Comm2S-01.pof
WARNING: "Inverted bounding box on submodel 'piece4a-destroyed' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
WARNING: "Inverted bounding box on submodel 'piece5a' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
Warning: Ignoring unrecognized subsystem piece5a, believed to be in ship Comm2S-01.pof
WARNING: "Inverted bounding box on submodel 'shcommb' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
WARNING: "Inverted bounding box on submodel 'piece1b' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
WARNING: "Inverted bounding box on submodel 'piece2b' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
WARNING: "Inverted bounding box on submodel 'piece3b' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
WARNING: "Inverted bounding box on submodel 'piece4b' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
WARNING: "Inverted bounding box on submodel 'piece5b' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
WARNING: "Inverted bounding box on submodel 'shcommc' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
WARNING: "Inverted bounding box on submodel 'piece1c' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
WARNING: "Inverted bounding box on submodel 'piece2c' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
WARNING: "Inverted bounding box on submodel 'piece3c' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
WARNING: "Inverted bounding box on submodel 'piece4c' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
WARNING: "Inverted bounding box on submodel 'piece5c' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
WARNING: "Inverted bounding box on submodel 'shcommd' of model 'Comm2S-01.pof'!  Swapping values to compensate." at ModelRead.cpp:2404
Warning: Ignoring unrecognized subsystem core, believed to be in ship Comm2S-01.pofSee how subsystem core is present again as it should be but now there are a lot of Inverted bounding box warnings... 

I upload an archive with the three models in case it can be useful. (Remember to fix the extension of the desired one)



[attachment deleted by ninja]

[Wanderer]

FS Open reports all subsystems with 0 hitpoints with the

Code: [Select]

Warning: Ignoring unrecognized subsystem piece1a, believed to be in ship Comm2S-01.pofSo it reports every and all subsystems etc stuff with that same warning even when there is absolutely no reason to do so

EDIT: OTOH it might just report any subsystem that is not navigation, engine, weapons etc system as unrecognized...

[Kazan]

to fix inverted bounding boxes you need to recompile from source .cob

[Kazan]

bob you didn't cvs add ogl_vertex_buffers.h ogl_vertex_buffers.cpp

[ARSPR]

to fix inverted bounding boxes you need to recompile from source .cob

But the problem is that:

• I have one existing pof which hasn't got any kind of inverted bounding boxes (whatever thing they are).
• I edit it in PCS2, I save it again, and then it has inverted bounding boxes

Are you sure there's nothing wrong with PCS?