Project64 1.6 Released!

[Clements]

I'm sure it would be put to great use

 

[seam]

ive noticed in some games if i have the jabos 1.6 audio set to "sync" it locks them at a lower framerate. but if i take it off of sync, it goes back to 60fps, but of course the audio pops. I tested like 30 or so roms, these are the ones i had this problem in. they are all USA roms except for sin and punishment.

castlevania64 57fps
mario party 2 57fps
castlevania legacy of darkness 57fps
pilotwings64 53fps
mario party 1 53fps
quest 53fps
sin and punishment 48fps

i have a 2ghz proc, with an fx 5600, 512 ddr 3200, and im using the newest directx and vid drivers. and the game is set to windowed at 512res, with no extra stuff on. i tried at different resolutions, but it made no difference. so im assuming this is some sort of problem and not a matter of my computer being too slow. can anyone else confirm this???

seam

 

[ChrisRetro]

The best way to run PJ64, is too manually setup a 60hz mode tailored to Your PC, and what it can handle.

Athlon XP's, Athlon 64's, P4's, should be able to handle a multiple of the original N64's Resolution.
For example, 1280x960 60Hz, using Powerstrip to set this mode up. Then make sure V-Sync is always on in your gfx card's control panel. Make sure V-Sync is on in PJ64, and the audio is synched.

For lesser machines, and lesser video cards, 640x480 60hz is the best place to start. 960x720 60hz, is also a good res to play N64 games in.

seam,
I've found on my 6800GT, that there's a few driver sets where V-Sync doesn't seem to work. I remember a few ATI Catalyst sets had a similar problem.
Do you have V-Sync set to Always On, and not Application Preference ?
Try setting "Full Screen Sync" in Jabbo's video plugin, to "Triple Buffer V-Sync".

 

[Poobah]

ive noticed in some games if i have the jabos 1.6 audio set to "sync" it locks them at a lower framerate. but if i take it off of sync, it goes back to 60fps, but of course the audio pops. I tested like 30 or so roms, these are the ones i had this problem in. they are all USA roms except for sin and punishment.

castlevania64 57fps
mario party 2 57fps
castlevania legacy of darkness 57fps
pilotwings64 53fps
mario party 1 53fps
quest 53fps
sin and punishment 48fps

i have a 2ghz proc, with an fx 5600, 512 ddr 3200, and im using the newest directx and vid drivers. and the game is set to windowed at 512res, with no extra stuff on. i tried at different resolutions, but it made no difference. so im assuming this is some sort of problem and not a matter of my computer being too slow. can anyone else confirm this???

seam

Not all N64 games run at exactly 60 FPS. The slightly-lower-than-sixty framerates achieved using 'Sync Game to Audio' are actually the correct ones. The real problem here is that the emulator doesn't let you set up the exact frame-rate limit for each game so a lot of 'em actually end up going too fast. That's why the 'Sync game to Audio' options are always present in audio plugins; it's the most reliable way of getting it running at the correct speed.

 

[ickle_moi]

fantastic work on the new version last time i played an n64 emu i had a geforce 2
with this ATI card and pj64 1.6 ive never seen n64 games run so well
top stuiff and many thanks

 

[Illissius]

I haven't looked at the source, so I have no idea. However, one of the programmers of Audio Overload(a multiplatform music emulator for NSF, SPC, etc) who is also a MAME dev had this to say when he looked at the source of 64th note to add support for USF to the program:

Hmm. I was fearing something like that might be the case. I'll have a look at 64th note, didn't know PJ64 had already been ported to non-Windows systems before...

 

[DK_4gamecube]

It's a dream come true, i had been waiting so long for a major improvement. Especially with what they say about DK64. I think we all owe them a big thank you for their hard work.

Illisius I love your quote. "Work is punishment for failing to procrastinate effectively."

 

[snes]

Pj64 is extreme cool but it's not perfect.Will there be updates in the future or was that a final release?

 

[Illissius]

Illisius I love your quote. "Work is punishment for failing to procrastinate effectively."

Thanks, however it's not actually my invention. Can't remember where I saw it, though, and it's unlikely that was the 'original', either.
It does, however, fairly accurately describe my work ethic

 

[Iriez]

Oh PLEASE.
The whole Xbox "Scene", is a farce. A scene whereby STOLEN MS Xbox SDK is used, along with illegal mod chips and illegally hacked bios code.
The scene is full of whiners and whingers, that just WANT, WANT, WANT, WANT. NEVER give anything back.
One only has to look at the GPL violations going on, and the lack of releasing any source code, only in spits and spats.
The whole Final Burn Alpha source, and ports to finalburnxxx, is a good example of the complete and utter disrespect given to emu authors, and their code. Jan Klaassen, asked for the porters of HIS code to stop adding hacked games, and more modern games. But, as usual, he was told to F - off, and they'll continue to add them, anyway.

