3d model

[mars_chaos89]

the time u load the *.ddd file model is around my time...it took like half an hour to load the model....

[mars_chaos89]

4. I need to look at the model more closely than I can right now (I don't REALLY have time for this response as I have prep work to do for a bunch of kids I'll be teaching this afternoon, but I'm trying to be helpful) but there are a number of issues. The kickers are that the UV Mapping is not what you showed me (I cannot say without putting more time in - tonight perhaps, after classes) and neither you nor I have a full copy of GLBasic to take account of the amount of time it takes for GLBasic to load 3D models. The time available to work in and the UV Mapping MUST both be addressed first, before you even consider painting a texture. I personally would dump the idea of "painting" an X on the surface and use a 3D "X" model that can be scaled, rotated, and moved into place - because that will cut out a lot of work elsewhere that requires a better understanding of 3D than you currently seem to have.

your suggesting me to load another 3d model(which is an 'X') rather than painting the model with x?that quiet interesting acutally...never thought of it...i will try to do it...

[mars_chaos89]

since im using a .ddd file format...didnt i should get my hand on it texture image?so how can can i get it?does uv mapper does the work?


i try to use the 3dconvert to covert the .obj file to .ddd file..still "converting frames <1>"

[mars_chaos89]

it took me about 1 and quarter hour to finish converting the model to .ddd file....

[Cliff3D]

I'm going to try it without any UV data, and if that's a VAST improvement perhaps with planar mapping.

This did NOT help. At all

your suggesting me to load another 3d model(which is an 'X') rather than painting the model with x?that quiet interesting acutally...never thought of it...i will try to do it...

Yes. I think that will get you a good-looking result without having to know a lot more about UV Mapping which is a whole disipline in and of itself.

it took me about 1 and quarter hour to finish converting the model to .ddd file....

Yeah - as I say, the model is too complex for GLBasic Demo, and if your clients/application cannot stand a wait of half an hour to load the plane, I would advise a lighter plane model - because GLBasic doesn't look likely to get much faster unless gernot has a seriously big surprise up his sleeves. Alternatively something like Deep Paint is specifically designed to let you paint things on the surface of 3D models.

since im using a .ddd file format...didnt i should get my hand on it texture image?so how can can i get it?does uv mapper does the work?


i try to use the 3dconvert to covert the .obj file to .ddd file..still "converting frames <1>"

*I* could, possibly, with a lot of work, figure out the existing UV Mapping or, more likely, remap the model (the existing uv mapping is a mess, frankly - it's possible that there is something meaningful hidden away in there and it only looks a mess because all the parts are jumbled in together, but that doesn't stop it from being an incomprehensible mess at present.

*I* could, with a huge (but probably lesser) effort, remap the model. Not as easily as the original plane modeller could, but these things can be done. You can remap it too, using UVMapper, but I doubt very much that the remapping would prove useful to you as a simple remapping - as you get from pressing just a few buttons in UVM - will leave large areas of the plane model inaccessible, and will cause ghost bits of "X" (or possibly entire X's) to appear on the model, AND will cause horrible smearing, where the shape of the X will distort.

It's hard to explain quickly and easily to anyone who doesn't already know the discipline of UV Mapping/model unwrapping, but IIRC I had a go the other day. Maybe showing an example would be better, but in the meantime trust me - a 3D model "X" is a better idea if you MUST stick with this plane model. If you can switch to a different model, choose one that has been designed to work well with texture maps. and has fewer vertices/facets!!

[Cliff3D]

Here's the model's UV Map. If we make changes in UV Mapper, that actually changes the 3D model. As you can see, right now it's a bit confusing/bit of a mess. I suspect that is because it is meaningless i.e. effectively "unmapped" - not suitable to the task. I could be wrong though, if each seperate object in the model is mapped seperately (IIRC there are over 400 "objects" in the model).

There's also an image of the model as a wireframe, in 3 orthographic views. From top-right going round clockwise let's call them "Front View", "Top View", and "Side View".

In the front view we can't see the sides or top and bottom, so we can't paint an X on them. In the top view we can't see the sides or the very front and back, so we can't paint an X on them. In the side view we get a great shot at painting on the side of the plane - but we can't see the top, bottom, front or rear so we can't paint on them.

I will also try to show how badly simplistic remapping will work, if you like, because it won't be ideal (but it will have to fit into time available)

A 3D "X" model is the way to go, with this plane.

[attachment deleted by admin]

[mars_chaos89]

ok...i will try to do a 3d "x" model to mark the plane...

[Cliff3D]

That would be great (saves me trying to find time to illustrate texture smearing and seams).

BTW, is a load time of 30 minutes (ish) acceptable?

[mars_chaos89]

for the time being it is...
or you do have a way to decrease the time?

[Scott_AW]

30 minutes?

[mars_chaos89]

yup...it took about 30 minutes to load the model that i'am using...

[mars_chaos89]

i had create the 3d 'X' model...but im stuck in calling 2 3d model on the same time...n how can i move the "X" around while not interfere the plane?

[Cliff3D]

for the time being it is...
or you do have a way to decrease the time?

Not immediately, not without changing the model. If you can change the model, decimating it a bit to simplify it would speed up loading.

I don't have a tool on hand and ready that would decimate that large a model, but they can be bought/written (not the latter, by me) and studying the model more closely you might be able to select objects that are not required and simply delete them from the model.

30 minutes?

Yes. This has been the essence of much hand-wringing - the model that mars is using is larger than GLBasic was designed for, really. So it struggles a little bit. It makes it slightly harder to evaluate GLBasic with a model that takes 6 times longer than the demo period to load

i had create the 3d 'X' model...but im stuck in calling 2 3d model on the same time...n how can i move the "X" around while not interfere the plane?

Ahh... good question. I would assume you could call X_MOVEMENT then X_ROTATION then X_DRAWOBJ *for each object* in turn, they would move independantly of one another.

If you can't get that working, then define your "X" in code rather than as a .ddd, using an array of variables to hold the (x,y,z) co-ordinates. You can then manipulate the x,y,z co-ordinates in code before creating the 3d object using X_OBJSTART (but I think you'll find the first method works).

[mars_chaos89]

if key(50)=true then mark()
function mark:
x_loadobj mark.ddd, 2
x_drawobj 2,0

is this the correct coding?
im using if because i want the 'x' is load when the user want only...so when the program is start the user just find the plane model and load it.

[Cliff3D]

if key(50)=true then mark()
function mark:
x_loadobj mark.ddd, 2
x_drawobj 2,0

is this the correct coding?
im using if because i want the 'x' is load when the user want only...so when the program is start the user just find the plane model and load it.

It depends on the rest of the structure of your main loop - you wouldn't want it to reload the "x" model every time through the loop, and you DO want it to show the X after the key has been released. But in essence yes, that's the flavour of it.

As you're not using the (messy looking) UV co-ordinates of the model, I plan on seeing if stripping out normal and UV data makes a .ddd that loads any quicker. Don't get your hopes up - it'll be a small improvement, I suspect, if any at all.