Jump to content
IGNORED

Uridium demo.


shoestring

Recommended Posts

7 hours ago, TIX said:

Since the big ships look more or less identical in 2:2 Antic5 ratio  (with little touch-up),

lets concentrate on the sprites.. things are looking pretty good either way in my opinion !

 

image.thumb.png.8dbe6f5eb5d728accc56f0f4aa5082d3.png

 

 

 

With those examples you show what I was talking about 10 years ago. There is no real loss, if a double scanline mode is used.

While it saves memory, some additional frames can give even more "live experience" to the gamplay.  

 

 

 

  • Like 2
Link to comment
Share on other sites

11 hours ago, José Pereira said:

Here's level_1 in 4x1 that I think doesn't look all that bad (with an enemy at the left side):

1149869151_01-Zinc21charlinesGRAYin4x1.thumb.png.f0d22f379de9a0f2129d74edbbb281e3.png

So black, white & grays more 2 on the enemy ship =6

Still 2 as PMG0&1 multicolour on our ship and one more left in GR.9...

Jose has trouble accessing Atariage so has emailed me with some additional notes, and to pass this on in the thread.
 

Quote

 

GR.10 9 colours registers: our ship: PM0 white + PM1 dark pale E (glass)=yellow (multicolour);
PM2: enemy shot (same as its dark colour luminance);
PM3: its shadow dark gray (same as in gfxs)
BAK: black;
PF0: light gray;
PF1: enemy ships light colour luminance;
PF2: enemy ships middle colour luminance;
PF3: coloured squares on the large ship;
BAK black, PM1 dark gray and PF0 light gray can then change as is on
C64 for other levels.


The PMGs would be, of course, more detailed in 2:1 ratio. Also enemy
ships explosion can be same ratio and a re-use of PM2 (if it was
destroyed maybe 'clean' that line shot).
Our ship shots, like is on C64, would be then maybe white.
 

As in GR. 10 the borders are by PM0 register that in our case is white
but also to have more visible playing area than better going to
48 bytes wide screen.


We'll also not include stars on the large ships scanlines as they
would look ugly in 4:1 ratio but only on the up and down of them
maybe in 3 'shining' colour using GR.15 bitmap mode 2:1 ratio. Maybe
even 'blinking' would make a nice effect. On C64 also enemies and our
ship seems to not go to these scanlines.

 

 

 

 

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

6 hours ago, shoestring said:

Jose has trouble accessing Atariage so has emailed me with some additional notes, and to pass this on in the thread.
 

 

 

 

Why now bothering with graphics 10?

People blame the lower scrolling resolution of horizontal 160 pixel, and now turn even down to 80 pixel?

And then there is the GRPIOR that doesn't allow to use all PMg over the graphics, as the colors of the PMg itself were acting in GPRIOR  with the background colors starting at 704...

 

Link to comment
Share on other sites

4 hours ago, emkay said:

Why now bothering with graphics 10?

People blame the lower scrolling resolution of horizontal 160 pixel, and now turn even down to 80 pixel?

And then there is the GRPIOR that doesn't allow to use all PMg over the graphics, as the colors of the PMg itself were acting in GPRIOR  with the background colors starting at 704...

 

I thought in that but really had a mistake on my colours distribution so here's them fixed:

11 hours ago, shoestring said:

GR.10 has 9 colours registers: 

our ship: PM0 pale green (EA) + PM1 dark pale (E4) (glass)= yellow (EE) (multicolour);
PM2: enemy shot (same as its dark colour luminance);
PM3: ours ship shadow dark gray (also on gfxs and shadows of them);
BAK: black;
PF0: white (also on gfxs, enemys and our ship shots);
PF1: light gray (also on gfxs);
PF2: enemy ships middle colour luminance;
PF3: coloured squares on the large ship;
BAK black, PM3 dark gray and PF1 light gray can then change as is on
C64 for other levels.


The PMGs would be, of course, more detailed in 2:1 ratio. Also enemy
ships explosion can be same ratio and a re-use of PM2 (if it was
destroyed maybe 'clean' that line shot).
Our ship shots, like is on C64, would be then maybe white.
 

As in GR. 10 the borders are by PM0 register that in our case is white
but also to have more visible playing area than better going to
48 bytes wide screen.


We'll also not include stars on the large ships scanlines as they
would look ugly in 4:1 ratio but only on the up and down of them
maybe in 3 'shining' colour using GR.15 bitmap mode 2:1 ratio. Maybe
even 'blinking' would make a nice effect. On C64 also enemies and our
ship seems to not go to these scanlines.

Also will look better large ships be in 4:2 then the enemys in 4:1 ratio while our ship and its shadow be in 2:1 ratio PMGs:

1901244878_01-Zinc21charlinesGRAYin4x2.thumb.png.d40590884ce15722ef39687b4328a7d5.png

