Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(+1)

Hi, liking this project a lot, hope you are doing well.

I'm using the paid version 0.2 Having problem with ultra wide screens and noticed several problems

1. When I click Detect small bodyparts on wide screen (any resolution above including 2560 1440) it will crash

2. The Filters doesn't seem to work on Ultra wide(3440 1440), tried tuning down resolution works out, (1920 1080 worked best, anything above could cause some filters to be dislocated) .

3. Screen latency to correct delay above 0 will break HDR (making screen super bright and that will cause filters to stop working)

4. Setting Screen Latency to correct delay above 0 frame at 3440 1440 resolution will make the screen glitch and tear (not a HDR issue)

I've also found out that this program works way better with HDR off (not sure if this is just me being slow to figure but you might include in an announcement for other people) .

Logs:

Windows version : Microsoft Windows NT 10.0.26100.0

CPU : Intel(R) Core(TM) i9-14900KF, Cores : 24, Threads : 32, Max clock : 3200 MHz

Adapter 0 NVIDIA GeForce RTX 4090

Screen Rect 0 : Rect { X = 0, Y = 0, Width = 3440, Height = 1440, Top = 0, Bottom = 1440, Left = 0, Right = 3440, Location = Point { X = 0, Y = 0 }, Size = Size { Width = 3440, Height = 1440 }, TopLeft = Point { X = 0, Y = 0 }, BottomRight = Point { X = 3440, Y = 1440 } } Orientation : 1

Screen Rect 1 : Rect { X = -1080, Y = -127, Width = 1080, Height = 1920, Top = -127, Bottom = 1793, Left = -1080, Right = 0, Location = Point { X = -1080, Y = -127 }, Size = Size { Width = 1080, Height = 1920 }, TopLeft = Point { X = -1080, Y = -127 }, BottomRight = Point { X = 0, Y = 1793 } } Orientation : 4

Adapter 1 Microsoft Basic Render Driver

Starting Screen Recorder

Max FPS of Overlay set to 164

Frame Latency of screen set to 0

DXGI initiated with a resolution of 3440 x 1440

DXGI using Video card 0 and monitor 0

Max FPS Record start at 164

MaxFPSRecord at 164

Detection starting using  model : ./model_fp16.onnx

Max FPS Detection start at 164

Use double Detection start at False

MaxFPSDetection at 164

DXGI initiated with a resolution of 2560 x 1440

DXGI using Video card 0 and monitor 0

Max FPS Record start at 164

MaxFPSRecord at 164

Detection starting using  model : ./model_fp16.onnx

Max FPS Detection start at 164

Use double Detection start at False

MaxFPSDetection at 164

Now usePreciseEyesDetection is at 1

Now usePreciseEyesDetection is at 1

Frame Latency of screen set to 1

Frame Latency of screen set to 0

Frame Latency of screen set to 1

Frame Latency of screen set to 2

Frame Latency of screen set to 3

Frame Latency of screen set to 4

Frame Latency of screen set to 5

Frame Latency of screen set to 4

Frame Latency of screen set to 3

Frame Latency of screen set to 2

Frame Latency of screen set to 1

Frame Latency of screen set to 0

DXGI initiated with a resolution of 2560 x 1440

DXGI using Video card 0 and monitor 0

Bad format from duplicated desktop :R16G16B16A16_Float

Frame Latency of screen set to 1

Frame Latency of screen set to 0

Frame Latency of screen set to 1

Frame Latency of screen set to 2

Frame Latency of screen set to 3

Frame Latency of screen set to 2

Frame Latency of screen set to 1

Frame Latency of screen set to 0

Frame Latency of screen set to 1

Frame Latency of screen set to 2

Frame Latency of screen set to 3

Frame Latency of screen set to 4

Frame Latency of screen set to 5

Frame Latency of screen set to 4

Frame Latency of screen set to 3

Frame Latency of screen set to 2

Frame Latency of screen set to 1

Frame Latency of screen set to 0

Error during DXGI capture : HRESULT: [0x887A0026], Module: [SharpDX.DXGI], ApiCode: [DXGI_ERROR_ACCESS_LOST/AccessLost], Message: The keyed mutex was abandoned.

DXGI initiated with a resolution of 3440 x 1440

DXGI using Video card 0 and monitor 0

Bad format from duplicated desktop :R16G16B16A16_Float

Frame Latency of screen set to 1

Frame Latency of screen set to 0

Error during DXGI capture : HRESULT: [0x887A0026], Module: [SharpDX.DXGI], ApiCode: [DXGI_ERROR_ACCESS_LOST/AccessLost], Message: The keyed mutex was abandoned.

DXGI initiated with a resolution of 3440 x 1440

DXGI using Video card 0 and monitor 0

Bad format from duplicated desktop :R16G16B16A16_Float

Frame Latency of screen set to 1

Frame Latency of screen set to 0

Frame Latency of screen set to 1

Frame Latency of screen set to 0

Frame Latency of screen set to 1

Frame Latency of screen set to 0

Error during DXGI capture : HRESULT: [0x887A0026], Module: [SharpDX.DXGI], ApiCode: [DXGI_ERROR_ACCESS_LOST/AccessLost], Message: The keyed mutex was abandoned.

DXGI initiated with a resolution of 2560 x 1440

DXGI using Video card 0 and monitor 0

Bad format from duplicated desktop :R16G16B16A16_Float

Error during DXGI capture : HRESULT: [0x887A0026], Module: [SharpDX.DXGI], ApiCode: [DXGI_ERROR_ACCESS_LOST/AccessLost], Message: The keyed mutex was abandoned.

DXGI initiated with a resolution of 1920 x 1440

DXGI using Video card 0 and monitor 0

Bad format from duplicated desktop :R16G16B16A16_Float

Error during DXGI capture : HRESULT: [0x887A0026], Module: [SharpDX.DXGI], ApiCode: [DXGI_ERROR_ACCESS_LOST/AccessLost], Message: The keyed mutex was abandoned.

DXGI initiated with a resolution of 2560 x 1440

DXGI using Video card 0 and monitor 0

Bad format from duplicated desktop :R16G16B16A16_Float

Error during DXGI capture : HRESULT: [0x887A0026], Module: [SharpDX.DXGI], ApiCode: [DXGI_ERROR_ACCESS_LOST/AccessLost], Message: The keyed mutex was abandoned.

DXGI initiated with a resolution of 1920 x 1080

DXGI using Video card 0 and monitor 0

Bad format from duplicated desktop :R16G16B16A16_Float

DXGI initiated with a resolution of 2560 x 1440

DXGI using Video card 0 and monitor 0

Bad format from duplicated desktop :R16G16B16A16_Float

Closing...

Screen recorder thread ends correctly.

(+1)

Hey ! Thanks for your logs, it's very interesting since I can't test HDR myself.

In 0.3 Hotscreen don't allow HDR at all. You said "Screen latency to correct delay above 0 will break HDR" and I also suspect that even the detection doesn't work with HDR.

I will try to handle HDR in next updates. It's not hard but I can't be sure that it works when I publish it.