What's new

PD graphic prob: Cam-/ Bombspy

daMatt

New member
Hiho...

I have a little problem playing PD. In fact, everything is fine, graphics are displayed correctly, no sound probs, etc.

But there is one little thing: When using Cam- or Bombspy, there isn't such a lense effect, like there should be. The display is just black (Cams' HUD is displayed correct though). This may not be a problem in Level2, but using it in the Chicago or G5-Level definitly is. I tryed all kinds of graphic-Plug-ins and settings. But i can't handle it.

Is there someone who knows how to fix that? I am using PJ64 as an Emulator
(and in fact, if i didn't had lost my PD Cartridge, i wouldn't use it at all ;) )

greetz, daMatt
 
Last edited:
OP
D

daMatt

New member
Hiho.

I tried the Gliede64 Plug-In already. But the result was a mess of pixels on my screen but no graphic. I tried a lots of settings with it too. But it didn't worked out till now. Any suggestions. By the way. Wtf is a wrapper? ^^; ( i rellay don't know)

I have a Radeon 9600 XT GPU by the way.

greetz, daMatt
 

Clements

Active member
Moderator
A wrapper basically translates Glide stuff to OpenGL or Direct3D which your graphics card can use. The Camspy/Bombspy is a tough effect to get working, but Glide64 does do it, but you may need to use the 'Read every frame' option (=slow) since hardware framebuffer does not work with Hacktarux's wrapper (yet).
 

Gonetz

Plugin Developer (GlideN64)
Clements said:
A wrapper basically translates Glide stuff to OpenGL or Direct3D which your graphics card can use. The Camspy/Bombspy is a tough effect to get working, but Glide64 does do it, but you may need to use the 'Read every frame' option (=slow) since hardware framebuffer does not work with Hacktarux's wrapper (yet).
'Read every frame' is for frame buffer effects which are processed by N64 CPU. Such effects cannot be detected by video plugin, thus plugin just read every drawn frame from video memory to main memory so CPU can access and modify it. Frame buffer effects in PD have been processed by plugin itself, thus 'Read every frame' is useless here. If hardware framebuffer emulation is not supported by your hardware, plugin will automatically use software framebuffer emulation, which is supported by all wrappers.
 
Last edited:

Top