Next Generation Emulation banner
1 - 20 of 139 Posts

· Registered
Joined
·
496 Posts
Discussion Starter · #1 · (Edited)
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.
 

· You're already dead...
Joined
·
10,293 Posts
what information does it record?
stuff from the console?

edit:
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]
Cpu=0
Vurec=0
Regcache=0
SafeCnts=0
InterlaceHack=0
SPU2Hack=0
Multithreading=0
GSMulti=0
Options=1267
[Misc]
Patch=1
PadHack=0
varLog=0
Hacks=7
i have multithreading on, but it says its = 0
is that correct?
and Hacks = 7?
whats that mean.
 

· You're already dead...
Joined
·
10,293 Posts
oh yeah, just opened up the ini and its the same thing :p
 

· PCSX2 Coder
Joined
·
11,343 Posts
and Hacks = 7?
that means youve ticked every single hack.

can you add the first chunk of the emulog to it as well? bit with specs and everything, makes it easier.

but any n00b who doesnt know what hes doing is unlikely to use your little program ;p

what would be even better, is if you could translate the options etc. that was you dont need a dev around to work out what options they have ticked etc.
 

· The Pest
Joined
·
1,854 Posts
Wow, great program, I just tried it out and I'd even go as far to say this could revolutionize the forum system here for PCSX2, maybe even INCLUDE it in the next PCSX2 release and mention it in the Readme, and people can just post it here...it'd simplify alot of things.
 

· You're already dead...
Joined
·
10,293 Posts
but we do need simplified options.
only the devs are going to know what most of the stuff means.

something like
Multithreading=0

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.
 

· PCSX2 Coder
Joined
·
11,343 Posts
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.
correct :)
001 = Disable ABS hack
010 = EE/IOP SYNC hack
100 = Tighter Async Timing
 

· You're already dead...
Joined
·
10,293 Posts
and i owe it all to my CS professors for forcing me to learn binary :p
 

· You're already dead...
Joined
·
10,293 Posts
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...
gsInit
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
CPU Speed
Graphics Card (It would be nice if it can detect graphics card)
Plugins
MTGS
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.
 

· The Pest
Joined
·
1,854 Posts
Keep up the great work - if only every noob who came to these forums used this, life would be easier :p
 

· PCSX2 Coder
Joined
·
11,343 Posts
most of the stuff in the ini is unimportant, but itd be cool if you could expand "Options=" as this is there cpu options. this is what the numbers are in hex (they are stored in the ini as a decimal)

MTGS = 0x1
Dual Core Mode = 0x2
Frame Limit On = 0x4
EERec = 0x10
VU0Rec = 0x20
VU1Rec = 0x40
COP2Rec (forced on, not needed) = 0x80
ForceABS (forced on, not needed) = 0x100

Frame Limit modes in Options:
Normal = 0x000
Limit = 0x400
Frameskip = 0x800
VUSkip = 0xc00

so for example, mine says Options = 147 which is 0x93 in hex, which shows i have

EERec Enabled
COP2Rec Enabled (but we dont need this info)
MTGS On
Dual Core Mode On

or another example 112 (which is 0x70 in hex) shows i have:

EERec Enabled
VU0Rec Enabled
VU1Rec Enabled
 
1 - 20 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.
Top