Shamus

It is an artifact of great evil, that can only be unmade by casting it into the fires of Mt. Doom from which it was forged.

What version are you using? If it's an official point release, you might want to try using one of the latest GIT snapshots: http://outrage.the-crow.co.uk/builds http://virtualjaguar.kicks-ass.net/builds

There's websites that generate this kind of thing. Something along the lines of: "She's a <adjective> <noun>, he's a <adjective> <noun>. They fight crime!!" Anywho, just thought I'd echo Albert's sentiment on the Dangerous Analysis piece on the whole CC debacle. Excellent stuff!

Please add me to the removal list.

I guess one man's sarcasm is another man's please-don't-shoot-me. ¯\_(ヅ)_/¯

Thanks triverse for the Carlsen interview, excellent! Now we have confirmation that the first Kickstarter was pulled because MK lied to the Kickstarter people (which seems to be the one constant in this story--MK and his lying). I'm a little disappointed that we still didn't learn why Mr. Carlsen looked like he was making his video at gunpoint, but still good info nonetheless. As to those complaining about the length of RetroGamingRoundup #99, it's all killer, no filler. Absolutely worth a listen if you're still reading this thread.

I think that whoever came up with the name "Coleco Turducken" for the RVGS mkII is a genius. I think going forward, this thing should only be referred to that way.

Well, consider this. If Al lives for another 80 years and does nothing write one post every second for the rest of his life, he will only be able to make around 2,522,880,000 posts. I think the universe is safe.

OK, so triverse's website is back, but there's no sign of the Carlsen interview there. :-/

Still eagerly awaiting the John Carlsen interview by triverse. I guess his servers are still on fire. :-/

You should always hold back a few to toss on eBay to undercut these guys.

If you're going to be really completist, you have to include the Breakout game in Rayman too.

If there's one thing the Jaguar does really well it's 2D sprites. The OP in the Jaguar is a monster in this regard, and you can throw a lot at it if you do it right (give it too much, and it fails spectacularly). It can handle bit depths from 1 BPP up to 24 BPP all on the same screen, so it's no slouch in the color department either.

Well, there's this bit of comedy, where he says he's going to do something to Star Raiders: http://atariage.com/forums/topic/243904-star-raiders-source-code-to-be-released/page-4?do=findComment&comment=3350822 You can guess the outcome of that.

Well, if you think about it, it makes sense that relative paths would blow up considering that the VJ executable is living down inside of an app bundle. I would bet you a nickel that if you made the relative path start with ../../../ (going up three levels, since it starts in virtualjaguar.app/Contents/MacOS/) it would see the software folder. Just a hunch.

Awesome! So it's the relative paths that are causing grief. Weird that it works OK on the first pass though.

Well, that's OK because VJ uses Qt5 (well, the latest in VJ's GIT repo does ).

The one on the right is obviously legit, just look at the quality of that label. Nice and sharp! BTW, I heard that they were working on a sequel called Sphere of Destiny but they never got around to it.

The reason is that nobody has stepped up to fill in the gap for our Mac users. That said, you can still find old versions at http://icculus.org/virtualjaguar/tarballs/ .

Well, my preference is to build everything statically on the Mac, that way you don't have to worry about having to bundle extra libraries and all of that kind of thing. As far as where to download VJ (for any platform), it's always been at http://icculus.org/virtualjaguar . As far as how to run from the command line, you have to run ./virtualjaguar.app/Contents/MacOS/virtualjaguar --help and it will print out all the options you need (I forgot that it was in an application bundle; makes it slightly more complicated ).

Well, you can pass --with-x=no to the configure script for SDL1 and that should take care of that. YMMV, of course.

In the Terminal, you have to navigate to where the VJ binary is (using cd). Then you type: ./virtualjaguar --log and it will create a log file for that session. To see all the options available to you, you would type: ./virtualjaguar --help

There's a mini-guide in the INSTALL file that comes with VJ, did you look at that? Compiling SDL1 shouldn't be any problem whatsoever if you follow the way it tells you to (i.e., not using XCode but using the terminal 'the Unix way'). Making it work with SDL2 is in the works, but isn't there yet.

If you launch it from a terminal and pass in the --log option, it will create a log file. That option is off by default. You should be able to see all the available options if you pass in --help as well (possibly; it doesn't work on Windows but it might on the Mac).

That would be awesome.