[Kazan]

what is the date of the version of PCS2 that you are using, i could not replicate such behavior

[edit]
there was a change in the way POF HDR2 bounding box is assigned in pcs_pmf_pof.cpp revision 1.21 - that was commited June 27, 2007 - so if your build is older than that i SMACK YOU for using a 7 month old PCS2 build

[ARSPR]

what is the date of the version of PCS2 that you are using, i could not replicate such behavior

[edit]
there was a change in the way POF HDR2 bounding box is assigned in pcs_pmf_pof.cpp revision 1.21 - that was commited June 27, 2007 - so if your build is older than that i SMACK YOU for using a 7 month old PCS2 build

Hey I didn't thought my English was so bad.    From my previous post:

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

BLA, BLA, BLA

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:

BLA, BLA, BLA

I'm using this build obtained through Bob's signature link. Remember that I needed the very latest build with the multiline enhancement in Special Points > Properties.


OTOH please also check the issue with the missing graphical info about where the used textures are UV mapped or which triangles are part of a selected subsystem. (I've already said this here)

[Bobboau]

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

DOH!
sorry, fixed

[Bobboau]

uploading version that has wire frame/highlighting in HTL mode.

has anyone thus far gotten NOTHING in the HTL versions (i.e. nothing but black, or a crash or a combination of the two with maybe a "great flaming graphics error of doom"?)

[ARSPR]

uploading version that has wire frame/highlighting in HTL mode.

has anyone thus far gotten NOTHING in the HTL versions (i.e. nothing but black, or a crash or a combination of the two with maybe a "great flaming graphics error of doom"?)

I've just reopened the mediavps edited Comm2s-01.pof, click in "Textures" and:

Code: [Select]

Great Flameing Graphics error of DOOM!!!!

Warning OGL reported "valor no valido" at .\pcs_file.cpp (2103)
 please report this issue to Bobboau

...or else...

And some more like this one

[Bobboau]

does "valor no valido" roughly translate to "invalid operation"?

or would "invalid value" be more accurate?

[Bobboau]

I just uploaded a new build with a few more error checks (and I made it so invisible textures don't draw as white anymore (so the com node won't show as a white box with spikes sticking out of either side)).
please run that and tell me the error OGL reported, the line number and file (for example ' "valor no valido" at .\pcs_file.cpp (2103) ') it'll probably be about the same but it will rule some things out and I'll be sure the line numbers match properly.

I'm assuming when you don't click on the textures or submodels everything is working fine.

[Col. Fishguts]

has anyone thus far gotten NOTHING in the HTL versions (i.e. nothing but black, or a crash or a combination of the two with maybe a "great flaming graphics error of doom"?)

No crash so far, but the more POFs I open in succession the longer it takes to load them.

[Bobboau]

are you sure you aren't just loading successively more complex models?

[Bobboau]

anyway sence this is the request thread after all I think this is the best place to mention I've just looked over the OBJ file format and I think I'll be able to make an importer for it, it supports everything we need in terms of geometry, so thats good, the only downside is it does not support higherarchy, so I'll need to either make some hacked together solution or OBJ import will only be a bunch of sibling objects and you'll need to rebuild the geometry in PCS2 (which fortunately enough you can do)

[Kazan]

what program is .obj?

PST: no new features! we're supposed to be in RC build feature freeze for 2.0 release

[edit]
flipped BBOXes just DON'T MAKE ANY BLOODY SENSE!

this is driving me up the wall.

i'm building the HDR2 bounding box off all the subobject bounding boxes on POF save, each subobject's bounding box is constructed off it's FS2-coordinate space polygon list _OR_ if BSP cached off it's PMF coordinate space list and then ran through POFTranslate(vector3d) so it's right in both cases.

[edit2]
bob.. make sure you're convering the MOI between the two coordinate spaces

[edit3]
just found a memory leak in POF loading

[chief1983]

I'm really hoping he just meant for 2.1 or 2.2, I want a stable 2.0 soon!

[Axem]

anyway sence this is the request thread after all I think this is the best place to mention I've just looked over the OBJ file format and I think I'll be able to make an importer for it, it supports everything we need in terms of geometry, so thats good, the only downside is it does not support higherarchy, so I'll need to either make some hacked together solution or OBJ import will only be a bunch of sibling objects and you'll need to rebuild the geometry in PCS2 (which fortunately enough you can do)

Oh Bob, you've made me the happiest modder ever! OBJ is what I (and quite a few people I know) export to start the long and horrible POF conversion journey.

[Bobboau]

  see what says, it's popular.

originally it was from wavefront, but it's a commonly supported file.

what all are we waiting for on the 1.0 (or 2.0 or what ever version number) release? aside from general settling. should we make some big huge push for developers to hunt for bugs?

I need something to work on while I wait for feedback from people. sitting here waiting hours between posts I get stir crazy.

MOI was done in the internal coordinate system, and more importantly is a function of an objects partial distance so it shouldn't have any problems, the numbers didn't seem like they were flipped any ware. but this is a perfect example of stuff I'm waiting for feedback on.

are bboxes still getting flipped?

[Kazan]

the official version number we're on RC builds for is 2.0 - so yes big bughunting push.  once we're confident all bugs are hunted down and destroyed we release 2.0 and start on 2.1

people tell me that they are getting flipped but neither goob nor i could find where this is happening - it did cause me to find a memory leak (probably what ASPR was talking about with "it gets slower as i load more models)

it was leaking the net size of all the BSP data for each file!

[edit]
oh.. and i revoked PCS1.x's recognition for BSP caching.

oh.. and isn't it nice having the internal PMF format instead of having to go straight to POF when it comes time to add new formats

[edit2]
using VBO's for rendering will interfere with some features in 2.1 possibly

[chief1983]

Bob, couldn't you just add a new branch to CVS for 2.1 stuff?

[Kazan]

Bob, couldn't you just add a new branch to CVS for 2.1 stuff?

 

that would be a good idea - because then we could backport bugfixes to 2.0.x builds while working on 2.1 unstable

[edit]
wow.. i'm a retard - that was POF::OBJ2_Get_BSPDataPtr NOT POF::OBJ2_Get_BSPData

not a memory leak.. wee double free CRASH!

[Bobboau]

yes and no, it's nice to have an internal format not dependent on POFs, but the way geometry is organized is horrifically ineffecent. if you would have used a index based representation of the geometry rather than a pure vertex based representation (that is a list of vertexes and polygons represented as a list of indexes into this list of vertexes rather than polygons being simply a list of vertexes) it would have been several orders of magnitude better. most (all that I am aware of) file formats are arainged like this and it's the cause of 90% (this is an understatement) of the time BSP compiling takes (tree generation for extremely complex models only takes about less than half a second, converting from PCS2 internal geometry to indexed geometry takes 30 seconds or more). the first thing I want to do after release is change this, because it's the biggest limiting factor in the programs design.

[Bobboau]

did we ever figure out how to work branching, because I tried that once already with the experimental BSP stuff and it didn't work out so great.

[Vasudan Admiral]

.OBJ import would indeed be cool. The lack of a hierarchy might make it very tedious though. Might you be able to generate at least some initial hierarchy based on the object names? Ie, anything called 'turret01a' would be parented to 'detail0', while 'turret01b' would go to 'detail1' etc.

As for other stuff that could be done, well the save as cob function is still partially broken: http://ferrium.org/mantis/view.php?id=36
And it would also be really cool to be able to open VP files and look at any models in there. <insert begging emoticon here>