You could send a relative path to your textures (such as textures\mytex.jpg instead of c:\bla\blubb\myprojects\delphi\megaman\textures\mytex.jpg).
If you have to send absolute paths, you can derive them from the starting folder of your application by using ParamStr(0) and concatenating your file names.

_________________
Viel Spaß beim Programmieren,
Mars
http://www.basegraph.com/

Where can I set the texture-Path?? The best way would be, saving the Textures in .3DS . But...
It would be cool if there was a property like:
TAll3DSMesh.texturepath
So it would be possible to set an explicite searchpath for every Mesh...

_________________
Blog: kevin-fleischer.de und fbaingermany.com

modell := TAll3dsMesh.Create(self);
modell.TexturePath := 'models\';
modell.LoadFromFile('models\hinterachse.3ds');

And all (läuft?! kann ja schlecht sagen goes oder?) is good ^^

and everything works

_________________
Viel Spaß beim Programmieren,
Mars
http://www.basegraph.com/

I think i have an idea, why my code don' work... What must I write by tAll3DSMesh(-?????-). If I whant to use "self" there...where have I to do this (in which procedure?)?

PS: Ohhhhhh real brute force english.... 8)

_________________
Blog: kevin-fleischer.de und fbaingermany.com

Just use NIL.

_________________
www.SaschaWillems.de | GitHub | Twitter | GPU Datenbanken (Vulkan, GL, GLES)

I think I've found another bug. When you mirror an object, it isn't rendered correct anymore with your loader. Although better than Lischke's loader, that didn't render mirrored objects at all, your loader seems to mirror the object wrongly (didn't yet took a look at the source where mirroring is taken into account).
Take a look at this small model I put together, left is how it looks rendered with gl3Ds.pas and right shows it in 3DS :



It seems that the right half of the brain is also (wrongly) mirrored on the Z-axis. But I don't know how 3DS stores mirrored vertices when exporting to .3DS, so it may be a fault within 3DS-export itself.

_________________
www.SaschaWillems.de | GitHub | Twitter | GPU Datenbanken (Vulkan, GL, GLES)

I have two neg. points to say.

1. You need so many librarys for your library! I think it would be coul, if you put all those Functions you need (from any library you use) in one library (gl3DS_helpers). This would even be an advantage when your library is spread over the whole inet.

2. It don't work! Ok, I think it's not a real problem, but i put your library to my uses part and tried to compile. I get 3 Faults. Always "Not enough Parameters". All those Errors depend to Loadtexture(); . This Function needs 3 Parameters, but you give only 2. As I see, you forget to give a Boolean-var to the Function. So what should I write in there? A Boolean with a Value of true or false?

PS: The Error occoure in Line 2232, 2234 and 2450.

_________________
Blog: kevin-fleischer.de und fbaingermany.com

Thanks for all the feedback.

Some short answers:
-I was not aware of mirrored 3ds meshes.
-The texture part is a work in progres and i changed the texture unit recently and i will do that again. I must have missed some calls to it.
-with create just use nil. Or if you use a form use the form there that way on closing the form the mesh will be destroyed also.
- 3DS files dont store paths to textures, they just store the texture filename (as far as i know). 3D apps search the textures on texture paths e.g. pointing to texture libraries. That is what the texturepath property is for. You better set the texturepath on tall3dsmesh even if the textures are in the same dir as where the 3ds file is. On loading the 3ds files all texture files should be loaded automaticaly.
-I am using many units for now, once i am happy with things that will be replaced. But not for now.
-Try using a tlist structure in stead of an array. Do use new(mesh) where mesh is a PAll3DSMesh structure.
-Do test the 3ds mesh loading directly into a tall3dsmesh directly if it is not working if it does not work there either that 3ds mesh is not supported yet.

I hope this answers some questions.

Keep up sending feedback, i need it.

_________________
http://3das.noeska.com - create adventure games without programming

I'm right now working on a gameproject where I use fairly complex scenery and on of the scenes I'm using shows a prehistorical forestscene. And for the foliage of the trees, I'm using planes but since planes in 3DS only have one side, parts of them get culled as soon as you enable back-face culling (which is a must cause it gains you a good amount of performance) so that the foliage isn't displayed correctly :


(Left : No two-sided materials, Right : Correct display with two-sided materials)

To get around this, you need to load a chunk called MAT_TWO_SIDED that contains nothing, but if it's present for a material, it's a two-sided material. If you have such a material, you'll just have to turn back-face-culling off :

MAT_TWO_SIDED :
This is very usefull if you're using backface culling (which gives you a nice performanceboost) and use planes for things like foliage. Since those planes normally would get backfaceculled some parts may not be visible and that may lead to a wrong display of things like trees and so on. So you just need to say 3DS that the material for such things is two-sided and then disable culling for all faces using that material.

Loading :


Applying :



P.S. : To get two-sided materials in 3DS, you'll have to check this in the material editor :

_________________
www.SaschaWillems.de | GitHub | Twitter | GPU Datenbanken (Vulkan, GL, GLES)

nice

It goes in the next release.

To make it easy for me: What is the hex number for: MAT_TWO_SIDED

_________________
http://3das.noeska.com - create adventure games without programming

Ah sorry, here is the ID the corresponding chunk :

_________________
www.SaschaWillems.de | GitHub | Twitter | GPU Datenbanken (Vulkan, GL, GLES)

I was just building a scenery for my current project, where I had some transparent objects in, and since your gl3DS now just draws mesh after mesh, I got some problems with that : Just create an object that's transparent and create a second object in it that's not transparent. Since your unit draws mesh 0 first, you'll only see the transparent object (cause you have to do sorting for transparent objects).

So I enhanched the loader so that it first draws all non-transparent objects and then at last the transparent objects. So that transparency works in most cases (as long as there aren't two transparent objects overlapping).
First thing I do now is to check if a mesh has at least one face that has a transparent material assigned, to make it easy, I do this in the calcvnormals-procedure as that get's called after all meshes are loaded and therefore is the best place for that :


After that it's easy to render all transparent objects last :


It's an easy to implement feature, but especially in scenes that have transparent objects in them, it's necessary.

_________________
www.SaschaWillems.de | GitHub | Twitter | GPU Datenbanken (Vulkan, GL, GLES)

the latest versions should render transparent meshes correctly already. I have a look at your code and see if it is better...

_________________
http://3das.noeska.com - create adventure games without programming

I've downloaded Version 2.4a from your homepage.
Is it posible that you packed a wrong Version of the Logger.pas to the Zip?
The Compiler don't know a methode named "Writeln()" (line 337 / .LoadTexture()).
Its no great thing to fix it myself but, its bether you know about it.

_________________
Blog: kevin-fleischer.de und fbaingermany.com