Don't release your source code, guys. I love your emulator, and have the utmost respect for you guys. You won't get ANY respect over at the xbox scene forums, only whining from those who THINK you should release it.
All the respect seems to only go to those who "Port" your code, and not the much deserved respect to you guys who've spent YEARS, not WEEKS, coding.

And to Poobah, STOP the whining, for the love of god.
If you really must play N64 games, then use your flippin PC. It's superior to using an Xbox, and you don't have to keep dealing with it's limited specs.

Firstly, I would like to point out that those people who are releasing FBAX builds with added drivers are not only rookies, but they are also thoughtless shitheads. The people that have done work on porting over N64 emulators to the xbox (lantus and oDD) are well respected, and have been more than fair in regards to respect to other authors. If you doubt my word, simply look at the interaction between Rice and lantus. Rice has been incredibly kind in regards to handing out his new source (when its not yet publically availible) and overcoming obstacles from it. This kind of positive environment has progressed the port fantastically (even though the project is in current idle-state).

Most of the emulation developers I think work on their projects from personal motivation, not outside, because they are not paid to do it. When you spend so much time on a project, you should 'expect' respect for your hard work, yes, but should you 'demand' it? That seems quite arrogant to me. The xbox scene is full of twats, yes, but its not like the N64 scene never was The fact is there will always be ignorance users, no matter what 'scene' you go to.

Just so you know, two guys (active emulator devs) have been working dilligently on OpenXDK to get it to a operational state. While 99% of the work done in the xbox scene violates the MS EULA (remember there are official developers that release homebrew too...dont doubt it for a second) there are efforts to get it to a legal state.

 

[mongo51983]

Great release! I was just wondering if all the fixes and stuff are for just the new jabo video plugin or for all video plugins?

 

[ChrisRetro]

Iriez, You're a decent chap, and I certainly don't envy your mod job over at xbox scene.
It seems as if it's an almost daily thing for brainless morons to requst a Dreamcast,Saturn,PS2,GC, emulator etc..
lantus and oDD, are some top people, especially Lantus with his superb Snes9x port to the Xbox.
I agree about Rice, and his kindness, and support to help get his plugin ported. But then one has to wonder what the hell is going on with Surealxxx ? It seems as if, again, a bunch of amateurs have almost raped the PJ64 1.4 source, hacked in Rice's latest source, and screwed the whole thing up.
It's like, "Hey, lets get Conkers going", and thats it. Sod any sort of protocol.

Just so you know, two guys (active emulator devs) have been working dilligently on OpenXDK to get it to a operational state.

I've been watching that, and it looks quite interesting. It will certainly give the whole scene a less 'dodgy' feel to it.

Once again, sorry to the mods to go off-topic. I just wanted a quick reply to Iriez. Last time, I promise

 

[Cönker1]

How about this:

P.S.: In the only game that works

How did you get the screen to show up like that? Like plugins and stuff.

edit: The picture shows 1080 with the big TV screen in the game displaying an image.

 

[CF2]

Just check "copy framebuffer to rdram" in advanced options. 9you have to uncheck hide advanced options)

 

[Trotterwatch]

Just check "copy framebuffer to rdram" in advanced options. 9you have to uncheck hide advanced options)

Shouldn't really need to, it should work with that option off.

 

[Lizking]

PJ64 1.6 is awesome, but Jabos D3D8 could use some work. This might have been stated earlier in the thread, but reading through 25 pages would take a bit too long.
It seems a bit unstable on my system, as sometimes going from windowed to fullscreen will leave me with a black screen that can only be remedied by a hard reset.
also, some stuff seems to be broken that isnt in D3D6, as shown in the attached image.
I really dont like that screenshots are in JPG only now. It would be nice to have a choice between JPG, BMP and PNG.
And I don't know if this is on my system only, but It won't allow me to take screenshots in fullscreen mode

 

[Trotterwatch]

Lizking > what graphics card are you using? I get none of those issues.

 

[Lizking]

a GF4MX 420. Sorry, I thought I had that information in my sig.
I'm using some absolutely archaic drivers (from late 2003), because whenever I try to update them, the Nvidia site dies constantly during the download.

 

[cooliscool]

Obviously your graphics card (lack of pixel shader support). Try using the Legacy Pixel Pipeline.

edit: Yep. MX 420 doesn't support pixel shaders (DX7 generation card) in the slightest, so using the Legacy Pixel Pipeline should fix your issues. It's under the Advanced tab in Jabo's config.

 

[Trotterwatch]

So as I thought, not Jabos issue Try the resolution above which should work.