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.

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.

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

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

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

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

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.

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...

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?

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

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.

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.

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...

java-gaming.org is not responsible for the content posted by its members, including references to external websites,
and other references that may or may not have a relation with our primarily
gaming and game production oriented community.
inquiries and complaints can be sent via email to the info‑account of the
company managing the website of java‑gaming.org