Search results

Well, I just tried playing with a model with a BSP tree, and I achieved partial success by including the tree.iff file, instead of copy/pasting the tree.iff.txt into the "de-compiled" model. EDIT: If your BSP tree is still not working as expected, try increasing the radius of the collision...

How big is the IFF file you compiled that includes the faulty BSP tree? On the other hand, did you see Killerwave's Capship tutorial? It explains how to use ModelC and WCPPascal to convert capships.

The dimensions according to Blender are: Length: 595.5235596 Width: 166.8859406 Height: 120.522583

Here you go...

Wing Blender 1.6.2 has been released. This is a patch release that adds importer support for v9 meshes (CALLISTO.IFF, TERRAIN.IFF, PV256.IFF, SHDALIEN.IFF, SHIELDFX.IFF).

OMG! Look what I found. This model is CALLISTO.IFF, which I was recently able to import into Blender, after some investigation into the v9 mesh format, and a few changes to my Wing Blender importer code.

Wing Blender 1.6.1 has now been released.

Well, that's actually an error on my part. It should work if you have only one shadeless material with that numeric filename, or if you use a non-numeric filename for the texture. EDIT: Fixed. A new release (1.6.1) is now available.

Here's two quick hints for using Wing Blender: If you don't want to include certain hardpoints in the exported IFF file, just hide them in Blender's viewport. If you want certain faces to ignore shading/be fully lit all the time (like the Midway's engine intakes, or the intakes on the Wasp and...

I don't know what that could be caused by, but I took a look at the original Excalibur model in a hex editor, and it has a BSP tree and REGN/BLCK forms for some reason.

It's possible, but I guess I'd like to keep my options open. The "export only active object" option is true by default. I guess I could ignore the filename the user enters if they choose to export every valid thing in the scene root, and instead just get the output directory and name the...

Good idea. I'll use an underscore to separate the base model name from the child model name. But the thing is, there could be multiple base meshes if you decide to uncheck the "Export only active object" option in the export view. If you do so, it will export every valid object in the scene...

I'm happy to report that I'm making good progress on the next version of Wing Blender (which is now 2.0.0 instead of 1.7, due to significant changes in the code), and it is getting closer to being ready for testing. I need some help, though. I don't know what I should do for exported mesh...

When I was recently looking through the 3D models I extracted from WCSO, I came across MERCURY.IFF. The name of each LOD for this model is "midway". Perhaps that's the Midway Prototype design? I haven't yet been able to take a better look it myself. EDIT: Unfortunately not. It's apparently just...

Another thing which I just recently thought of was allowing users to customize the RANG chunk because I think it specifies the distances for which each LOD is "activated". You would parent an empty object named as follows to any LOD object greater than 0: drang=<dist> Where dist is a whole or...

In case anyone missed it, here's an overview of what I'm working on for Wing Blender 1.7. The new naming covention for the main model, if the user decides not to use the active object as LOD 0, will be: detail-<lodn> where <lodn> is the LOD number. The new naming convention for child models...

Congratulations on the Fan Project of The Year Runner Up award! I've been working some more on Wing Blender. The latest version of the Wing Blender master branch now allows users to exclude the FAR chunk. I've created a new branch for the next version (1.7) of Wing Blender, and it will be...

I have no idea how the BSP trees for WCP/SO capships and corvettes work, or how they are built. Sorry. :( However, BSP tree construction is on the roadmap for future Wing Blender versions. And if there's anyone willing/able to help me with that, then great!

To clarify: Option 1... Sets the child object CNTR to 0,0,0. Generates a hardpoint at its origin position, relative to its parent. Does not modify its origin position. And option 2... Sets the child object CNTR as the vector between the child object's original origin point and the hardpoint...

Since this came up, I figured I should come up with some way of exporting child objects in a way that makes it easy to attach them as child objects, EPODs, or special addons like the wasp's booster pack So, how would you like me to go about implementing this? Each object that is a child of the...