posted 12-12- 06:03 AM               

For those that want it, it is at:

http://opstudio.webjump.com

or

http://people.smartchat.net.au/~bryan_rus/OPS
Please let me know if it has any problems

posted 12-12- 10:19 AM               

I'm about to grab it and if this does in and out of OPS you are my GOD !! lol

thanks alot man

you keep this openplane stuff alive

posted 12-12- 05:38 PM               

------------------

posted 12-12- 06:23 PM               

The way the OBJ plugin and the LOD plugin load texture ID's is a little different. Because the OBJ has support for a material library, the loaded SM file is scanned for a texture with the same name as the one assigned to a polygon in the imported mesh (or it creates a new one if it doesn't exist). This means that, if there is a material library, the LOD should always have the right texture on it, regardless of whether the texture even exists in the current file or not.

For LOD files, the only reference to the texture is a texture ID. So, if you export a LOD from a P51 that is using the main texture, and import it into a spit, the polygons in the LOD will probably use the main Spit texture (if it has the same ID).

The Imported mesh will only inherit the texture from the LOD it replaces when no texture can be derived from the imported File. In the LOD plugin it should always use the imported texture ID. The OBJ plugin will do generally this when there is no OBJ Material library present.

To checkout what’s happening, look at the LOD file you are importing and note the texture ID(s) assigned. Look at the textures for the loaded SM file, and see if the texture with the ID you noted in the LOD file is the one that is actually being applied or not.

How do you get around this? You will obviously need to add the texture you need into the SM file, and then change the LOD files texids to this new texture (mental note : add a "Add Texture" function )
How do you add a new texture? Either wait for me to get off my ass and add this feature or cut and paste a model that uses the texture you want (texture references are passed as texture file names for cut/copy/paste).

It is possible that I have done something wrong in there, so if you check all of this out and it still looks screwy then let me now and I'll have a closer look.

posted 12-12- 07:40 PM               

Anyway, I have now solved the problem by combining two struts to a single object and thus freeing one up for the wire I've been trying to add. The part now arrives in OPS and I just export it, change the texture references by hand in the lod file and import the LOD back into OPS. (I have a suspicion the problem is arising from adding a texture index number in AC3D that doesn't yet exist in the ASC file - what I ought to do is check the lod file out before using builder.) So I've got around the problem which may have nothing to do with your program.

posted 12-13- 05:38 AM               

I am having problems with your LOD plug-in as well relating to textures:

If I import a LOD with a new texture ID, this ID is overwriten. I had a LOD with a texture ID of 4 open in OPS. I imported a LOD that was just like this LOD but had texture IDs of 4 on some polys and 26 on others. Both were valid texture IDs and showed up in the texture list. After I imported the new LOD all of the texture IDs were 4.

I am not sure what is happening. - Maybe the texture IDs of the LOD I am replacing are over-riding the new LOD's texture IDs.

I will send you more info as I test... Any ideas?

This plug-in will speed up dev much!!!

Also thanks for fixing the rotate key!!! So far very stable at Version 1!

------------------
-Sv =FC=

WWI in SDOE!

posted 12-13- 02:06 PM               

I understood it was impossible to have more than one texture on a single lod. I don't why, but someone posted something to that effect some time ago.

posted 12-13- 06:06 PM               

SV : The way the plugins work (when importing) with textures is that if a valid texture ID (>0) for a LOD polygon is passed up to OPS then it will be used, other wise the texture ID of the first Polygon of the existing LOD is used. This also applys to flags and material.

The LOD plugin always sets the texture id to the one it reads from the file, so in theory it should always pass the right texture ID. Of course not every thing happens according to the theory so I'll have a peek at it tonight.

posted 12-13- 08:01 PM               

Michael,

You can indeed have multiple textures per LOD. Just select the surface in question in AC3D and set the surface type (colored box). Then edit this surface and set the "shinniness" value to be the texture index you need. This will put this texture number next to this polygon in the LOD file. Works great!

What used to be hard to understand was mapping single textures across multiple polygons - even different parts of single textures to various polygons within a LOD - usualy in the name of "skinning." This is all easy to do now if you follow:
http://www.schoolmusic.com/chickencoop/se5a/v6/index.htm

This is info on how to texture map.

------------------
-Sv =FC=

WWI in SDOE!