mupenplus crash when playing Conkers Bad Fur Day

[GoogleCodeExporter]

Describe your system:
 - Linux distribution: ubuntu
 - Machine type: (32-bit or 64-bit) 64 bit
 - Mupen64Plus version:1.4
 - Plugins used:RiceVideo

For visual artifacts, give:
- game name and CRC/MD5 hash (printed on console)
MD5: 00E2920665F2329B95797A7EAABC2390

- description of the artifact (missing polygons, flashing, wrong colors, etc)

Describe the problem:

mupenplus crash when playing Conkers Bad Fur Day

console outbuts this
Signal number 11 caught:
    errno = 0 (Success)

Please provide any additional information below.

Original issue reported on code.google.com by vitbur...@gmail.com on 15 Jun 2008 at 4:50

[GoogleCodeExporter]

and just say were mupenplus crashes it wen you make a new game in Conkers Bad 
Fur Day

Original comment by vitbur...@gmail.com on 15 Jun 2008 at 6:24

[GoogleCodeExporter]

Thanks for the bug report. 

I have the same US version of the ROM. MD5: 00E2920665F2329B95797A7EAABC2390
I was able to get past the new game screen to the 1st level just fine. The game 
has 
a lot of artifacts, and runs really slow on my PIII, but doesn't crash. In our 
new 
RCS status, I'd list it as 3 stars (lots of issues, but possibly playable on 
some 
systems). I used Glide64 and Rice 1.4. Glide64 gave better results, but Rice 
worked 
none the less. Glide64 also has a Conker's setting, btw. 

I'm on Debian unstable. Anyway... please give more info. Your video card, 
driver, 
and relevant video plugin settings. Ubuntu version and if you're using the 
binary 
or compiled it yourself would also be nice so other devs. can test. 

Original comment by sknau...@wesleyan.edu on 16 Jun 2008 at 9:20

[GoogleCodeExporter]

o this is geting wert almost ewry time it crashe mupenplus or get a blank stren 
after
you make a new game i am more vorit this may be all other games work fine for 
me 
this is only this that crash mupenplus there may be more game that are affected
i am usen the lates verson of  ubuntu 64-bit i am usen the binary but i can 
compiled it
also here is the log for wen crash mupenplus

Original comment by vitbur...@gmail.com on 16 Jun 2008 at 6:01

Attachments:

• mupen+

[GoogleCodeExporter]

o i thing i see were the bug is it seam it only crash mupenplus when or get a 
blank
stren the  Dynamic Recompiler is use 

Original comment by vitbur...@gmail.com on 16 Jun 2008 at 6:30

[GoogleCodeExporter]

Are there any options I can set for the Rice plugin, the graphics are quite 
glitchy
using this plugin.  I've tried using the Glide64 plugin but it's jerky.

Original comment by wyattmei...@gmail.com on 23 Jun 2008 at 9:36

[GoogleCodeExporter]

Andr - Sorry, looks like this is a real bug with the 64-bit dynarec. On 32-bit 
it 
isn't an issue. Thanks for the extra info.

Wyatt - None that I know of. What CPU / GPU / video driver are you using? 
Glide64 
gives the best visuals for Conker's (actually most games) but might have higher 
system requirements. Since Conker's was one of the last N64 games released and 
has 
some of the best graphics (nicer lighting and reflection effects, higher 
polygon 
count, etc.), its natural that it has higher requirements than most other 
games. 
For example, my PIII 650 / Radeon 9700 Pro / r300 OSS driver can get ~25fps in 
Mario64, just barely play Zelda OOT, but looks like a slideshow in Conker's. 

Original comment by sknau...@wesleyan.edu on 27 Jun 2008 at 2:26

[GoogleCodeExporter]

I could not replicate this crash with a 64-bit source build from the trunk (rev 
693).

When you see flashing textures in Rice Video (as with this game), it is usually
caused by the wrong screen update setting.  If you edit the ini file at:
~/.mupen64plus/RiceVideoLinux.ini, search for the section with the name "CONKER 
BFD",
and add "ScreenUpdateSetting=1" after the other lines.  This fixes the flashing
artifacts in this game.

Original comment by richard...@gmail.com on 29 Jun 2008 at 3:18

• Changed state: Invalid

[GoogleCodeExporter]

@7: Hmm. I have that exact problem. Is it my fault for not reading some
readily-visible readme.txt-ish document or does the documentation need to be 
updated?

Original comment by stephan....@gmail.com on 29 Jun 2008 at 11:08

[GoogleCodeExporter]

No that information is not in any of the documentation yet.  This was something 
that
I found after a lot of debugging - I suppose I should find a place to mention 
this.

Original comment by richard...@gmail.com on 30 Jun 2008 at 4:16