Report your problems here.

First, thanxs for you're hard work on this plugin. I hope someone will continue on it. :satisfied

In the overview of new features you state that banjo tooie and yoshi's story is fully playable. I just tried them both with Project 64 1.5 b1 and yoshi's seems to hang when you select the lucky fruit. (it just stays at that screen)

Banjo Tooie doesn't boot at all, but I believe that this is because the emulator doesn't support it because of the copy protection.

It this correct and what to do about Yoshi's Story?

You need emulator to play Tooie, all emulators that support it have not been released in public.

I said they are full playable in the plugin point of view.

Yoshi should be full playable, try 1964.

Where can i download the plugin and which emu's does it work 4?

Thanks for the info,

I've tried 1964_072 and it continues and plays great!!

Though somehow I've seemed to get past this point in Pj64, but I can't explain it. Maybe the new RSP plugin?? I don't know.
But i love the plugin already.

Thanks again Rice!!! :cool:

You can get the plugin binairy and source right here:

http://www.emutalk.net/showthread.php?s=&threadid=6928

or look at http://www.emu64.com

When I run Wipeout 64, I get this. Is there a way to avoid this bu

My Problem!!!

My Thread (http://www.emutalk.net/showthread.php?s=&threadid=6950)

if you read my release note carefully and completely, you should understand that your problem is dependent on your video card, and this plugin is using best setting for Nvidia GF2, does nothing at all the match its combiner/blende setting to your very video card DirectX caps.

Well, put this way, and as I said in the release note, you need to wait for someone to pickup the project and make it working for other video card, because different video card is really implementing DirectX in different ways. And many video card does not have good DX8 driver yet.

Most other DirectX plugins are using DX7 interface, since DX7 has been out for long time, video card usually support DX7 better than DX8, it's the reason why you have less combiner/blender problems with DX7 plugins.

btw, 16bit is not supported good enough, if you can, just use 32bit.

Whops sory I posted a bug report on the other thread ???

By the way, I also get that video problem with WO64. I have a GF2 mx installed.

hi guys, I'm just posting to see if anyone else has this problem. Pokemon Stadium, menu images are suppose to be fixed aren't they.

well I still get the multi colour on the menu images in the main menu.

also how do I post pics, I'll show you guys

Originally posted by Waan2k
hi guys, I'm just posting to see if anyone else has this problem. Pokemon Stadium, menu images are suppose to be fixed aren't they.

well I still get the multi colour on the menu images in the main menu.

also how do I post pics, I'll show you guys


Set the FrameBufferSettings in Complete

I still get only 5-10 fps with that plugin..
I tried every setting in project 64 and the plugin itself
I real don't knwo what I do wrong..
what's the newest ini for that plugin and where do I have to put it
to..maybe it's that but why is it that slow.......


:o :o

Originally posted by Oravla
Originally posted by Waan2k
hi guys, I'm just posting to see if anyone else has this problem. Pokemon Stadium, menu images are suppose to be fixed aren't they.

well I still get the multi colour on the menu images in the main menu.

also how do I post pics, I'll show you guys


Set the FrameBufferSettings in Complete


Just use default options, will be fine.

harb, I have searched through some of your older posts - but can't find one where you state your system specifications. I have noticed however that you have encountered problems with plugins and emulators before - so list your system specs, and let's see if the problem can be isolated. (Send me a PM if needs be) {sorry all for the off topic post}

as MADrigal I posted a bug report on the other thread...:sleepy:
so copy paste...
"first sorry for my english in french ;-)
i have tested your plugin Rice and the 2d gfx is awesome, you really did an excellent work but i have some problem with the 3d gfx (see after)... and i saw that the plugin use pure HW T&L with my radeon 8500 and I have the same bug when i choose Direct 3d HAL T&L with Jabo's plugin so i want to know if it could be possible that you can let us (in the option menu) choose between Direct 3D and Direct 3D with Hardware T&L?
because the 3d gfx make all the game unplayable :-(
Please do something!!
Thanks again and vive la france!!! "

PS: I m not the only one who have this bug, radTube got it too...
PS 2: This damn bug wasn't in the previous version (unofficial daedalusD3D8 0.08...)

Please do something!!!!! (again lol)

now the screen ...

Genenral problems:

After using a while, mainly when loading a new ROM, I get random BSOD : nv4displ.dll, page fault in non paged area, (Detonator 30.82).

Yesterday, when I closed a ROM in 1964 0.8.3c (I was playing in windowed mode), the desktop resolution was changed to the window resolution, then 1964 crashed. No problem in PJ, and it is fixed today in 1964 ?? kinda strange.

Today after I played a while, in 1964, the plugin has suddenly (after I restarted a rom) lost the ability to show textures. No problem in PJ. Strange, once again...
No more problems 30 min later. The only thing I changed is the ROM CD...

The winframe mode has little effect.


Game specific problems :


Beetle Adventure Racing : Unknown plugin error, for every frame during the options before the race (select car etc.). Dunno ingame, since I got bored after the 20th error and stopped the emulation.


DR Mario 64: background broken, pill not visible. With the default options. Ok but slow with frame buffer on copy&back. Pill flickering in PJ64, not in 1964 0.803c.


ExtremeG2: Fills the main memory (6 Mo free out of 576, paging a lot) during menu. You can see 1964 eating more and more memory in the task manager


FzeroX : major texture problems. + 'priority' (zbuffer?) : some things that should be hidden by the track apear over it (buildings and orange pyramid in the first race).


Harvest Moon, missing characters/text in menu


Mario Tennis : when using recomended setting (faster+recheck), my computer runs short of video memory when the emulator is using the framebuffer (splitted screen that presents players before the match / replay)

RR64: Use "Normal combine" to see the track. There are "priority
bugs" here too. (cfr screens)

Super Mario 64 (E) : The text is now broken (it was already in the
last version of the plugin). The text is still good in the official Daedalus plugin.

And here is the strange "missing textures" problem that occured a while back.

Someone reported Mario's head being black, in another thread. Note that this problem apeared and disapeared with no apparent reason, only in 1964... :!!!:

Very similar texture issues as to what is being described so far. See my specs below. I am confused however, as most info points to a Zbuffer problem, doesn't the GF2 and GF3 series use the same type? (hope that's worded right) I just thought the main difference in these two cards was the GF3 is faster and has a little more things it can do.

I also have problems when loading ROMs that sometimes they are just black screen, but I can hear the game sound. Does that just mean the game is not currently compatible to the plugin?

And finally, in my FrameBuffer settings for the plugin. I have two "Double Buffer Copy" in the list. Is this a bug? or is it known? And does it matter which one I use?

hmm, i have win98 and win2k, but in win2k, PJ64 says unable to initilise unofficial daedelus plugin.. etc

Originally posted by dayve
hmm, i have win98 and win2k, but in win2k, PJ64 says unable to initilise unofficial daedelus plugin.. etc Stupid question here: do you have DX8 installed in win2k?

shit, i am a jackass, maybe if i delete my post no-one will know how stupid i am.

heh, cheers mate

Sorry i post in
http://www.emutalk.net/showthread.php?s=&threadid=6928&pagenumber=3

1) theres known problems with 1964 0.8.3c.
2) there are still known Z-Buffer probs with the plugin.
3) make sure you have the custom RSP.dll, as it has a "Bypass Errors" option:
Original RSP.dll will report errors when it comes to unknown or unimplemented opcodes, and it can not continue after the error.
If this option is turned on, such errors will not be reported and the opcodes will be just ignore. Of course, there will be unknown side effects by doing such bypass. So try it by yourself.
(and i notice if it isnt used, crashes/hangs happen very frequently :)
4) there isnt two "Double Buffer Copy" entries in the plugin, the drop down box is a bit short (width wise) if you look they are both different. :)

