Shamus

"Have you ate Atari™ today?"

I see taco based comments are becoming more prevalent; i sincerely hope this trend continues and more taco based content is forthcoming!

It definitely depends on the quality of the tacos. For instance, there's a place out near here that makes some really good Mexico City style tacos, and then there's those things that Jack in the Box™ has the unmitigated gall to call tacos (/me suspects those are 3D printed).

Unlike the Retroarch guys, I fully believe in giving credit where credit is due, and not pretending like it's something other than what it is. If you look at the sources for RMAC and RLN (which I highly doubt you can be bothered to do), you would see and understand this. I did not take SMAC/SLN (which, let's be clear, were created from MAC and ALN sources) and make minimal cosmetic changes to it and announce to the world + dog that here was something entirely new to the world and aren't I great for having created this new thing; I forked it and gave it a new name in the same spirit that SubQMod did with MAC and ALN. Also unlike the Retroarch guys, I and others have actively gone through the codebase and improved it and fixed many bugs with it and added capabilities to it that SMAC/SLN never had (I am not going to list them here as they are already listed in the GIT log for each project). If you compare the codebases (again, I doubt you can be bothered to do any such thing) you would find that they have diverged quite a bit and thus RMAC and RLN are pretty much their own things now. So, in sum, the Retroarch guys are a bunch of parasites who contribute nothing back to the codebases they use and get their glory from and give no credit to the authors whose works they use as a basis for their little frontend kingdom; while I and the others who help me are busy writing and improving on the things we have inherited. Don't compare us with them, we are not even remotely similar. But please, keep spouting off about things you don't understand. If you keep digging that hole, I'm sure you'll get to Oz in no time!

Writing to the blitter with the 68K is certainly possible and I and others have used that technique successfully. I would encourage you to get hold of the JTRM done by John Mathieson and read the section on the blitter, as the blitter is a very complex piece of hardware that most of the time will not do what you expect of it if you don't understand all the bits that go with it. If you can't find a copy, let me know and I'll post it here. Which version of VJ are you using? Writing to B_CMD should not cause VJ to be unresponsive and if it is, that's a bug in VJ and not the Jaguar hardware. Have you tried the "Fast Blitter" option, to see if that works any better for you? Have you tried running it in Alpine mode to see what's happening with the emulated hardware?

Well, if you knew anything about how the Retroarch guys do things or even bothered to look at their repository, you would know that basically all they are doing is slapping a front end on--to every emulator that they can get their hands on (which was probably a contributing factor as to why byuu changed the name of bsnes to higan--Retroarch still calls it the bsnes core, and I seriously doubt they've done a blessed thing to it). But of course, you know nothing about it; so you feel free to spout your opinion as if it had any bearing or relevance whatsoever when it's based on your complete and utter lack of knowledge of the situation. Bravo sir, bravo.

Pretty much. :-/

This is too funny, especially when you see things like this in the comments to that video: Sorry to burst your bubble, but the RetroArch kiddies aren't doing anything with Jaguar emulation, much less improving anything. Their level of 'compentency' extends only to ripping off other emulators (and rebranding them as their own creation) and contributing nothing back--not to mention pissing off the authors of said emulators and labelling them as inferior beings for not deigning to bow to their greatness and kissing their rings. Best laugh of the day, thanks for that!

Dunno about those, but RMAC & RLN are built from their sources. Can be found here.

No emulator works 100% like real hardware, but VJ (for all its faults, which are many) is closer than PT IMNSHO.

One of Virtual Jaguar's goals is support playing CD games with the host CD player. It's been a long slow slog trying to get it right, but it is coming.

Sauron is right; BIOS images have not been needed since the middle of 2011.

Wow, after checking out issue #1 it's clear where a lot of the misinformation surrounding the Jaguar came from: it came straight from Atari! Page 5 deals out the BS with a huge shovel. I can see why developers were initially interested, seeing specs and capabilities like that, and then getting disillusioned later once the reality of what it really could do (vs. what Atari said it could) became apparent. My, oh my.

This is the case. There is no VLM source, unless Yak has it and releases it. Otherwise, time to break out the disassemblers.

LOL @ the broken toys reference, best laugh I've had all day—especially considering the source and the broken things it champions. This is odd, because I spent some time making sure that RLN could link against stuff created by VBCC. If you don't mind sending me the project, I could see if it's something I missed.

I'm afraid I have no insight into why this happens. Maybe someone with better 68K knowledge can chime in.

The Skunkboard doesn't map the BIOS ROM space, it only maps out the cart space. So what you want to do is impossible.

There is no vertical blank interrupt (VBI) on the Jaguar, only a video interrupt (VI) which can occur on any scanline(!). The only way to ensure that you are in the vertical blanking period is to watch VC (video count) and wait until the correct number of lines has gone by, or set the VI register to the correct value. It sounds like you're trying to use the Palette RAM as a read source? If so, that might not be so stable. Like Zero said, welcome to the world of Jaguar development! BTW, if you have the time to make notes on the differences between what VJ does and real hardware does, I'd love to see those.

* + # is definitely not hardwired in, you have to write the code to make it do anything.

I found this in the T2K sources (dated 1994-01-26). TEMPEST.ZIP

At least one person (that I know of) reported success using the patch on Checkered Flag on VJ, so it should work.

No.

"Not with liars and psychopaths"

Great, this means I have to update VJ to support 2K EEPROMs now.

It doesn't matter what it says in the .txt file, it matters what it says on the title bar. If it says "Virtual Jaguar GIT 201xxxxx" (where xxxxx are numbers), then you don't have an official release. CJ is right about the latest bleeding edge version of VJ--the DSP is undergoing some experiments and is a bit unstable ATM. Best to use 2.1.2 for now.