10 replies to this topic

[Wackojacko10101]

I'm trying to use surfaces as a 3d texture, but when I try to draw to it a slight glitch occurs. The walls seem to over lay in the strangest places.

I've found the problematic code if it helps.

surface_set_target(surface)draw_sprite(_guy,0,16,16)surface_reset_target()

Thank you in advance for any any help.
and a big thank you to Gear God, Bikekid2222 and Frankpiet.

Edited by Wackojacko10101, 19 September 2009 - 07:38 AM.

[Southman]

turn off 3d mode first, then make the surface.
surfaces dont work right in 3d mode, if you read the manual, you would know that

[frankpiet]

it looks like hidden surface removal is off.

try turning it on:

d3d_set_hiden(1)

[Newly Discovered]

not only is the depth crazy, but you'll notice that models no longer go through each other, it's either in front, or behind.
I used surfaces to create 3D shadows:


I figured out it was wrecking the depth, so I set up this script:

depth=-objCamera.depth+distance_to_point(objCamera.x,objCamera.y);

this is in the step event of every object. this will adjust the object's depth based on the distance to the camera, fixing the depth issue.
the only problem now though, is because 3D objects no longer go through each other, you cannot draw more than one thing per object.
you can't set the depth per thing you draw right? so, having a human model made from arms, legs, torso, and head, everything is on a single depth, and the script does nothing to help this.

Edited by Newly Discovered, 29 August 2009 - 12:07 AM.

[brac37]

not only is the depth crazy, but you'll notice that models no longer go through each other, it's either in front, or behind.
I used surfaces to create 3D shadows:


I figured out it was wrecking the depth, so I set up this script:

depth=-objCamera.depth+distance_to_point(objCamera.x,objCamera.y);

this is in the step event of every object. this will adjust the object's depth based on the distance to the camera, fixing the depth issue.
the only problem now though, is because 3D objects no longer go through each other, you cannot draw more than one thing per object.
you can't set the depth per thing you draw right? so, having a human model made from arms, legs, torso, and head, everything is on a single depth, and the script does nothing to help this.

Indeed! For convex bodies, you can turn on backface culling to get things right, but with your bodies, you must divide them into parts. I have a similar experience with running games with Linux Wine.

[Newly Discovered]

I don't know if you can tell from here, but the trees are all made from a single object (obviously).
They're made with a cylinder down the middle, and then 5 walls set at different angles.

When you go up next to them, it's very clear the depth issue is in play.
I tried setting culling on, but that just defeats the purpose of having it off (so you can see both sides of the wall instead of drawing the exact same, but flipped).

I read that if you turn off d3d, you can use surfaces. but it probably isn't possible (in my 3D shadows) to turn it on, get 3D projection for shadows, turn it off, render those shadows to a surface, turn it back on, and draw the floor with the texture as the surface, is it?

[Pie Person!]

I recommend that we stay far away from surfaces. This kind of thing is hard to manage, video memory is always hard to manage; its unflexible, a lot of graphics cards poop when Game Maker doesn't handle the video memory properly; and it is oddly abstracted, many times it seems that you have to cheat around to get the proper results.

Especially in 3D mode, you should pick another method rather than using surfaces. Surfaces are always worse.

[Imerxion]

I figured out it was wrecking the depth, so I set up this script:

depth=-objCamera.depth+distance_to_point(objCamera.x,objCamera.y);

this is in the step event of every object. this will adjust the object's depth based on the distance to the camera, fixing the depth issue.
the only problem now though, is because 3D objects no longer go through each other, you cannot draw more than one thing per object.
you can't set the depth per thing you draw right? so, having a human model made from arms, legs, torso, and head, everything is on a single depth, and the script does nothing to help this.

You can do that.. Or you can reset the Z buffer after you build your surface and add it as a texture..

{
  _surface = surface_create(128,128);
  surface_set_target(_surface);
  d3d_set_projection_ortho(0,0,100,100,0);
  draw_clear_alpha(color,alpha);
  //Draw something :3
  surface_reset_target();
  //Make teh texture
  japan = sprite_create_from_surface(_surface,0,0,128,128,0,0,0,0);
  //reset z buffer
  d3d_end();
  d3d_start();
}

Edited by Imerxion, 30 August 2009 - 08:39 PM.

[Schreib]

Surfaces are fine to use in 3D. Why are people so concerned? Video memory management doesn't change in 3D.

[weckar]

well, since the data for z-buffering and surfaces have a tendency to overlap and override each other...

Anyway, there's a reason surfaces are destroyed when using d3d_start()

[GearGOD]

since the data for z-buffering and surfaces have a tendency to overlap and override each other.

Its simply GM's poor implementation. When a rendertarget is set, its contents (depth/stencil buffer included) are cleared. If the contents are to be preserved, the target needs to be resolved before being unset, and written back into during the reset. GM does not do this. Its not a bug, its not a tendency. Its simply how rendertargets work.

Theoretically, you should be able to draw to surface without destroying anything if you ensure that the surface drawing is the first operation that occurs during a step of the game loop.