Next Generation Emulation banner

The Bug Reporter Utility - Do not post bug reports

50928 Views 138 Replies 39 Participants Last post by  SXTC
Current Stable Release: 1.14
Current Beta Release: NA

I decided to create the "Bug Reporter". This program creates a text file in the same folder as PCSX2.exe called Bug Report.txt. That text file then could be posted on the forums when a person has a game problem.

Users must put this exe file in the same directory as PCSX2.exe for it to work.

1.01 Speed Hacks have now been converted from binary to English.
1.02 Increased readability. More information included in report (emulog.txt).
1.03 OS Check. Some useless information removed.
1.04 Removed even more useless information. Increased readability for the average user.
1.05 *Removed even more useless information. Increased readability for the average user.
1.06 Grabs user's active video card. Removed redundant erom stuff.
1.07 Fixed speed hack detection. Improved Operating System detection. Changed compression method for zip.
1.08 Now converts cpu option data from a numeric value to readable english text.
1.09 Gets the service pack of the os. Data from Gabest's plugin is now included.
1.1 Fixed some minor errors and added a visual theme. A link to the PCSX2 Game Troubleshooting Guide is now included. New exe icon that happens to have more meaning than the one before it. Various other things.
1.11 Added SSE4 detection (Gabest's SSE4 version confused my GPU checking method). Removed theme due to compatibility issues. Physical memory detection added.
1.12 Modified physical memory checking (what a nightmare).
1.13(Beta) Converted the Code from Visual Basic 6 to Realbasic. Almost same functionality as 1.12. Added a check to see if a Direct X SDK is installed. The link in the bottom left corner has been removed (freak accident will put back). App now fully utilizes the aero theme. You must have at least Windows 2000.
1.14 Fixed the crash error (fileinuse error code 104). Also updated sync hacks/gamefixes detection to coincide with PCSX2 0.9.6.
See less See more
1 - 15 of 139 Posts
what information does it record?
stuff from the console?

nevermind, i tried it out.

this is a great idea.
it records information about PCSX2's settings, plugins, and PC specs.

some of the info is a bit confusing though.
[Cpu Options]
i have multithreading on, but it says its = 0
is that correct?
and Hacks = 7?
whats that mean.
See less See more
oh yeah, just opened up the ini and its the same thing :p
but we do need simplified options.
only the devs are going to know what most of the stuff means.

something like

should be changed to
Multithreading On

that way, its obvious what it means.

and I was a bit confused the hacks option, but i think i get it now..
since theres 3 hacks, and hacks = 7, I guess then we're reading this in binary.
so binary 7 is 111, and the "1" stands for a hack being on, whereas "0" would be a hack is off.
See less See more
and i owe it all to my CS professors for forcing me to learn binary :p
i like it,
but i still think it needs to be cleaned up a bit.
lots of that information is useless for detecting bugs.

such as...
F1 - save state
(Shift +) F2 - cycle states
F3 - load state
F10 - dump performance counters
F11 - save GS state
F12 - dump hardware registers
MapUserPhysicalPages failed to unmap
error 87.
Closing gs thread
it would be nice if the program only records important information like
Problem with the Game
CPU Speed
Graphics Card (It would be nice if it can detect graphics card)
Speed Hacks
Custom FPS

its just a pain to have a gigantic info log, when you only care about half of the things on it.
See less See more
From what you just said Refraction, i noticed that my ini has alot of garbage data.

[Cpu Options]
i have MTGS mode on, and Dual Core mode On as well.
but they're listed as Off in my ini above..

the only thing that seems to be correct is the Options value.

so is everything junk data except the Options?
and those values should just be ignored, and the real values should be determined by what value Options has..
i'm guessing thats the case...

i believe those options are always on. thats probably whats ment by "forced on"
See less See more
yeah i just noticed that those two values you were talking about are conflicting in binary.

like most values are easy, such as the first three that don't conflict when you add them up...
001, 010, 100

but 0x100 is 1100100

and when you add that up, it conflicts with "Frame Limit On" which is 100

i'm hoping refraction messed up when he listed the value of 0x100 or else its going to be a big pain :/
i'm not sure, but it think its useless data
i have..

the only thing i think is important there is Hacks, which you already did.
i'm a bit curious what "patch" means, since i have it set to 1
my values were weird because i was copying them straight from the ini file.
not with your program, sorry if i confused you.

with your program i get
Patches on = True
-Disable ABS hack = True
-EE/IOP SYNC hack = True
-Tighter Async Timing = False

but is there a way to turn patches off?
i'm guessing this is always on
See less See more
wow, never noticed that lol :lol:
for that to work though, the user would have to crash PCSX2 before running bug reporter.
or else the info it gets might have something to do with some other program.
it might be more trouble than its worth.. but who knows..
i tried the latest version, its looking good
videocard detection is working perfectly
Mkilbride2588, you might wanna change the app priority back to Normal.

running it on high might cause crashes; you probably have been safe so far since you're using a quad-core.
lol, gamersat678's tool saves the day :p

generally you don't want to run a game or something thats going to take along time @ high priority since that tells windows to focus on that instead of some other important background programs/system processes which can lead to crashes..
that not help me for post a error in pcsx2 svn 343 when i play naruto ultimate, how can i see the real problem(bugs and errors caused) that makes pcsx2 reading naruto ultimate ninja on sv 343 with this program?
the bug reporter was made to help us determine if the problems people have are do to inproper PCSX2 settings/user error.
Lots of times people report bugs, and then they don't even have the latest plugins, or they have speed-hacks on, which can cause some problems.

to see the real problems, you'll have to debug PCSX2. but leave that to the developers, because its likely you won't know what you're doing. :p
1 - 15 of 139 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.