[ASM68000] rubik's

[heavy]

vbl issue

test
rubiks.S

[Arnaud.68000]

For your VBL issue, change IFD by IFNE, I do not know what IFD does although ASM2 accepts it.
Here are the commands i found, maybe you wanted a similar one :

IFC Conditional Assembly String Equality Test.
IFDEF Conditional Assembly Symbol Definition Test.
IFEQ Conditional Assembly Equal to Zero Test.
IFGE Conditional Assembly Nonnegative Test.
IFGT Conditional Assembly Greater than Zero Test.
IFLE Conditional Assembly Nonpositive Test.
IFLT Conditional Assembly Less than Zero Test.
IFNC Conditional Assembly String Inequality Test.
IFNDEF Conditional Assembly Symbol Not Defined Test.
IFNE Conditional Assembly Unequal to Zero Test.

I read your code and have changed mine using SECTION.
That's clear that the code is more simple, thanks.

WaitVBL:
Why do you prefer use a variable RASTER=300 instead of using parameters DISPLAY_Y+DISPLAY_DY ?
Same question for the copperlist


CopperList

What does ?

dc.w $ffdf,$fffe
dc.w $2c0f,$fffe,$100,0

and why do you duplicate END instruction ?

;Fin
dc.l -2
dc.l -2

[heavy]

IFDEF not recognized by asmtwo (not diff. with IFNE or IFD, try it yourself....)
I have no more vbl issue with the nop added if DEBUG disabled
and no more bug with coplist when adding or removing lines

raster=300 just for testing other values !
for the coplist, just because it's too long and for testing other values too

$ffdf,$fffe => more than 256 lines, just a test when adding lines on coplist

[Arnaud.68000]

I use ASM Two 0.96w and IFNE is recognized.

I have VBL issue with your code using IFD, if i replace by IFNE your code is working

Amazing !

[heavy]

what ??? I talk about IFDEF
IFNE is recognized
IFD is recognized

I also use ASMTwo 0.96w and ASMone 1.0.5 / TFA

too many timing problem (the code, winuae 32, winuae 64)

[Arnaud.68000]

Yes, i confirm IFNE and IFD are recognized with ASW-Two, I tested on a simpe code.

If I replace (also in my code) IFNE by IFD I got a VBL issue... I need to understand.
Maybe a mistake on a variable ?



For timing, I use winUAE 64, A500 OCS, cycle-exact (full)
I don't know if it solves the pb

[Antiriad_UK]

Originally Posted by a/b

Eh, it's simple stuff made for a demo, nothing more nothing less. Didn't check Arnaud's code in detail, french gives me exception #4 ;p, but it looks like a completely different approach.
As I said, dual playfield is the critical part, makes rendering trivial. Simple "script", takes a series of +/- 1-6 (6 possible moves, sign determines rotation direction), selects one of 6 predefined poly/corner sets, generates inner 3d points, does some math and throws everything at the screen, Tops everything off with shiny line vectors to hide ugly edges ;P. The usual convex vector demo stuff.
Playfield priority (and the consequent remapping of colors) is based on the sum of corner z coords.

I really like that

[KONEY]

Did I compile the correct source?

[heavy]

works fine today (original version and modified ones) !
depend of the start config used of winuae (a500 512k/512k ocs). problem with ecs mode

but with original version from github if you uncomment the line 1684 dc.w COLOR04,MIRROR_SCROLL_COLOR
no more cube and a guru