Open PabloNewt opened 3 months ago
@PabloNewt i have also screen shakes ... do you think it comes from v1.1 ?? my gbsc came directly with the v1.1 firmware ... im using a one chip snes with RGB Cable from Retrogamingcables in the uK
I didn’t have shakes with v1.1 or v1. My issue is with active frame lock not properly working in v1.1. But I do use RGB with a SFC. Did you have the sync on RGB button pressed down?
Yeah my problem is only on sfx games and super gameboy... idk why ....
PabloNewt @.***> schrieb am Mi., 12. Juni 2024, 03:12:
I didn’t have shakes with v1.1 or v1. My issue is with active frame lock not properly working in v1.1. But I do use RGB with a SFC. Did you have the sync on RGB button pressed down?
— Reply to this email directly, view it on GitHub https://github.com/RetroScaler/GBSC/issues/10#issuecomment-2161875503, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJCJFMVEVBJKA5N4PMBYSOLZG6OARAVCNFSM6AAAAABID5TCJ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRRHA3TKNJQGM . You are receiving this because you commented.Message ID: @.***>
With the v1.0 firmware from December 2023 I get the "Active FrameTime Lock enabled, adjusting external clock gen frequency" as expected with active Frametime Lock enabled (shown within the Debug UI ) with the external clock enabled. However, after loading v1.1 firmware binary it no longer showed this message instead showing an older message associated with older logic (from before Feb 2023). This makes me think something is wrong with the latest v1.1 firmware binary. I downgraded to v1.0 and behavior is back to as expected. For me something wrong with this functionality is a problem as it prevents screen tears I was getting before getting the December 2023 build. I checked the latest code from https://github.com/ramapcsx2/gbs-control and the logic is definitely still there to produce the Debug message I was expecting. I could build it myself but would prefer to wait for a new/corrected "official" firmware binary here.