Ok this is not right so I have no choice but to respond.
@Calamity: I'm not taking defamation without defending myself.
As maybe you're unaware I suffer from a chronic condition that leaves me with very limited time in between my symptoms, so I have to spend my time on my TODO list very wisely.
You know I'm aware, you sent me a pic from the hospital after all, I told you to take all your time resting instead of taking care of the GILT issue. It would be petty of you to pretend I don't know or didn't care to make me look bad. You wouldn't do that, right ?
I'm sorry that doing tests for you is not on top of my list.
I've never asked for
tons of measurements, just asked only for one, or two measurements exactly, since I'm curious how it compares to baseline. It should have take about 5~10 minutes in total.
I couldn't have guessed there were issues with what I asked since you kept being silent about it.
And anyway I accepted to purchase a GILT so you wouldn't have to be disturbed.
Remember that part ?
Or do you really want to make me look like I wanted to exploit your time without a care like an egoist ? and forget like I've paid for your device specically so I would measure myself ? (but you omitted to tell me I couldn't) did I protest or complain ? no I just paid and gladly.
The amount of lag in triplebuffer mode should be a more or less fixed amount of frames, supposedly inferior in GM vs. baseline, that's what Calamity said, but it was never confirmed.
Your test confirmed how a previous statement about the default lag with d3d9ex was wrong (frame_delay off), I was of course curious to know about the other statement about when it's switched to triplebuffer and finally learn the end of it.
Regarding the tests, I'm not sure why you need the triplebuffer, if your display supports VRR just use it.
- I don't use GM only on my primary setup, I also use it on other computers/displays that don't support VRR or Emudriver.
- Knowing how much triplebuffer lags matters in cases we don't/can't use syncrefresh and frame_delay.
- I was asked that question several times by other users, I'm not the only one curious, and many users don't have a setup fit for Emudriver/VRR anyway.
- I've told you all that already including in private, why pretend I didn't?
Anyway this is a 100% legitimate question coming from GM users, it's a whole part of it after all.
Pretending it doesn't matter is like when ppl here were pretending flat panels use doesn't matter so why bother? but this is what most people use, like it or not the world goes beyond the scarcely populated walls of BYAOC, and Calamity made Groovy competent for these displays, the best at it in fact, so it's useless after all he worked on to act like one aspect somehow doesn't exist/matter. It unfortunately still does until everyone on Earth is equipped with a gsync/freesync display (or finds a somewhat rare monitor like mine), which is still far away in the future.
The only time GM may start tearing in VRR is when your desktop's refresh rate is lower than the game's resolution. Just make sure your monitor's RR is above 60 and that's it. You say you need tests just with triplebuffer, but that's not enough, there are more switches that can affect the lag, so you need as many combinations of commandline switches as possible to get a full picture (Yes I know you are illiterate in that matter, but GM overrides some ini settings, so you need to learn how to use commandline args whether you like it, or not)
As Calamity said GILT requires that game runs with syncrefresh, VRR, or in native RR of the monitor, otherwise the lag spread will become longer then the frametime, which in turn makes the tests meaningless with any device, or camera. You just need to make sure GM is not dropping/doubling frames (the integrated moving bar toggle in the LUA script serves that purpose)
There was no tearing at all when I tried, even with frame_delay off and syncrefresh, the LUA plugin would crash immediately in all cases even with exactly 60.00Hz games, if it was still seeing uneven refresh under these conditions then the problem was elsewhere.
I bet this is related to this monitor being driven by Emudriver, which is a rather unique thing since AFAIK I'm the only one doing this (more people could but compatible monitor's aren't too common and ppl don't even imagine something like that is possible.
Maybe you could have found out if I'd kept reporting the errors to you, Id'have battled command line despite my illiteracy until it'd worked, but you weren't cool with me at all, so I've quit and anyway can't do anything anymore since I've sent back the device already, I gave you a tracking number.
It was simple, before telling me to buy a GILT you could simply have not ignored my question -repeatedly- and simply said this couldn't be measured by it or not without roundabout ways, and that it was still in beta and you needed testers anyway.
ONE sentence.
I would have accepted these conditions, in fact I accepted them afterwards anyway, and I would have done a ton of testing for you, but you still refused to talk about what I asked and started to have demands, which is why I stopped being friendly.
What I can't gut is that on top of having been dishonest, and seeing your post is a narrative to cover that and put all the blame on me, you had the nerve to complain to Calamity who threatened me of a ban.
I'm a honest person, straightforward, you guys aren't, yet I'm the one being blamed.
@Calamity; before you attempt to censor this post, someone made a narrative that's very unfair, even defaming to me so I'm responding on the same ground with nothing but the
truth.
If you want to censor that and kick me out now, well that's between you and your conscience. I'd advise you wait until I got the refund at the very least, so I can confirm we're through.
You guys should know there is a simpler other way to get out of this cleanly, it's just a few words, but I'm betting it's more comfortable to nuke me, right?
Asking people to show honesty these days is too much, people systematically complain about people like me who refuse to act like a phony. I don't care if I'm disliked, but still, I don't let anyone dirty my purpose, intentions, words and actions, oomek's been completely unfair here, and that's wording it kindly, so it's my right to respond.
Come clean and I'll even edit/erase my posts in this thread if you want, and if you edit yours too, end of drama.
@calamity The new firmware does not stop the test when frame drops are detected, it displays the information on the screen and continues the test. When you update the firmware make sure you also up to date with the software/script included in the zip file.
In regards to the triplebuffer lag, whatever, if you guys don't ever share your finds I guess I can just hope someone with a GILT some day will let the cat out of the bag, or I'll finally get a good-enough camera and find out. *shrug*
It's just extremely sad that developers are SO BAD at dealing and communicating normally with average user people, that they give people no choice but to either give up, or wrestle them in the mud to the bitter end...when a simple few words sentence of honest reply at the beginning would have done it and avoided all the drama.