2 problems in 1.5 and 1.6

[StealthSudaka]

Ima big fan of Pj64, Ive had it for a long time... I started with 1.3 and now Im on 1.6... but since 1.5 Ive been getting the same two problems :

1- Whenever I enable Anti-aliasing it quits and i get this error that says "Switching resolutions failed to initialize Direct3d, error code: 8876017C D3DERR_OUTOFVIDEOMEMORY"

the funny thing is that it used to work before!!

2- Whenever I press Ctrl Enter to enable fullscreen, it goes fullscreen but windowed.. and moved to the right side of my monitor.. with amazingly SLOW emulation speeds.

the funny thing is that this ALSO used to work!!

did I do something ? I havent changed any plugins or anything.. why does that happen?

 

[squall_leonhart]

Switch back to the Dx6 plugin.

i also get a similar issue, where if i go back to a window after loading a save state in full screen, it locks the display up.

i also once got that outofvideomemory error as well but haven't seen it in a while.

all i can say is that theres some serious bugs in the Dx8 plugin that aren't in the Dx6 plugin, even though the Dx8 plugin has more features its also introduced more bugs.

what kind of video card have you got and what driver version are you running?

 

[StealthSudaka]

yea..

what kind of video card have you got and what driver version are you running?

well I know it works on dx6 plugin perfectly... but the graphics just aint the same

I have an ati radeon 9550 agp, catalyst 6.3 (if thats wat u meant by driver version), and uh... yea.

like you said might be just a compatibility issue with graphic cards... a stupid bug in dx8 plugin.

 

[Smiff]

i have a radeon9550, should be best with the dx8 plugin.. although i'm using older drivers, perhaps ati messed something up in the new ones.. did it used to happen with older drivers? whats your resolutions and vram size?

as for "serious bugs in the Dx8 plugin".. well there are no problems like this that we know of, so some more info would be good please. it hangs every time you load a state in fullscreen then return to windowed? which drivers are you using?

 

[StealthSudaka]

mm

i have a radeon9550, should be best with the dx8 plugin.. although i'm using older drivers, perhaps ati messed something up in the new ones.. did it used to happen with older drivers? whats your resolutions and vram size?

as for "serious bugs in the Dx8 plugin".. well there are no problems like this that we know of, so some more info would be good please. it hangs every time you load a state in fullscreen then return to windowed? which drivers are you using?

well actually I dont remember switching drivers during my extensive use of the Pj64 emulator.. the thing is that one day it works beautifully with anti-aliasing to the max as well as anisotropic at full... then one day I clicked on the Pj64 icon.. and as soon as the window came up I got the error "failed to initialize Dx8 plugin"
I hadnt done anything overnight....
then when that error stopped showing, I began to get that "outofvideomemory" error everytime I enabled Anti-aliasing... as well as the fullscreen problem where it went fullscreen to the right of my desktop.. and emulated very slow... my guess is because it was still windowed when it went fullscreen.
with the dx6 plugin that doesnt happen.
My resolution in 1024x768 (desktop and Pj64 wise)
Vram size.. I dont if card size or ram but I got 1024 of system ram and 256 on my video card.

 

[Smiff]

yes sounds like a driver issue... try uninstalling your video drivers, and going back to say... v5.9. make sure all driver settings are cleared, can't remember if ati provide a standalone uninstaller or what.
also remove/disable any ATI tweak utilites you have in case they are interfering.

 

[squall_leonhart]

Smiff, its happened with every driver i can remember using.

even the Det 50's and FW60's

as long as i load a save state in a window. i can freely switch between full screen and window mode.

but if i load the save state in full screen mode, then if i try to switch back to window mode, it locks in full screen.

the game is still playing, i can move, and the sound is there, but the entire image just locks up.

i can honestly say its the Plugin as if i do managfe to get out of it.

if i try to run another rom i get a cannot establish direct3d bug, and it mentions the plugin.

