What's new

slow...slow...slow

Status
Not open for further replies.
M

mann

Guest
you guys want to see weak ass computer try this

Celeron 465 MHZ
8 Mb Open GL intel i810 integrated video card
160mb of Ram
15gb HD Quantam Fireball ATA66

I get 30 friggin fps on zelda oot which sucks!!!
 
Last edited:

Doomulation

?????????????????????????
mann said:
you guys want to see weak ass computer try this

Celeron 465 MHZ
8 Mb Open GL intel i810 integrated video card
160mb of Ram
15gb HD Quantam Fireball ATA66

I get 30 friggin fps on zelda oot which sucks!!!
That's much for such a crappy system! It should run at like 10 fps. Well, it depends on where you are. Try to be in a town or something similar. What does the fps get to there?
 

BlueYoshi

New member
My system is:
AMD-K6 450 Mhz
64 MB RAM
Ati Rage Pro Turbo 8 MB

I can run Super Mario 64 on Corn perfectly with sound. About 3 times faster than on real N64. On Project 64 some games are playable and run with 40 - 50 FPS when most of Windows services are stopped and explorer(biggest memory hog) is terminated.
 

matadem

New member
Well I get about 59 FPS

My system P3 733 mhz , 192 mb ram , geforce 32 mb mx

on my laptop it runs with mariokart 41 fps max
Celeron 700 , 312 mb ram , 8 mb shared video
 

james.miller

HELL YES. IT'S ME!
im not braggging about my pc. there are some that are a lot faster than mine. i just wanted to see how the different specced machines effected the speed of the emulator
 

snipeer

New member
Just while we're at it about specs and FPS, can someone
help me out here?

I'm trying to run Zelda 64 and my specs are:

Athlon 1GHz (Thunderbird. ie. Socket A, not SlotA)
PS. Not overclocked.
256 MB SDRAM (not DDR)
Voodoo Banshee 16 MB
WinXP

Now, I have Direct X 8.1 as I have XP.
Now here is the problem:

I cannot use Jabo's D3D plugins (any of them...I've
tried two...ie. D3D6 1.4 andD3D7 1.4)
It gives me a "Direct3D failed to initilize
your HAL device"... message. It also mentions to check
that my 3D card is compatible with Direct3D 6.0, which
I think it is...

Using Glide 64 0.1, I get good FPS (stays at 59-60) but with a
blank/black screen...

Using 1964 OpenGL Build 4, I get VERY slow...like 4-7 for
the "nintendo 64" intro screen. I get about 20 FPS
when it's a black screen. Also, the colours are weird, and there
are many graphical errors, even in the intro video.

Using glNintendo64 0.1b, I get errors before loading:
"EXT_packed_pixels not supported, some textures won't load correctly!"
"IBM_textured_mirrored repeat not supported, some textures won't load correctly!"
"NV_register_combiners not supported, combiner support disable..." (the three dots is a quote, not to say there is more
stuff following. )
Then:
"Unknown x86 opcode 88.
Location 1E64D66
loc: 9005D2
fgh2"
Then it crashes and exits.

Finally, using "New TR64 OpenGL v0.5" plugin, I get great
graphics...(all the colours are right, no artefacts etc...)
BUT it is going at 2-3 FPS....

Anyone know what the hell is going on, seeing how it seems
the Glide64 (at least) is supposed to work well for Voodoo
owners like myself?

I'd have expected better performance than 2-3 FPS...
 

snipeer

New member
I forgot to mention that Lex said that you had to run
it in full screen if you use Glide64....

Well, for me, I get an error box popping up if I try
to enter full screen, and then PJ64 exits...
 

james.miller

HELL YES. IT'S ME!
i think its the banshee thats the problem. the pj64 help file says that any voodoo under a voodoo 4 isnt good enough. so im almost certain its the banshee. bin it and get a geforce
 

snipeer

New member
My Banshee being a bottleneck is
pretty obvious I would think...

However, it is unlikely, in my opinion, that
it would bottle it at 2-4 FPS...

Surely it is at least playable? (considering
what others have said regarding their system specs?)
 

LD.

*poke*
You're using Xp... XP sucks for Glide since there were no official drivers released for it... look at www.voodoofiles.com and try and find some decent banshee drivers for XP, that might help you out running Glide64. As for the DirectX message, make sure you're running your desktop in 16bit colour :)

As for proving the speed of Glide64, you can't. There is no fps counter for Glide64. I can see the fps because I have a Voodoo2 addon card, and two seperate monitors :) I get Glide64 running on one monitor, and my desktop on the other. I'll run some tests or something, see what kind of speeds I get :)
 

snipeer

New member
It's pretty much a constant 2-4 FPS...(Well, ok, It's like 2-5 maybe...but throughout the entire intro movie....(I had to sit
there for quite a while to see it.) It NEVER sped up...Always
around 2-5, and that's being lenient. Put it this way, it's NEVER
been over 15, even for just a black screen.

I've been to voodoofiles before posting the first msg and got the file that looked promising, located at:

http://www.voodoofiles.com/4807

But I got nowhere with it. Made no difference whatsoever...
One thing to note might be when I'm installing the drivers, I get
about 4 (?) 1904 errors...saying that certain dlls didn't register.
(Some obviously didn't because I don't have the hardware, like TV Out I think was one...)

I am now running in 16 bit colour...and the FPS (using TR OpenGL
goes up to 3-4...yay!....[not])
Using Glide 64, I have the exact same problem...(Blank/black screen without full screen, full screen = error box that doesn't
say anything...) but the FPS is now hovering at around 128 FPS...
(I took off the FPS limit...That was what was limiting it at 60 FPS...
which should mean I can run PJ64 at full speed with my system, except for some weird reason it's not displaying...(the sound plays fine, and the graphics isn't constant, but fluctuating, so I assume it is in fact processing, but not displaying..))

Note: when I am quoting my FPS, it is in windowed mode, and I don't know if that is reliable or not, going by what others are saying about Glide64 opearting at full screen only.
 

snipeer

New member
Forgot to mention that Jabo's plugins work now, after changing the colour to 16 bit.

And they work at a good speed...(unlimited would make it
between 47-180 [around there....])
If it's a black screen, it might go over 200...

Anyways, the problem is, the graphics is BAD...and I don't mean poor graphics, which I can live with. I mean, the sky is red, not blue, and that there's a white chunk over most of the screen from the second shot onwards....

Put simply, it's pretty much non-playable in terms of graphics, but in terms of speed, it's fine.

Also, TR OpenGL plugin is the ONLY one I have found that faithfully reproduces everything...All the others I've tried give me artefacts or just don't work, for (at present) unknown reasons.
The TR OpenGL has great colour, and everything is right, except for the damn speed....

And no, the speed isn't because of the FPS limit.
 

james.miller

HELL YES. IT'S ME!
thats a bit of a pickle mate. let me get this right. glide64 is toooo slow and with jabo the graphics are crap?
 
Status
Not open for further replies.

Top