Replies: 4 comments 1 reply
-
|
Interesting! You should make a PR that implements the fix you demonstrate. |
Beta Was this translation helpful? Give feedback.
-
|
Lag you're noticing is between hardware mouse, and rendered UI. Common solution for this is to when dragging rendered items turn off hardware mouse, and turn on software mouse that sticks to rendered UI. If you use Chrome Browser you could see this if you're using some program that adjust display color temperature according to location and time of day (f.lux or redeye for example), because hardware cursor is unaffected by this color shift change, and software cursor is not, so cursor color changes once switch between hardware and software cursor happens. |
Beta Was this translation helpful? Give feedback.
-
|
sliderrr.webm |
Beta Was this translation helpful? Give feedback.
-
|
Ok I tried changing renderer_mtl.mm and there were random frame drops for some reason and I honestly don't want to invest more time into this, maybe drawables were being discarded without doing the drawn callback, and I'm not using bgfx anymore so its no benefit to me |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
out_foo.webm
You have to use 'CVDisplayLink', record your command buffer there and call [commandBuffer presentDrawable:view.currentDrawable atTime: hostTimeSeconds];, using the 'const CVTimeStamp* outputTime' from the CVDisplayLink argument. Otherwise you get absolutely horrendous frame lag. anyone with a mac can open any bgfx demo and try resizing an imgui window and see for themselves, the mouse is like 5 frames behind
Beta Was this translation helpful? Give feedback.
All reactions