N64 lower grapics plugins?

[Starfox1000]

I am trying to use a emulator at school but it's REALLY slow


anybody got any grapics plugins that are faster?

(i don't mind if the grapics are bad)

I am using project 64 emulator :matrix:

 

[Doomulation]

Most of the time, it's the core that sucks CPU cycles. Jabo's sound plugin, being LLE, also sucks CPU cycles. The RSP too.
The best way to get a speed boost is to try another emulator. 1964 is a fast one. There's also a speed guide pinned in the 1964 forum I think.

 

[Iconoclast]

Actually, the graphics plugin affects emulation speed the most. Next on the list is the emulator. The audio plugin, Jabo's DirectSound, is comparitivly inferior to these two things. Whether I use schibo's, Azimer's or Jabo's, I have seen no worthy difference in emulation speed between these plugins with the speed limiter off. Despite being LLE, it is still inferior in affecting speed.

1964 is, indeed, the fastest decent core N64 emulator. It also comes with a very, very fast graphics plugin, which runs the fastest on 1964 in particular, unless your system is incapable of or very bad at emulation through DirectX.

Now, here's a tutorial for you to experiement. Obtain the ROM known as Virtual Chess 64. Try using the following emulator-graphics plugin combos to emulate the game.

1. Project64, Jabo's Direct3D 8
2. 1964, Rice's Daedalus 5.2.0
3. Mupen64, Glide64
4. Nemu64, Nemu64 Graphics

You'll notice that Nemu64 is the slowest emulator, not just for its heavy CPU usage, while 1964 is the fastest core emulator. In Nemu64, however, the primary reason for the slow speed is the default graphics plugin it comes with, not the emulator. Change Nemu64's graphics plugin with the F8 keyboard shortcut to something like Jabo's Direct3D. Much faster, now, though a little bit more faster when using Project64 here.

Now, 1964's speed limiter is set to On at default, so while the game is running, press F9 to turn it off. Look at that speed fly. 450 FPS, on my system.

As for Mupen64, it's going to be at a constant 60 FPS, because though there is a speed limiter for this emulator and an option to turn it off, it is difficult to access easily. It's not a good emulator for those who often turn off the speed limiter.

 

[Toasty]

In any event, try posting the specs of the computer you're using, Starfox1000. If it's a 75MHz Pentium or something like that, there's no amount of tweaking that will give you decent speed.

 

[Starfox1000]

i don't know the schools pc specs since i don't own them.


the only plugin that works in school is (that has ok grapics) 1964ogl.dll but i get 6 FPS!!!

the plugins that come with project 64 says something about direct3d (not sure if the school has it):down:

 

[Doomulation]

You can check the specs anyway. Goto Start -> Run and type dxdiag, then enter. You'll find the specs on the main page. Goto display to find the graphics card. My guess it that the computers are crap, and that achieving good speed will be hard, if not impossible.

 

[Starfox1000]

The menu is blocked by the school............

 

[Clements]

If you can't access the run prompt, and the School is using Windows 2000 or XP, create a shortcut to C:\$Windir$\system32\dxdiag.exe

$Windir$ being the name of the Windows directory, normally either WINNT or WINDOWS. That normally gets around it. Chances are the hardware is extremely outdated, though.

 

[Starfox1000]

When i try to open it a message says i don't have privileges to open.


but i normaly get past this but making it into a zip folder but does not work for the shorcut.

(that is what i do to open project 64 and it works.)


so what should i do?

 

[Doomulation]

Chances are they've blocked execution of all applications but the ones they've specified. Can you access System, though? Control Panel -> System. Or Windows Key + Pause.
You can also try to run msinfo32.exe or download CPU-Z and run it if you're allowed to.

 

[Cyberman]

I think you are pushing your luck VERY hard.

First off if Direct3d isn't functioning it was on purpose. Likely they either removed (from a preinstallation HD) it or did not install it, so students won't be able play games on the school machine. OpenGL is on all Windows machines by default because that is installed as a software emulator as part of the OS. OpenGL 1.1 or 1.3 is supported by it so it's quite minimal. You can't install DirectX unless you have administrator rights as far as I know. 6fps is not too bad for software emulation of OpenGL by the way.

I think you are going to have to deal with the fact they don't want you playing games, and if you want to try playing them you'll have to live with the slowness of software emulated OpenGL, and no DirectX. That's life. Shrink your window size too about 640x480 and live with the slowness I suggest, because unless you do something that likely violates the rules you probably signed to use the computer lab, you can't do anything about it.

Be happy if you even have sound dude. Seriously.

Cyb

 

[Doomulation]

There is just one fact that you missed
Windows 98+ has DirectX installed by default, but I'm tipping more towards an old computer with an integrated (or very poor) graphics card, which when drivers are not updated, cannot run D3D.

 

[Iconoclast]

School security is not gullible, unless the software is. I go to school here; I would know. And I've always been hacking around their security on my free time. If you get a No Permission message, trying to bypass that, like creating a shortcut or executing it from another method, is about as feeble as trying to bypass a vBulletin forum No Permission message: All possible ways are blocked, because the command itself is blocked for the underpriveleged user, not the PHP that links to it.

Now, first off, Toasty sort of jumped to conclusions, but he's right: This guy seriously needs to use upgraded hardware, UNLESS the slow emulation speed is caused by the game where the graphics fail to load, and believe it or not, this will happen with some games. If you use Jabo's Direct3D with these kind of games, say, Indiana Jones and the Infernal Machine, this slowdown to 6-or-so FPS will not occur, but you get a microcode failure. The fact that a shitty OpenGL plugin worked for him but not any of the DirectX plugins does not prove, for absolute certain, it's his system, either. 1964 OpenGL bypasses microcode failures, giving you a black screen for those games, and probably crashing sooner or later.

I'm only saying, I'm not prepared to jump to blaming his hardware yet. It could be the game he's trying to play or the emulator he's using for it. Take Top Gear Overdrive as an example; using Project64 with that game with somewhat below-spec cards is miserable while on Mupen64 it's all fixed.

 

[Cyberman]

There is just one fact that you missed
Windows 98+ has DirectX installed by default, but I'm tipping more towards an old computer with an integrated (or very poor) graphics card, which when drivers are not updated, cannot run D3D.

On win2K I had to install D3d.. that doesn't mean Direct X wasn't installed. As you said you have to update it to run your hardware. Without administrator access ... this is all just hot air.

Cyb

 

[Doomulation]

School security is not gullible, unless the software is. I go to school here; I would know. And I've always been hacking around their security on my free time. If you get a No Permission message, trying to bypass that, like creating a shortcut or executing it from another method, is about as feeble as trying to bypass a vBulletin forum No Permission message: All possible ways are blocked, because the command itself is blocked for the underpriveleged user, not the PHP that links to it.

Now, first off, Toasty sort of jumped to conclusions, but he's right: This guy seriously needs to use upgraded hardware, UNLESS the slow emulation speed is caused by the game where the graphics fail to load, and believe it or not, this will happen with some games. If you use Jabo's Direct3D with these kind of games, say, Indiana Jones and the Infernal Machine, this slowdown to 6-or-so FPS will not occur, but you get a microcode failure. The fact that a shitty OpenGL plugin worked for him but not any of the DirectX plugins does not prove, for absolute certain, it's his system, either. 1964 OpenGL bypasses microcode failures, giving you a black screen for those games, and probably crashing sooner or later.

I'm only saying, I'm not prepared to jump to blaming his hardware yet. It could be the game he's trying to play or the emulator he's using for it. Take Top Gear Overdrive as an example; using Project64 with that game with somewhat below-spec cards is miserable while on Mupen64 it's all fixed.

Perhaps. But the classic "failed to initialize Direct3D" usually refers to that it is a very old card or some integrated crap which requires driver update to work properly. And to mention that the speed is very poor also seem to point towards that the cpu is weak as well. For schools, computers aren't updated that often. I have seen old 400-1000 MHz computers or around there, so it's not unfeasible.
All we're trying to point out here is that the evidence is pointing towards improper hardware. Maybe we're wrong, maybe not. But until proven otherwise, I think it is safe to assume that the hardware is weak.

On win2K I had to install D3d.. that doesn't mean Direct X wasn't installed. As you said you have to update it to run your hardware. Without administrator access ... this is all just hot air.

Cyb

In DirectX, Direct3D is a part. And it is pre-installed in every OS from 98 and beyond. However, that does not mean you have the correct version installed. You cannot run DX9 apps with only DX8 installed. So you may be partially right. You might have been running applications that required a newer version. And as we know, all new software that is written usually take advantage of the newest versions - ie DX9 (or DX10 if you go for Vista).

 

[Iconoclast]

It's very easy to assume his hardware is weak, I understand that. So easy, it seems safe, but it's not impossible that it could be the game he's trying to play. Maybe, what you could've done was, assume that it was his hardware, but at the bottom of your post, include an "unless, what game are you trying to play?"

It could be that his hardware IS weak, but not so weak that it runs at 6 FPS, unless his hardware is actually only a little bit under system specifications AND he's trying to emulate a CPU-consuming ROM at the same time, making it seem like it's just his system. He or she needs to be questioned as to what game(s) he or she is trying to play.

 

[Clements]

School security is not gullible, unless the software is. I go to school here; I would know. And I've always been hacking around their security on my free time. If you get a No Permission message, trying to bypass that, like creating a shortcut or executing it from another method, is about as feeble as trying to bypass a vBulletin forum No Permission message: All possible ways are blocked, because the command itself is blocked for the underpriveleged user, not the PHP that links to it.

The level of security depends on how the user restrictions are put in place by the system administrator(s). At my University, most things can be easily circumvented by shortcuts and by using Command Prompt. Direct access to the C:\ and Run prompt are forbidden, but dxdiag can still be easily accessed through these other means. Thus my suggestion.

 

[Doomulation]

It's very easy to assume his hardware is weak, I understand that. So easy, it seems safe, but it's not impossible that it could be the game he's trying to play. Maybe, what you could've done was, assume that it was his hardware, but at the bottom of your post, include an "unless, what game are you trying to play?"

It could be that his hardware IS weak, but not so weak that it runs at 6 FPS, unless his hardware is actually only a little bit under system specifications AND he's trying to emulate a CPU-consuming ROM at the same time, making it seem like it's just his system. He or she needs to be questioned as to what game(s) he or she is trying to play.

Maybe, but then again, we already asked for the specs and until then, we can only speculate. There is no point arguing about what we do not know. I think it's a lost cause to play this, but let's acquire the specs first and see if we can find a few tricks to help out. THEN we decide.

 

[Iconoclast]

Yes, but some people don't know DOS or how to use a command prompt. One way to break into the C drive with Windows Explorer is to open something like Microsoft Word (anything with a File/Open), choose the Open command, type C:\ in the file name box, press Enter, the program browses for the file you want to open in the C drive. Now, right-click a folder, and choose Explore. I doubt this starfox dude knows DOS, so just saying, this would be an easier method.

Maybe, but then again, we already asked for the specs and until then, we can only speculate. There is no point arguing about what we do not know. I think it's a lost cause to play this, but let's acquire the specs first and see if we can find a few tricks to help out. THEN we decide.

Try not to mistake me, now. I'm not arguing with you about what I don't know; I'm only using what I do know, the possibilities of other causes of his slow emulation, to remind anyone here that, just for future reference, system specifications ain't the only thing to ask for.

I'm not saying you should've asked for the game he's trying to play AND his system specs in the same post; I'm just giving a suggestion for future times of helping users with emulation slowdown issues.

 

[Starfox1000]

I can't open most controls i tryed stuff like shortcut and open C:\ does not work


don't have permissions

I am trying to play Super mario 64

i can't get the pc specs sorry but i know it's windows xp.


would it help if i print screen i show you?