Metal Gear Solid 3 : Subsistance Bad Input Lag & Poor Frametime Consistancy
#11
(01-20-2018, 08:40 AM)jesalvein Wrote: Blink where did you see this ?

here
https://github.com/pcsx2/pcsx2/issues/594

howcome they dont release a monthly build that includes all the work done in that month

their daily builds dont include everything from v1.40 upto the daily build right?

Sponsored links

#12
builds are released more often than monthly. it's more every 2-3 days.
and yes, they include all fixes.
that said, this is fixed in OGL.
you'll probably get bad framerates anyways.
CPU : AMD Ryzen 7 3800X
Mobo : Asus PRIME B450-PLUS
GPU : NVIDIA GeForce RTX 3070
RAM : 16 Go
#13
(01-20-2018, 08:08 PM)jesalvein Wrote: builds are released more often than monthly. it's more every 2-3 days.
and yes, they include all fixes.
that said, this is fixed in OGL.
you'll probably get bad framerates anyways.

so the 4meg daily file has everything fixed from the 2016 v1.40 up untill today ?
it says on their github that the opengl fix is in their V1.60 which isnt out yet
#14
Yes, it includes all the fixes from 1.4.0 to the present. The 1.6 you are probably seeing on Github is the "release milestone" - that just means we want certain things to be done before 1.6 is released; but it's not actually out yet. Wink
#15
(01-20-2018, 08:12 PM)El Diablo Wrote: so the 4meg daily file has everything fixed from the 2016 v1.40 up untill today  ?
it says on their github that the opengl fix is in their V1.60 which isnt out yet

then it's not fixed.
sorry for you

(or try latest git instead of asking those questions...)
CPU : AMD Ryzen 7 3800X
Mobo : Asus PRIME B450-PLUS
GPU : NVIDIA GeForce RTX 3070
RAM : 16 Go
#16
(01-20-2018, 03:24 AM)smartstrike Wrote: use this settings instead

doing that made the frametimes even worse
[Image: 7xZFT2Z.jpg]
#17
(01-20-2018, 08:12 PM)El Diablo Wrote: so the 4meg daily file has everything fixed from the 2016 v1.40 up untill today ?
it says on their github that the opengl fix is in their V1.60 which isnt out yet
If it says fixed in v1.6.0, that means it's fixed in the v.1.5.0 development build, which will become v1.6.0 when a final release version is ready.
#18
(01-20-2018, 08:15 PM)CK1 Wrote: Yes, it includes all the fixes from 1.4.0 to the present. The 1.6 you are probably seeing on Github is the "release milestone" - that just means we want certain things to be done before 1.6 is released; but it's not actually out yet. Wink

how come you guys dont release the fixes compiled into an installer?

(01-20-2018, 08:16 PM)jesalvein Wrote: then it's not fixed.
sorry for you

(or try latest git instead of asking those questions...)
the guy above u just said its fixed?
ok now im confused
#19
(01-20-2018, 08:21 PM)El Diablo Wrote: how come you guys dont release the fixes compiled into an installer?

the guy above u just said its fixed?
ok now im confused

The fixes will be compiled into an installer once we're ready to release 1.6. It's not time yet Wink
#20
(01-20-2018, 08:24 PM)CK1 Wrote: The fixes will be compiled into an installer once we're ready to release 1.6. It's not time yet Wink

i seeee, would be nice if u guys done a monthly installer or even quaterly

so what u think is the root cause off the frametime issue, i have never seen my frametime bar that bad before, enabling vsync in pcsx2 didnt seem to doo much either
u know what, let me copy paste the daily build and check back in here after

urgh, i really dont wanna pull out my ps2 to play this, it looks so crap on a Flat screen 1080P tv
so blurry and the ps2 controller is crappy too




Users browsing this thread: 1 Guest(s)