3DS model loader test "TDSTest" not working

Engines, Libraries and Tools Xith3D Forums
#1

I only see a black screen. Does anybody has a clue whats going on? Should this work? when did it last work?

Debug-Output:


******************************************************
 TDSLoader Debug Output
   file: C:\development\projects\xith-tk\demo\models\jeep1.3ds
******************************************************
Processing chunk: 4d4d
Skipping Chunk: 2
Processing chunk: 3d3d
Skipping Chunk: 3d3e
Processing chunk: afff
Processing chunk: a000
Processing chunk: a010
Skipping Chunk: 12
Processing chunk: a020
Skipping Chunk: 12
Processing chunk: a030
Skipping Chunk: 12
Processing chunk: a040
Processing chunk: a041
Processing chunk: a050
Skipping Chunk: a052
Skipping Chunk: a053
Skipping Chunk: a100
Skipping Chunk: a084
Skipping Chunk: a087
Skipping Chunk: a08c
Processing chunk: a200
Couldn't find image in classpath
Skipping Chunk: a351
Skipping Chunk: 100
Skipping Chunk: 1400
Skipping Chunk: 1420
Skipping Chunk: 1450
Skipping Chunk: 1460
Skipping Chunk: 1500
Skipping Chunk: 2100
Processing chunk: 4000
Processing chunk: 4100
Processing chunk: 4110
Processing chunk: 4140
Processing chunk: 4160
Skipping Chunk: 4165
Processing chunk: 4120
Skipping Chunk: 72
No key frames found!

BTW. how do you guys handle bug/task tracking? The xith-tk issue tracker seems unused.

#2

I’ll have a look at it in the next 30 minutes. OK?

The tasks weren’t tracked at all. Recently started a dev-plan for version 1.0 to do this. And Amos made one for version 2.0. The bugs are only tracked on this forum. I guess a bug tracker system sould be useful.

Marvin

#3

I’m very sorry. I had a look into the test, but I cannot find the failure. The test is quite simple so I guess, the failure is related to the loader itself (maybe due to the BranchGroup changes). We’ll have to wait for Amos and ask him to fix it. He has a deeper knowledge of the TDS loader.

Marvin

#4

I’ll have a look today (a bit later), I’m sucessfully using that loader, well with little modification though, but I should be able to spot the problem.

Bohdan.

#5

What modifications did you make? Does it make sense to commit them?

#6

This was a while ago when I make them and it was regarding for examle situations like that. I often will get a model exported like 3ds says, and it would have a fake references to not needed textures, or textures with “blank” path, like path="", and loader would normaly crash on these kind of things, so it was sort of “safety” modification, very litle. Maybe something else I did also, I could check. If this is something of interest - I can point on this modifications, no problem. I just was taking that as something specific to my case, you may never get to such a problems…

Edit: so this is when the exported 3ds model is not actually 100% properly exported… Don’t know why it is happening like that, but it often does, for me at least :slight_smile:

#7

Safety is always good ;). So if your modifications don’t do a harm, please look, if you can commit them.

#8

Yes, these changes are just kind of neutral, so no harm :), ok, I’ll post it sometime later today, and I should fix that TDS test too, I believe.

Edit: Ok, I can confirm I have TDS test working already, but with my “loader modified” thought, don’t have time right now to dig what actualy was wrong, but will do today later, so you can leave it for me, will be definitely done.

#9

To fix TDSLoader (newdawn’s):

in “org.xith3d.loaders.tds.newdawn.FaceArrayProcessor” uncoment line:

 int flags = file.readUnsignedShort();

or make it like that:

 file.readUnsignedShort();

otherwise proper stream reading will stop on chunck “0x4120”, as pointer will not shift properly, and on next chunk wrong tag will be read and its length etc…

Bohdan.

P.S. Having done that see also if the model can be scaled in TDSTest or translated further from the camera, as it is loaded to much to close… I have tried actually to change “scale” in RotatingModel, but it doesn’t seem to have any effect, is it working?

P.S.2 BTW, “galleon.obj” resource is missing, so OBJTest doesn’t work too, for me…

#10

Do you have CVS write access? If not I can make the changes this night and commit them. Otherwise please commit them yourself.

Should be.

It’s not missing. The path is wrong. Prefix “demo/” to the path and it should work.

Unfortunately I cannot do all this now, since I have an uncompilable state at the moment.

Marvin

#11

Yes, please commit changes, I don’t have developer access.

hmmm… I can’t find that file in xith-tk tree at all… though I have very recent cvs update currently…

#12

done.

That was wrong. The path was correct! But the View as set to close to the model.

The file is there. And the test is working. Please recheckout. Maybe you have set your filters wrong ???. check your filesystem, if the file is there. If it is not, please load it manually from web-CVS or something like that.

If that also doesn’t work, please post again.

Marvin

#13

It seems that file (“galleon.obj”) was deleted (it is in the attic, anyhow), that’s why it is not possible to check it out…

#14

Strange ??? It was on some kind of CVS ignore list. I’ve now readded it to CVS.

Marvin

#15

@Marvin: Thanks! BTW, check your PMs

#16

Would you like to have CVS access ? Are you registered on java.net ?

It would be more convenient for you when you make changes to Xith3D. And the whole community would benefit of your fixes.

#17

The TDSTest is working now, thanks!

#18

[quote="<MagicSpark.org [ BlueSky ]>,post:16,topic:28356"]
Would you like to have CVS access ? Are you registered on java.net ?

It would be more convenient for you when you make changes to Xith3D. And the whole community would benefit of your fixes.
[/quote]
Yes, thanks, it would be great ;D, if you could.
Yes, I’m registered.

Bohdan.

#19

Have you already requested a dev-role on the project? This would help Amos to find you on dev.java.net.

#20

Alright, I see… So I go there and see how to do that :slight_smile: Thanks for information!

Edit: Done ;D