-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No Latency Measurement Output #2
Comments
@Ravnger Does the mouse move left and right during start measurements? Make sure the monitor is not set for HDR mode See if the application is capturing frames, by selecting these keys right shift + Enter the console windows will prompt a message "image file saved" this will save to file a captured_frame.bmp It should have a image of the area you set to capture frames for. If its saving the capture image then next is to make sure the threshold setting is at a level that triggers measurements. |
Same issue here. the Command Prompt outputs "image file saved" but no image shows on desktop, Also I have a GTX 1070 with HAGS enabled and low latency/ ultra low latency disabled. |
@JohnnYDeveloperAHK The captured image should be on the disk where FLM.exe runs from. Check that it has the file created and it has a image. |
I changed the threshold to 10, Now after |
The capture region in the game should be relatively "quite" no random smoke or particles, etc.. Try lowing the threshold down from 5 also, there are a few other setting in the flm.ini file you can also try. Take a look at the users guide "Troubleshooting" currently we are using option 1 if that does not work try option 2. It will show on screen debug values used internally by the tool. Values of BG/SAD/ThSAD > 0 shows the tool is running captures if they are 0's all the time then issues maybe a GPU drive issue or game is blocking ability to do desktop capture. |
@NavNTCMP I tried it again today, and the mouse cursor moved back and forth extremely rapidly, and in about 10 seconds I got this: Edit: I completely re-installed the application, and it still occurs. |
@Ravnger Just checking usage: When ATL+T is set to start measurements using the mouse move option, the game camera scene movements are expected to move left and right without you moving the physical mouse. In some cases, you may have to physically press down a mouse key. The tool sends timed system level mouse move events to measure latency against captured frames. When you physically move the mouse, it interrupts the measurements, and you get spikes (high values) in the reading as the tool now received additional movement while it was calculating the latency. Rapid movements of the game scene left - right indicates the tool is capturing frames well. if the dot "Measurements" do not move, either the captured frames are too noisy meaning there is no stability in pixel transitions in the frames captured, capture region has no changes, or no frames are being captured. You can check if any spike measurements are captured by enabling the show all measurements per line option in the "user options". if all measurements are similar in range (Stable measurements) then that is the latency measured for the game. |
@NavNTCMP I assume DXGI doesn't work in exclusive fullscreen? That's likely why I didn't get any output. As for the rapid mouse movement, you say that's normal behavior, but maybe it's a little too fast. |
Whenever I start and end recording, which I do for around 30 seconds, I see "started measuring" and "stopped measuring" without any latency measurements in between. This happens on all FLM Latency Display Mode settings. The game I am testing is Minecraft Java, and I have positioned the game window within the capture region bounding box.
I am also using the default configuration settings, and have tried re-downloading the application, and it still occurs.
The text was updated successfully, but these errors were encountered: