What's new

feedback for v1.5 final release

ShadowFX

Guardian
Sometimes, when I try to reset (F1) after the emulator was heavy under preasure in emulating KI Gold, most of time PJ64 will crash (not always though).
 
EMu-LoRd said:
Sometimes, when I try to reset (F1) after the emulator was heavy under preasure in emulating KI Gold, most of time PJ64 will crash (not always though).
Yeah I know...:) Please be patient:)
 

Athabaska

New member
Hi everyone there! (this is my third message in just a few minutes...) :bunny:

Well, it seems that the FAILED TO ALLOCATE MEMORY error still happens in my system despite the compatibility modes are turned on or off. Why is that? Do I need to free the RAM or is it a common bug?

Thanks to everyone.

A reveure!!! ;)

[UPS!!! :sleepy: My system...

- Pentium 4 1.6 Ghz
- 384 MB RAM
- GeForce 2 MX 400 32 MB with nVidia WHQL 29.42 drivers
- Windows XP Home Edition]
 
Last edited:

bositman

New member
Utramaniac:Unfortunately i dont have extreme g...i think that we are talking about different kinds of "pauses".
Can you tell me some other roms where this happens so i can test?
The crash on reset happened to me as well dunno what it is.
Athabaska:This is a very weird error...what can i say? Try deleting pj64 and all registry settings and reinstall it.
 
Last edited:

bositman

New member
Its an option(counter factor) located at options-settings-rom settings and will be available after youve loaded the rom
 
Many,I can't remember now...well a few that are coming to my mind now,Fighting Force 64,Winback...
Test only the games that are not on "protect memory",this is what we're looking for,the pauses that are caused by the 1.5 video plugin.
 

crhylove

Banned
amd vs. intel....

just for the record i posted price as part of the comparison, this allows amd to completely obliterate intel. but yeah, there are some p4 advantages. :)

/me is typing this in 16 colors until the new box gets here (long story), man is it ugly compared to my geforce3ti200!!

/speculation: my best guess as to the unreleased source of pj 1.5 is out of respect for azimer/others? and their inclusion of banjo tooie decryption. but given the current community i doubt any of the emulators have seen their last official version, cept maybe uhle, and i imagine it will have more unofficial versions in the future.

anyway, man pj 1.5 really does rock. back to my good box for a bit.....

rhy
 

jvolel

Destoryer of worlds
ack banjo tooie randomly crashes!!! damn if i knew that was going to happen i would of saved!! aaaaaaaaahhhhhhhhhhh crap!!
 

Boooooommm

The Wanderer
Jabo's 1.5 has only caused me problems.... not to mention that it doesn't show some effects right on Zelda MM (the mask change effect with the blue background isn't displayed right). Jabo's 1.5 is unstable, and I really didn't notice such a big speed improvement on PJ64.... Anyway, I hope these problems get fixed ;)
 

KyleKatarn

New member
Yeah PJ64 rocks :D
ALl games pretty much run flawlessly or thereabouts
My friend has pentium 4 1.8ghz 128mb ram and radeon ve.. rofl and thats a dell or heeltt packard crap deal.. rofl..
anyway he gets the access violation error EVERY time he tries to l oad banjo tooie.. heheh must be that radeon VE ..such a cursed thing, not to mention crap..
SO i take it people with radeons gotta run compatibility mode.. any reason why thats so.. Just curious :D
 

LD.

*poke*
64ultramaniac said:
LD. said:
Anyhoo, I get an unhandled opcode with Banjo-Tooie. The crash out happens just after completing the Ordnance Storage mission thing (the first-person dynamite diffusion thing) in Glitter Gulch Mine. Apart from that, I've had no real problems with the emulator so far. Lovely work :)
I have to ask you: Is this with the default rdb settings and it's a good rom?If the answer is yes to both questions then try to set a higher self-mod. code method. (I think by default is on check memory advance)

The ROM is Banjo-Tooie (U) [!], all settings are default.

I tried running it on Protect Memory, and with Advanced Block Linking off, but I still get an unhandled opcode.

The most annoying thing is that I jabbed F5 while I was fiddling, overwriting my previous state. So now I've got a save state that crashes out after a second or so with an unhandled opcode, and an EEPROM that sends me back to the start of the game (silly me didn't use native saves enough).

Which sucks.
 

crhylove

Banned
the new jabo plug...

totally rocks for me. i must admit though, that it doesn't play dr. mario still... :)

i'm just ecstatic that jabo is still coding.

we should start a paypal campaign to get him and rice together for a week. :) (airfare, etc.).

then all your base are belong to us.

rhy
 

Top