Project64 2.2

[shinra358]

Works very well. Especially with gliden64.

[RPGMaster]

Originally Posted by ferlanga

How does 2.2 perform compared to 2.1?
I recall 2.1 fixing some graphical issues but at the same time lowering the framerate on some games (fighter's destiny 2 being an example) to the point where I just kept using 1.6

The main difference in 2.2 compared to 2.1, is default settings + rdb changes. 2.1 itself is still good and generally better than 1.6. All you had to do was change settings...

Of course there are some fixes in 2.2 though.

[JPMC]

When I make a save state on PJ64 2.2, and go into the .zip, my OS C: is in the zip file, and there is no usual .pj file in there, also, there is another issue but it was problably my graphics plugin, the game never started and PJ64 froze, I switched to the best plugin out there, Glide64 and it worked. Jabo really sucks actually because many problems has been detected by me. Hopefully this can be fixed in the next publication of PJ64. Thanks!

[Tasoulis]

So far i don't see any any differences with version 2.1

The games that i had problems with are still broken. Pilotwings crashes with a weird box-like texture just like in version 2.1 (you can see this at the end of the first stage demo as it always happens there).

So, even after all these versions, i still have to keep version 1.6 for some games

[Frank74]

Originally Posted by Tasoulis

So far i don't see any any differences with version 2.1

The games that i had problems with are still broken. Pilotwings crashes with a weird box-like texture just like in version 2.1 (you can see this at the end of the first stage demo as it always happens there).

So, even after all these versions, i still have to keep version 1.6 for some games

Pilot Wings crash is caused by cheat fix in RDB (shadow fix). Cheat is enabled for Jabo and Glide plugins.
You need to uncheck Use TLB and Advanced Block Linking when the cheat fix is used.

Does anyone know if GlideN64 works ok?

[Tasoulis]

Originally Posted by Frank74

Pilot Wings crash is caused by cheat fix in RDB (shadow fix). Cheat is enabled for Jabo and Glide plugins.
You need to uncheck Use TLB and Advanced Block Linking when the cheat fix is used.

Thanks, i wasn't aware of this.

Originally Posted by Frank74

Does anyone know if GlideN64 works ok?

Tested a few early N64 games and so far it works OK with 2.2 version. Pilotwings has the shadow glitch though (needs a new cheat fix?)

[Frank74]

You could try adding ",GLideN64" to the RDB cheat plugin setting.

CheatPlugin0=Jabo's Direct3D8,Glide64 For PJ64,GLideN64

I can't use GLideN64, don't have OpenGL 4 support.

[Predator82]

Haven´t OpenGL 4.0 too & most works fine
only some things didn´t work right without 4.0 for example the Extreme-G-logo (experimental n64 depth needs 4.0)

[Ambient_Malice]

I was under the impression that Gonetz was supposed to be fixing the shadows in Pilot Wings. Hasn't happened yet, though, apparently.

Did fix the shadows in Turok 3, though, which is nice.

[Tasoulis]

After about 2-3 hours testing games and saving different plugins and settings for each one, the emulator decided to revert everything at default settings for whatever reason after i started it today...

Is there any way to get my settings back? Or do i have to start over? And how can i make it sure that the emulator won't screw me over again?

Edit: i guess backing up Project 64.cfg somewhere should be sufficient.