[Kazan]

kk think i have it fixed then.. commiting to CVS.. checkout bob's next build

[Water]

Well, strictly speaking, vertex bloat, I phrased it wrong before. I take it you downloaded the models? The UV mapped, non-converted model has 5k-some vertices, the un-UV mapped one has 1600ish. But after going through PCS2, the UV mapped model is back down to 1600ish. I don't know why, but then, I am rather new at this. I just know it's nice, because it had me worrying and trying to figure out wtf was going on. Which, apparently, nothing was

Here is why you have 4188 extra verticies in your model.
Each triangle face has 3 verticies ------ A cube with 6 faces = 12 triangles

With all the triangles JOINED together in a cube = 8 vertices (1 vertex per corner - shared with several faces)
With the triangles NOT joined together = 12 faces x 3 vertex per face = 36 verticies (4 or 5 vertex per corner)

[TrashMan]

damn HTL Hecate still won't open..

Can somoene send me the .cob of it pls?

[Bobboau]

I don't suppose you have VS2005?
if you could run it through the debugger on your system it would tell us were the bug was.

[TrashMan]

Unhandled exception at 0x10007657 in pcs2.exe: 0xC0000094: Integer division by zero.


IF I CLICK CONTINUE:
Unhandled exception at 0x10007657 in pcs2.exe: 0xC0000094: Integer division by zero.

IF I CLICK BREAK:
No symbols are loaded for any call stack frame. The source code cannot be displayed.

[Kazan]

don't click continue.. find the line in PCS2 that it occurs at

[Bobboau]

oh, divide by zero,

but I meant actually compile a debug build and run it. I'll zip up my local code base and upload it for you.

http://freespace.volitionwatch.com/blackwater/pcs2_source.zip

although now that I think about it, there are a bunch of other dependencies (wxWidgets, DevIL).
better idea, I'll upload a debug build, it should produce the name of the function causing the problem if you hit the debug button when it crashes.


http://freespace.volitionwatch.com/blackwater/pcs2d.zip

[TrashMan]

Debug build fails to start at all..

"This application failed to start becoause hte application configuration is inccorect. Reinstalling the application might fix the problem."

You know what - forget it...I'm not gonna touch the HTL Hecate

[Kazan]

ah ha! you don't have the mscv 8 redistributables... link is in the PCS2 wiki page

(well you do.. but not a fully up to date version i bet)

[Bobboau]

come on, we need to get this bug fixed, it's only going to bite us in the ass if we leave it.

I just noticed, you never actual answered my question, do you have VS2005? sence you were talking about stack frames an source code I figured you did, but if you don't have those dlls, then maybe not.

[TrashMan]

Ya, I have MVS 2005...don't recall when I installed it tough..probably the same time I installed SQL server 2005...

I'm gonna DL those files and try again..

EDIT - still nothing..

[Bobboau]

ok, I just tried packing all of PCS's external dependencies into a zip, and it came out to be more than 40mb, if I upload that would you be willing to download it and the source compile it on your end and try to run it in debug? if you compile it I garentee it'll run.

and kazan I just noticed a bug with our BSP compiler, think about what would happen if a polygon landed exactly on the split between two bboxes. like you might get if you converted a cube and it split  it in half, you'd have 4 polys that were on the split plane.
another clue our bbox functions use point<=min && point>=max.
if you still aren't seeing it, in this unusual but easy to reproduce situation, there will be polys that are consitered to be on both halfs of a split, or in both child bboxes, the way our code works this will result in duplicate polygons.

[Bobboau]

and what is wit the uninitialized head node in PackTreeInSLDC? shouldn't that be split not head, head isn't initialized, and you are using split every were else in there.

I think I figured out a fix for the problem mentioned above, unfortunately it has an extremely slim opening for infinite loops, but I can not think of a situation were it could ever actually happen, I'll be committing it shortly.

[Bobboau]

I hope we can get 1.0 rolled out soon I have a neat little geometry class I want to use in place of all our kaz_vector<pcs_polygon>s, it'll make auto-facet calculations ridiculously fast, and will enable us to make vertex/index buffer sets realy quick too.

[Kazan]

you mean 2.0

but yeah i just need to write the code to reverse engineer smooth v faceted v autofaceted and the autofacet angles of a kaz_vector<pcs_polygon>

[Hades]

Hey Guess what? PCS2 can't open Hecate but it can open HTL Lucy.

[Bobboau]

so you can't open the Hecate either?

[Water]

Hey Guess what? PCS2 can't open Hecate but it can open HTL Lucy.

My version opens fine from vp with textures, But what  vp file/version is yours from?

[Col. Fishguts]

so you can't open the Hecate either?

I just tested with the Hecate from the media_vp and the build from your sig,  it CTDs every time I try to open it.

EDIT: The same thing happens with cruiser01 and cruiser01x, the HTL Fenris and Leviathan.
EDIT2: And corvette2t-01 (Deimos?)

[TrashMan]

AHA! So now we have a bigger problem on my hands...and you don't need me anyore for testing now that you have other....guinea pigs