Is Pj64 fast enough?
- Thread starter zilmar
- Start date
squall_leonhart
The Great Gunblade Wielder
...does it copy the framebuffer to system memory or Vram? it would be faster if it was to Vram as vram is actually a propery framebuffer...
MIDIman403
New member
Speed and additions
Speed is fine on my laptop.
I think the emulator is great but could use a new interface. I think the interface should be similar to that of WMP 11. I'd also like to be able to double output to a tv and put player one on, say the laptop, and player two on the tv. That would be great. Then, 007 would be better to play without seeing the other person's screen. (That might be difficult, but hey, that would be cool to be able to do.)
Speed is fine on my laptop.
I think the emulator is great but could use a new interface. I think the interface should be similar to that of WMP 11. I'd also like to be able to double output to a tv and put player one on, say the laptop, and player two on the tv. That would be great. Then, 007 would be better to play without seeing the other person's screen. (That might be difficult, but hey, that would be cool to be able to do.)
Agozer
16-bit Corpse | Moderator
I would have to agree. Thre's nothing really flawed about the current look of the Rom Browser; at least that's what I think.NaSeR said:I think that he wants Project64 to use the xp style interface because looks good, but personally: I don´t spend time seeing the interface, but the games itselfsmoreover it will increase the minimun specs.
Iconoclast
New member
I don't have any experience with crashes in Project64 compared to 1964. Just about every frickin' game (though very rarely).
As for speed, I think it should just all be evened out. I mean, I'm just saying the way I think this works. I think it's more like, the more game support is implemented into Project64, the more decrease in general speed. Maybe take some speed out of the relatively fast games and put a little of it in some slower but fairly popular games. That's basic, but about all I can say. I don't know much about how speed works.
Oh, but there is this. Sometimes, when I exit Project64 without directly closing the ROM first, I get a Dr. Watson's error message, Project64.exe has encountered a problem and needs to close. We are sorry for the inconvinience. I've never heard of that happening to anyone else, so I think it's the registry, as when I first installed Project64, it was unable to write to some parts of the registry (since I have a limited account...I hate Windows XP for that).
But for those who do get crashes in Project64, speed isn't as important as the prevention of crashes in the games, unless a major sacrifice of speed is involved. But there are PCs out there that can emulate at high speed to counter games with slow speed, but not control the likeliness of a game crash. So I would have to say the prevention of crashes is a fair deal more important.
As for speed, I think it should just all be evened out. I mean, I'm just saying the way I think this works. I think it's more like, the more game support is implemented into Project64, the more decrease in general speed. Maybe take some speed out of the relatively fast games and put a little of it in some slower but fairly popular games. That's basic, but about all I can say. I don't know much about how speed works.
Oh, but there is this. Sometimes, when I exit Project64 without directly closing the ROM first, I get a Dr. Watson's error message, Project64.exe has encountered a problem and needs to close. We are sorry for the inconvinience. I've never heard of that happening to anyone else, so I think it's the registry, as when I first installed Project64, it was unable to write to some parts of the registry (since I have a limited account...I hate Windows XP for that).
But for those who do get crashes in Project64, speed isn't as important as the prevention of crashes in the games, unless a major sacrifice of speed is involved. But there are PCs out there that can emulate at high speed to counter games with slow speed, but not control the likeliness of a game crash. So I would have to say the prevention of crashes is a fair deal more important.
squall_leonhart
The Great Gunblade Wielder
MIDIman403 said:
NOT EVEN POSSIBLE~!
I find it to be like this... Project64 is awesome but, there's always the cutoff line between fast and slow. Now I run on a high end computer that can handle games like Counter Strike and World of Warcraft much too easily but, PJ64 is much different as all other emulators. In PJ64 the problem that I face is simply this... I can have it run on a limited FPS and it'll run but, if I put, settings towards quality then it'll glitch up and if I make it so that there is no limited FPS then it'll go mad fast but, there's no post in between where it'll stay at one FPS without fluxuating...
the master 123
New member
Speed in generally on my computer is good(even with a a intel extreme graphic) but I can't get some games to work well. I have only 1 real problem and that is pj64 crashes when I take a screenshot in full screen mode.
Counter Strike and Warcraft are games designed to work natively with your hardware. Emulators must convert code into native hardware code. This sort of overhead is what makes emulators slower than games that run natively. It's apples and oranges.
The method of separating out graphics, sound and/or CPU time into different threads would not necessarily run the emulator any faster, since it has to sync all the chips properly and output the results into a single thread... current dual-core architecture does not support independent synchronization of that type. If anything, it would make emulation slower.
PJ64 Satisfaction Rating: 100%
I started using this program about four years ago and have never had any problems. Everyone seems to think crashing is a problem but it is extremely rare for me. The only thing I have trouble with is the flicker in some games but I think if I really applied myself I'd be able to get around that too. I've got a HUGE romset and I'd say a 90%+ compatability. Kudos to you Jabo, great job and keep up the good work. (happy b-day btw. Real life can really be a hinderance to other pursuits, i'm 25 myself.)
Dude Mann
PS - Jnes is awesome, too! Here's to classic gaming!
I started using this program about four years ago and have never had any problems. Everyone seems to think crashing is a problem but it is extremely rare for me. The only thing I have trouble with is the flicker in some games but I think if I really applied myself I'd be able to get around that too. I've got a HUGE romset and I'd say a 90%+ compatability. Kudos to you Jabo, great job and keep up the good work. (happy b-day btw. Real life can really be a hinderance to other pursuits, i'm 25 myself.)
Dude Mann
PS - Jnes is awesome, too! Here's to classic gaming!
Samurai Snack
PJ64 Cheat Master
I use Jabo'sDirect3D8, Jabo'sSoundPlugin, N-Rage controller plugin and PJ64 Version-1.6 and PJ64 isnt that slow, a few crash problems on Gauntlet:Legends and interface glitches on California Speed but other than that, not bad.
EDIT: Why would you have 5 games going at the same time anyways?
EDIT: Why would you have 5 games going at the same time anyways?
Iconoclast
New member
Gauntlet Legends was just programmed that way. The core emulator and graphics plugin are to blame. The only emulator to run Gauntlet Legends at, like, five times as fast as PJ64 is the 1964 emulator, at least on my system.
To be on topic, this user is suggesting that emulator speed should be sacrificed for extra game support because he claims that it is already extremely fast. This applies only to his system specifications, not mine and not yours. Just because he has a very fast PC for emulation doesn't mean all of us will be unaffected by Project64's sacrifice of emulation speed in the next version, so his emulation experiences prove insufficient reasoning to slow down the emulator a little for all of us.
Anyway, I don't remember if I've ever said this before, but I think it would be pointless to try and make Project64 faster by sacrificing any amount of game support or preferring speed over game support, because that would be competing with the 1964 emulator's major advantage: Speed. There should be more focus on improving what Project64 is already good at, not competing with the strongpoints of other emulators. Besides, the problem of slow emulators can always be fixed by upgrading your system specifications, but the problem of game support can only be fixed by the emulator author and sometimes sacrificing speed. The answer should be obvious.