Gamebase20 version 2!
Moderator: Moderators
-
- Vic 20 Devotee
- Posts: 247
- Joined: Sat Jun 30, 2007 5:48 am
- Mayhem
- High Bidder
- Posts: 3007
- Joined: Mon May 24, 2004 7:03 am
- Website: http://www.mayhem64.co.uk
- Location: London
-
- Vic 20 Devotee
- Posts: 247
- Joined: Sat Jun 30, 2007 5:48 am
So, that might be interesting for you :Mayhem wrote:... Although the listing says this should be for 8k RAM, and the listing I have runs in unexpanded, so someone managed to adapt it otherwise.
Found it somewhere in internet.
All listings of Compute! and Compute Gazette on *.d64 and some on *.d81
i've put it to megaupload : ( ca. 9,5 MB)
http://www.megaupload.com/?d=IXZQR99U
- Mayhem
- High Bidder
- Posts: 3007
- Joined: Mon May 24, 2004 7:03 am
- Website: http://www.mayhem64.co.uk
- Location: London
-
- Vic 20 Devotee
- Posts: 247
- Joined: Sat Jun 30, 2007 5:48 am
I wanted to throw this out their. I was checking out some games in gamebase 20. I came across a game called Get Lost! and tried it out. I noticed that in the 3-D view of the maze that a pixel was out of place. The pic in GB20 doesn't have the out of place pixel. I then tried the version that I had in my collection I downloaded from Arma's website. The pixel discrepancy was not their. Maybe this one needs to be checked. This may be something that happened on my computer. I did have a hard drive failure recently.
Rob
- Mayhem
- High Bidder
- Posts: 3007
- Joined: Mon May 24, 2004 7:03 am
- Website: http://www.mayhem64.co.uk
- Location: London
- Kweepa
- Vic 20 Scientist
- Posts: 1303
- Joined: Fri Jan 04, 2008 5:11 pm
- Location: Austin, Texas
- Occupation: Game maker
Is this the pixel that's out of place?
Weird!
http://www.youtube.com/watch?v=TfM6WHOCXtE
It kind of looks like the Shift-P graphic is wrong, possibly when it was copied down from ROM to RAM.
Weird!
http://www.youtube.com/watch?v=TfM6WHOCXtE
It kind of looks like the Shift-P graphic is wrong, possibly when it was copied down from ROM to RAM.
- Mayhem
- High Bidder
- Posts: 3007
- Joined: Mon May 24, 2004 7:03 am
- Website: http://www.mayhem64.co.uk
- Location: London
-
- Omega Star Commander
- Posts: 1375
- Joined: Thu Jan 31, 2008 2:12 pm
- Website: https://robert.hurst-ri.us
- Location: Providence, RI
- Occupation: Tech & Innovation
I think that is a good move, too, because the 2.4 development effort has been unbelievable so far. For my Linux preferences, I am going to have to write a gamebase export into something I can transform over for my frontend... but looking forward to that tinkering! 

Any technology distinguishable from magic is insufficiently advanced.
https://robert.hurst-ri.us/rob/retrocomputing
https://robert.hurst-ri.us/rob/retrocomputing
- Mayhem
- High Bidder
- Posts: 3007
- Joined: Mon May 24, 2004 7:03 am
- Website: http://www.mayhem64.co.uk
- Location: London
The reasons are... well, yes, there has been a lot of development. 2.2 sadly broke TAPs, and 2.3 broke the paddle support, so 2.4 fingers crossed won't have any gotchas hurting GB20! It is likely that I will disable support for 2.2 and 2.3 in the emulator wizard as well. If people want to use them, they can add them in manually.
And then after v0.3 I have to decide about supporting the newer Gamebase frontend, with more fields to fill, and a slightly different GUI. So yes, v0.3 of GB20 will be Gamebase 1.2 compatible, but after that, it's probably going to be 1.3 only.
And then after v0.3 I have to decide about supporting the newer Gamebase frontend, with more fields to fill, and a slightly different GUI. So yes, v0.3 of GB20 will be Gamebase 1.2 compatible, but after that, it's probably going to be 1.3 only.
Lie with passion and be forever damned...
- Mayhem
- High Bidder
- Posts: 3007
- Joined: Mon May 24, 2004 7:03 am
- Website: http://www.mayhem64.co.uk
- Location: London
Quick question to people: v0.3 of GB20 as it stands still supports the format used by v1.2 of the Gamebase frontend. If you load the database into v1.3 then it will be converted on first use. After the release of v0.3, would you prefer me to switch to the new v1.3 database format instead? It does mean people on v1.2 would have to update their frontend.
Lie with passion and be forever damned...