Project64 1.6 Released!

[Nathanew]

Yes, I had to reload a savestate and rebegin where I left. It's frustrating time to time

 

[Viper_Viper]

I havent had any probelms yet with 1.6 (yay!)

 

[jeffkong]

Does Project64 improve the N64 frame rate, or is the frame rate exactly the same as the N64s?

is there a way to improve it?

I've been wondering this for a while, I see frame rate drops but I don't know if it's just my computer.

 

[Clements]

The frame rate is the same as the real N64 with no way to alter it without slowing or speeding up the game.

 

[RadeonUser]

Well an N64 game is usually set to either run at 60 fields per second or 50 fields per second. PJ64 is faster than the N64 in the sense that it tries to closely follow that number. On the N64 it rarely holds steadily at that fps due to its hardware limitations.

Setting "Sync Game to Audio" on Jabo's audio plugin (or anyone else's audio plugin who has a similar feature) will attempt to close in on the N64's fps based on the audio but it cannot / does not meet the N64's speed.

In a nutshell with a fast enough system (cpu and graphics) N64 emulation is always faster than the native console.

 

[Helicobacter]

I've tested only 3 Games and with Mario Tennis I get a FPS-Rate of about 30-33. With Jabo's older PlugIn i got 59-60 FPS. And I have the bad feeling it isn't the only game. Seems no perfect Grafics-PlugIn will ever be possible. With every new release some Games get better and some worsen.

My suggestion would be a new feature: Automatic Dynamic Configuration Adjustement, which sets automatically the optimal settings while loading a specific ROM and sets the configuration back to default, if a unknown/flawless ROM is loaded.
The problem is I'm not a programme,r so I can't establish such e new feature.

Are the changes of Service Pack 1 already included in Project 64 1.6?

 

[Clements]

Jabo's D3D8 is more picky about hardware, for me Mario Tennis works much better with D3D8 than D3D6 despite the obvious resolution problems in the menus.

As the last question, Project64 1.6 contains all the stuff that effectively was in SP1, as well as all my changes I made after SP1, and also has a lot of cool extra stuff on top from Gent and the team which include updated cheats, documentation, RDB updates and such.

 

[RadeonUser]

I've tested only 3 Games and with Mario Tennis I get a FPS-Rate of about 30-33. With Jabo's older PlugIn i got 59-60 FPS. And I have the bad feeling it isn't the only game. Seems no perfect Grafics-PlugIn will ever be possible. With every new release some Games get better and some worsen.

My suggestion would be a new feature: Automatic Dynamic Configuration Adjustement, which sets automatically the optimal settings while loading a specific ROM and sets the configuration back to default, if a unknown/flawless ROM is loaded.
The problem is I'm not a programme,r so I can't establish such e new feature.

Are the changes of Service Pack 1 already included in Project 64 1.6?

Well yes everything was built atop of the 1.5 plugins and core. The documents, rdb, cheats, etc... were updated as well to reflect the changes done to PJ64 as a whole.

The D3D8 plugin is more intense video memory and feature wise so there *may* be slowdowns that were previously not there before. That's why the D3D6 plugin is still included, there may be instances where the D3D6 plugin is better at handling things on older hardware.

And there's already a feature like that in... It's the rdb and special optimizations for certain cards in Jabo's graphics plugin. Sadly a complete auto detection type deal for Jabo's graphics plugin will never happen due to the robust amount of video cards and driver combinations out there.

The rdb cannot be set to "auto" since there is no 'intelligent' cpu core method that can be adjusted on the fly. Programming wise I would imagine this would be a complete nightmare and would come down to working with each game to achieve the wanted result.

Any experienced devs do chime in as I havent been overly active in emulation scene in the past 2+ years or so... I could be wrong and am spewing crud for all i know

 

[RadeonUser]

Jabo's D3D8 is more picky about hardware, for me Mario Tennis works much better with D3D8 than D3D6 despite the obvious resolution problems in the menus.

As the last question, Project64 1.6 contains all the stuff that effectively was in SP1, as well as all my changes I made after SP1, and also has a lot of cool extra stuff on top from Gent and the team which include updated cheats, documentation, RDB updates and such.

Uhm... care to tell me what changes were added that were yours? The rdb was changed from the 1.5 SP1 and Gent did most (if not all) of the cheat support and other documentation with help from Pixii, Trotterwatch, and the rare chime-in from me (very rare chime-ins the last weeks too....)

I'd check with the rest of the team right now but they're either working or asleep right now... lain:

 

[Gent]

Uhm... care to tell me what changes were added that were yours? The rdb was changed from the 1.5 SP1 and Gent did most (if not all) of the cheat support and other documentation with help from Pixii, Trotterwatch, and the rare chime-in from me (very rare chime-ins the last weeks too....)

I'd check with the rest of the team right now but they're either working or asleep right now... lain:

I did actually follow the unofficial RDB thread and adjusted some that made sense, mainly i liked some of the GFAQ changes but most of them were fixed with d3d8, all the new entries and Name changes i actually gave Clements under the nick of Chris_W as i was at work most of the time while following that. The major over haul was the naming in the RDB because of constant chats with cowering we started to look at the amount of (M) Multi-lang roms there were and changed accordingly. The result is what you now see in the RDB and no doubt when the new GoodN64 comes out. Now on the Newer Jap RDB i have a few problems with such as Roms that are not releases but placed in there. These Guys Dumped them themselves and do not intend to release or let Cowering check them. So in effect there's no way of checking and will never go in Goodn64 which in respects means they should never be in a PJ64 RDB as they are not known and rendered as a Bad Rom.

 

[Smiff]

Helicobacter you don't post your system specs so i'll guess you have an older graphics card. i'm always amazed how little gets broken for the amount of HLE going on in the video..

Gent i'll be in to try to talk about some of this later.. i sorta wish you'd made a detailed change log for the RDB but i understand why you didn't..

 

[ScottJC]

Perfect Dark is awesome, can only really enjoy it now emulated because of my recent upgrades.

 

[Clements]

I did actually follow the unofficial RDB thread and adjusted some that made sense, mainly i liked some of the GFAQ changes but most of them were fixed with d3d8, all the new entries and Name changes i actually gave Clements under the nick of Chris_W as i was at work most of the time while following that. The major over haul was the naming in the RDB because of constant chats with cowering we started to look at the amount of (M) Multi-lang roms there were and changed accordingly. The result is what you now see in the RDB and no doubt when the new GoodN64 comes out.

Yeah, I had no idea that 1.6 was on the way, I thought it was discontinued, so I thought it needed an update since it appeared no one else was doing it, and Smiff was having a break . Little did I know that behind the scenes all my RDB name updates had already been done and then some. I'm glad some of my GameFAQ ideas made it in though, now it looks much better.

 

[RadeonUser]

Yeah, I had no idea that 1.6 was on the way, I thought it was discontinued, so I thought it needed an update since it appeared no one else was doing it, and Smiff was having a break . Little did I know that behind the scenes all my RDB name updates had already been done and then some. I'm glad some of my GameFAQ ideas made it in though, now it looks much better.

Ah so thats where those came from, ok :blush: I knew Gent was working with cowering at one point but Gent tends to follow the whole cloak and dagger routine when it comes to these things :whistling

 

[DeVoN`]

good job! this version is very cool ^^

 

[Heimidal]

PJ64 1.6 crash

I've only had this happen with Castlevania (U) V1.2 so far...

Randomly I get a crash usually after 5 minutes or so with the following error:

SP DMA Write
SP_DRAM_ADDR_REG not in RDRam space

Then I close this window and I get the error:

Unhandled R4300i opcode at 80000550
bltzall t1, cx8000643C

I'm running XP SP2 with a Radeon 9800 PRO

This happens with every graphic plugin I've tried (all Jabo's, Glide64, and so on)

I've played F-zero and Mario Kart with no problems with the current setup...

This also happens when I have everything unchecked under the RDB configuration menu..

any ideas??

 

[Allnatural]

I've only had this happen with Castlevania (U) V1.2

I don't see a [!] in the filename. Could be a bad rom. Besides that, things like:

-overuse of cheats
-overuse of savestates
-incorrect self-modifying code (not usually this one, but worth checking if nothing else works)


While I'm on Castlevania, I noticed a plugin note for V1.2, [video] primary_framebuffer:menus, but not V1.0. Does the problem actually effect just the one version, or was that a line tagged for removal (and missed)? I can't be arsed to check myself.

 

[ScottJC]

Chameleon Twist (U)'s notes say it requires the rumble pak, not true any more. works perfectly fine without it.

 

[Smiff]

thanks ScottJC.. that's exactly the kind of info i want right now.. you've posted a lot of good stuff actually (where's the beer smiley).

edit: actually no i think you might be wrong this time, i think nothing has changed 1.5>1.6 here. but what the comment should have read in the first place was "controller pack must NOT be seen" or something similar. can you double check this please?

 

[ScottJC]

No Problemo! :beer: