OBS Shortcut / Hotkeys Stopped Working [Fix/Workaround]

Just a quick fix/workaround for something I bumped into with OBS this past few days - for some reason, the Hotkeys (Shortcut Keys that you press to start Recording, Take Screenshots, etc) seemed to stop working once you took the focus off of OBS itself. For example, if I started OBS, then started a game, and hit the keyboard key that was configured for OBS to Record (while it was in the background), it didn't do anything (eg. / to start recording). I did figure it out though, it was a real easy fix for now; so I wanted to share it here.

There was a Windows Update recently [for me] and so I thought maybe OBS needed more Permissions or something; so I just ran OBS in Administrator Mode - and it worked!

All you have to do is Right-Click the Icon that starts up OBS and choose "Run As Administrator" (possibly under More > Run As Administrator, for example, if using the Start Menu for launching OBS). That's it!
Now you should find that you can start up a game and/or ALT+TAB to the game, leave OBS running in the background, and OBS will faithfully start Recording/Taking Screenshots/etc again. 

Sorry I haven't posted for some time now; my own illness (not COVID) has been acting up this year. A lot. Anyway, HTH

~T

It's Not Just You™ - Paladins (Beta), Having Issues Not Starting or Not Running In 64-bit Mode, Battlegrounds [Notification, Updated As Encountered]

[Currently, this post is mostly in Text-Only Mode, to speed up the ability to publish it... 

I may return to add some Images and/or Screenshots in the future.

This post will be Updated for the next few days, as I encounter new related information.]

If you are trying to play the newest addition to Paladins, Battlegrounds, which is being released in Alpha Testing Stage in their Latest Update - and you are having issues with either (1) the game not launching/starting or (2) the game running in 32-bit mode [which stops you from being able to enter the Battlegrounds, which requires 64-bit mode] - just letting you know, It's Not Just You™...

For the past little while, I have been trying to get into Paladins and try out this new Game Mode, and take a look at any new changes; but I have been running into multiple issues with the game itself. If related Paladins Forums 'everywhere' (Steam, Reddit, Official Forums, etc) are any indication, many, many others are having issues as well.

I wanted to take a moment to make this posting because, even though it seems there are a few people that have 'gotten it running', there are many others, like me, that have not. I wanted to share this experience and related information, so that others may know that, well... It's Not Just Them.

Since I have run into multiple issues and have tries multiple steps so far, I will share them here in Point Form as a list:


Issues Seen/Encountered:

• Game not starting [Launcher will start, but game itself will not show up]
• Game not stopping [Game will not Terminate, Steam says it is Running still, but it is not, or has not started]
• Game not running in 64-bit mode [Game starts in 32-bit Mode and therefore The Battlegrounds can not be tested/run, as it states in-game "64-bit Mode Required"]
• Cannot Verify Integrity Of Game Files, via Steam [Steam states to 'exit any game files or tools' related to the game, but none are running]

Steps Taken/Tried:

• Put "-Use64" [without quotes] into Optional Game Command Line Parameters (Options/Commands) in Launcher
• Put "-dx11" [without quotes] into Optional Game Command Line Parameters (Options/Commands) in Launcher
• Checked "Use 64 bit Client" in Launcher Options [this has never been 'unchecked' by me]
• Verified Cache ['double-checked' the game files through Steam, to see if they are what they are supposed to be]

Unfortunately, since I cannot make the game 'run in 64-bit Mode and enter The Battlegrounds' in a repeated a reliable manner - I cannot make a section containing a 'Fix' at this time... I will continue to observe various Forums and Support Responses, try various Suggested Steps (from the Developers and other helpful Paladin Players (there are a lot of them out there!)), and see if I can make any progress that results in stable and repeatable game launching and gameplay. If I do, I will return here and add it as a 'Fix' section. 

For now, despite them not working for me/on my system, there are a few isolated people that have had success with some of the Steps listed. If you are experiencing any of these issues with Paladins at this time, try some or all of them above. Perhaps one of them will work for you, too. 

Good Luck with it - and try to stay positive, remembering - It's Not Just You™!

Quick Tip: NVIDIA 'In Game Overlay' Stopped Working? Here's How To At Least Get It Going Again [Fix / Workaround That Might Work For Some, Updated 2018-04-26]

Whether it wants to be called Shadowplay, Share or [as of the time of this post] In-Game Overlay; it doesn't really matter to most people I think - we just look for something to record our gameplay once in a while, maybe take some Screenshots, 'and just work'. Thankfully, NVIDIA's In-Game Overlay [or whatever it may be called by the time I finish this post, heh] does just that. Most of the time.


Although I rotate between a handful of different recording programs off and on (such as Bandicam, Action, Playclaw and others - just for fun and also slowly working on another 'Game Recording Comparison' for the future), In-Game Overlay [built into the NVIDIA Drivers, aka "for free"] records when I want, it records a Buffered Loop (a timed, re-recording of 'the last xyz seconds', to save when needed) - and it even takes Screenshots and more. However, sometimes this big fella has just 'stopped working' lately. No saving Screenshots, no Recording, no Error Message, Nothing; and I wasn't sure why... After only a tiny bit of Troubleshooting, I quickly figured out how to at least 'get it going again' and I just wanted to share that here for you all, in a Quick Tip™.

To be honest [I always believe in being completely honest], I am still not sure why NVIDIA's In-Game Overlay stopped working - but I did figure out how to simply get it working again - and here's what I did:

• Once I noticed the Overlay wasn't taking Screenshots, I looked to see if the Overlay itself or more of the (many) NVIDIA utilities were still running, in the Task Manager. They were. [The In Game Overlay's Executable is still called "NVIDIA Share.exe", btw]
• Thinking that something might have gone wrong with the Overlay utility, I opened up NVIDIA's GeForce Experience.
• In GFX [my accro.], I clicked on the 'gear' in the upper-right corner, "Settings".
• In the Settings area, I clicked on the switch/toggle for In-Game Overlay.
• Although it took longer than normal, it eventually turned Off. Clicking it again, it turned back On.

That's it! After those steps, the In-Game Overlay was working once again. Taking a Screenshot, for example, the notification from the Overlay came up, and the Screen was saved. It also started Recording again, without issue. Here is a 'Tutorial Image' of the steps to take:

Tutorial Image of what steps to take to 'restart' the NVIDIA In Game Overlay;
the recording utility built into the NVIDIA Drivers
(Click to see Full Size)

Although I do not have any details on why it failed, I still thought this short 'tip' would be helpful for people that might run into this ("shadowplay not recording" or "in-game overlay not taking screenshots", etc) - so I wanted to share it here. HTH!

...

Update, 2018-03-26: Just a quick Update, that as of March 2018, I have run into somewhat of an extension of this issue, where GFX is no longer responding to this simple 'toggle' of the In-Game Overlay... Doing so (which used to temporarily 'fix' the issue above), now merely results in an 'error' message box, stating "That Didn't Work. Try Restarting Your System.", which although polite, is not very informative as to what caused the error or what else can be attempted to isolate/troubleshoot the issue further:

Doing some more research online, I see many others running into this issue, as well as its' 'extension' here... However, there still is no absolute 'fix' for this problem yet [at least, none that is verifiable and repeatable, which I prefer to have as a qualification to my sharing it here as a "fix"] - therefore, I cannot say for certain what can be done to fix it, even though a wide range of things have somewhat worked for others (some early steps work, others must use further steps), such as:

• Uninstalling/Reinstalling GeForce Experience
• Installing an older version of GeForce Experience
• Utilizing a third-party 'drivers uninstaller' to completely remove NVIDIA's GPU Drivers and Reinstall NVIDIA's GPU Drivers/GeForce Experience [AMD users can get a similar utility directly from AMD]
• Reinstallation/Formatting of entire system (eg. Windows) and Reinstalling NVIDIA GPU Drivers and Reinstalling GeForce Experience

...

Update, 2018-04-26: Just another Update, that as of April 2018, I was looking at this issue once again [since it still occurs, where InGameOverlay/Share just 'stops working' randomly (for no apparent reason)] and found that NVIDIA has this exact symptom listed as an "Open Issue (Windows 10)" in their Driver Updates now (Change Log / Release Notes); which basically means it is 'a known issue', but that they do not have a fix/patch at this time. This was found in the Release Notes for NVIDIA GPU Driver version 397.31, found here:

https://us.download.nvidia.com/Windows/397.31/397.31-win10-win8-win7-desktop-release-notes.pdf

(USA Source of NVIDIA GPU Drivers, Release Notes)

As you can see, under the Windows 10 Section, it lists this very problem as an Open Issue. Good Luck, NVIDIA - I hope you find a solution someday!

Excerpt of the Driver Release Notes, showing this problem as an 'open issue'
Click to see Full Size

Again, once I find out what actually is a solid fix for this issue, I will state so here and post it in big, bold lettering [lol], along with a Tutorial Image (text on an example image of the solution, etc). Until then...