|
Post by dgo on Nov 18, 2014 9:50:17 GMT -5
Wow. I'm not entirely sure I can fully grasp the breakthrough (on a technical level) here yet, but this sure is revolutionary. Amazing how the envelope keeps getting pushed on the good old Motorola/Vectrex Bios. Really impressive!
gonna test on hardware soon
|
|
|
Post by christophertumber on Nov 25, 2014 23:48:47 GMT -5
|
|
|
Post by gauze on Nov 26, 2014 0:33:30 GMT -5
most cool, sir
|
|
|
Post by VectorX on Nov 26, 2014 0:43:49 GMT -5
Pretty astounding to see on the Vectrex
|
|
|
Post by christophertumber on Jan 25, 2015 21:15:54 GMT -5
Here's what I did today, what did you do? Between Christmas and this ridiculous cold/flu that's been going around I've been AFK for a few weeks. This has given me some time to rethink the internal design. And I've decided to complete redo the base engine There's a few reasons for this. First I've settled on an alternative optimization plan. In order to fully optimize as much as I'd like (no subroutines, no loops) I think I'd need significantly more than 64K. So there has to be some compromises and I think I've figured out a better way. At least what I've got up and running below is a solid 50fps with a simple, placeholder Boss and the capability to display more enemy shots. Also, previously I was treating all enemy sprite objects (ships and shots) identically with the same data structures and subroutines. However, I actually that a waste of both RAM and logic for simple objects like shots which just go in one direction, don't have hit points, &etc. So I decided it makes sense to treat them completely separately try to force it which results in a bunch of unnecessary exception handling. I do get to re-use a lot of what I've already done (with some changes) for example, the player ship and shots are re-used. That's why this came together fairly quickly. I do still need to add collision detection and enemy ships back in to return to where I was but this is actually progress. Sorta. newkernal.bin (4.71 KB)
|
|
|
Post by andygarton on Jan 26, 2015 3:38:50 GMT -5
Brilliant stuff! I'm just feeling my way in Vectrex programming so apologies if this is a silly question - does this make any/some/extensive use of the built in BIOS routines, or have you had to re-implement them all for speed?
|
|
|
Post by Mayhem on Jan 26, 2015 5:25:39 GMT -5
Wow, that's definitely impressive
|
|
|
Post by binarystar on Jan 26, 2015 6:07:56 GMT -5
That looks killer Chris, looking forward to seeing the end result.
|
|
|
Post by cNp on Jan 26, 2015 7:39:30 GMT -5
Awesome (once again!) Chris! It's amazing what you're getting out of the Vectrex these days!
cNp
|
|
|
Post by christophertumber on Jan 26, 2015 7:54:08 GMT -5
does this make any/some/extensive use of the built in BIOS routines No, about all I'm still using are the joystick and button polling routines and I'll probably replace those at some point (to remove the overhead from parsing parameters).
|
|
|
Post by christophertumber on Jan 26, 2015 7:55:37 GMT -5
Collision detection/death and the previous rudimentary soundfx are back in. Because who needs sleep on a Sunday night, amirite? newkernal.bin (5.53 KB)
|
|
|
Post by binarystar on Jan 26, 2015 10:00:53 GMT -5
running really nicely on my vec, great work christopher
|
|
|
Post by andygarton on Jan 26, 2015 10:29:40 GMT -5
Same here, really impressed with the smooth rendering, and virtual absence of flicker, despite the high number of vectors.
|
|
|
Post by christophertumber on Dec 22, 2015 20:18:40 GMT -5
Been ages since I posted anything, kernal has been rewritten - Well, let's say a couple times Finally pretty happy with where it's at though I might need to make some changes to reduce ROM use a little bit in order to be able to include more ship designs. Runs on: Real Vectrex MESS 154 Does not run properly on: ParaJVE 0.7.0 Hrm, forum won't let me upload. Tells me file is too big even though it's only 64K and the upload dialog says maximum 1 MEG. Sorry guys
|
|
|
Post by VectorX on Dec 22, 2015 20:26:24 GMT -5
What is it, an attachment? This forum's been maxed out for attachments for months now. If that's what it is, you'd just have to upload it to Dropbox or something and link to it. Whatever the deal is, nice to see you get back to this
|
|