You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @vbousquet
Skutter and I have been working on a Flex for the Swords of Fury ROM... for the Fallout table. So, we have substituted several lines of characters so it matches Fallout.
Several testers, and myself, are seeing artifacts/glitches. I have tried changing the timer to and while some are better than others (for me 6ms was the best I could get), others even going to 1ms didnt help.
The latest code we separated into two timers so we can adjust them separately. But this has not helped either.
In the latest table (link below) the F12 menu lets us change the timers from 1 to 40.
I get a few artifacts with the current default settings (Main Refresh 3ms, Update Refresh 40ms). Though, its not as good as when I have a single timer set to 6ms.
Would love your expert advice on this. My original theory was having the Update refresh be faster (processing changing characters) than the Display refresh would fix the issue... oddly I'm seeing fewer artifacts with opposite. Maybe there is something we are not accounting for?
Hi @vbousquet
Skutter and I have been working on a Flex for the Swords of Fury ROM... for the Fallout table. So, we have substituted several lines of characters so it matches Fallout.
Several testers, and myself, are seeing artifacts/glitches. I have tried changing the timer to and while some are better than others (for me 6ms was the best I could get), others even going to 1ms didnt help.
The latest code we separated into two timers so we can adjust them separately. But this has not helped either.
In the latest table (link below) the F12 menu lets us change the timers from 1 to 40.
I get a few artifacts with the current default settings (Main Refresh 3ms, Update Refresh 40ms). Though, its not as good as when I have a single timer set to 6ms.
Would love your expert advice on this. My original theory was having the Update refresh be faster (processing changing characters) than the Display refresh would fix the issue... oddly I'm seeing fewer artifacts with opposite. Maybe there is something we are not accounting for?
Really appreciate the assistance!
https://mega.nz/file/wz1REBbL#l8sQqM6_S-I0buZC4wsGemiHnaF0jkLjR_qmjNINUuI
The text was updated successfully, but these errors were encountered: