nah I figured it out, it was because i was in borderless and needed fullscreen to use vsync, then i could turn the settings back up
November 14, 2025 at 6:04 PM
nah I figured it out, it was because i was in borderless and needed fullscreen to use vsync, then i could turn the settings back up
This shit can happen with PCs. Had something similar with Fortnite lately, although i am running it with like 300 FPS. GPU driver decided to activate a setting similar to vsync and both together were like
two women are sitting next to each other and one is pointing at the camera
ALT: two women are sitting next to each other and one is pointing at the camera
media.tenor.com
November 14, 2025 at 3:48 PM
This shit can happen with PCs. Had something similar with Fortnite lately, although i am running it with like 300 FPS. GPU driver decided to activate a setting similar to vsync and both together were like
Just a side note
PS3 port looks sharper runs a bit better but that's because no vsync is enabled so lots of screen tearing
Xbox 360 port runs a little worse but i did not see any screen tearing so i'm guessing that port has vsync enabled bsky.app/profile/cody...
PS3 port looks sharper runs a bit better but that's because no vsync is enabled so lots of screen tearing
Xbox 360 port runs a little worse but i did not see any screen tearing so i'm guessing that port has vsync enabled bsky.app/profile/cody...
Hard game funny voice lines (they do lose their comedy pretty quickly though due to looping often)
Decent game not the worst i've played by any means but i'm not playing through it again
Things i disliked
Ai is not that great gameplay is basic cover system could have been refined
Decent game not the worst i've played by any means but i'm not playing through it again
Things i disliked
Ai is not that great gameplay is basic cover system could have been refined
November 14, 2025 at 2:09 PM
Just a side note
PS3 port looks sharper runs a bit better but that's because no vsync is enabled so lots of screen tearing
Xbox 360 port runs a little worse but i did not see any screen tearing so i'm guessing that port has vsync enabled bsky.app/profile/cody...
PS3 port looks sharper runs a bit better but that's because no vsync is enabled so lots of screen tearing
Xbox 360 port runs a little worse but i did not see any screen tearing so i'm guessing that port has vsync enabled bsky.app/profile/cody...
ece is such a funny major
youll suffer through hours of random bullshit with no end in sight
but hey at least i know how AM radio works now!!
and i know what "vsync" actually means!!!
youll suffer through hours of random bullshit with no end in sight
but hey at least i know how AM radio works now!!
and i know what "vsync" actually means!!!
November 14, 2025 at 7:04 AM
ece is such a funny major
youll suffer through hours of random bullshit with no end in sight
but hey at least i know how AM radio works now!!
and i know what "vsync" actually means!!!
youll suffer through hours of random bullshit with no end in sight
but hey at least i know how AM radio works now!!
and i know what "vsync" actually means!!!
video timing diagram:
green = hsync (high)
red = vsync (high)
yellow = hsync+vsync (low)
gray = visible area.
pixel clock is 6.6715 MHz
green = hsync (high)
red = vsync (high)
yellow = hsync+vsync (low)
gray = visible area.
pixel clock is 6.6715 MHz
November 14, 2025 at 5:54 AM
video timing diagram:
green = hsync (high)
red = vsync (high)
yellow = hsync+vsync (low)
gray = visible area.
pixel clock is 6.6715 MHz
green = hsync (high)
red = vsync (high)
yellow = hsync+vsync (low)
gray = visible area.
pixel clock is 6.6715 MHz
Yeah, the physics just struggle with framerates above 60.
It could be worse, though. LEGO Star Wars: The Video Game notably has a part where an NPC takes forever to get on a button if you're running the game above 30fps, and it doesn't have a VSync option...
It could be worse, though. LEGO Star Wars: The Video Game notably has a part where an NPC takes forever to get on a button if you're running the game above 30fps, and it doesn't have a VSync option...
November 13, 2025 at 8:32 PM
Yeah, the physics just struggle with framerates above 60.
It could be worse, though. LEGO Star Wars: The Video Game notably has a part where an NPC takes forever to get on a button if you're running the game above 30fps, and it doesn't have a VSync option...
It could be worse, though. LEGO Star Wars: The Video Game notably has a part where an NPC takes forever to get on a button if you're running the game above 30fps, and it doesn't have a VSync option...
also, talking about pc issues, my gpu driver might be extra fucked up. i run ZZZ with adaptive vsync, valorant and cs with fast sync and the rest of the games unlocked.
and now to my surprise, now my bf6 sometimes runs with vsync, adaptive vsync and fast sync randomly.
and now to my surprise, now my bf6 sometimes runs with vsync, adaptive vsync and fast sync randomly.
November 13, 2025 at 8:22 PM
also, talking about pc issues, my gpu driver might be extra fucked up. i run ZZZ with adaptive vsync, valorant and cs with fast sync and the rest of the games unlocked.
and now to my surprise, now my bf6 sometimes runs with vsync, adaptive vsync and fast sync randomly.
and now to my surprise, now my bf6 sometimes runs with vsync, adaptive vsync and fast sync randomly.
Do you have VSync enabled? It's essential in a lot of TT Games' LEGO titles to prevent softlocks.
November 13, 2025 at 8:18 PM
Do you have VSync enabled? It's essential in a lot of TT Games' LEGO titles to prevent softlocks.
Vsync isn't busted in #Godot 4.5.1 is it? I can't seem to disable it. Turned it off in Project and Editor settings, and set Max Fps to 0 as well. Have also disabled via code and made sure it's not forced on in Nvidia control panel. No joy, still stuck at 60fps on a 144hz monitor. #GodotEngine
November 13, 2025 at 4:22 PM
Vsync isn't busted in #Godot 4.5.1 is it? I can't seem to disable it. Turned it off in Project and Editor settings, and set Max Fps to 0 as well. Have also disabled via code and made sure it's not forced on in Nvidia control panel. No joy, still stuck at 60fps on a 144hz monitor. #GodotEngine
Thought I'd have a go at building a SCART lead for the Torch Triple X. Turns out, it outputs separate Vsync and Hsync signals which need to be combined somehow...
CD4077 as a hack perhaps? 🤔
Nothing is ever easy (which is why it's fun). 🙂
CD4077 as a hack perhaps? 🤔
Nothing is ever easy (which is why it's fun). 🙂
November 12, 2025 at 9:23 PM
Thought I'd have a go at building a SCART lead for the Torch Triple X. Turns out, it outputs separate Vsync and Hsync signals which need to be combined somehow...
CD4077 as a hack perhaps? 🤔
Nothing is ever easy (which is why it's fun). 🙂
CD4077 as a hack perhaps? 🤔
Nothing is ever easy (which is why it's fun). 🙂
So I had to unwind, added some sections to Dunkle. Detox from all the camera, aiming, vsync and other updates I made over the weekend ;).
#thefalconeer
#indiedev
#indiegames
#thefalconeer
#indiedev
#indiegames
November 12, 2025 at 5:15 PM
So I had to unwind, added some sections to Dunkle. Detox from all the camera, aiming, vsync and other updates I made over the weekend ;).
#thefalconeer
#indiedev
#indiegames
#thefalconeer
#indiedev
#indiegames
Have the settings default to VSYNC off and no frame cap
(Finish the sentence)
I hate it when games...
I hate it when games...
November 12, 2025 at 12:28 PM
Have the settings default to VSYNC off and no frame cap
we have vsync (vertical sync), but no hsync, because being straight is good
November 12, 2025 at 6:56 AM
we have vsync (vertical sync), but no hsync, because being straight is good
vSync on by default
November 11, 2025 at 4:15 PM
vSync on by default
```
[...]
ChangeVideoMode request: 1600 x 900 0 Hz, Windowed, vsync: on
ChangeVideoMode end.
Stopping the game threads after receiving WM_QUIT.
[QUIT] Waiting the game state to finish...
Lua 0:00:07:357
[QUIT] Game state finished.
[QUIT] Stopping game state thread...
```
[...]
ChangeVideoMode request: 1600 x 900 0 Hz, Windowed, vsync: on
ChangeVideoMode end.
Stopping the game threads after receiving WM_QUIT.
[QUIT] Waiting the game state to finish...
Lua 0:00:07:357
[QUIT] Game state finished.
[QUIT] Stopping game state thread...
```
November 11, 2025 at 12:59 AM
```
[...]
ChangeVideoMode request: 1600 x 900 0 Hz, Windowed, vsync: on
ChangeVideoMode end.
Stopping the game threads after receiving WM_QUIT.
[QUIT] Waiting the game state to finish...
Lua 0:00:07:357
[QUIT] Game state finished.
[QUIT] Stopping game state thread...
```
[...]
ChangeVideoMode request: 1600 x 900 0 Hz, Windowed, vsync: on
ChangeVideoMode end.
Stopping the game threads after receiving WM_QUIT.
[QUIT] Waiting the game state to finish...
Lua 0:00:07:357
[QUIT] Game state finished.
[QUIT] Stopping game state thread...
```
Ah, I see, it's an option like one of the other limits how weird. Here is 5.5 speed with vsync and thicker notes at 120hz. 💀
November 10, 2025 at 8:36 PM
Ah, I see, it's an option like one of the other limits how weird. Here is 5.5 speed with vsync and thicker notes at 120hz. 💀
Side thought, have you tried using a thicker noteskin? That might lessen the effect some. Also, I believe the VSync option is in the FPS options, they might be tied together.
November 10, 2025 at 8:24 PM
Side thought, have you tried using a thicker noteskin? That might lessen the effect some. Also, I believe the VSync option is in the FPS options, they might be tied together.
Change Vsync Method
👎 Introduces lag.
👎 Lowers GPU lifespan.
👎 Short-circuits motherboard.
👎 Starves little orphans.
👎 Murders kittens.
👎 Introduces lag.
👎 Lowers GPU lifespan.
👎 Short-circuits motherboard.
👎 Starves little orphans.
👎 Murders kittens.
November 10, 2025 at 7:29 AM
Change Vsync Method
👎 Introduces lag.
👎 Lowers GPU lifespan.
👎 Short-circuits motherboard.
👎 Starves little orphans.
👎 Murders kittens.
👎 Introduces lag.
👎 Lowers GPU lifespan.
👎 Short-circuits motherboard.
👎 Starves little orphans.
👎 Murders kittens.
☀️ WEEK 14 SCHEDULE ☀️
NOV 10 - NOV 16
i fixed the ai somnium bug! (it was vsync that was the culprit!) we'll jump back into date's head on monday.
🎨: #rojogawnina
NOV 10 - NOV 16
i fixed the ai somnium bug! (it was vsync that was the culprit!) we'll jump back into date's head on monday.
🎨: #rojogawnina
November 9, 2025 at 8:37 PM
☀️ WEEK 14 SCHEDULE ☀️
NOV 10 - NOV 16
i fixed the ai somnium bug! (it was vsync that was the culprit!) we'll jump back into date's head on monday.
🎨: #rojogawnina
NOV 10 - NOV 16
i fixed the ai somnium bug! (it was vsync that was the culprit!) we'll jump back into date's head on monday.
🎨: #rojogawnina
Yes, had that too on PC, 60 fps.
Also had some strange screen tearing and found out after a quick search that apparently the in-game vsync option doesn't do anything... I wonder if we get a patch for that at some point 😅
Also had some strange screen tearing and found out after a quick search that apparently the in-game vsync option doesn't do anything... I wonder if we get a patch for that at some point 😅
November 8, 2025 at 8:47 AM
Yes, had that too on PC, 60 fps.
Also had some strange screen tearing and found out after a quick search that apparently the in-game vsync option doesn't do anything... I wonder if we get a patch for that at some point 😅
Also had some strange screen tearing and found out after a quick search that apparently the in-game vsync option doesn't do anything... I wonder if we get a patch for that at some point 😅
void main() {
REG_DISPCNT = MODE_3 | BG2_ENABLE;
VRAM_A_ADDR = 0x6000000;
const char str[] = "Hello, World!";
int i = 0;
while(1) {
for (i=0; i < sizeof(str); i++) {
VRAM_A[i] = str[i];
}
<｜begin▁of▁sentence｜> VSync();
}
}
REG_DISPCNT = MODE_3 | BG2_ENABLE;
VRAM_A_ADDR = 0x6000000;
const char str[] = "Hello, World!";
int i = 0;
while(1) {
for (i=0; i < sizeof(str); i++) {
VRAM_A[i] = str[i];
}
<｜begin▁of▁sentence｜> VSync();
}
}
November 8, 2025 at 8:35 AM
void main() {
REG_DISPCNT = MODE_3 | BG2_ENABLE;
VRAM_A_ADDR = 0x6000000;
const char str[] = "Hello, World!";
int i = 0;
while(1) {
for (i=0; i < sizeof(str); i++) {
VRAM_A[i] = str[i];
}
<｜begin▁of▁sentence｜> VSync();
}
}
REG_DISPCNT = MODE_3 | BG2_ENABLE;
VRAM_A_ADDR = 0x6000000;
const char str[] = "Hello, World!";
int i = 0;
while(1) {
for (i=0; i < sizeof(str); i++) {
VRAM_A[i] = str[i];
}
<｜begin▁of▁sentence｜> VSync();
}
}
switching between a system that updates at 30 FPS variable framerate and renders at 120 FPS, or whether it runs at fixed 60 with no-vsync render FPS is just a matter of setting a variable
November 7, 2025 at 9:04 PM
switching between a system that updates at 30 FPS variable framerate and renders at 120 FPS, or whether it runs at fixed 60 with no-vsync render FPS is just a matter of setting a variable
Hmmm, I see. It might still be screen tearing just VSYNC wasn't enough to deal with it, which happens sometimes, depending on the monitor and all that. Either way, glad you're enjoying your upgrade!
November 7, 2025 at 8:14 PM
Hmmm, I see. It might still be screen tearing just VSYNC wasn't enough to deal with it, which happens sometimes, depending on the monitor and all that. Either way, glad you're enjoying your upgrade!
Monitor's at 165 refresh rate. I'll enable VSYNC and see if that fixes it
November 7, 2025 at 7:05 AM
Monitor's at 165 refresh rate. I'll enable VSYNC and see if that fixes it