Project64 2.0.0.11

[squall_leonhart]

Originally Posted by zilmar

if you turn off the speed limiter then the recompiler should be faster, should be like double the speed.

A recompiler still needs to compile which is where you might be seeing the slow down. Try disabling the advanced block linking, that requires even more time in compiling.

The recompiler in 1.6 starts games (and levels, movies, cutscenes) a whole lot faster than in 2.0

and no, not really at all. not even using fps limiter, ABL, faststart/ cache etc and games are still sluggish to start with the 2.0 recompiler

1.7 is faster than 2.0!

[dsx_]

Originally Posted by squall_leonhart

The recompiler in 1.6 starts games (and levels, movies, cutscenes) a whole lot faster than in 2.0

and no, not really at all. not even using fps limiter, ABL, faststart/ cache etc and games are still sluggish to start with the 2.0 recompiler

1.7 is faster than 2.0!

what about after starting/loading?

[squall_leonhart]

choppy first few seconds after loading a profile in MM
same with Zelda64, and when entering dungeons.

Kirby64 also choppy and stuttery

Honestly, i might just change to the interpreter.

[xQuarkDS9x]

Originally Posted by squall_leonhart

choppy first few seconds after loading a profile in MM
same with Zelda64, and when entering dungeons.

Kirby64 also choppy and stuttery

Honestly, i might just change to the interpreter.

That's odd I've been playing OoT v1.0 with this new release and the only choppyness I had was in bringing up the start menu at first in OoT but afterwards it was fine due in part because i'm using a texture pack.

[squall_leonhart]

has nothing to do with the texture pack

the recompiler cache is getting slapped around like a bitch and left bruised and bleeding.

and if you run uncapped, you'll see it, since the interpreter will run far faster than the recompiler

[zilmar]

Originally Posted by squall_leonhart

has nothing to do with the texture pack

the recompiler cache is getting slapped around like a bitch and left bruised and bleeding.

and if you run uncapped, you'll see it, since the interpreter will run far faster than the recompiler

if you turn off frame limitor, do you see the interpreter still run faster then the recompiler ?

[xQuarkDS9x]

Originally Posted by squall_leonhart

has nothing to do with the texture pack

the recompiler cache is getting slapped around like a bitch and left bruised and bleeding.

and if you run uncapped, you'll see it, since the interpreter will run far faster than the recompiler

I just tried running OoT again this time uncapped with Interpreter and it was fluctuating around 100-120 VI/s. However when I tried again with recompiler it was around 220-270 VI/s. Unless i'm testing this wrong recompiler here on my machine at least seems faster then interpreter.

[squall_leonhart]

i was referring to the amount of time you sit on a blackscreen or hung pause subscreen when uncapped, not actual vi's.

[squall_leonhart]

Originally Posted by zilmar

if you turn off frame limitor, do you see the interpreter still run faster then the recompiler ?

in golden eye and majora's mask, the frame limitor, and audio sync settings don't change a thing

goldeneye starts faster with fastsp disabled, but the missions are still alot longer to load.

on majora's mask and zelda64, the opening scenes, and subscreens still take a lot longer under the recompiler.

I shall record it later after i get some sleep.

[elbeto57]

Im not been here for a loooooooooooooooong time, so were i can get the 2.0 or newst release?