|
|
|||||||
| About Us | Register | FAQ | Members List | Calendar | Mark Forums Read |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|
#1 (permalink) |
|
Emu author
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Join Date: Oct 2001
Location: The Netherlands
Posts: 114
|
Virtual Jaguar GCC/SDL v1.0.6 was released today. As allways you can get the versions from the the *official* Virtual Jaguar GCC/SDL Website. There's a source and a WIN32 binary download available. Here's what's new in this new release :
- Added support for gzipped ROM files. [Adam Green] - Added OpenGL support. Because of this, aspect ratios in the various graphic modes should be correct now. Thanks goes to Niels for enlightenment in this area. :-) [Shamus] - Moved all platform specific video code to video.cpp. This should make it easier to add functionality to the video subsystem without having to chase code around in places where it didn't belong. [Shamus] - Key bindings are now customizable. [Shamus] - VJ now uses a config file (vj.cfg) for commonly used settings. Settings in the config file can still be overridden by command line switches. [Shamus] - Preliminary GUI mouse support. [Shamus] - Fixed an off-by-one bug in the Object Processor when dealing with scaled bitmap objects. [Shamus] - Fully virtualized screen size. What this means is that we can keep the Jagaur screen displayed in a convenient size (320 x 240) and the graphics that various ROMs display will now be properly centered (more or less, they were really centered for a TV display). [Shamus] - Border color is now displayed properly. [Shamus] - Fully pipelined DSP core. Because of this, Wolfenstein 3D now has sound. To use the old core, use the -nopipeline switch. [Shamus] For the people that are to lazy to browse, you can download the releases using the following direct links : Download the source release from here Download the WIN32 Binary from here. Download the MacOS X Binary from here. Download the Debian Linux Binary package from here. Make sure you put all Virtual Jaguar v1.0.6 requests/bugs/etc in this thread! Also, make sure you say what version (source, CVS, binary) you used and on what platform! Regards, Niels Wagenaar http://sdlemu.ngemu.com
__________________
Better a penguin that rox than Windows that often locks! Last edited by nwagenaar; September 25th, 2003 at 10:12. Reason: Updated with Debian and MacOS X binary links |
|
|
|
|
|
#3 (permalink) |
|
Emu author
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Join Date: Oct 2001
Location: The Netherlands
Posts: 114
|
Re: Virtual Jaguar v1.0.6 (pre)support thread
Updated the thread with the latest information and downloads. I hope that Adam Green will give us information soon about the MacOS binary
__________________
Better a penguin that rox than Windows that often locks! |
|
|
|
|
|
#4 (permalink) |
|
Registered User
Join Date: Sep 2003
Posts: 3
|
Re: Virtual Jaguar v1.0.6 (pre)support thread
Hi, I tried to run AVP and got the following log:
VirtualJaguar v1.0.6 (Last full build was on Sep 23 2003 02:56:30) Memory: Allocating 4194304 bytes of memory for <Jaguar 68K CPU RAM>...OK Memory: Allocating 262144 bytes of memory for <Jaguar 68K CPU BIOS ROM>...OK Memory: Allocating 6291456 bytes of memory for <Jaguar 68K CPU ROM>...OK Memory: Allocating 4096 bytes of memory for <GPU work RAM>...OK Memory: Allocating 128 bytes of memory for <GPU bank 0 regs>...OK Memory: Allocating 128 bytes of memory for <GPU bank 1 regs>...OK --> GPU stats were reset! Memory: Allocating 8192 bytes of memory for <DSP work RAM>...OK Memory: Allocating 128 bytes of memory for <DSP bank 0 regs>...OK Memory: Allocating 128 bytes of memory for <DSP bank 1 regs>...OK Memory: Allocating 65536 bytes of memory for <Jaguar Object processor Y blend lookup table>...OK Memory: Allocating 65536 bytes of memory for <Jaguar Object processor CR blend lookup table>...OK Memory: Allocating 16384 bytes of memory for <TOM RAM>...OK Memory: Allocating 131072 bytes of memory for <CRY/RGB mixed mode LUT>...OK Memory: Allocating 65536 bytes of memory for <DAC buffer>...OK DAC: Successfully initialized. Memory: Allocating 65536 bytes of memory for <JERRY RAM/ROM>...OK VJ: Loading "/home/nemesis/share/emu/jag/Alien vs Predator.jag"...OK (4194304 bytes) CRC: DC187F82 EEPROM: Creating ./eeproms/DC187F82.eep cd_bios: reset --> GPU stats were reset! 68K PC=802000 SP=00200000 TOM: Vertical Display Begin written by M68K: 40 TOM: Vertical Display End written by M68K: 2047 TOM: Horizontal Display Begin 1 written by M68K: 203 TOM: Horizontal Display End written by M68K: 1664 TOM: Vertical Interrupt written by M68K: 499 TOM: Vertical Interrupt written by M68K: 499 TOM: Video Mode written by M68K: 06C1. PWIDTH = 4, MODE = 16 BPP CRY, flags: BGEN (VC = 234) DAC: Writing to SMODE. Bits: JERRY: Writing 0000 to SCLK (by M68K)... DAC: Writing 0 to SCLK... JERRY: Writing 0013 to SCLK (by M68K)... DAC: Writing 19 to SCLK... DAC: Changing sample rate to 20774 Hz! DAC: Writing to SMODE. Bits: INTERNAL WSEN FALLING TOM: Vertical Display Begin written by M68K: 28 TOM: Vertical Display End written by M68K: 2047 TOM: Horizontal Display Begin 1 written by M68K: 203 TOM: Horizontal Display End written by M68K: 1664 TOM: Vertical Interrupt written by M68K: 511 TOM: Video Mode written by M68K: 06C7. PWIDTH = 4, MODE = 16 BPP RGB, flags: BGEN (VC = 503) TOM: Vertical Display Begin written by M68K: 28 TOM: Vertical Display End written by M68K: 2047 TOM: Horizontal Display Begin 1 written by M68K: 203 TOM: Horizontal Display End written by M68K: 1664 TOM: Vertical Interrupt written by M68K: 511 Sound was opened a few times, but the GLX window remained blank. Xfree86 4.3.0, Debian, gcc 3.3.2, Linux 2.4.23-pre4, Matrox G400 It works fine as before with -nogl Bug: putting command line options before the rom name causes a segfault. |
|
|
|
|
|
#5 (permalink) |
|
Emu author
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Join Date: Oct 2001
Location: The Netherlands
Posts: 114
|
Re: Virtual Jaguar v1.0.6 (pre)support thread
I know from personal experience that the Matrox G4X0 series have crappy support for OpenGL on Linux systems (but this could've changed in the past year).
Perhaps you could try upgrading your GLX items to the latest version and test OpenGL with it. Concering the bug when you put a commandline switch before the rom name, it's not a bug In the docs as well as in the switches output it clearly states that the ROM name should be put as 1st option, switches as last items.That we don't check about an non-existent switch, that is a bug. Fix should be available on CVS in the couple of days (as soon as I have time for it). Regards, Niels Wagenaar http://sdlemu.ngemu.com
__________________
Better a penguin that rox than Windows that often locks! |
|
|
|
|
|
#6 (permalink) |
|
Registered User
![]() ![]() Join Date: May 2001
Location: Colombia, Medellin
Posts: 102
|
Re: Virtual Jaguar v1.0.6 (pre)support thread
Im trying to complie but i got this error
Code:
gcc -Wall -Wno-switch -Wno-non-virtual-dtor -O3 -D__GCCUNIX__ \ -Dstricmp="strcasecmp" -fomit-frame-pointer `sdl-config --cflags` -I. -Isrc \ -Isrc/include -I/usr/local/include -c src/objectp.cpp -o obj/objectp.o src/objectp.cpp: In function `void OPProcessList(int, bool)': src/objectp.cpp:454: error: integer constant is too large for "long" type src/objectp.cpp:458: error: integer constant is too large for "long" type src/objectp.cpp:463: error: integer constant is too large for "long" type src/objectp.cpp:507: error: integer constant is too large for "long" type src/objectp.cpp:519: error: integer constant is too large for "long" type src/objectp.cpp:533: error: integer constant is too large for "long" type make: *** [obj/objectp.o] Error 1 Last edited by nwagenaar; September 23rd, 2003 at 23:44. Reason: The layout was crapped up :( |
|
|
|
|
|
#9 (permalink) |
|
Emu author
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Join Date: Oct 2001
Location: The Netherlands
Posts: 114
|
Re: Virtual Jaguar v1.0.6 (pre)support thread
Yep, this is indeed a new feature with GCC 3.3. I have a diff against the current VJ v1.0.6 sources (with many thanks to Ryan Underwoord) which solve this issue.
I reccon this will also work on GCC 3.2 and earlier. So, do you feel lucky to implent it in the CVS? ![]() Regards, Niels Wagenaar
__________________
Better a penguin that rox than Windows that often locks! |
|
|
|
|
|
#11 (permalink) |
|
Registered User
![]() ![]() Join Date: May 2001
Location: Colombia, Medellin
Posts: 102
|
Re: Virtual Jaguar v1.0.6 (pre)support thread
Does anyone compiled it with gcc 3.3.1, because i did but the games that got to work are giving me segfaults, ie Atari Cart, Aliens vs Predator is giving me just a red screen, Rayman works sort of but segfaults anfter a while.
|
|
|
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|