And just a piece of it for you seeing better with need to 'zooming' it:

189627866_01-Zinc21charlinesGRAYin4x2_justapieceofit.png.bd4a0105fcdc8c11f975202a413203cf.png

I think it could look nice and would be a new 'way of'...

 

Now @emkay there's only one thing there (just a pixel) that doesn't work with priority that is Prior_1 to be used... Guess what is it?

Clues: Our ship is PMGs so goes over all gfxs whatever they are (there's only a PMG register PMG3 on gfxs) and also enemy ships are just PFs and soft sprite 'bitmap masking' over large ship gfxs so no problem and theirs shots are PMG2 so always over whatever.

But that pixel can have a simple solution just enebling an A8 Hardware register ;).

Where's the Wally?

:grin:

:thumbsup:

Edited by José Pereira
Forget solution by using a Hardware register (it'll be used for other thing...). Yes, still remains that just single pixel but could not be all that important and workable.
  • Haha 1
Link to comment
Share on other sites

1 hour ago, José Pereira said:

And just a piece of it for you seeing better with need to 'zooming' it:

189627866_01-Zinc21charlinesGRAYin4x2_justapieceofit.png.bd4a0105fcdc8c11f975202a413203cf.png

I think it could look nice and would be a new 'way of'...

Gotta say this is starting to look too low res now, the details don't really look 3d any more. Dropping the vertical white highlights has really lost something.

       263148675_Screenshot2020-11-20at11_11_45.thumb.png.9cc6c3a91e91b003aad31291a5d4265c.png

  • Like 2
Link to comment
Share on other sites

56 minutes ago, Mr Robot said:

Gotta say this is starting to look too low res now, the details don't really look 3d any more. Dropping the vertical white highlights has really lost something.

      

It's a huge ship, I don't see why we can't have vertical white highlights..

it just needs some love !

..looking for a way to draw the little diamond shaped thingies !

edit:  done ?

 

image.thumb.png.fa2c96101c8570a9c134c5b7486989ef.png

 

 

 

Edited by TIX
  • Like 3
  • Thanks 1
Link to comment
Share on other sites

That's much better, could the dark grey be one more shade darker? Also add one more line of dark at the beginning of the narrow neck to make it look more like the is height there.

 

Here's a thought, if the verticals are that thick, what does it look like if the horizontals are two pixels wide? It will probably be too much but worth a try.

 

Link to comment
Share on other sites

3 hours ago, TIX said:

It's a huge ship, I don't see why we can't have vertical white highlights..

it just needs some love !

..looking for a way to draw the little diamond shaped thingies !

edit:  done ?

 

image.thumb.png.fa2c96101c8570a9c134c5b7486989ef.png

 

 

 

 

You know the problem? What you see in the picture has nothing to do with the Atari's hardware.

To have any separated colored moving object over the ship, you'd need to use playfield  colors, so you're restrictes to 80 pixel width based software sprites. 

You cannot set colored PMg over the ship in GTIA 10, as the colors are a part of the background. 

You could do some trickery using Playfield color 4  (711)  and the missiles active set to one color.

 

 

 

Link to comment
Share on other sites

On 11/10/2020 at 3:30 PM, shoestring said:

I've also made some changes to the RMT as well, I think it sounds a little better now. 

uridium-sketch.v1.3.rmt 1.67 kB · 12 downloads

Has emkay shared his version of this tube? I think he should.

I don't need to be credited here, just had some 15 mins fun on this.

Link to comment
Share on other sites

52 minutes ago, miker said:

Has emkay shared his version of this tube? I think he should.

I don't need to be credited here, just had some 15 mins fun on this.

He shared the previous version, 1.2. But I’m sure someone can do better than this. It would be nice with some drums but I couldn’t find a way to make the bass channel sound decent after splitting it. 

Link to comment
Share on other sites

16 hours ago, Stephen said:

Let's really save some CPU time.  We don't get too many ANTIC mode 8 games!

mockup.png.a5485f520654556a262bec1f69bb525d.png

 

Better yet, let's hookup 8 of these in parallel and really kick ass in Mode 8 with 8 colors, 8X Players and Missiles, and essentially an 8 core CPU! However one small but significant problem - we'd also need an OS capable of working with parallel processors ;) . One can always dream.

 

Atari-800-Expansion-Board-CPU.jpg.24c89e80ec73ee0dd9efcc5ba868c5a4.jpg

Sorry for the off topic... carry on.

  • Like 1
  • Haha 2
Link to comment
Share on other sites

  • 3 weeks later...

I had a bit of a set back a couple of weeks ago and lost everything in a HD crash, yup.. my own fault. That includes source code for the A8 diagnostic software I wrote and all my arcade related stuff.

 

