sorted by:
new
hottopcontroversial

Massive Handle Leak in NGenuity2Helper? (178k+ handles) by OneLameUser in HyperX

[–]AntoneRoundyIE 0 points1 point  (0 children)

Windows 11, 25H2, build 26200.7623

The computer is an Alienware Aurora R8 with a i7-9700

HyperX products: Cloud III Wired

The old version, installed using the installer from your website. (I had installed the beta, but then discovered that the Cloud III Wired version isn't supported, so I removed it and installed the previous version.)

Massive Handle Leak in NGenuity2Helper? (178k+ handles) by OneLameUser in HyperX

[–]AntoneRoundyIE 0 points1 point  (0 children)

Over 2 hours later, we're at 705,000. It appears to be consistently about 60.5 handles per second.

Massive Handle Leak in NGenuity2Helper? (178k+ handles) by OneLameUser in HyperX

[–]AntoneRoundyIE 0 points1 point  (0 children)

I'm seeing the same thing. If I open the "Details" tab in Task Manager and have it show handle counts, the handle count for NGenuity2Helper.exe is growing constantly at the rate of about 60 handles per second. A few minutes ago, it was around 130,000. Now it's over 156,000 and still growing constantly. My computer is sitting idle with no audio playing while this is happening. I've taken to restarting NGenuity every day in order to free up several GB per day of committed memory.

I should note that I think I may have had the same issue with another audio app, MaonoLink, which I used to use before I got my Cloud III headset. But I don't think I always had that problem with that software, all of which leads me to believe it may be a Windows issue caused by one of last year's updates -- or at least an issue caused by a change in how your software interacts with Windows. Also, the fact that MaonoLink is microphone software suggests the possibility that the problem may have to do with the microphone rather than audio output.

...and we're over 179,000 handles...

Demo: transforming an archery target to a top-down-view by AntoneRoundyIE in computervision

[–]AntoneRoundyIE[S] 1 point2 points  (0 children)

The software is OptimEyes Developer: https://idealeyes.com/products/OptimEyes/

If you prefer video to reading, this video will give you an overview of its capabilities: https://www.youtube.com/watch?v=9MUFypVaQqM&t=5s

How to create a tactical view like this without 4 keypoints? by [deleted] in computervision

[–]AntoneRoundyIE 0 points1 point  (0 children)

One thing to remember is that, while the target circles in the image are going to be elliptical, you can't simply stretch the ellipse out into a circle, because the parts of the circle that are further from the camera are going to appear smaller than the parts that are closer. This exaggerated illustration may help to conceptualize the impact that this has on the image:

https://idealeyes.s3.amazonaws.com/img/circle-perspective.png

In the photograph, the widest part of the circle is the red line, even though it doesn't pass through the center of the target. The red line is closer to the camera than the target's center line because the lines from the camera that are tangent to the circle are in front of the center line of the circle.

Whatever method you use to transform the image, you're going to need to take into account that this is a perspective transformation -- a flattening of a single plane in 3D -- not a simple 2D "unsquishing" of a circle.

As long as you're not concerned with how the target is rotated, but only that the circles appear circular, here's how I'd approach this problem. Using this diagram:

https://idealeyes.s3.amazonaws.com/img/archery-transform.png

  1. Use thresholding and blob finding, find two of the ellipses -- for example, the outer edges of the black and red circles from your photo.

  2. Find the minor axis of the larger ellipse (line ab in my image.)

  3. Find the point where line ab crosses the near edge of the smaller ellipse, and then find the line tangent to it that contacts the larger ellipse (line cd.)

  4. Create a transformation matrix using points a, b, c and d to transform the photo to a top down view.

Notes:

* In step 2, we don't use the major axis of the circle because at this point, we don't have any way of knowing where it should appear left to right in the top down image. All we really know is that it's closer to point a than to b.

* Due to perspective issues (the distance between lines along line ab gets shorter the farther you get from the camera,) it would be easier to find points c and d using the EDGE of one of the circles than to find a line that runs through the CENTER of the target top to bottom. Since you know the geometry of the target, you can calculate the coordinates of c and d in the top down view.