gap,

Bear with me as we go through this first part of working with the sorter as you have it now.

That is a version I did not want to release as I could fore see the very questions your asking.
:)

It will fix your issues now once you understand the limitations and how to edit things.
Future versions will make all this a non-issue and will just be a 'click-done'
type thing.
:D

If you've gotten this far? Open the obj file you just exported and search for use.
You should have 2. Those will be listed as material_0 and material_1
There should also be a new mtl file.
Now you can run the sorter on the obj file exported from Meshlab.

Take my questions as reminders of features which need for attenction. At this stage, I think I am the one who knows more about the limitations of TDW's importer, as most other modders who have messed with his tool seem to use max as their main 3d program, and TDW himself has probably designed his importer over max-generated files :yep:

:up:

I am sorry that I can't test your full method right away, but it is 2 AM here in the old Europe, and my HD cleaning will take some time. I hope to install meshlab within the next 24 hours :salute:

Take your time Mate.
:)

Your issues have solved several things I was unsure of and could not prove.
Now that they are known? I can program around them and help TDW improve his fantastic work with some real great info.
:up:

I'm thinking he did do alot with wings-3d at one time.
:hmmm:

I still can not figure out what he is doing on import though.
I did take your files and run them through S3D into a dat, exported then imported to a GR2. That GR2 showed a weird ratio compared to going through Meshlab and my sorter.

Now I may have a better understanding of 3D file formats and how they work. I don't know for sure.
I know TDW is the better at programming once he understands things.
Me? I hack along to get things to work.
:haha:
He creates ART!
:up:

As for you doing the most with importing and such?
I agree you have the most detailed information and knowledge on useing the GR2 Importer by TDW.
I would not be working with you if it was any other way.
:salute:
Say the problem of messed up textures never happened? I'd never had started up a project that I lost all the source code for. I'm weird that way.
:har:

considering that I don't have the sorter, I guess I'll just have to wait.
But I will mess around with the meshlab to see if I can figure out at least the UVs.

In the mean time I'll work on correcting my model encompassing your suggestions. :)

The sorter won't fix your UV problems.
All it does is re-order the information of an obj file to allow TDW's program to read it.

If everything goes as I hope today I'll have a little better version ready.
It will eliminate alot of the hand editing on the sorted file.

Thank you a lot :D :up::yeah:privateer :rock::salute::sunny:

I mentioned I did an import/export useing S3D to adjust the file.
Here's a screen shot of both test imports to GR2.
Look closely at the Vertices count.

http://i108.photobucket.com/albums/n...re_Imports.jpg

The top file was done useing S3D , the bottom useing Meshlab and then sorting the file.
The top GR2 file size is 1,485 KB
The bottom is 411 KB

That is a major saveings and the UV's for both are correct.
:yep:

Yes, I used to think so until recently, but all my attempts to perform loose imports of Wings3d-exported object files have failed. Only max-exported objects gave the desired results with loose imports. Strict imports didn't pose any problem though, no matter the exporter used.

Tried that. S3d, Softimage Mod Tool and Blender obj files all show UV map distorsions when imported through GR2 Editor.

I got to amend your statement: I am the one who had the worst problems using the GR2 Importer by TDW. I would be curious to hear from BIGREG and Silentmichel who have laso used it extensively.

Is that the last version of the balloon that I sent you yesterday? Exported straight from Wings3d, that object only has 3,226 vertices, which is even lesser than the 4,020 vertices count of the meshlab export...

Yes it is.
BUT! it gets the filter in mesh lab run on it!
We converted to pervertex from perwedge.
Some of the verts are repeats but with specific tex co-ords.
It's that whole thing I told you about on shuffleing things like that.
You can't think of an import to a GR2 as a 'perfect copy' of your obj file.

Also, look at the version done through S3D? Not even close to your verts count!
So did you get Meshlab installed yet?

Ok thank you, that makes perfect sense, and it explains why objects exported from game (both using GR2 editor or S3d) have so many redundant vertices/edges. :up:

Until now I was erroneously convinced it was due to poor optimization by devs :doh:

Exporting from a GR2 or with S3D?
I'd run it through Meshlab and use a couple of filters to reduce things right off the bat.
:D

It's not the Tool used causeing that extra info. They are direct exports of information in the files converted to the obj format with no post-processing done. It's perfect translation so to speak.

I always use Wings3d's 'Cleanup' command on recently exported objects for getting rid of isolated or very close vertices, followed by a 'Weld Point Tool' processing in Softimage Mod Tool. I also find Mod Tool's poly reduction tool very useful, but I only use it on my own high poly models. :yep:

@ privateer

I have saved the texture in jpg format and changed model's mtl file according to your instructions, but everytime I open the model in MeshLab (v 1.3.2_64bit), I receive the following message:

http://img811.imageshack.us/img811/6807/knso.jpg

The obj file itself is still the one exported from Wings 3d, of course. What do I do wrong? :hmmm:

Are you the wrong (bad) opinions about the developers?
Import/export from/to obj-files by TDW's (or privateer's) program does not have any relation to developers.
I think. :D