[Water]

(nor do I know for sure how to name things or create a hierarchy)

Select an object in Blender, press n, edit the name.
To parent something. select all the children objects then the parent object last and press ctrl-p

[Goober5000]

Since nobody bothered to tell me where I should split the thread, I'm moving the entire thing wholesale to the FSUpgrade forum.   If you want it split, you can do it yourself and then move the "announcement" part back into the Announcements forum.

[Spicious]

Hey, I exported a POF from PCS2 to DAE, and I can't open it in Blender... Possible bug, it happened with the Mihos, and I think earlier with the Aeolus (not positive on which ship it was earlier). The import script (v1.4) crashes, and the python console says the error was opening some geometry mesh.

That's not very descriptive.

[Spicious]

Maybe next weekend...

[pecenipicek]

a new build?

frankly, i still have the newest one from your sig crashing on the finish of loading the pof, but the older one (12th october or so) completely wipes the UV's of everything(when exporting to dae that is).

[Scooby_Doo]

I'm having a slight issue with glowpoints.  In pcs2 and max they show up in their correct position, but in-game they are offsetted by a considerable amount.  The model itself is centered at 0,0,0.  The glowpoint,glowpoints and helper are all x-formed (glowpoint and helper are at 0,0,0). Whats going wrong?

[Spicious]

Do they have a parent subobject set? (This may or may not have anything to do with the actual problem)

[Scooby_Doo]

Setup is:

Code: [Select]

detail0
     helper
          glowbank
               glowpoint


PCS2 confirms the parent subobject is detail0.   Also it seems to be off on only one axis at a time (on one model it's x, on another it's y)  Oh and it's not just the glowpoints, thrusters and eye points are included.

edit: also I dunno if this could be an issue, but detail0 offset is (-0.000013:0.000000:-0.000000), while in max it's at (0,0,0).  .000013 is kinda small compared to the offsets.

[Spicious]

That's just a rounding error.

Are they still in the right place in PCS if you reopen the pof? Can you make a simple setup where this happens?

[Scooby_Doo]

I think I got it fixed... but don't be surpised if i have this problem latter.  detail0 turns out wasn't exactly at (0,0,0).  I ended up taking apart the heirarchy, resetting detail0's pivet point, then moving everything to match the offset. Ugh, but at least it works.

[Spicious]

Based on statistics and some creative rounding, I'm going to conclude all future problems as user error.

Any thoughts on storing glowpoint data in a way useful to modellers?

[Scooby_Doo]

Wouldn't a simple "$attribute: value" work?

Another idea I'd like to see done is for turret angles. I assume you read the x,y,z rotation when you read the dae file?

[Spicious]

It would, but I'm trying to avoid someone coming up with a much better way of doing it and me having to do another rewrite of something a bit later.

Do you mean the stuff for multipart turrets with non-regular rotation axes?

[Scooby_Doo]

Correct, I'm always seeming to have problems with them, ask poor Keldor    I'd assume you'd have to assume some standard default position, like the turret must start faced up pointing forward, then rotated to where it's suppose to be in-game.

As for the glowpoints, theres one thing even more important for me than the attributes, it's numbering and group numbering.  Making landing/launching bay lights that blink in sequence is rather difficult when none of the glow groups are in order.

[Spicious]

What do you want done with turrets?

Glowpoint properties and MOI should save and load now.

[Aardwolf]

Is the link in your sig being updated?

Also, did Kazan ever do anything about the geosphere things crashing?

[Spicious]

Yes and I doubt it.

[pecenipicek]

I have just found a rather retarded idiocy of C4D's importer. Basically, if the model has a texture attached to it, C4D doesnt import the UV map, but imports the texture.

however, if the texture is removed from the list, the UV imports nicely, and the texture can just be drag'n'dropped casually... for the example i used GVF Toth

Code: [Select]

<node id="detail0" name="detail0">
<translate>0 0 0</translate>
<instance_geometry url="#detail0-geometry">
<bind_material>
<technique_common>
<instance_material symbol="Fighter09-01-mat" target="#Fighter09-01-mat">
<bind_vertex_input semantic="CHANNEL1" input_semantic="TEXCOORD" input_set="1"/>
</instance_material>
</technique_common>
</bind_material>
</instance_geometry>
</node>

idiotic, and the reason is something related to semantics proper. i'll provide a proper example once i gather all the details

[DaBrain]

The current version can't load or import most models anymore. It constantly crashes for me, even when I try to load a vanilla standard model (i.e. bomber10.pof)
It crashes right after the model appears in the viewport for POF files and before that for DAE files.

Code: [Select]

AppName: pcs2.exe AppVer: 0.0.0.0 ModName: wxmsw28_core_vc_custom.dll
ModVer: 2.8.9.0 Offset: 000de499


[Aardwolf]

I meant omnipoints. Someone summon Bobboau, Kazan mentioned he might know more about them.