rainbow fuji logo with sourcecode on github

[ascrnet]

On 7/28/2021 at 6:06 PM, tane said:

This version (latest checked in Github) is not working with some programs. For example when adding an image (G2F) thereafter, it will not work all times, the image doesn't start.

it's ok that it doesn't work, since both are using the $2000 address that's why there is a memory conflict.

but your idea is to use it as a presentation?

 

On 7/29/2021 at 6:49 AM, Jetboot Jack said:

This the one Atari UK provided to developers - used on several of the final games produced for the 8bit line...

 

It was the same data as the Xanth F/X Swan demo - https://demozoo.org/productions/98552/

 

      sTeVE

I just did a quick check and the screen design is different. I think they just took it as an idea but did it their way.

 

Xanth F/X Swan

  5100: x5   blank 8
  5105:      blank.i 8
  5106:      mode E @ B740
  5109: x7   mode E
  5110:      mode E @ B740
  5113: x7   mode E
  511A:      mode E @ B740
  511D: x55  mode E
  5154:      blank 8
  5155:      mode F @ 6800
  5158: x31  mode F
  5177:      blank 8
  5178:      blank.i 8
  5179:      mode 2 @ 5608
  517C:      waitvbl 5100

the other

  2000: x6   blank 8
  2006:      blank.i 8
  2007:      mode 6 @ 201C
  200A: x8   mode 6
  2012:      blank 8
  2013:      mode 2 @ 20D0
  2016: x3   mode 2
  2019:      waitvbl 2000

for me it has some small differences.?

[Gunstar]

On 4/22/2021 at 1:56 PM, ClausB said:

Tighter, slower, and less wide, since you're asking.

Yes, it's all out of proportion like a 4:3 image stretched on a 16:9 screen.

[Gunstar]

On 4/24/2021 at 8:24 AM, pps said:

Maybe this one suits to your eyes

 

Zip contains all the sources and executeable file: rainbow_fuji.zip

It's properly proportional, but isn't there enough screen real estate to make it slightly larger still too?

 

Sorry, I see now that this thread is months old and lots more changes and different versions made and you are probably long done caring about changing it any more. I'm always kicking myself for not keeping an eye on the post's date before I start replying like it was today!

Edited July 31, 2021 by Gunstar

[tane]

1 hour ago, ascrnet said:

it's ok that it doesn't work, since both are using the $2000 address that's why there is a memory conflict.

but your idea is to use it as a presentation?

Ok, I knew that, let's say there is no conflict of addresses, for example the first org could be $3000 and the one before the font $4000, and the rainbow works. But if then the image has (I guess) player-missiles on, the image won't load.

 

Also if you turn off the display just before, the rainbow doesn't show up. Is there any way to re-enable the display?

  lda #$00
  sta $D400                       ; DMACTL
  sta $22F                        ; SDMCTL

 

[pps]

4 hours ago, Gunstar said:

It's properly proportional, but isn't there enough screen real estate to make it slightly larger still too?

 

Sorry, I see now that this thread is months old and lots more changes and different versions made and you are probably long done caring about changing it any more. I'm always kicking myself for not keeping an eye on the post's date before I start replying like it was today!

Haha, you're right, I have finished my work here Make it larger is possible. I did this fast and wanted to have about the same resolution as good old ATARI code. btw final usage of this (by me) is in my outline 2021 demo: >>Colored FX<<

[ascrnet]

23 hours ago, tane said:

Ok, I knew that, let's say there is no conflict of addresses, for example the first org could be $3000 and the one before the font $4000, and the rainbow works. But if then the image has (I guess) player-missiles on, the image won't load.

 

Also if you turn off the display just before, the rainbow doesn't show up. Is there any way to re-enable the display?

  lda #$00
  sta $D400                       ; DMACTL
  sta $22F                        ; SDMCTL

 

ok, it is difficult to help if you don't share the complete source code to check the behaviors that your program is having.

to activate the screen is :

MVA #$22 SDMCTL

this position if you set it to 0 you turn off the antic chips.

18 hours ago, pps said:

Haha, you're right, I have finished my work here Make it larger is possible. I did this fast and wanted to have about the same resolution as good old ATARI code. btw final usage of this (by me) is in my outline 2021 demo: >>Colored FX<<

You got a good demo ?

[pps]

@Gunstar: version especially for you

 

fujulogo_r_up_down_255x220.zip

[Gunstar]

@ppsI love it, it's perfect! Thank you.  And I love the Colored FX screen shots! I downloaded it and will check it out as soon as I get my 800 put back together.

Edited August 1, 2021 by Gunstar

[tane]

15 hours ago, ascrnet said:

to activate the screen is :

MVA #$22 SDMCTL

this position if you set it to 0 you turn off the antic chips.

Thanks. Not tested as I decided to build a new logo from zero, but I found that adding a "cli" at the end (or the beginning of something that is not shown), re-enables the screen.

 

[pps]

On 7/29/2021 at 12:06 AM, tane said:

Is there a way to restore the system to its default before exit the program? What to add here?:

exit
   jmp WARMSV

 

 

If in the G2F code is commented this line, it helps, but I'd like to have a full compatible Fuji Rainbow Logo program instead of to make hacks to other programs.

I'm not sure what you exactly want to get. 

But you can store original addresses of DL and VBI in fujilogo program. Then you need to change that exit, restoring them and finally end with a rts. Change run to ini on last line of code. 

 

Compile this. Then add just after the basic off code and before main program of g2f source:

  opt h-
  ins 'FILENAMEOFRAINBOWFUJI'
  opt h+

Then compile this and it should give you a file, where you get the fujilogo plus a g2f picture loaded then.

[tane]

Thanks, something I understood about how it works the VBI with the literature below, but I need to do a post-PhD to get properly ?, still I'm in the copy-paste level. If I find an easy example I could get how to use it.

 

https://playermissile.com/dli_tutorial/

https://user.xmission.com/~trevin/atari/antic_insns.html

https://www.atariarchives.org/c2bag/page069.php

 

So I'm opening paths in a different way (Graph2Video). I hope to get it finished.  ?  Only the NTSC shape for now.

 

[Jetboot Jack]

On 7/31/2021 at 1:50 AM, ascrnet said:

it's ok that it doesn't work, since both are using the $2000 address that's why there is a memory conflict.

but your idea is to use it as a presentation?

 

I just did a quick check and the screen design is different. I think they just took it as an idea but did it their way.

 

Xanth F/X Swan

  5100: x5   blank 8
  5105:      blank.i 8
  5106:      mode E @ B740
  5109: x7   mode E
  5110:      mode E @ B740
  5113: x7   mode E
  511A:      mode E @ B740
  511D: x55  mode E
  5154:      blank 8
  5155:      mode F @ 6800
  5158: x31  mode F
  5177:      blank 8
  5178:      blank.i 8
  5179:      mode 2 @ 5608
  517C:      waitvbl 5100

the other

  2000: x6   blank 8
  2006:      blank.i 8
  2007:      mode 6 @ 201C
  200A: x8   mode 6
  2012:      blank 8
  2013:      mode 2 @ 20D0
  2016: x3   mode 2
  2019:      waitvbl 2000

for me it has some small differences.?

Indeed, same outcome - but the point being that once Xanth had done it and Atari used it - it became something Atari UK requested and supplied data for, wether Russell did his own char mode version or you used the bitmapped version…

 

sTeVE

[tschak909]

I love how this thread took off.

 

-Thom