Here is what the "Double Buffer Copy" looks like to me

http://home.stltoday.com/~lazertag/webimages/temp/D3DpluginREL2.gif

I did check out the source just now and can see one is "Double Buffer copy" and the other "Double Buffer Copy Sync".

I just can't tell which is which. I assume the top one is the default?

and what does sync do?

The second is "Double Buffer Copy / Sync", it is slower than "Double Buffer Copy".

two more bugs,

1. when coming out of full screen, only the gui with the rom entries is visible, but the vi/fps counter is still moving, as well as the registers. If you go back into full screen, you can see the game again. Doesnt happen wit jabo.

2. When coming out of full screen, the plugin remains in the full screen resolution, until you click outside the window of the program, where it then proceeds to shut down, and return the older resolution. Doesnt happen wit jabo.

Suggestion: The 1964 main window should be independent from the plugin. Be its own window, instead of being controlled by plugins.

For example, 1964 could have its own resolution, at a desired size, and when the game is started, the main window is hidden and a new one is brought, that would be the plugin window.

I'm not sure if this has been discussed before, but I've found some graphical glitches in Yoshi's Story with the Daedalus Direct3D8 Rel. 2 graphics plugin. First of all, it's absolutely fantastic that people are working on it to get games like Yoshi's Story work, I really appreciate it. But now the bug..

The textures in Yoshi's Story aren't aligned well; you have to wait, say 4 seconds, and then the textures are placed in their right position. This doesn't let you play the game well. I made a small gif animation of the situation. First, the textures are misplaced, and in frame 10 they jump back to their proper positions. As soon as you move left/right and the scenery moves out of the screen, it's going back to another weird position. Maybe this would help you Rice? But you probably know of this problem, or am I the only one who has it?

Oh, and one small glitch; Yoshi's shadow is white instead of black. Keep on developing the Daedalus plugin though, it's gonna be great!

when i try to start a game with daedalus plugin(after the releases 0.8..i didn't have any probl with 0.7 releases)this thing appears at the status bar :REF simulated pure hw vp(down)and the framerate keeps falling(it starts at 45 and it goes to 0.6).I suspect that the plugin turns on software mode but not use the hardware.My gfx card is a voodoo3 2000.Please if there is a way to fix this problem.....I remind that with 0.07b release everything was ok.

Its been mentioned here many times the Unofficial DaedalusD3D8 plugin is developed for "nVidia cards", and also needs DirectX 8.1, so its not going to work with a Voodoo based card.

yes get the same results as conker :-/

basically it should say ur gfx card rather than 'REF (simulated pure hw vp)'. thats definitely an indication to tell u ur gfx card is not supported. it worked in 0.07 cos that was a dx7 release, which is supported by voodoo cards. however dx8 is not, and therefore theres no chance of seeing this plugin working properly unless u buy a supported gfx card.

Originally posted by sk8bloke22
basically it should say ur gfx card rather than 'REF (simulated pure hw vp)'. thats definitely an indication to tell u ur gfx card is not supported. it worked in 0.07 cos that was a dx7 release, which is supported by voodoo cards. however dx8 is not, and therefore theres no chance of seeing this plugin working properly unless u buy a supported gfx card.


yeah but first of all i must fix my damaged car,
i need to find a job i guess :)
anyway that's what i thought about the problem
back to jabo's