EmuCR Feeds
Email Us

EmuCR:Virtual JaguarVirtual Jaguar SVN r364 is released. Virtual Jaguar is an open source emulator based on Jagem (Virtual Jaguar) for Linux, MacOS X, and Windows. The source also compiles on BeOS. Virtual Jaguar is an awesome Atari Jaguar emulator with great compatibility.

Virtual Jaguar SVN Changelog:
r359
Merging qt-experimental into trunk.
r360
New artwork for CD loading.
r361
Fixed 24BPP mode (used R twice instead of B), fixed problem with Object
Processor not running correctly (should be from VC=0), added some keys to the
cartridge dialog to allow dismissing and running using ESC & Return.
r362
Fixed OP scaling bug for sizes of 7.0 and up.
r363
Various UI enhancements, like keyboard list searching in cart dialog.
r364
Removed no longer used config options from config dialog.

EmuCR:Virtual Jaguar
EmuCR:Virtual Jaguar

Download: Virtual Jaguar SVN r364
Source: Here

15 Comments:

  1. Can anyone get a .jag file to boot with this program or is only Jagulator able to do that?

    ReplyDelete
  2. Quitle frankly Jagulator is better , virtual jaguar author only updated the emu because the guy of jagulator is progressing at a incredible speed and IS ACTUALLY MAKING MORE PROGRESS IN A MONTH THAN THIS GUY HAVE MADE IN 5 FUCKING YEARS
    http://www.jagulator.com/index.html
    Im sure hes just only envy over the AWESOME GUY OF JAGULATOR!

    ReplyDelete
  3. Why do they have to be so divided ... I wish there was more of a team mentality of achieving a way to maintain games way past their physical existence hardware and software included. Instead its a competition of egos something I just do not have time for and I believe one of the number one things that hold many projects back. Even open source projects often have the in crowd and they tend to push away help from people they don't like ... luckily not everyone acts so childish.

    ReplyDelete
  4. At this time, Jagulator is definitely not better. VJ actually supports sound in some games, and is receiving a lot of attention lately. Jagulator has potential for sure, but it is NOT better whatsoever. The best thing it has over the others is speed (others just need to be optimized) Accomplishing a lot in a short amount of time means nothing until it gets as good as the competition. Impressive, yes. Better, hell no. When Jagulator is compatible with as many games as VJ, has sound, AND is speedy (plus without graphical glitches everywhere), then it will indeed be better.

    ReplyDelete
  5. Yeah, Jagulator is better, has no sound and less compatibility, and is x86 only.

    Really, if you hate Virtual Jaguar so much, why do you post here? If you have nothing constructive to say, you should keep it to yourself and spew your hatred elsewhere.

    ReplyDelete
  6. @Comment #1-
    I can get either .jag or .j64 files to function in the emulator. I suspect other Jaguar file formats will work fine as well.

    ReplyDelete
  7. There seems to be a lot of confusion surrounding the various file formats that
    Jaguar programs come in, and a lot of this confusion seem to come from
    Cowering's GoodJag renaming tool. Note that it simply gets some files wrong,
    and it also incorrectly renames cartridge images with an extension that
    belongs to an already established extension (.jag is a Jaguar Server
    executable--read on). To clarify, there are basically four major types of
    Jaguar binary images that are NOT cartridge images:

    .abs
    .jag
    .rom
    .bin

    The first type, the .abs file, is a DRI/Alcyon format absolute location
    executable. These come in two different flavors and contain load and run
    addresses in their headers. Note that some files which have an .abs extension
    are really incorrectly labelled .bin files with no header information
    whatsoever.

    The second type, the .jag file, is a Jaguar Server executable. These files
    contain header information that tells you where to load and run the file's
    executable code. Note that as of this writing (8/5/2005) that the GoodJag ROM
    renaming tool by Cowering incorrectly renames Jaguar cartridge ROM dumps to
    have a .jag extension (a better choice, and the one supported by Virtual
    Jaguar, is .j64)--if you're trying to run a ROM image with a .jag extension on
    VJ, it will misinterpret it as a Jaguar Server executable and likely fail to
    run.

    The third type, the .rom file, is an Alpine Board/ROM Image file. These files
    have no header, but are known to load and run at $802000 in the Jaguar memory
    space. Again, these are *different* from cartridge dumps since they load at a
    higher address than a Jaguar cartridge.

    The fourth type, the .bin file, is simply a Jaguar executable with no header.
    Since these files contain no information about where they load and execute,
    Virtual Jaguar does not support this file type. Go bug the author to release
    either a file with proper headers or a file in Alpine ROM format. Virtual
    Jaguar is not omniscient (yet)! ;)

    There is a fifth type of file that is supported by Virtual Jaguar, the .j64
    file, which is simply a 1, 2, or 4 Meg dump of a Jaguar cartridge ROM which
    loads at $800000 in the Jaguar memory space.

    ReplyDelete
  8. i think that the best emulator of Atari Jaguar is Project Tempest for the moment

    ReplyDelete
  9. Take a look at the t2k emulator, it emulates not many roms, was made mainly for Tempest 2000, but runs some game better, then the others, e.g. Defender 2000

    ReplyDelete
  10. DioJag? You've got to be kidding. That thing will *never* be a decent general purpose Jaguar emulator because it's been optimized to play T2K. And Project Tempest? Again, you've got to be kidding. That project is dead with lots of emulator bugs that have never been fixed and never will be.

    And really, what does any of this have to do with Virtual Jaguar? Please take your trolling somewhere else.

    ReplyDelete
  11. This build does not work. I cannot get any games to load on this one. Can anyone fix this? So I'll have to downgrade to the previous one since I can get that one to load.

    ReplyDelete
  12. BIOS goes in your "roms" folder now; the latest version in SVN properly handles the case you're running into (by running the cart directly if no BIOS is found).

    So either put the BIOS files in "roms" or uncheck the "Use BIOS" option in the config dialog. :-P

    ReplyDelete
  13. Oh, and Griking is the biggest gay!!!11!1!1!

    ReplyDelete

Can't post a comment? Try This!