[Spicious]

Which additional Collada formats do you want supported?

You're welcome to implement support for other formats. I'm not going to do it though.

[FreeSpaceFreak]

The one generated by Blender 2.6 please, see attachment.

[attachment deleted by a basterd]

[pecenipicek]

i think they mean the COLLADA 1.5 format.

[rhettro]

What FSF said. Thanks.

[chief1983]

What I would have liked to see is a more versatile means to add support for formats to PCS2.  A dynamic format library loading ability would be great, then people could add support for formats without modifying or having access to the core PCS2 code at all.  All that would be needed is to define a set of functions that PCS2 would use to read the model through the library, and perhaps a way of getting what file extensions the library supports so it could be added to the file open dialogs.

[Spicious]

The one generated by Blender 2.6 please, see attachment.

Nice; IDs but not names and polylist for triangles. You seem to be missing textures for everything apart from DAMAGE too. Try the attached build (which has since been updated to actually render untextured areas with VBOs enabled).

Can anyone spot today's lesson?

What I would have liked to see is a more versatile means to add support for formats to PCS2.  A dynamic format library loading ability would be great, then people could add support for formats without modifying or having access to the core PCS2 code at all.  All that would be needed is to define a set of functions that PCS2 would use to read the model through the library, and perhaps a way of getting what file extensions the library supports so it could be added to the file open dialogs.

It's a nice idea in theory, but would anyone actually write plugins?

[attachment deleted by a basterd]

[FreeSpaceFreak]

Right, my findings. This build correctly imports DAEs exported by Blender 2.6, and at first sight there don't seem to be any issues with it. It also still opens the older DAE version. Good job, Spicious

However, the Blender COLLADA exporter is still WIP (at least, I hope it is). Modifiers are completely ignored (as opposed to the 2.49b exporter, where you can choose to apply them), only objects in visible layers are exported (not so much an inconvenience, but something to keep in mind anyway) and textures now seem to be handled via materials instead of directly from the UV editor. From 5 minutes of messing around, it appears you need to have one material for each texture, and have UV coordinates selected for the material texture mapping.

If this is true (not quite certain yet) and will remain so, that would suck, since it significantly increases the workload of UV-unwrapping (you now need to assign not only a texture to each face, but also a material, and AFAIK that can't be done in any convenient way). For fully UVed models with just one texture this would be no big deal, but as soon as you want two textures on one object you'd have to assign materials face by face.

In conclusion, I recommend sticking to the 2.49b exporter for now, it's really much more convenient for POFfing purposes.

[chief1983]

I think it's more likely down the line that someone would write a plugin rather than sort through the entire PCS2 codebase to add support for a file type, but perhaps only marginally more likely.

[Rga_Noris]

Just an FYI, face by face is not necessary. You can just assign the image in the UV editor like normal, then in poly select mode press ****f G and click image, then assign the material.

[FreeSpaceFreak]

Just an FYI, face by face is not necessary. You can just assign the image in the UV editor like normal, then in poly select mode press ****f G and click image, then assign the material.

Ah, I could have known there'd be a better way. Thanks

[rhettro]

My model loaded from Blender 2.6 Collada output as well. Thank you Spicious!

[Alan Bolte]

I'm sure this would be extremely low priority, and I have no idea how difficult it would be, but the lack of text DPI scaling compatibility is kind of annoying, since I either have to copy-paste things into notepad to read them or switch user accounts to one running at 96 DPI.

[Zacam]

Ever since the BSP version (in fact, any PCS2 build post Feb 19 2011) the Radius for stored glowpoints get's eaten (reset to zero) even after being altered and saved, they go back to zero and they don't display in-game.

[Spicious]

Good catch.

[attachment deleted by a basterd]

[Zacam]

Danke. Works perfectly.

[FreeSpaceFreak]

So is this a new-BSP build, an old-BSP build, or has new-BSP become the standard?

[Spicious]

It's the standard now. Is it causing problems?

As an aside: any engine glows without normals would also have had their radii set to 0.

[FreeSpaceFreak]

It's the standard now. Is it causing problems?

Not that I know of, just trying to keep track of the different versions

[Talon 1024]

Why is this new build of PCS2 saving as COB by default (when you don't give a file extension) when the newer builds can't even open COB? Shouldn't it be saving as POF or DAE instead?

[Talon 1024]

Oh, and one last thing...  Can we please have a move up/move down button so that we can exchange the weapon point positions in the weapon banks without having to do a lot of copydeleting?

Ex. Moving bank 1 down would make bank 2 become bank 1 and bank 1 would become bank 2 and so on...