|
#1
|
|||
|
|||
![]()
Upgrade current alpha to allow beta users access.
conatins: |
#2
|
|||
|
|||
![]()
Great! Finally support for per rom settings
![]()
__________________
PC: Asus P8Z68-V PRO | Intel Core i5-2500 3.3 GHz | Kingston HyperX Genesis DDR3 8GB 1600MHz | Asus ENGTX570 DirectCU II Consoles: Nintendo 64 | Nintendo GameCube | Nintendo Nintendo Wii | Microsoft Xbox 360 |
#3
|
||||
|
||||
![]()
Haven't seen this kind of thing before but with these versions Gauntlet Legends starts up fine with the re-compiler but not the interpreter.
|
#4
|
|||
|
|||
![]()
Interpter of the r4k or the RSP .. with the RSP it goes in a perm loop waiting for a response from r4k engine which it will not get since it is not multithreaded.
|
#5
|
||||
|
||||
![]()
oh right sorry, the r4k interpreter I meant.
Now, the RSP interpreter works just fine with Gauntlet Legends. Actually I've been having it on while completing a game save using the beta version but using the RSP re-compiler on the 1.6 version. Only issue is if I start the game using the RSP interpreter on 1.7 but then switch to the re-compiler, there is an endless streak of errors similar to this. ![]() The [r4k] interpreter, though, is what I meant from before. Project64 1.6 starts Gauntlet Legends with the r4k interpreter or the re-compiler, but I've never succeeded in getting the r4k interpreter to initialize the game on the recent alpha. I haven't checked this on all the legacy beta versions. |
#6
|
|||
|
|||
![]()
What is the purpose behind the the V/I refresh rate setting? Its default is 1500.
The changelog refers to here: http://forum.pj64-emu.com/showpost.p...7&postcount=18 But the link does not work (access denied - alpha testing forum?). |
#7
|
||||
|
||||
![]()
Love the settings UI.....
|
#8
|
||||
|
||||
![]()
Yeah I guess. Great emulator btw. =P
Hard for me to comment on style and stuff, when it comes to software or design. My idea is to develop in such a way that there is minimal interface needed to apply stylistic measure to, in order to keep neutral or professional. |
#9
|
|||
|
|||
![]()
Well, at least we know the emulator is still being worked on. Maybe in two years we can have a public 1.7 build
![]() |
#10
|
||||
|
||||
![]()
Of course we know the emulator is being worked on, it's been announced like a thousand times :P
|