Orion_

yes, but, see what you can do with a ct60 on a falcon, it's so much better

at least, I will personally mostly use it like that, but you can of course use/mix the power of the 2 systems, though I think it will be somewhat difficult.

you have no idea how powerful the jagcf dsp is. Plus, I really doubt to see a working jag2 someday... Sounds more like that is what you hope.Oberon IS finished BTW. Your DSP outside the cart will allow some advantage but you still have to get what it does to the rest of the Jaguar. You will not be transfering data very swiftly over that cart bus. You will have serious issues dealing with it. Im betting it's part of the delay. Oh and the DSP in the CF offers no compatibility and extra power that would help a Jaguar game. The fully backward compatible Oberon however does. oberon is not the jagII, show me a working jagII and then I will applause. the CF DSP don't need compatibility, because you run it on a plain Jaguar, so your argument is pointless, it's not like if the JagCF was a complete new console like the jagII which then must offer compatibility. the jaguar will only be used for pad, and video, blitter for getting the frame from the jagcf sdram, the whole game will most of the time be renderer inside the jagcf system which offer fullspeed computation.

you have no idea how powerful the jagcf dsp is. Plus, I really doubt to see a working jag2 someday...

it's better to make a new and more powerful chip instead of a trying to get the unfinished jag2 running that will cost a lot because it's a whole new console

no you can't, you don't have master bus control on the cartridge port. (or something like that)

again, the JagCF CAN'T dump roms use your brain 2 seconds, how do you expect to dump a rom from a cartridge if the cartridge port is already taken by the JagCF and if you read the topic, it's said that the rom ability will be available only to developers so please read what we say and not continue dreaming of what JagCF's detractors say

Neither did we you can't do that using JagCF, the only actual way is BJL + an atari so blame the BJL author, not us

I want my JagCF

Read: "gpu debugger" , not "Jaguar 'simu/emu/debug'-er" my plan for the moment is to use it for my next project, why do you think I released the source *edit* and I really don't see the point between cry and the gpu O_o by the way, If I had ripped the mame code I should not have any bug in the instruction emulated, and it's not the case, I just found a bug in my sharq instruction... Oh and i looked at the mame source code, i really don't see where you see similarities, they use one function per instruction, instead of case/switch for me, if you see that the structure for instructions is the same, then try to code a gpu instruction emulator and you will surely choose the same structure has you don't have any other way to do it ...

lol so what ? %) comments are mandatory within a source code ? I mean, in assembly I have a lots of comment (sometimes one per line) because, read your asm code one month later without comments and you won't understand what it does and how it does it but pascal language is so easy that, reading the variables names if correctly chosen, it's obvious what the code do.

If I used the mame code I would not have release it opensource, because I would fear that peoples found that I did it. and also not bothering converting everything in pascal language ..... but well, think what you want, I know what I've coded ^^

so what can I say ? .. I even didn't know that mame had a jag emulator. I didn't look at the mame code but you know, you don't have 100 manners of coding an emulator... I understand I would have find it strange too.

WHAT ?! I didn't use ANY already written code for this project, it's all mine. damn I'm getting tired of releasing free stuff for the jag community and getting attacked like this......

that is what you think. I could have made a public release one month ago instead of a private beta, and say everywhere "hey looks everyone, I released a debugger faster than gorf !" I didn't, I even not talked about your debugger or compared it to mine, just posted on jagware and AA programming forum that it was released and hope it will helps jag devs, that's all. it's you who start attacking me here claiming I've stolen your "original idea", well a debugger is not that original for devs, you know swapd0 already did a remote debugger for the jag.

you should put your glass on, 2 windows for you, one for me, no step button, 2 register list instead of one editbox per register for you, pict for each register and line of code whereas you have only text, and so on ... for the rest, a debugger is a debugger, it have obvious similarities.

so a debugger is something that was never coded before and you were the first to create it ? what a joke... so because you first had the idea of developping a debugger I should wait months and months for you to release it and not code one myself ? I had in mind to code a debugger for the gpu for a long time, before you actually post on jsii, but was too lazy to start it, but I was tired of trying to "blind" debug my gpu code on jaguar so I decided to start this debugger, and actually coded it in about 2 days for the initial release, your post is from end of october and there is still nothing released so it's great to post picture of interface "mock-up" but it's better to actually release real stuff, I don't mind if features are missing in my debugger, it's actually enough for me to debug my code, and the sources are available so anyone can add features ... and talking about the picture you post I don't see any "step" button to debug the code, and your interface is very big taking all the screen with some useless info (like opcode in hex and bin format..)

Hi there, I just released my little Jaguar GPU Debugger, I hope it will be useful to anyone coding on jaguar here http://www.jagware.org/index.php?showtopic=499

you must first have a 3D engine for the jaguar.

thank you

[...]

if so, then it will only be the jagcf early prototype, because the final is not yet finished and will only be manufactured for the first time with the first developers's ones some video of this prototype have already been made at the AC 2007 with a presentation of some of the jagcf features

so why are there more developers (than on the jaguar) in the others homebrew communities that have flash card device for their system ? simply because most of you developers here don't have the homebrew spirit and want money like if you were working for a game company

you say that a logic analyzer which measure things precisely and show exactly what happen inside the jaguar is lying and that we should better believe you than the analyzer ?? LOL !

you should have check the video capture of my game "seaplane" when I show the preview at the RGC 2006 and in some video at AC2007 and I have no proof that surrounded actually run in main ram because you forbid to disassemble any of your code.