|
#71
|
||||
|
||||
![]()
Nope, happened on your's too. Okay.
__________________
My rig: CPU: Intel Core i7 4470 3.4 GHz to 3.9 GHz Video card:: MSI nVidia GTX 970 4 GB GDDR5 OS: Windows 7 Professional 64-bit RAM: 16 GB DDR3 SDRAM 10600 HDD: 2 x Western Digital 1 TB HDDs Monitor: 23" Asus Full HD LED Oh, and Snes9x > Zsnes in every way |
#72
|
||||
|
||||
![]()
Well, if it happened on both mine and zilmar's RSP interpreters I think it's safe to say it almost certainly can't be an RSP-related bug, but, you're welcome to help me test a saved state to help me find where in the game it happens or whatever if you have any disagreement.
__________________
http://theoatmeal.com/comics/cat_vs_internet |
#73
|
||||
|
||||
![]() Quote:
__________________
My rig: CPU: Intel Core i7 4470 3.4 GHz to 3.9 GHz Video card:: MSI nVidia GTX 970 4 GB GDDR5 OS: Windows 7 Professional 64-bit RAM: 16 GB DDR3 SDRAM 10600 HDD: 2 x Western Digital 1 TB HDDs Monitor: 23" Asus Full HD LED Oh, and Snes9x > Zsnes in every way |
#74
|
||||
|
||||
![]()
I would most like it if people could test weird N64 ROMs, usually ones with special gfx microcodes most HLE gfx plugins don't support, things most likely to raise "error" messages in my RSP plugin so that I can comment their support more informatively.
I just tested Mario no Photopie actually. Before I had to use Project64 RSP 1.7.0.9 to get any gfx to show. Now that I support SP semaphore correctly using zilmar's new semaphore handler in PJ64 2.0, however, my RSP plugin sends the correct data.... ![]() ![]() First case I have ever seen of the semaphore mfc0 rewrites making a difference in emulation support.
__________________
http://theoatmeal.com/comics/cat_vs_internet |
#75
|
||||
|
||||
![]() Quote:
So essentially games from companies like Factor 5 or Rare that used unorthodox microcode? And also to report messages that pop up during the ROM boot execution?
__________________
My rig: CPU: Intel Core i7 4470 3.4 GHz to 3.9 GHz Video card:: MSI nVidia GTX 970 4 GB GDDR5 OS: Windows 7 Professional 64-bit RAM: 16 GB DDR3 SDRAM 10600 HDD: 2 x Western Digital 1 TB HDDs Monitor: 23" Asus Full HD LED Oh, and Snes9x > Zsnes in every way Last edited by the_randomizer; 17th April 2013 at 05:20 AM. |
#76
|
||||
|
||||
![]()
Definitely! Any message boxes from my dll, very good to know
Factor 5, Rareware, Boss Game Studios, ... a few other games using unique gfx. I made a list a very long time ago; I don't remember. Also games using special tasks like JPEG decoding (PKMN Stadium 1/2), HVQM video decompression (PKMN Puzzle League), other task types or stuff in Resident Evil 2, but that's not the best guideline to give you folks since you can never know just by playing a game whether it does customized tasks, just if video plugin supports it.... I'm going to download Neon64 homebrew image since angrylion said that was one of the ROMs entering a permanent loop caused by SP status signal semaphores. Any weird ROMs people can think of... go ahead.
__________________
http://theoatmeal.com/comics/cat_vs_internet |
#77
|
||||
|
||||
![]()
Question:
How to test Gauntlet Legends with Project64 2.0 + LLE RSP? I still can't let this game run will LLE RSP. |
#78
|
||||
|
||||
![]()
You will have to use rsp_pj64.dll, not rsp.dll.
rsp_pj64.dll is the base RSP plugin with the following macros defined: Code:
#define SEMAPHORE_LOCK_CORRECTIONS // Recommended only for CPUs supporting it #define WAIT_FOR_CPU_HOST // Never use, except with some ROMs on Project64 2.
__________________
http://theoatmeal.com/comics/cat_vs_internet |
#79
|
||||
|
||||
![]() Quote:
Search Youtube with "Mario no Photopie on Project64 1.6.1" then you can find this video. |
#80
|
||||
|
||||
![]()
The challenge was getting it to work with LLE gfx.
Getting it to work on HLE gfx plugins is easy.
__________________
http://theoatmeal.com/comics/cat_vs_internet |