if it was drivers it would mention the nv4.dll and drop my system back to a safe running state. (ie windows XP disables the video driver when it detects an error and forces it back to vga mode)

Running with the Dx6 plugin it all works fine.

It does the same thing on my other machine which has a TI4800SE in it when i put it on the Dx8 plugin. (it is a Dx8 card after all).

neither Rices plugin, or the DX6 plugin cause this issue, so it does appear to be something in the video plugin.

you might need to test some newer drivers out.
also. this problem might be related to the fact that Radeon 9xxx has PS1.4 and VS1.1. (plus sm2.0)

but Nvidia cards below the 5200 only have PS1.1/VS1.1.

im not sure what it is. but if i try to load full again when it locks up. it creates a general exception fault (blah blah blah, a general exception has occured in the application (pj64.exe) with the module (your dx8 plugin) and must close.

or. if i do manage to get out of full screen and back to the main rom browser, if i start a new rom, then i get the can't establish full screen error.

heres my event viewer info

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date:  8/04/2006
Time:  8:35:45 PM
User:  N/A
Computer: ATHLONXP2000
Description:
Faulting application project64.exe, version 0.0.0.0, faulting module jabo_direct3d8.dll, version 1.0.0.1, fault address 0x000017e9.
For more information, see Help and Support Center at [URL="http://go.microsoft.com/fwlink/events.asp"]http://go.microsoft.com/fwlink/events.asp[/URL].
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 70 72 6f   ure  pro
0018: 6a 65 63 74 36 34 2e 65   ject64.e
0020: 78 65 20 30 2e 30 2e 30   xe 0.0.0
0028: 2e 30 20 69 6e 20 6a 61   .0 in ja
0030: 62 6f 5f 64 69 72 65 63   bo_direc
0038: 74 33 64 38 2e 64 6c 6c   t3d8.dll
0040: 20 31 2e 30 2e 30 2e 31    1.0.0.1
0048: 20 61 74 20 6f 66 66 73    at offs
0050: 65 74 20 30 30 30 30 31   et 00001
0058: 37 65 39 0d 0a            7e9..

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date:  8/04/2006
Time:  8:35:20 PM
User:  N/A
Computer: ATHLONXP2000
Description:
Faulting application project64.exe, version 0.0.0.0, faulting module jabo_direct3d8.dll, version 1.0.0.1, fault address 0x00015590.
For more information, see Help and Support Center at [URL="http://go.microsoft.com/fwlink/events.asp"]http://go.microsoft.com/fwlink/events.asp[/URL].
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 70 72 6f   ure  pro
0018: 6a 65 63 74 36 34 2e 65   ject64.e
0020: 78 65 20 30 2e 30 2e 30   xe 0.0.0
0028: 2e 30 20 69 6e 20 6a 61   .0 in ja
0030: 62 6f 5f 64 69 72 65 63   bo_direc
0038: 74 33 64 38 2e 64 6c 6c   t3d8.dll
0040: 20 31 2e 30 2e 30 2e 31    1.0.0.1
0048: 20 61 74 20 6f 66 66 73    at offs
0050: 65 74 20 30 30 30 31 35   et 00015
0058: 35 39 30 0d 0a            590..

 

[Trotterwatch]

You running anything like Windowblinds? Just wondering if that could be causing some interaction.

but Nvidia cards below the 5200 only have PS1.1/VS1.1.

GF4 cards support PS 1.3.

 

[squall_leonhart]

You running anything like Windowblinds? Just wondering if that could be causing some interaction.



GF4 cards support PS 1.3.

correct. which is nothing more then PS1.1 with a new vertex memory call function.

nothing changed much...

and yes.. i do run windows blinds, but i have created a profile so that project 64 isn't skinned and uses the Win9x theme system instead.

but i've already tested agaisnt that and turning it off and going back to default windows themes did abso nothing. so its definitely not that.