Dead Hackers Society
Other BBSes »
 
 
Demoscene  Coding  CT60  Buy/sell

Atari coding BBS
 
Re: Texture U/V misunderstanding
Posted by: Orion_ Jan,26.2015-15:47 

no there is a misunderstanding.
when I write move.l #$0001FFFF,d0 ; U = 1 V = -1
I mean: U increment = 1/256 , V increment = -1/256
so that would be something like: Uinc = 0,00390625, Vinc = -0,00390625
My texture are always 256x256 (8bits)
if V happen to be negative then it will wrap at the bottom of the texture.
(since we keep the lower part of the longword it will automatically wrap if it overflow 65535)

About your loop, I never really understand what "addx" do.
Giving the loop code is nice, but guessing the correct value to put in those register is a bit hard :/
from what I understand, D0 would be V in 8.8 fixed point value
D1 would be U in integer value ?? (where is the fixed point part since you don't do any shift ??)
why doing an add.L on D0 since it a 8.8 fixed point value ?? add.W ?
why addX ?
Orion_ is #confused#








[All messages in this thread]    [Start new thread]

Topic Posted by  Date 
Texture U/V misunderstanding Orion_ Jan,24.2015-17:41
  Re: Texture U/V misunderstanding ggn Jan,24.2015-21:43
    Re: Texture U/V misunderstanding Orion_ Jan,25.2015-18:07
      Re: Texture U/V misunderstanding ggn Jan,25.2015-20:51
  Re: Texture U/V misunderstanding mikro Jan,26.2015-10:05
    Re: Texture U/V misunderstanding Orion_ Jan,26.2015-15:47
      Re: Texture U/V misunderstanding Orion_ Jan,26.2015-17:54
      Re: Texture U/V misunderstanding mikro Jan,27.2015-11:26


Reply to this message
Name:
Topic:
Anti-troll code:

Message:

What's the anti-troll code?
That's your personal code to be able to add comments and messages on the dhs.nu site.
Don't have a code or forgot it? Fix it here.
© 1994-2024 Dead Hackers Society Contact: Anders Eriksson