Recorder overlay disappears or crashes when entering fullscreen mode in chrome games
-
@FBX-Recorder Thanks for the response. I tried re-installing the driver and setting the encoder in FBX to the nvidia one (there's only one nvidia option, the other two are the intel ones) and it still doesn't work, in fact, it's worse...the overlay for the "START: (hotkey)" in regular view only has the top ~10% of the prompt box (i.e. just the black edge, not the actual words). Sometimes it appears when I go into full screen...one thing I noticed is that the prompt box and text are smaller when I go into full screen, so maybe it has to do with resolution? Thanks.
-
Ok, very strange. Can you:
- Go to the Support tab and send us a report
- Try the "Intel Quick Sync" hardware encoder
Thanks.
-
I sent the report, thanks. Using the Intel GPU doesn't work either...
I got the recorder to work on some sites by messing with the NVIDIA control panel settings, but some of the FBX settings (in the "SETTINGS" tab) don't seem to work, namely: the "When you switch away from the game being recorded" setting, when it's set to "Pause recording..." or "Continue recording", it still stops recording when I switch away, and also the "Clicking X on the main window", when it's set to "Minimize...", it still exits when I click the X...I'm not sure if these things are related...?
Thanks.
-
Hi. We need you to get v2.13 of FBX, just released on Tuesday and send another report. Thanks!
-
I downloaded the version from the "download" link for the main site but it's 2.12, not 2.13...report sent anyhow.
Thanks!
-
Thanks. 2.12 is correct - my mistake. Can you tell us what game you are trying to record. So the main problem is still that you switch to fullscreen in Chrome, start recording, and the FBX overlays disappears?
-
Well, on my previous laptop (identical in specs to this one except slightly different and superior graphics card as described in the first post), when I opened Chrome the overlay with the prompt: "START: [hotkey]" appeared immediately and worked consistently when I entered full-screen mode. Now it's not appearing at all when I open Chrome and sometimes appears in full-screen mode (although at a smaller size/higher resolution) and when I press it often it disappears and I end up with a 1 sec video that "video failed to load" in the Recordings tab. I've tried with different sites and have the same or similar issues all around.
Thanks.
-
The developer has taken a look at your report - thanks. If you want to record Chrome in fullscreen mode, you need to switch to fullscreen and then start recording, not before. If you keep getting problems, then close all instance of Chrome and restart it.
These days Chrome keeps running in the background even if you close all its windows, so you need to go to its tray icon, click that and select 'Exit' from its menu.
The reason recording is working differently on the two laptops may be because Chrome uses hardware video acceleration on one and not the other. It can vary from PC to PC. FBX can only record Chrome when its using hardware acceleration. if you're not seeing the FBX overlay you could google for how to force Chrome to use h/w acceleration.
Hope this helps!
-
Yeah...I do record AFTER switching to fullscreen...
Thanks for the info on hardware acceleration. I checked and hardware acceleration is disabled. I followed the all the steps to enable it and the associated processes in chrome and when I start chrome and check the "chrome://gpu" tab it said the hardware acceleration was enabled, but then when I open FBX recorder and switch back to that tab it says software only, hardware acceleration disabled :(. I tried this several times restarting things but every time, after I start/run FBX the hardware acceleration changes from enabled to disabled...
Thanks!
-
Unfortunately Chrome recording doesn't work in all cases, and it looks like we're unlikely to get it working that PC. One last thing you could try is a driver update. We're working on a new recording system that will just record the screen contents, so it should always work for Chrome.
