Zerosquare

Are you expecting actual art direction from a company that released Trevor Mc Fur?

There should be a piece of brown cardboard between the bottom of the board and the metal cage. You can see it here at 6:05: Is it missing on your Jaguar?

If you can't do single-stepping, what I'd do is write a bit of code that computes a checksum of your memory buffer, and display it. Simplify/remove parts of code until you get the same results on VJ and real hardware.

Have you double-checked that all memory is initialized?

@CyranoJ: was it the same wonky Jag I sent you? I did replace the caps when attempting to fix it ; I think I remember it made the buzzing noise louder, so it may not be related to the fault. @SainT: can you share the differences you've observed (possibly in another topic)? While there are some known instances of games working on some Jaguars and not others, I don't recall anything as unpredictable as what appears to affect the JagGD. There may be some still unknown effect at work here.

That's because it uses the 68k to read the "standard" buttons ; only the rotary and mouse are handled on the DSP. It also includes a small delay between setting the bank and reading the buttons states (this was to be extra sure that it'd work reliably even when using TeamTaps and/or extension cables -- someone had reported an issue related to that). I'm not so sure. I've never played with the ESP32, but the specs I found say it is dual-core and that the clock speed ranges from 80 MHz to 240 MHz. With such specs it should be possible to do better than 300 ns (but you may need assembly code for that).

Have you tried it on another Jaguar?

As if kids read video games manuals ?

And as a reminder, here's what the doc says:

The audio/input engine I wrote (that's been used in a number of Reboot and rB+/Jagstudio games) uses almost every register in both banks, and I'm not aware of any problems. Here's the code I use: Int_DSP_StackPtr .equr r31 ; Interrupt (bank 0) DSP stack Int_DSP_Flags .equr r28 ; Interrupt DSP flags backup Int_Tmp1 .equr r29 ; Interrupt temporary register #1 Int_Tmp2 .equr r30 ; Interrupt temporary register #2 ; Start of interrupt: save DSP flags movei #D_FLAGS, Int_Tmp1 load (Int_Tmp1), Int_DSP_Flags ... ; End of interrupt movei #D_FLAGS, Int_Tmp2 ; get flags address bset #10, Int_DSP_Flags ; clear the interrupt latch load (Int_DSP_StackPtr), Int_Tmp1 ; get last instruction address bclr #3, Int_DSP_Flags ; clear IMASK addq #2, Int_Tmp1 ; point at next to be executed addq #4, Int_DSP_StackPtr ; updating the stack pointer jump (Int_Tmp1) ; and return store Int_DSP_Flags, (Int_Tmp2) ; restore flags

Yes. This is normal. It's a possibility, some people had the same problem and the power switch turned out to be defective. Try bypassing it completely. Also, clean the contacts on the cartridge port and cartridge. The Jaguar won't power on if it doesn't detect that a cartridge is inserted. Not really. Most Jaguars have never been recapped and still work fine. Yes. But for testing, it's not critical.

They're the same as the PC tools, just compiled for the ST. You can find them here: That was the Lynx, indeed (as the designers of the Lynx also designed the Amiga).

The voltage and polarity are correct, but as @Mitch says, you've got to check that it can supply 1.2 A or more.

As far as I remember, it's soldered in. But it shouldn't be too difficult to desolder if needed.

It's hard to tell what's going on in your photo, but try resoldering the brown wire to the contact on the right.

It's been discussed here: https://atariage.com/forums/topic/294841-bluetooth-controller-adapter/?do=findComment&comment=4972853

I don't see what you mean. Who doesn't like waiting for 5 minutes for Tetris to load?

DiamJag is based on an earlier game called DiamantiX for the TI-89 calculator, also developed by Orion_: http://onorisoft.free.fr/retro.htm Which is itself similar to Sokoban, a Japanese game that has been ported on virtually every platform and has countless versions: https://en.wikipedia.org/wiki/Sokoban

I had the same idea a long time ago, but never actually tested it: The black triangle is drawn by drawing a parallelogram (cyan) clipped by a rectangle (pink). Arbitrary triangles are drawn by subdividing them into right-angled triangles: But there are several issues: - as mentioned, this only works right for simple flat lighting, not Gouraud or texture-mapped - it's inefficient for skinny triangles - subdividing triangles has a computation cost - according to SCPCD, the blitter's clipping feature is buggy, so it may not work as it should

Ah yeah, you're right. I forgot about it.

As far as I remember, the first version of Raiden runs fine on PAL consoles, it's just not optimized for it so you get some black bars. If it doesn't run at all, I'd say you either got a bad ROM image or there's something wrong with your Skunkboard.

Usually, it's either a reset button, or a way to switch between 50 Hz and 60 Hz modes.

The Jaguar is 64 bits. This is a 8 bit game. So obviously, the Jaguar version should support 8 players at the same time.

After 30 years of Jaguar, you're still surprised?

The first step of recovery is admitting you have a problem...