What's new

A REAL Plugin issue with Kirby 64

india349

New member
I believe I have found an actual plugin issue with Kirby 64, no, not the health bar...

In world 3 (Aqua Star), course 4 (the one that starts out underwater), Kirby falls through the first section with the rockets and those enemies that shoot the red spikes out at you.

However, when you go to the next screen, the action immediately gets choppy (while normally running at 59 fps) and an error pops up in a dialog box saying "Access Violation, graphics error", something along those lines. I would bring up exactly what it says, but the emulator crashes immediately afterward.

This is using Jabo's Direct3D 8 plugin that comes with Pj64. I tried the plugin with Mupen64 and the same result, emulator crash. I used the Direct3D 6 plugin and although it then works past that section, the graphics are screwed up.

I tested all the advanced options with the plugin and none work, so I'm trying to find a better way around this. I can't use the OpenGL plugin, my computer doesn't seem to have compatible hardware. Any suggestions?

Thanks. india349

PS, I'd be willing to post my .eep file if anyone is interested in testing this particular level. Thanks again.
 
Last edited:

squall_leonhart

The Great Gunblade Wielder
i do not get this error, make sure to disable all cheats and reload the game from a native save file, also make sure there are no memory resident TSR's running and that the game image is ok.
 
OP
I

india349

New member
I've no cheats on, playing only on in-game saves, and I verified the rom with GoodN64, it's fine. I even updated my DirectX to the latest one on Microsoft's website, but nothing works. I was able to get through the level though; it seems only that one section to do this.

I'm just interested in knowing what exactly the problem is...the OpenGL and Glide64 w/ wrapper plugins don't seem to work so Direct3d's all I have.

Thanks
 

Smiff

Emutalk Member
yeah id be interested in trying that, please post your save and detailed instructions. it may be fixable or workaround-able.
 

squall_leonhart

The Great Gunblade Wielder
i'll test this with my version, and then see if i can reproduce it by changing settings, it might be something to do with the RDB, since i have customised my own from the default settings it could be why i don't get these errors.

ok, onto the testing of the settings.

Ini defaults to
check memory advance
4mb
default
use first save type
2
Register caching
use TLB.

save game has the entire game finished, and cheats off.


last edit

i can confirm that the graphics get choppy, but i got no error regarding direct3d

the Dx6 plugin works fine here, no choppyness and no crash and no graphics corruption.

please post your system specs and the current video driver you are using.

something i just noticed,

if you keep kirby close to the floor or at the top of the screen, the game doesn't slow down as much if at all, possible framebuffer problem?

first image is the Dx6 plugin
second image is the DX8 plugin at the bottom.

and the third image is the DX8 plugin when you swim in the middle of the screen.
 
Last edited:

Typify

Nolife
Yep, the graphics get choppy (unless you swim at the bottom of the level) but there's no error message for me.
 
OP
I

india349

New member
Sorry, should have checked back sooner.

I'm using the intel graphics controller that's on my computer with Jabo's Direct3d 8 plugin. Here's my native save file.

View attachment 32928

Kirby uses the D-pad, so make sure that's set up in advance.
At the title screen, press Start to go to Files

File 1 is saved, press A.

A screen with a jungle-looking planet labeled Neo Star shows up. Press Left on the D-pad to go back to Aqua Star and press A.

Move the crayon to the square marked with the 4 dotted die, press A.

Kirby enters the level sinking in the water. Avoid the enemies and exit on the bottom right side of the screen. Advancing forward on this next screen causes the error on my computer.

Thank you for the help!
india349

In regards to the other posts, I did notice keeping Kirby toward the ground makes it less choppy but as the camera scrolls around to be behind kirby, just before you reach the falling rocks, the game's choppiness speeds up and the error will occur no matter where I am on screen.

My specs:

Pentium 4 2.50 GHz
256 MB Ram
Windows XP Home SP2
Intel Graphics Controller
RealTek AC'97 Audio

:)
 
Last edited:

Smiff

Emutalk Member
uh oh. before trying that i'll make an educated guess its an(other) AV that only occurs on below min spec hardware..
 
OP
I

india349

New member
Well, you get what you pay for, I guess, haha. It's fast enough, no doubt, but I was still able to complete level so no harm done. Just curious.

I do remember I used Kirby with Glide64 on my old Voodoo3 and it played flawlessly, except the obvious health meter issue. Odd.
 

squall_leonhart

The Great Gunblade Wielder
thats because a Voodoo3 is a 3D accelerator with its own GPU, the Intel graphics chip uses the cpu to render images, and doesn't have all the Dx Caps required to play the game decently.

you could possibly benefit from scoring yourself a cheap 6600 or 6200, either will play kirby with the Dx6 plugin.

Smiff, i hope your not saying that we all have below spec hardware, because the choppyness happens on all systems with the Dx8 Plugin.
 

nilled

New member
weird... well I'm a noob at this and I got 1964, the kirby 64 rom, a controller, a sound plugin, and a vidio plugin, I can even get it to start, but everything is really glichy, and evertime I get hit kirby freezes, kirby also freezes when he uses most single powers, and some double powers... help? please.
 

nilled

New member
once agian, noob. this computer doesn't even belong to ME exactly, I'm kinda young, and as my older brother say's "your generation is hopeless. I just want to play the game
 

Agozer

16-bit Corpse | Moderator
Go Start --> Run, type dxdiag and Press Enter. The DirectX Diagnostics Tool should pop up. The first page should show the overall specs. Also click the Display tab and check what it says under Device.
 

Top