« previous next »
Pages: 1 ... 5 6 [7]   Go Down

Author Topic: Texture drawing  (Read 38404 times)

0 Members and 2 Guests are viewing this topic.

Offline chattahippie

  • LV6 Super Member (Next: 500)
  • ******
  • Posts: 358
  • Rating: +27/-0
  • Super Member! :D
    • View Profile
Re: Texture drawing
« Reply #90 on: August 16, 2011, 05:14:02 pm »
Quote from: t0xic_kitt3n on August 16, 2011, 05:12:29 pm
That looks very nice, though it looks like there is a "seam" between the two triangles you are drawing. Is that intentional?

I think that he is showing off it's 3d aspect by tilting them, as if a square was folded partially
« Last Edit: August 16, 2011, 05:15:24 pm by chattahippie »
Logged

Offline ben_g

  • Hey cool I can set a custom title now :)
  • LV9 Veteran (Next: 1337)
  • *********
  • Posts: 1002
  • Rating: +125/-4
  • Asm noob
    • View Profile
    • Our programmer's team: GameCommandoSquad
Re: Texture drawing
« Reply #91 on: August 16, 2011, 05:14:26 pm »
Quote from: zeldaking on August 16, 2011, 05:05:23 pm
That looks very nice, good job. Is this for some other project?
Yes, for a first person shooter.I'm not giving much information about it (just in case it won't work).

(Yet) an other question: what should be the best (when you look at memory and speed) way to do z-ordering? a z-buffer (which contains the depth of every pixel) or to save the avarage depth of every polygon, then sort the polygons and draw them in the correct order (furthest to nearest)?

EDIT:
Quote from: t0xic_kitt3n on August 16, 2011, 05:12:29 pm
That looks very nice, though it looks like there is a "seam" between the two triangles you are drawing. Is that intentional?
It's not intentional. It's caused by the texture being rotated a bit differently on the two triangles. This is just the way affine texture mapping works.

« Last Edit: August 16, 2011, 05:17:16 pm by ben_g »
Logged
My projects
 - The Lost Survivors (Unreal Engine) ACTIVE [GameCommandoSquad main project]
 - Oxo, with single-calc multiplayer and AI (axe) RELEASED (screenshot) (topic)
 - An android version of oxo (java)  ACTIVE
 - A 3D collision detection library (axe) RELEASED! (topic)(screenshot)(more recent screenshot)(screenshot of it being used in a tilemapper)
Spoiler For inactive:
- A first person shooter with a polygon-based 3d engine. (z80, will probably be recoded in axe using GLib) ON HOLD (screenshot)
 - A java MORPG. (pc) DEEP COMA(read more)(screenshot)
 - a minecraft game in axe DEAD (source code available)
 - a 3D racing game (axe) ON HOLD (outdated screenshot of asm version)

This signature was last updated on 20/04/2015 and may be outdated

Offline ztrumpet

  • The Rarely Active One
  • CoT Emeritus
  • LV13 Extreme Addict (Next: 9001)
  • *
  • Posts: 5712
  • Rating: +364/-4
  • If you see this, send me a PM. Just for fun.
    • View Profile
Re: Texture drawing
« Reply #92 on: August 16, 2011, 07:18:57 pm »
That looks awesome, ben_g.  Great job. :D
Logged

Offline fb39ca4

  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1749
  • Rating: +60/-3
    • View Profile
Re: Texture drawing
« Reply #93 on: August 16, 2011, 07:31:27 pm »
It depends on the situation. When there isn't very many polygons, sorting is faster, but past a certain number, (I think around a hundred) the sorting algorithm becomes too slow and z-buffering wins. Also keep in mind only z buffering is able to correctly show intersecting polygons.
Logged

Offline ben_g

  • Hey cool I can set a custom title now :)
  • LV9 Veteran (Next: 1337)
  • *********
  • Posts: 1002
  • Rating: +125/-4
  • Asm noob
    • View Profile
    • Our programmer's team: GameCommandoSquad
Re: Texture drawing
« Reply #94 on: August 18, 2011, 02:21:24 pm »
Quote from: t0xic_kitt3n on August 16, 2011, 07:31:27 pm
It depends on the situation. When there isn't very many polygons, sorting is faster, but past a certain number, (I think around a hundred) the sorting algorithm becomes too slow and z-buffering wins. Also keep in mind only z buffering is able to correctly show intersecting polygons.
I know z buffering is only able to correctely show intersecting polygons, but also: one byte isn't accurate enough for polygons close to each other, so I need two byter for every pixel on the screen, so that would make 1228 bytes, which is really much, and I'm wondering if it's worth it to use that many bytes for only the graphical part.
Logged
My projects
 - The Lost Survivors (Unreal Engine) ACTIVE [GameCommandoSquad main project]
 - Oxo, with single-calc multiplayer and AI (axe) RELEASED (screenshot) (topic)
 - An android version of oxo (java)  ACTIVE
 - A 3D collision detection library (axe) RELEASED! (topic)(screenshot)(more recent screenshot)(screenshot of it being used in a tilemapper)
Spoiler For inactive:
- A first person shooter with a polygon-based 3d engine. (z80, will probably be recoded in axe using GLib) ON HOLD (screenshot)
 - A java MORPG. (pc) DEEP COMA(read more)(screenshot)
 - a minecraft game in axe DEAD (source code available)
 - a 3D racing game (axe) ON HOLD (outdated screenshot of asm version)

This signature was last updated on 20/04/2015 and may be outdated
Pages: 1 ... 5 6 [7]   Go Up
« previous next »