hodalaplus
New Member
I found this problem because I develope a browser source page using html5 engine,
I set the browser source setting to 60 fps and the page also output on screen that it runing at 60 frame per second perfectly.(so the browser engine using by obs is efficient enought to handle this page.)
But the problem is it just look like only 15~20 fps in obs preview and twitch.
Setting the browser source to 5 will actual down the fps look in preview, but setting fps higher look like not affect, event the program is actual really running 60 frame in obs.
Is this a bug something block the setting number doesn't actual commit when setting fps higher than 30+, or is there a page that can verify my browser souce can run a animated page at 60 fps?
Here is an example page that showing it is running at 60 fps in obs browser source(by showing fps on page),
but actual look like 15~20 fps in obs preview.
https://www.shadertoy.com/view/4ddXW4
(according to another thread, this demo must use --enable-gpu flag to start obs to get a right render of the page,
but this problem also appear in the html5 engine that dont need --enable-gpu flag in my case.)
I set the browser source setting to 60 fps and the page also output on screen that it runing at 60 frame per second perfectly.(so the browser engine using by obs is efficient enought to handle this page.)
But the problem is it just look like only 15~20 fps in obs preview and twitch.
Setting the browser source to 5 will actual down the fps look in preview, but setting fps higher look like not affect, event the program is actual really running 60 frame in obs.
Is this a bug something block the setting number doesn't actual commit when setting fps higher than 30+, or is there a page that can verify my browser souce can run a animated page at 60 fps?
Here is an example page that showing it is running at 60 fps in obs browser source(by showing fps on page),
but actual look like 15~20 fps in obs preview.
https://www.shadertoy.com/view/4ddXW4
(according to another thread, this demo must use --enable-gpu flag to start obs to get a right render of the page,
but this problem also appear in the html5 engine that dont need --enable-gpu flag in my case.)
Last edited: