[Official] Virtual Jaguar/SDL v1.0.7 thread.

[JCrouse]

One more thing. Where can I find a list of key codes I can use in the cfg file so I can change the inputs. I have an SDLtest utility that reports what key was pressed but it doesn't seem to correspond with hardly any of the keys in your cfg file. Especially the higher numbered ones.

Thanks,
John

[Shamus]

The keycodes come from SDL_keysym.h. We do plan on integrating change-on-the-fly key mapping in the not-so-distant future, but for now, that file is your best bet.

As far as GUI suppression goes, this shouldn't be that difficult to do (with a command line option like -nogui or somesuch). Will put it into the TODO.

[JCrouse]

I am trying to understand the file extensions. I have readm the docs. You say to read the stdout.txt but all that's in there is hardware information from my system. The readme says to learn more about the command line syntax type vj -h or vj -help. Neither one of them work for me. I then went to the forum (here) and saw the post about cowering .jag extensions. I believe I have a cowering set. They all have a .jag extension. They load and run fine throught the GUI. However I get the error, couldn't be loaded (like the other guy) when attempting it from the command line. If I rename the extension I still get the same error. Is it just that the Cowering dumps are not the correct type or that they just have the wrong extension as you stated in your reply? Sorry for being long winded I'm just trying to learn and also give as much information as possible.

Thanks,
John

[Shamus]

Are you using 1.0.7? The extension problem was fixed in the latest version. I'm not sure about the command line (as I hardly ever use it anymore), but I'm pretty sure it works the way it should (again, in the latest version). You can immediately tell what version you're using by running it with the GUI and going to Info|About.

Here's the latest VJ run from the command line on my system:

Microsoft(R) Windows 98
   (C)Copyright Microsoft Corp 1981-1999.

C:\MinGW\Source\virtualjaguar>vj -help

C:\MinGW\Source\virtualjaguar>type stdout.txt
Virtual Jaguar GCC/SDL Portable Jaguar Emulator v1.0.7
Based upon Virtual Jaguar core v1.0.0 by David Raingeard.
Written by Niels Wagenaar (Linux/WIN32), Carwin Jones (BeOS),
James L. Hammons (WIN32) and Adam Green (MacOS)
Contact: http://sdlemu.ngemu.com/ | sdlemu@ngemu.com
Usage:

vj [romfile] [switches]
  -? or -help     : Display usage and switches
  -frameskip 1-10 : Enable frameskip 1 - 10 (default: none)
  -joystick       : Enable joystick/gamepad
  -joyport 0-3    : Select desired joystick port
  -bios           : Boot cart using Jaguar BIOS ROM
  -nobios         : Boot cart without using Jaguar BIOS ROM
  -dsp            : Force VJ to use the DSP
  -nodsp          : Force VJ to run without the DSP
  -pipeline       : Use the DSP pipelined core
  -nopipeline     : Use the DSP non-pipelined core
  -gl             : Use OpenGL rendering
  -nogl           : Use old non-OpenGL rendering
  -fullscreen     : Enable fullscreen mode (default: windowed)
  -window         : Enable windowed mode
  -pal            : Force VJ to PAL mode (default: NTSC)
  -ntsc           : Force VJ to NTSC mode

Invoking Virtual Jagaur with no ROM file will cause it to boot up
with the VJ GUI.

My guess is that you're not using the latest version...

[JCrouse]

Thank you for the prompt reply. Yes, I am using the latest version. FWIW, I am trying the latest version on three different systems, all running XP. The help command line parameters don't work. Also, as previously ask, will the Cowering set work by renaming the extension (It doesn't for me) or are these just dumped in a way that is incompatible with VJ's command line. As I stated, they work with the GUI.

>> Edit
I also just tried the -help on a Windows ME system with the same results, nothing. Just thought you'd like to know.
>> Edit

Thank you,
John

PS: What EXACTLY is the commandline syntax? Is it as simple as:

vj romname.j64

I beleive this is all that should be needed since the location is specified in the cfg file, however, I've tried the full path with and without quotes and nothing works.

[Shamus]

To answer your question about the Good set, yes, renaming the extensions of the actual cartridge dumps to .j64 will work (this will NOT work for demos and other homebrew programs).

Currently vj doesn't look at the config file to find paths for a ROM passed in on the command line (it should). Supplying the full path works as long as you do it right. For example, if you have a ROMs subdirectory with a zipped ROM named foo.zip, you would say

vj ".\ROMs\foo.zip"

for VJ to find the ROM.

When you run VJ, does it create a stdout.txt, stderr.txt or a vj.log file in the same directory where VJ lives? It should.

[JCrouse]

Updated File!!

Here is a little app that will allow you to exit Virtual Jaguar with the ESC key, making it a little more front end and cabinet friendly. See the included Readme.txt file for more details and usage instructions. This was only tested on Windows XP SP2 and requires the Microsoft .Net framework 1.1. To get this go to http://download.microsoft.com and do a search for the file dotnetfx.exe.

Enjoy,
John

[Shamus]

Using this file isn't necessary with the latest version in CVS--it now bypasses the GUI if you pass a ROM in on the command line.

[JCrouse]

Originally Posted by Shamus

Using this file isn't necessary with the latest version in CVS--it now bypasses the GUI if you pass a ROM in on the command line.

Shamus
I'm slightly confuse (happens often ). The purpose of my wrapper is to add the ability to exit with the ESC key. This would generally be considered a feature of a cabinet friendly emulator. Are you saying this is what the latest CVS does, or that this is planned? The CVS stuff is good, but I can be patient and wait for your official release. I tried the latest CVS last evening. Here is my feedback, for what it's worth. First, I had to set the "UseJaguarBios" to 0 to get it to play a game. Maybe this is normal but I do have a bios and have it in the proper folder and am pathed to it in the cfg file. In the 1.0.7 it worked well when set to 1. Then when I got a game to launch (as a commandline parameter) the GUI seemed to function the same as in 1.0.7, meaning it wasn't visible if I fed it a rom as a command line parameter. Then when I hit the ESC key (to exit), the GUI popped up. This again seemed to be the same functionality as 1.0.7. At least to me. Anyways, this is just feed back and requires no reply. I like your emulator and will continue to keep an eye out for updates. ALos, in the latest CVS, when I just click on VJ and launch the GUI, no roms showed up in the default folder (even though I was pathed to it) and I couldn't swithc folders any way. This may be normal. Anyways, GREAT JOB SO FAR and I REALLY look forward to your next update.

Thanks for your time,
John

[VIP_EJC]

i can't get the atari virtual jaguar gui to appear - i read an old version manual which says to type the command line /.vj or double click on the vj executable - so i double clicked the executable but nothing happens and i don't know where to type command lines - when i first open the vj executable there's just a screen with tie dye colors - there's no file input or any other menu commands like most all emulators - please help me - thank you

[lemoncade]

The readme tells me to read the "install" file. but the zip "virtualjaguar-1.0.7-win32-bin" does not come with one. Can someone link it? or paste it's contents? I have no idea how to install this emu.

[tillin9]

Howdy, thanks for this terrific emulator! I've been a longtime user under Windows, but am trying to get the Linux port to work as well and having some issues.

First, the source link on the homepage still has the } problem.

Second, there are some runtime issues:
While virtual jaguar compiles and runs, the cursor is really slow in the GUI, making loading ROMs difficult. Once I start a ROM, processor use skyrockets and besides a message saying emulation is starting, nothing happens. This is a known working ROM, that works fine with virtual Jaguar under windows. Also, just for the compatibility chart I've played through Trevor McFur many, many times under Windows and there were no issues. Finally there is no way to exit besides kill -9. The quit in the GUI doesn't quit and neither does the close from the window manager.

I'm using this on Debian Etch, I tried both my compiled version and the Gentoo binary posted in this thread. Any ideas?

[Ricardo99]

Love the emulator, bought a Jag when they 1st came out, had all the major titles for it. This emulator is a godsend as my Jag has sadly broken. Great job on this so far guys, really is. It's been quiet for sooo long though, just hoping you haven't given up on the project like so many others have. Hoping you keep up the good work.

Ricardo99.

[robert_]

Uh, the casting of alias->ptr to unsigned char in src/memory.cpp:138, it makes my gcc 4.1.2 gag on the fact that the conversion will loose digit precision.

Thanks,
- Robert

robert_@sandbox virtualjaguar-1.0.7-src$ ./compile

*** Checking compilation environment... OK
*** Compiling Virtual Jaguar for generic Unix/Linux...

gcc  src/m68kmake.c -o obj/m68kmake.elf
obj/m68kmake obj src/m68k_in.c

                Musashi v3.3 68000, 68010, 68EC020, 68020 emulator
                Copyright 1998-2000 Karl Stenerud (karl@mame.net)

Generated 1962 opcode handlers from 503 primitives
gcc -Wall -Wno-switch -Wno-non-virtual-dtor -O2 -D__GCCUNIX__ -ffast-math -fomit-frame-pointer `sdl-config --cflags` -Iobj -c src/m68kcpu.c -o obj/m68kcpu.o
cc1: warning: command line option "-Wno-non-virtual-dtor" is valid for C++/ObjC++ but not for C
gcc -Wall -Wno-switch -Wno-non-virtual-dtor -O2 -D__GCCUNIX__ -ffast-math -fomit-frame-pointer `sdl-config --cflags` -Isrc -c obj/m68kops.c -o obj/m68kops.o
cc1: warning: command line option "-Wno-non-virtual-dtor" is valid for C++/ObjC++ but not for C
gcc -Wall -Wno-switch -Wno-non-virtual-dtor -O2 -D__GCCUNIX__ -ffast-math -fomit-frame-pointer `sdl-config --cflags` -Isrc -c obj/m68kopac.c -o obj/m68kopac.o
cc1: warning: command line option "-Wno-non-virtual-dtor" is valid for C++/ObjC++ but not for C
gcc -Wall -Wno-switch -Wno-non-virtual-dtor -O2 -D__GCCUNIX__ -ffast-math -fomit-frame-pointer `sdl-config --cflags` -Isrc -c obj/m68kopdm.c -o obj/m68kopdm.o
cc1: warning: command line option "-Wno-non-virtual-dtor" is valid for C++/ObjC++ but not for C
gcc -Wall -Wno-switch -Wno-non-virtual-dtor -O2 -D__GCCUNIX__ -ffast-math -fomit-frame-pointer `sdl-config --cflags` -Isrc -c obj/m68kopnz.c -o obj/m68kopnz.o
cc1: warning: command line option "-Wno-non-virtual-dtor" is valid for C++/ObjC++ but not for C
gcc -Wall -Wno-switch -Wno-non-virtual-dtor -O2 -D__GCCUNIX__ -ffast-math -fomit-frame-pointer `sdl-config --cflags` -I. -Isrc -Isrc/include -I/usr/local/include -I/usr/include -c src/memory.cpp -o obj/memory.o
src/memory.cpp: In function ‘void memory_memoryUsage(FILE*)’:
src/memory.cpp:138: error: cast from ‘void*’ to ‘unsigned int’ loses precision
make: *** [obj/memory.o] Error 1

[Shamus]

Yeah, I've recently gone through and fixed the source to be more gcc 4.2.x friendly. Getting rid of all the warnings about type punned pointers was a lot of fun. At any rate, I've been trying to get hold of Niels but no luck so far. I'm trying to get the repository over at icculus switched over to subversion but Ryan over there won't do it without Niels's approval. At any rate I've set one up on my private server and will try to get fixes out sometime soon.

The reason for the delay on 1.1.0 is that the new blitter is being rewritten with using the actual ASIC nets for Tom and Jerry. Also, some kind soul with actual hardware and the ability to probe it for us has donated their findings on the CD attachment which will make it possible to run CD games on VJ directly from the CD drive. We're striving for accuracy before optimization here, please keep that in mind folks. Also, I'm aware of the speed issues with respect to the Linux port; I'm looking into it but in the meantime you might try running it fullscreen and see if that speeds things up there.

I may post an interim 1.0.8 that should take care of most (if not all) of the issues you guys are having with the emu right now since I've been neglecting updating CVS. If I can't find Niels fairly soon, I may just update the web page to point to my server so people can experiment with broken code. At any rate, the new blitter has already made a huge difference in a lot of games that were broken before, but it's slooooooow. Also it looks like the BIOS and DSP are becoming more and more required for proper running of games as well which of course means *more* slowdowns...

Please bear with me in the meantime--once I get it all sorted out VJ is going to rock.

[Ricardo99]

Damn that's good to hear Thought the project had died, was really gutted
I'm looking forward to the next release with bated breath, my poor old Jag has died ! I think Jerry kicked the crap outta Tom tbh..... So VJ is my only means of playing jag games for now and it's sooo close to being perfect. So glad to hear you are still working on it...thanks for the great work and amount of effort you guys have put in to it...brilliant, thanks

[robert_]

Originally Posted by Shamus

Yeah, I've recently gone through and fixed the source to be more gcc 4.2.x friendly. Getting rid of all the warnings about type punned pointers was a lot of fun. At any rate, I've been trying to get hold of Niels but no luck so far. I'm trying to get the repository over at icculus switched over to subversion but Ryan over there won't do it without Niels's approval. At any rate I've set one up on my private server and will try to get fixes out sometime soon.

So, your copy actually COMPILES in gcc 4.2.x? Awesomeness.

Originally Posted by Shamus

The reason for the delay on 1.1.0 is that the new blitter is being rewritten with using the actual ASIC nets for Tom and Jerry. Also, some kind soul with actual hardware and the ability to probe it for us has donated their findings on the CD attachment which will make it possible to run CD games on VJ directly from the CD drive. We're striving for accuracy before optimization here, please keep that in mind folks. Also, I'm aware of the speed issues with respect to the Linux port; I'm looking into it but in the meantime you might try running it fullscreen and see if that speeds things up there.

Hey, don't count me out! I'm planning on seeing if I can acquire a Jaguar... I'd be more than happy to let you peek and poke at it and whatnot when I get it

Originally Posted by Shamus

I may post an interim 1.0.8 that should take care of most (if not all) of the issues you guys are having with the emu right now since I've been neglecting updating CVS. If I can't find Niels fairly soon, I may just update the web page to point to my server so people can experiment with broken code.

Hooray broken code!

Originally Posted by Shamus

At any rate, the new blitter has already made a huge difference in a lot of games that were broken before, but it's slooooooow. Also it looks like the BIOS and DSP are becoming more and more required for proper running of games as well which of course means *more* slowdowns...

Please bear with me in the meantime--once I get it all sorted out VJ is going to rock.

Super Awesomeness! So this might mean that I can actually get to play Wolfenstein 3D without it being a mess!

- robert_