01-24-2016, 11:52 AM
Pages: 1 2
tambre
01-24-2016, 12:08 PM
(01-24-2016, 11:52 AM)Ekaseo Wrote: [ -> ]i used a build with updated llvm 3.7
Well, there's likely your problem.
Ekaseo
01-24-2016, 12:22 PM
(01-24-2016, 12:08 PM)tambre Wrote: [ -> ](01-24-2016, 11:52 AM)Ekaseo Wrote: [ -> ]i used a build with updated llvm 3.7
Well, there's likely your problem.
nope... still have the problem, probably because cellsync is causing some issues again,last time i checked, it didnt show any cellsync errors and i got that much fps, but now it drops to 3-5 fps, and after some time it climbs to maybe 9-11 fps
tambre
01-24-2016, 12:30 PM
(01-24-2016, 12:22 PM)Ekaseo Wrote: [ -> ](01-24-2016, 12:08 PM)tambre Wrote: [ -> ](01-24-2016, 11:52 AM)Ekaseo Wrote: [ -> ]i used a build with updated llvm 3.7
Well, there's likely your problem.
nope... still have the problem, probably because cellsync is causing some issues again,last time i checked, it didnt show any cellsync errors and i got that much fps, but now it drops to 3-5 fps, and after some time it climbs to maybe 9-11 fps
And why are you assuming cellSync is causing problems?
Nekoteki already said, that those "errors" are not errors.
I'm not sure why'd you even want to use the recompiler - it's basically worse for most cases than the interpreter 2. Simply use interpreter 2.
Ekaseo
01-24-2016, 12:35 PM
(01-24-2016, 12:30 PM)tambre Wrote: [ -> ](01-24-2016, 12:22 PM)Ekaseo Wrote: [ -> ](01-24-2016, 12:08 PM)tambre Wrote: [ -> ](01-24-2016, 11:52 AM)Ekaseo Wrote: [ -> ]i used a build with updated llvm 3.7
Well, there's likely your problem.
nope... still have the problem, probably because cellsync is causing some issues again,last time i checked, it didnt show any cellsync errors and i got that much fps, but now it drops to 3-5 fps, and after some time it climbs to maybe 9-11 fps
And why are you assuming cellSync is causing problems?
Nekoteki already said, that those "errors" are not errors.
I'm not sure why'd you even want to use the recompiler - it's basically worse for most cases than the interpreter 2. Simply use interpreter 2.
because the time i posted i got 21-30 fps, i didnt have those errors at all, so i just assumed that thats the case, since this is the same build.
Pages: 1 2