So I had to start this project virtually from scratch and then use the xex I uploaded here to disassemble/reverse engineer what I did which helped me get back up to speed and on track rather quickly.

 

I now have the Manta's bullets working ( using soft sprites ) in the attract mode with collisions to objects in place ( that includes destruction of parked ships and collisions to the obstacles on it ).  Though that didn't take much work because the original game uses soft sprites for the players bullets as well.

 

 

 

 

 

Uridium.atr Uridiump.xex

  • Like 6
Link to comment
Share on other sites

  • 1 month later...
  • 1 month later...
  • 3 months later...
On 12/9/2020 at 10:18 PM, shoestring said:

I had a bit of a set back a couple of weeks ago and lost everything in a HD crash, yup.. my own fault. That includes source code for the A8 diagnostic software I wrote and all my arcade related stuff.

 

So I had to start this project virtually from scratch and then use the xex I uploaded here to disassemble/reverse engineer what I did which helped me get back up to speed and on track rather quickly.

 

I now have the Manta's bullets working ( using soft sprites ) in the attract mode with collisions to objects in place ( that includes destruction of parked ships and collisions to the obstacles on it ).  Though that didn't take much work because the original game uses soft sprites for the players bullets as well.

 

 

 

 

 

Uridium.atr 179.64 kB · 24 downloads Uridiump.xex 21.24 kB · 39 downloads

Any news on this project? ?

  • Like 1
Link to comment
Share on other sites

Progress is rather slow at the moment. There's a lot happening right now,  I should have more time with yet another lockdown but then work has gone crazy too with the number of security breaches and requirements at work.

 

I have converted the project to run on VBXE which is something I've been considering and exploring since the beginning, keeping the mode 2 screen with bitmap overlay for bobs.

 

There really was no way to utilise a screen with interleaved character sets ( per level x 15 ) and still have enough left over/vacant positions for software sprites. Maybe a better coder can find a way without too much compromising?. Also factoring in that you have to facilitate additional shapes for objects on the platform that have been destroyed and the 2 unique star shapes, all previously overlooked when looking at this initially. Consider Zinc ( level 1 ) where I have undamaged tiles adjacent to their respective damaged ones, when this is run through my interleave util, I'm barely left with anything. Memory is another issue, with lack of DRAM access under the I/O.. but this alone wouldn't solve my overall problem.

 

image.thumb.png.4a249c1e7c5a728d0bd96556f5e4c0d9.png

 

Currently in it's state,  the game is somewhat playable but very very much unfinished. Options screen is responding to joystick input, some of these currently have no affect ( volume for example ).  The last two weeks or so,  building and working on the Sprite engine for the Manta, the Bullets are somewhat complicated.. but will go back in place once I get the overlay working fully as I'm now using BCBs to copy the bullets across all character sets [ in case the manta moves up or down the screen ]. There are ~12 frames just for bullets in each character set, and this changes based on the Manta's orientation, it can fly sideways and roll about its horizontal axis whilst shooting bullets. Manta responds to left and right on the joystick, but no up and down yet, shadow is cast but it's all still very glitchy....  though I suspect this is to do with the bad synchronization of the bob ( sprite frame and x/y coords in the BCB) updates which I'll look at shortly.

 

The bulk of my time has been spent decoding what I call "bg object data" and creating visuals in charpad to represent them. This helps me locate and make the relevant changes to the actual data for each charset when relocating a shape or tile to a different position ( since I'm now working with 128 per sheet ).  So for example runways data is 5 columns, 3 bytes each which represent a position in the character set. 

 

;================================ Struct 17
    ; Runway objects 1
    ;
    .byte 05,03                                                             ;  5 columns, first column is 3 x 8 pixels in height                                                      
    .byte 14,55,13                                                        ;  Column #42
    .byte 03
    .byte 14,55,13                                                        ;  Column #43
    .byte 03
    .byte 14,55,13                                                        ;  Column #44
    .byte 03
    .byte 14,55,13                                                        ;  Column #45
    .byte 03
    .byte 14,55,13                                                        ;  Column #46

 

image.thumb.png.d2dc4c42e35410e3177c854b01d823b0.png

 

 

This is very time consuming process and so far almost completed Gold ( and still 14 more to verify ) before taking a look at how I'd implement the Sprite engine and test it out as an overlay. I've had to re-arrange shapes  in each charset , especially for the collision detection to work seamlessly ( objects you can destroy, obstacles you can run into ..etc ), not enabled currently.

 

For some reason some black random dots ( that don't seem to be turned on in VBXE ram )  have started appearing once I enabled the bob overlay which aren't present on the screen on the real hardware, so I'm hunting a bug somewhere that Altirra is picking up, any VBXE programmers have any clues ?. Maybe this weekend I can find the time to look at it more.

 

 

 

Edited by shoestring
  • Like 7
  • Thanks 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...