(While I am capable of decompiling ParaJVE, that would go against his
current terms of usage)
Thanks for any an all suggestions. (have access to windows and mac osx, so
soemthing that will build and run in either is great)
In case you're wonderig why, I'm back at trying to get my supercharger cart
up and running - which would essentially run the game on the 68030, with a
block of memory readable by the vectrex. The vectrex would play sound fed
to it via that memory, as well as sets of vectors to draw.
Dan.
you can get the source at
http://www.valavan.net/vectrex.html
It is a windows program that uses DirectX.
That would be an awesome achievement if you were able to make a
supercharger cart.
Keep us posted on progress....
VectrexMad!
> On Nov 22, 9:55 pm, Dan Lingman <dling...@rogers.com.nospamplease>
> wrote:
>> Hi all. I'm looking for a vectrex emulator that comes with source. I
>> n
> eed
Thanks - will keep you guys posted on how this is proceeding. First
thing will be to get the dual emulators running together. Then, get the
vectrex side of the code pulling data from the shared memory bank, and
drawing that. Next, get some 68030 code in place to feed in updated
vectors. Once all of that is in place, it's time to shift gears over to
the hardware side of things...
Dan.
Never heard about the supercharger cart before, that seems like a very
interesting project!
Although I don't want to open the emulator sources yet, I'm willing to
help if possible - when time permits ;-).
What kind of synchronisation would you need with the emulator : would
it be tight (cycle-accurate) or rather loose (say, one update of the
memory block per "frame" every 1/50 seconds)?
Also, what programming language would you use to interact with the
vectrex emulator?
If you intend to use java, it would be conceivable to provide you with
an I/O "cartridge" API for ParaJVE (especially if running in the same
JVM) ; otherwise, it would still be possible to implement that via
local sockets (if you don't need a such a tight synchronisation).
Franck.
On Nov 22, 10:55 pm, Dan Lingman <dling...@rogers.com.nospamplease>
wrote: