Project64 (v2.1.0.1)(Beta)(Bug-Reporting)

[Melchior]

This thread is where I will post any bugs or Crashes I may encounter.


I had the new Glide64 (v2.0.0.1) plugin highlighted in the main settings drop-down menu
Options-->Settings-->Plugins
crash occurred when I went clicked on the "about" button before I had clicked apply button. O_o
also I believe one or two of the other plugin selections were empty do to renaming plugins to include there version info.

The other crash occurred on exit of ROM [was testing the new Glide64 plugin w/ the flickering issue on Star Wars - Shadows of the Empire (U)(v1.2)] or maybe it was just after that when I went to exit PJ64 all-together....


I have attached all the files I have include the windows crash reports...

Zilmar does PJ64 include Debugging-symbols? and if so what format...
ie. WinGW gdb ^_^
I have MinGW v4.7.2 installed ^_^ so I can compile C and C++ ^_^

I am out of Library Net time (1.5 hrs) so I'll finish my statement tomorrow

[squall_leonhart]

i see you have windows xp with tortoisesvn installed

this might be a source of problems because windows xp is not as good at handling dll injection as later operating systems.

realistically, we want the dmp files generated from the crash instead of the dr watson logs as then we can run them through windbg

[Melchior]

could a mod please move battlelord60's post into its own thread as its off from what I am posting, ie. This thread is a single place for me to post bugs I encounter for this specific version.
thx
____________________________________________

Originally Posted by squall_leonhart

i see you have windows xp with tortoisesvn installed

this might be a source of problems because windows xp is not as good at handling dll injection as later operating systems.

realistically, we want the dmp files generated from the crash instead of the dr watson logs as then we can run them through windbg

I was only able to upload 5 files for the 1st post plus from the library PC I had run out of time too so I couldn't finish my post.

I attached the dump files Dr.Watson created the other day.

[twostars]

Originally Posted by Melchior

I had the new Glide64 (v2.0.0.1) plugin highlighted in the main settings drop-down menu
Options-->Settings-->Plugins
crash occurred when I went clicked on the "about" button before I had clicked apply button. O_o

This one's caused because Glide64 attempts to read from the settings (for translation) before showing the about box, however the plugin's not *really* initialised here, as it's loading the plugin on-demand, so Glide64's unable to access the settings, and therefore crashes.

Edit:
These 3 commits should fix it.

github.com/twostars/project64/commit/bf4c108ce2734ed72c787370f5abb4155418c447
Ties plugins in a little better, removes a lot of redundant code (builds base for this fix).

github.com/twostars/project64/commit/ec3b329908f77389b0138355a2f4a35e28bcb766
Addresses this particular issue by replacing on-demand plugin loading with a wrapper which will call the existing, appropriate plugin class so as to ensure it's consistent with the plugin's expectations of what has been initialised (in this case, settings -- little bit overkill, but it's hardly performance-critical code).

github.com/twostars/project64/commit/c07208a9d2ae9edbc2ba204160402fb9eeba6fd9
Updates the VS2008 project files (I use VS2010, so figured I'd better update it too).

[squall_leonhart]

I don't see any reason for the Jabo crash, it could be bad sound drivers though.

[Melchior]

Originally Posted by squall_leonhart

I don't see any reason for the Jabo crash, it could be bad sound drivers though.

My Motherboard is a ASUS P5NSLI (v2)(bios-r1801) its old stuff, 2007 Mobo w/ its integrated SoundMAX
CPU-Z Report

My drivers are as up to date as they will ever be. updates are my specialty ^_^

[squall_leonhart]

try setting

[Dsound]
Autobuffer=0
SoftwareBuffer=1
AdditionalBuffer=0
Volume=100

in project64.cfg

[Melchior]

Originally Posted by squall_leonhart

try setting

[Dsound]
Autobuffer=0
SoftwareBuffer=1
AdditionalBuffer=0
Volume=100

in project64.cfg

ok I'll try it when I get home...

[Nekokabu]

bug report here? ok?

1."Pause emulation when window is not active?" option
disable this option in emulation, emulation is pause state.

2.Savestate
a)When save a state with a name, Full path is included in Zip file.
b)If you press the F5 key shortly thereafter, it is saved in the file that you specified earlier.
Toggle window forcas, It is in the correct file name.

[Melchior]

Originally Posted by Nekokabu

bug report here? ok?

1."Pause emulation when window is not active?" option
disable this option in emulation, emulation is pause state.

2.Savestate
a)When save a state with a name, Full path is included in Zip file.
b)If you press the F5 key shortly thereafter, it is saved in the file that you specified earlier.
Toggle window focus, It is in the correct file name.

This Thread is for me to report my current bugs I come across in PJ64 (v2.1.0.1) or maybe one thread for each bug... you should take your post and create your own thread and ask a Moderator to delete your post on my thread. thx.