project64
[Bug]: many strange things
Expected behavior?
I've been trying different versions of Pj64, most of them seem to have bugs related to video and debugging plugins. This is what I found: I was hoping to be able to use the debugging tools, the command window, the memory searcher and the memory viewer are what I use the most, as well as the dump.
But I wanted to extend their use further to be able to decipher more things in the current game I am analyzing. Like the use of function tracing with Stack Trace or writing ROM to RAM with DMA Log.
Actual behavior?
DMA Log not work, freeze not work, GLide64 not work, Stack Trace not Work, Elon Musk not work.
Steps to reproduce the problem
Enable debugging, try using DMA Logo Track Trace, nothing is visible. If you double click on the blank space in the Stack window, it will try to open the memory viewer at some random point. Also most of them I can't freeze areas of memory, even the activated cheats are deactivated when I try to check again in the cheats window. Some version (Legacy) only works freeze if you freeze 1 byte in the Memory viewer.
Error messages?
For the Video plugins, errors usually appear that mention some .cpp script and the game simply ends or just does not start and the window stays black.
What game were you playing?
I'm mostly doing it with Conker Bad Fur Day
Specifications and build details
Project64: (include commit version number and whether you are using the 32-bit or 64-bit version)
OS: (include version and OS build number using WinVer):
CPU: Xeon
RAM: 16GB
Graphics: Saphire 4GB
Using included plugins
- [X] I can confirm I am using the included RSP, audio, input, and graphics plugins
Plugins used while the issue occurred
Graphics plugin (and HLE or LLE): Glide64 fxxxxx (from dev) Audio plugin: default Input plugin: default RSP plugin: default
Copyright Compliance
- [X] There are no infringing files attached to this bug report.
@ImanCol First of all, you didn't include your operating system, or the model number of your CPU and graphics card.
Second of all, Glide64 and GLideN64 are 2 different plugins, so please specify which you are talking about. Providing version numbers would be helpful as well, you didn't fill those out.
Third, please indicate if you are using the latest stable version of Project64 or the latest development build.
Fourth, there is no such thing as debugging plugins, only graphics/video plugins, RSP plugins, audio plugins, and input plugins. I'm not sure what you meant by "debugging plugins". The debugger and other advanced features are not plugins, they are included with the emulator core.
Fifth, Project64 Legacy is a totally different emulator with a different code base. So comparing the 2 isn't really comparable. The latest stable version and the latest development version are the only emulators worth comparing here.
Sixth, you were incredibly vague about what doesn't work. Please be more detailed, otherwise we can't really help you at all. You mentioned an error message, but that was a core error, and had nothing to do with the debugger, memory viewer, etc. That can most likely be fixed by switching to another graphics plugin or enabling the CPU interpreter.
It seems that you might be experiencing separate issues and this probably could be resolved with using the CPU interpreter and Parallel-RDP graphics plugin with the latest development build.
Your post seems a bit trollish, so please provide useful information or close your issue.
@ImanCol First of all, you didn't include your operating system, or the model number of your CPU and graphics card.
Second of all, Glide64 and GLideN64 are 2 different plugins, so please specify which you are talking about. Providing version numbers would be helpful as well, you didn't fill those out.
Third, please indicate if you are using the latest stable version of Project64 or the latest development build.
Fourth, there is no such thing as debugging plugins, only graphics/video plugins, RSP plugins, audio plugins, and input plugins. I'm not sure what you meant by "debugging plugins". The debugger and other advanced features are not plugins, they are included with the emulator core.
Fifth, Project64 Legacy is a totally different emulator with a different code base. So comparing the 2 isn't really comparable. The latest stable version and the latest development version are the only emulators worth comparing here.
Sixth, you were incredibly vague about what doesn't work. Please be more detailed, otherwise we can't really help you at all. You mentioned an error message, but that was a core error, and had nothing to do with the debugger, memory viewer, etc. That can most likely be fixed by switching to another graphics plugin or enabling the CPU interpreter.
It seems that you might be experiencing separate issues and this probably could be resolved with using the CPU interpreter and Parallel-RDP graphics plugin with the latest development build.
Your post seems a bit trollish, so please provide useful information or close your issue.
I'm trying really hard to come and talk about these problems, I've asked in several places and all the answers just tell me that pj64 is "unstable". Anyway I can't find a better debugger for games, for now, but I try to make them work and I don't get the expected use.
As I said, I was trying to use the Stable version, Release (which is Project64-3.0.1-5664-2df3434). And then I also used the Yes Dev version (which is Dev-4.0.0-6446-02e816b)
Starting with Release, try testing on the old config (Project64 Video) When opening Conker BFD USA, It takes some time to respond, but then it responds and works.
Then I tried Glide"N"64 (For Modern PC) It works. Not working. Enable debugging "components". Start with Lock Value in the Memory Search window.
I tried freezing the values from the Memory Viewer. It doesn't work This makes it more tedious because it only allows you 1 byte.
Now try to view DMA Log and Stack Trace. DMA Log doesn't show anything, all blank.
In Stack Trace everything is blank, there is no information, but if I press or double click somewhere in the window, the Commands window opens.
There is no documentation that tells me why it doesn't work and the one here doesn't indicate that. https://hack64.net/docs/pj64d/
Try the Dev Version:
Using GlideN64, and trying to start Conker, I got this message.
Try the Dev Version:
Using Pj64 Video, and trying to start Conker, I got this message.
When starting the emulator for the first time
I tried to configure everything manually (I don't see GlideN64 listed?)
Using the available plugin I get this
try with an older Dev version (Dev-4.0.0-6442-eb985de, the only one available in .zip)
GlideN64
(I tried to change the plugin to Pj64 Video, and it crashed)
At this point using Pj64 video seemed impossible because the emulator crashed, and I just got a black screen.
About my PC specs, I already mentioned that I'm using a Saphire Nitro + 4GB, 16GB RAM, a 12-Thread Xeon CPU, Win 11
the default plugins weren't loaded because you're missing visual c or dx redist installed runtime files.
The long startup times on 4.0 are because of JIT changes, and advanced block linking has not been optimized for these changes yet, you can turn it off entirely on high end systems.
I haven't used Pj64 in a long time, and this issue wasn't related to the Video Plugin, but to the debugging features. I don't know if it's been fixed or if some still work and others don't.