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

GTAV/Online - 'Black Chrome' Reflections Issue Fixed In Latest AMD GPU Drivers [Notification]

Just a quick Post to let other AMD GPU users know that AMD has, as of today, fixed the issue where enabling Reflections Antialiasing made reflections not appear and/or made chrome appear 'black'. 

Here is a Screenshot example of what it looked like:

(from my Screenshot at https://steamcommunity.com/sharedfiles/filedetails/?id=2369464566 )

And here is a Screenshot example of what it looks like now:

It's Fixed! Thanks, AMD 👍

The latest AMD Driver Release Notes, as of this post, can be found here, if interested:

https://www.amd.com/en/support/kb/release-notes/rn-rad-win-21-1-1

HTH ~T

No Man's Sky 'Not Starting' or 'Failing To Launch'? - Here's What Worked For Me [Notification/Tutorial]

[Text-Mode Only: This posting is being shared as Text-Only, to speed up the ability to share it, at this time. 

I may return to add helpful screenshots/diagrams/etc, at a later date.]

Update 1: Added link to driver download, for the version that worked for me (NVIDIA website)
Update 2: Oddly, the GOG version was working - but as of 09.02 neither game starts up at all

For the past week or so (since the BEYOND release) I've had a problem trying to get back into No Man's Sky to check it out... The game just wouldn't start/launch. I noticed that it was popping up in the Windows Taskbar but then it would 'close itself' or 'crash' - either way, resulting in the game closing up and I wasn't able to play and try out the new stuff!

After messing with it off and on for about a week, I finally figured out something that worked - No Man's Sky actually starts now, and I can play! Here are the things I tried at first:

• Restarted PC/system
• Re-installed NMS
• Verified Cache (Steam version**)
• Disabled Anti-Virus temporarily while running game (third-party AV, Windows Defender, etc)
• Ran game as Administrator
• Ran the Compatibility Troubleshooter for the game executable (Windows 10, did not affect result of game closing itself upon starting it)
• Dusted out system and hardware (to help with potential overheating, corruption/errors due to heat and dust issues, etc)
• Re-installed NMS to C: drive (Windows/main drive/partition, then moved NMS back to other SSD [I had it originally on], as it made no difference)
• Re-installed GPU drivers (videocard 'system files that Windows uses to 'talk' to the hardware' [is how I describe "computer drivers" to others])
• Ran Windows Update (there was an Update package, did not affect result of game closing itself)
• Considered re-installing Windows 10 (then did not do it - this time - lol)

I tried a ton of other little things as well, like re-installing Visual C++ libraries for Windows (system files that are part of Windows that many, many programs utilize) - it had apparently worked for many people, and I saw this mentioned in a few different Game Support forums (eg. Reddit, Steam, GameFaqs, etc) if you want to try this, these can be found at the Microsoft website, here:

https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

With all of these steps (many of them mentioned by helpful users on multiple forums online - most of them I knew and tried myself), at some point, they would 'get the game working' for many people. Sadly, not for me. I had to hunt around and 'hack away at the bushes of the problem jungle' on my own for awhile... Finally, I found something that got No Man's Sky working for me - here is what I did:

'Roll back' the GPU drivers (videocard system files that Windows uses to 'talk' to the hardware) to an older version, then re-install the latest version of the GPU drivers (non-'clean' install). BOOM it worked! 

Here is the steps I took that finally got No Man's Sky working:

• Regress the GPU drivers [re-install older and older versions of the GPU drivers] until the game works (for me, that meant I re-installed older drivers over and over until NMS started 'fully and without issues' - for me, that was NVIDIA GPU Driver version 391.01 - this driver can be downloaded directly from NVIDIA's website, however, their own Search for Drivers does not go back that far... I found these older versions by going to Google and searching "NVIDIA driver 391", for example, then following a Link that goes to NVIDIA's Driver website [as opposed to other third-party websites, not that they are always 'bad', some are great, but I wanted the official NVIDIA drivers from them, for this]). If you want to try the exact version I found worked for me, the link to NVIDIA's release of that Driver is here:
  https://www.nvidia.com/download/driverResults.aspx/131443/en-us
• Once game is verified as 'working without issues', re-install latest GPU Driver (version 436.xx as of the time of this posting) 'on top of' the currently installed Drivers [newer versions of NVIDIA Drivers 'uninstall' the older versions, but just do not chose the 'clean' install, where it deletes your Profiles, etc]. I found I also had to select to install the "NVIDIA HD Audio" and "NVIDIA 3D" options, as well...

That's it!

Although professionally I am a Computer Tech, I'm not a Developer/Programmer, so I'm not 100% sure why it got No Man's Sky working finally (but I can assume some things, like the game needing some older Windows System libraries that got 'corrupted' or lost, somehow, and other things that could have occurred) - but I'm just glad that the game runs once again. 

Of course, this may not be your specific issue with NMS not starting for you, my dear reader; but perhaps it can help the game to run for you, too. Good Luck with it - and a many-a-Good-Journey to you, Traveller! 

Addendum: As of 09.02, both versions (GOG and Steam) now do not start up (they do not run properly) - the game appears in the Taskbar for a moment, then closes itself. I shall try some Troubleshooting again, and if I find another 'fix', I will return to share it here...

**Oddly, the Good Old Games (now GOG.com) version, that I received as a gift a while ago, worked fine... Only the Steam version of NMS had issues... During the course of Troubleshooting the Steam version, the GOG version stopped working [lol] - then, after 'fixing' the Steam version, the GOG version was working once again. Possibly, the issues were related, but I am not sure. Hopefully, one of the steps mentioned herein (or my 'final solution' step [maybe I should rename that]) will work for you

And More: How To 'Browse' Steam Screenshot Folders with PaintShop Pro [Fix / Tutorial with Steps]

After playing around with both Steam and PaintShop Pro recently, I have found a 'Fix' for an issue where PaintShop Pro was not able to see any Screenshots in the Steam-created Screenshot Folders, when trying to "Browse" within PaintShop Pro... Here is what it looks like in PaintShop Pro when trying to "Browse" to a Steam Screenshot Folder within the graphic editing application itself:

As seen above, the Browsing utility in PaintShop Pro says "No Files Found" [circled in Red] - but obviously there are files/images in the folder, as opening the same folder with Windows Explorer just below it (Windows 10) shows there are tons [I take way too many Screenshots, heh]. 

I examined the Properties of the Screenshots generated by Steam, but they are nothing out-of-the-ordinary, they are typical .JPG (JPEG format) image files. 

PaintShop Pro is able to "Browse" other folders I have with Screenshots, so perhaps it had something to do with Permissions [was my thinking]...

I ran PaintShop Pro as Administrator, but it seemed to make no difference. 

I then examined the Preferences of PaintShop Pro. I have been in there before, to change some of the behaviour of the editing program, namely Caching and Colour Correction/Import and Precise Cursors [I really prefer the Precise Cursors, I Recommend using them!]

In PaintShop Pro's Preferences, I found there are some Exclusions that were already in the program [built-in, on install] that, while helpful, interfered with where Steam keeps game Screenshots by Default.

These Exclusions, in PaintShop Pro, are located in:

File > Preferences > General Program Preferences 

In the Manage category, Excluded Items section, there is a button for Uncataloged Folders.

[These folders are not utilized by PaintShop Pro, and while I'm not sure why, I assume it is because they are large System Folders and may result in duplicates or 'garbage' images being read, which would take up time and excessive space for Thumbnails]

In these "Uncataloged Folders", I found a listing of
C:\Program Files
and Steam itself is installed (by Default, in Windows) to
C:\Program Files (x86)

It appears that PaintShop Pro thinks that "Program Files (x86)" is part of, or is, "Program Files" [due to the space in the former] - so it excludes that folder from use; thus, it is not possible to Browse those folders with PaintShop Pro [was my thinking].

Removing the "C:\Program Files" from the Uncataloged Folders, I tried to open a game's Screenshots Folder (unchanged, where Steam normally keeps them by Default) with BROWSE in Paintshop Pro...

It worked! 😁

That was it then - it appears removing that Folder (C:\Program Files) from the Uncataloged Folders category, is all that needs to be done and Paintshop Pro can then Browse and Catalogue [create Thumbnails for] those Folders.

In the image I created just below, there is an open Steam Screenshots Folder in the background, showing that Steam's Screenshot Folders indeed now work with PaintShop Pro.

Here is a large collage/screenshot showing what I found and how to change it [It looks a little busy/crazy - so I will explain it just underneath, heh]:

In the 'Tutorial' image above, I have indicated the following areas below on how to 'fix' this issue with PaintShop Pro:

» The Large 'Green Arrow' shows that I have a Steam Screenshot Folder open in the Browse/Manage are of PaintShop Pro [It now works! There are Screenshots seen in the background middle workspace] 

» The Smaller 'Yellow Arrows' are indicating the 'trouble folders' of "Program Files" and "Program Files (x86)" that PaintShop Pro seems to have issue with [These folders, generated automatically by Windows, hold most Programs and installed Applications. The 'x86' Folder is generally used for backwards-compatibility with older (32-bit) Programs] 

» The Red 'Roman Numerals' (I., II., etc.) indicate the Steps To Take to navigate to the "C:\Program Files" listing in the "Uncategorized Folders" section of the Excluded Items in PaintShop Pro 

» The Red 'Information Icon' is simply the Panel that must be opened, using these Steps, to see/edit the Folders to be discluded from the "Browse" capability of PaintShop Pro

Here are the Tutorial Steps, in order, to remove this Exclusion and allow PaintShop Pro to Browse/Manage Steam Screenshot Folders and Images:

1. Click on "File"
2. Select "Preferences"
3. Go into "General Program Preferences "
4. Click on the "Manage" section on the left of the Preferences panel that comes up
5. In the "Excluded Items" section on the right, click on the button for "Uncataloged Folders"
6. In the "Uncataloged Folders" panel, select the "C:\Program Files" listing and click on the Delete button
7. Click Ok, above the Cancel button
8. Click Ok, to close the Preferences Panel
9. You are now back at the main PaintShop Pro interface

That's it!

Hopefully this finding can help others that want to use Paintshop Pro with Steam Screenshots, now easily Browsing them all (with Thumbnails being Cached for faster access/listing) with PaintShop Pro.


Hope That Helps!

~ Troy from The Game Tips And More Blog



[Note: I am not affiliated with Corel or Steam/Valve, and have not, and will not, receive any compensation in any form, for mentioning them here. I am merely an enthusiastic gamer who utilizes their products, and likes to share helpful information for others when I can]

Quick Tip: How To Run SimCity 4 in 1920x1080 (Widescreen) Resolution, as of 2019.01 [Tutorial]

Update 2019.03.14: Added Screenshot Example of SimCity 4 running in Widescreen (16:9/1.78 Aspect Ratio)

[Text-Only Mode - this is currently being posted in Text-Only Mode, to speed up posting as soon as was finished, to help others as quickly as possible. I may return here and add some related Screenshots... Soon™]

Recently, I've been getting back into game like SimCity (2013) and SimCity 4 (2003) [found on EA/Origin and Steam, respectively], having fun building up cities and looking forward to large skyscrapers filling the skyline, keeping my Sims happy as they churn through their little lives... Looking through a SimCity forum, while I was reading up a bit about Omega (which is 'new to me') I came across someone posting a Thread asking about 'how to run SimCity 4 in 1920x1080' resolution. I saw some replies from other helpful people, but oddly, none of the options/command-lines worked [as of the time of this posting], with typed-in options such as "-w" (for running in Windowed Mode) and so on... Wanting to help, I went experimenting in Steam's SimCity 4 that I owned and looked a bit more online about other possible solutions as well - and I eventually found out what works, as of today! Here is what worked for me:

• In Steam, where SimCity 4 is listed in your game Library, Right-Click on the game name and Select (Left-Click) Properties.
• In the center section, click on the button labelled "Set Launch Options...". This adds commands to the game that would be 'typed in and utilized', if the game was run in that type of interface.
• In the box of Launch Options, type (or copy-paste) the following into the area:
  
  
  -CustomResolution:enabled -r1920x1080x32
  
  
  [be sure to include the hyphens and have only one space between the two commands]
  
• Click on OK to close that panel, then click Close to close the Properties of the game in Steam

That's it! 

Running the game (and after the Introduction Cinematic/Movies play [if you have not disabled them] as they are rendered and play in a fixed resolution), you should find the territory/region screen gloriously taking up all of your screen space... Here is what it will look like:

Example of SimCity 4 (Steam version shown) running in Widescreen (16:9 Aspect Ratio) Mode in Windows 10,
after following the steps shown above [other steps found online did not work for me personally]

Have fun building up your Sim City! 

[Don't forget to take lots of Screenshots! heh]

~T

Dungeons - How To "Sacrifice Gold" to The Zombie King ("Cash Cow" Quest) [Tutorial Steps]

[Text-Only Mode: This post is currently in Text-Only Mode, to speed posting of it, to help others as quickly as possible (after thinking of it). I will return to this post and add related Screenshots....Soon™]

Recently, I was playing DUNGEONS - the Dungeon-Keeper-esque 'make dungeons for NPC heroes to die in' game - the original/first one, from 2011 (Realmforge Studios/Kalypso Media Digital).

In it, I ran into having to 'send Gold' to your superior in the game ('your Boss'). Gold isn't the only thing you have to send/tribute with; but on one particular level, I ran into an issue where I could not satisfy the Quest - despite trying to do exactly what it wanted. I finally figured it out on my own, and wanted to Share the issue and resolution/fix here, to possibly help others...

I ran into this issue on the level "Sleepy Manor", where there is a Quest called "Cash Cow", which requires you to tribute ("sacrifice") 500 Gold to The Zombie King (your 'boss' in the game). Now, there is a pillar near your Dungeon Heart, that when clicked on, states "use this to send resources to your superior" - but not how to do it....

I walked my Dungeon Lord up to the pillar and Left-Clicked on it (which just brings up the popup information about it) and tried Right-Clicking on it (which did nothing except make a small noise) but nothing happened. The Quest (called "Cash Cow") was still listed on the left side of the screen in white text - despite my having more than enough Gold to complete this Quest... So, I looked around online a bit, in forums, etc. but did not find any specific information on this step and how to do it. I even looked at the Manual that comes with the game, to see if it listed how to do it. Nothing. Lastly, I asked in the usually-helpful Steam Discussions (Forum) for the game. There was no response for a few days, so I continued to 'Troubleshoot the issue'...

I finally figured out that you can't just click on the pillar, you have to first switch to First Person view mode AND THEN Right-Click on the pillar. There is no notification that it is completing the Quest, but it will be completed, if you have enough Gold. To summarize the steps, here they are, listed just below.

To help others, here is how you "sacrifice gold" to The Zombie King in Dungeons: 

» There is a pillar near your Dungeon Heart, which states to 'use it to send resources to your superior' (but not how to do it)

» You can't just walk up to it or stand near it and left-click or right-click on it, it won't work (as of the time of this posting)

» You have to switch to First-Person view mode (via the "Through The Eyes Of The Lord" Spell in your spellbook/toolbar) and then Right-Click on the pillar while in First-Person mode (which is actually just a close-up Third-Person with a fixed camera floating behind the player)

» To verify it was done/completed (there is no message/popup that tells you it was done), look at the left side of your screen, where the 'quests' are listed; the white text listing to do it (saying "CASH COW - Sacrifice 500 Gold...") should have disappeared

That's it!



Hopefully, this Quest will now be complete for you, as it was for me. I also posted this in the Discussion Thread at the Steam Official Forum for the game [that I had asked/started], to make sure that others running into this now know how to get the quest completed.

HTH!

Fallout 76 - Stuck In Power Armor? Here's One Way To Get Out Again... [Tutorial]

[Text-Only Mode: This post is initially being Uploaded as Text Only, to speed up posting time and enabling it to reach people faster. I may return to this post and add some Screenshots for it... Soon™]

I personally ran into the issue of "not being able to exit my Power Armour" earlier this week - then saw that literally dozens and dozens of players have run into this in Fallout 76, after looking around online. Now, the game just officially launched Online only a couple weeks ago almost to the day, so I expect there to be some issues and/or bugs (not many Online game launches are 100% Bug-Free and Problem-Free). Bethesda does helpfully have a method posted at their Support Site for 76, but sadly, that method did not work for me personally. Here then, is my method that got me free of my 'Starcraft2-like-mobile-prison' of Armour - hopefully it can work for you too, friends:


(Taken from my original posting at the Official Bethesda Game Forums, reworded slightly)


If I may help, with something to do when this happens:

• Stash or otherwise get rid of all Fusion Cores, except the one in the Armour
• Deplete the FC until Zero (Power Attacks in the PA help)
• DO NOT EXIT THE POWER ARMOUR once it reads "Zero, get the hell out"
• Restart Game
• Upon entering a new game, you should be able to Exit the PA by holding the key used to enter it

That's it! Now you should be free of your metal moving tomb and able to utilize Workbenches in the world, once again...

Initially, I had not found a solution that worked for me anywhere online (in Forums, etc) - and as those who are experiencing this know, being 'stuck in your Power Armour' impedes the game quite severely actually, as you cannot use Workbenches/Workshops at all and cannot even Repair your Power Armour (as you cannot Exit it, to Repair it in a Power Armour Station) - so, I opened a Ticket with Bethesda about it, a week ago. They were actually quite speedy to Reply, pointing me to their online Support Site, at their Knowledge Base, where there was an Article stating two things to try (one of 'just logout' and another of 'unequip pieces of armor and wait two minutes'), found at: 

https://help.bethesda.net/app/answers/detail/a_id/43986/kw/stuck%20power/

As of the time of this writing, I see that they have also Updated the Article (just today), adding a slightly-modified version of my method above, that I submitted to them as a Reply (where I "found out a way that worked for me, which was not one of the other two helpfully-suggested methods") - that's fine with me if they found a repeatable method of their own; as long as others are helped in escaping their 'mobile prisons of steel', out there! 

Hopefully, the incoming December 4th Update of 76, will help with this issue, clearing it up for everyone. Until then, try out my method above - perhaps it will be the one that works for you, dear reader - and See You In Appalachia!

Quick Tip: NVIDIA "Device Not Found" Issues Possibly Fixed In Latest Driver Update [Notification]

Recently, I have been running into an issue I hadn't seen since I last owned an NVIDIA videocard** - a "Device Not Found" error. Thankfully, this problem may be seen even less now, as a recent NVIDIA Video Driver Update, released just now, may fix this issue. If you have been running into a "Device Not Found" error, or the possibly-related "No DirectX 10 or 11 adapter or runtime found" error - with an NVIDIA GPU - grab the Driver Update and see if it makes a difference for you!



I've had a few of these occur the past while, although moreso the last time I owned an NVIDIA videocard**, this 'old issue' popping up again only recently, with GTAV (Grand Theft Auto 5: "No DirectX 10 or 11 adapter or runtime found") and off/on with Playclaw [doing some testing with it for a future 'comparison/shootout' of various game recording programs, I was running into "cannot start encoder for empty frame" and "device not found" errors]. To be fair, AMD GPU's also have similar issues [such as, one which states "The Device Has Restarted", usually after a game/screen 'freezing up' on your for a few seconds]. With NVIDIA releasing an Update today, that stated in the ChangeLog/PatchNotes that an issue of this type has now been 'fixed', hopefully we'll be seeing these errors even less:

The NVIDIA Driver Patch Notes, stating an issue has been fixed that may directly solve these problems.
Click to see Full Size

The actual 'fix' states that the "Driver may get removed after the PC has been left idle for an extended period of time". I say that this may be related to the issue(s) stated above, because I found that after leaving the system on all night, going to play a game the next day, I would often run into these issues/errors (moreso than if I had been continually using the system). These errors would pop up even if I had the GPU Power Saving settings on "High Performance" or "Always On" [I live in an apartment where electricity is included in the price of the rent, so I don't mind leaving the system on 'all night' to perform tasks (backups, video compression, etc)]. A simple Restart usually 'fixes' everything, no errors come up after that, no "Device Has Been Removed" or anything - that is, until I leave the system on 'all night' again... Then these types of errors show up, once I try to utilize the system in the morning. So, hopefully this latest Driver Update from NVIDIA solves, or at least reduces, these types of errors.

Example of one of the errors this Driver Update may possibly fix: "No DirectX 10 or 11 adapter or runtime found"
(Experienced with an NVIDIA GPU while trying to play/startup GTAV after not touching the PC for a long time, shown Full Size)

If you are running Windows 10 and an NVIDIA GPU, be sure to grab this latest Driver and see if it helps reduce their occurrence for you - I'll try to return to this post and let you know if it does/doesn't for me, too. GL!



[Note: I apologize, but I have misplaced/lost a few Example Screenshots of the errors stated herein. Ones showing the "Device Not Found/Ready" or "No DX3D Device Found" or "d3d11: failed to create device" and similar errors, all of which I have run into when trying to use the system after not interacting with it for a while, and took Screenshots of. I will continue to look for these as I can, and once I find them, I will add them into this posting.]




** Disclaimer and Personal Veracity Statement: Although I currently own an NVIDIA GPU, I have owned both AMD GPUs and NVIDIA GPUs in the past, and will do so in the future. I have no personal preference between the two, purchasing one or the other as Upgrades depending on my needs at the time and my financial limitations at the time I need to Upgrade. I have not, and will not, receive any compensation for mentioning either companies' products herein. I am merely an enthusiastic user (of both) and try to share helpful information about them, as I can.

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™!

The Elder Scrolls Online - "PatchManifestError" In TESO Launcher [Workaround]

[Text-Only - This post is initially Text-Only, to allow posting this as fast as possible, to help others.
I may return and add additional graphics/screenshots pertaining to the article... Soon™]

Just now, I ran into an issue starting up TESO, where the Launcher gave an error message - oddly, it was slightly different than the message my Gamer Wife beside me got - one of us got "Error 210" while the other got "Error 206". Here is an example of what the Error Message within the TESO Client Launcher looks like:

Popping into the Steam forum and the Official Bethesda/Zenimax Forum for the game, I saw a number of people mentioning they are getting this too, just today, like me. So, I wanted to come here and post a 'quick fix' that can get past the error message and allow fellow gamers, like me, to be able to play the game as quickly as right now, tonight [actually it's more of a 'workaround' than a true 'fix', as it doesn't solve whatever issue is happening with the Launcher/Client/Servers... I will post this as a "Workaround"].

Similar to an earlier issue with the TESO Launcher I talked about here at The Blog, the 'workaround' involves bypassing the Launcher itself and starting up the game manually via the Executable files... The instructions to do this are below.


For the Steam Version of TESO:

• Open Steam
• Right-Click on TESO in the Library and choose Properties
• Click on the "Local Files" tab
• Click on the "Browse Local Files" button to show the directory/folder of the game
• Navigate into THE ELDER SCROLLS ONLINE > GAME > CLIENT folder
• Double-Click on "eso64.exe" to launch the game (or "eso.exe" if running 32-bit Windows/Game

For the Standalone Version of TESO:

• Right-Click on the Shortcut (the icon that runs the game) on the Desktop (or in the Start Menu) for TESO and choose Properties
• Click on the "Open File Location" button in the Properties of the game shortcut
• You should find yourself in a Windows Explorer windows, looking at the "Launcher" folder of Zenimax Online
• Go up one folder level to "Zenimax Online" (click on the Zenimax Online folder in Explorer)
• Navigate into THE ELDER SCROLLS ONLINE > GAME > CLIENT folder
• Double-Click on "eso64.exe" to launch the game (or "eso.exe" if running 32-bit Windows/Game)

That's it! Now the game should start up and you will just have to Login within the game itself.

Unfortunately, I do not know what has caused this error, and I have not seen any Official Postings by Bethesda/Zenimax to explain it, as of the time of this writing. Although it appears to be some sort of Server/Launcher error, I cannot say specifically at this time. However, having testing this Workaround on different machines and with both the Steam Version of TESO and the Standalone/Web version of TESO, I can safely say that this should work for you, fellow gamer.

Hopefully that helps - and See You In The Game!

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...

Fallout 1 - Get It For Free... Happy 20th Birthday! [Notification]

Just a quick notification that, in celebration of the Fallout's series debut, exactly 20 years ago to this very day, it is Totally Free on Steam, right now, from Bethesda - but only for today... Grab it before the end of the day and play one of the most RPG-Genre-Expanding, Post-Apocalyptic-Exploring Classics of PC gaming. Have fun (and thank you, Beth)!

http://store.steampowered.com/app/38400/Fallout_A_Post_Nuclear_Role_Playing_Game/

Addendum:

After trying the game out (not playing it since I had the CD version way back when!), at first, all I got was a Black Screen, but I could hear the audio of the game playing in the background... After doing some light troubleshooting, including re-installing DirectX and other steps, the easiest 'solution' that I eventually found was to simply choose the "Classic Version" from the Steam Launch Options. Here is what that looks like, below (these options did not show up if I used the Desktop Shortcut or clicked on the .EXE file to start the game, but they appeared consistently if I used the PLAY button in the Steam Client):

Tutorial Screenshot of simply choosing the alternate version of the game to run, if you encounter a 'black screen', where you can hear the audio of the game, but not see anything else concerned with the game
(Click to see Full Size)

After choosing that version, above, the game repeatedly ran fine with audio and video together in harmony, on my system (currently an AMD FX-8350 CPU and NVIDIA GTX 1060 GPU running Windows 10). I hope it works for you dear reader, as it did for me, if you run into that little initial problem... Enjoy!

[Note: It is unclear at the time of this posting, if the game it completely free 'forever', or if it is just 'free to play' for the day - UPDATE, it indeed seems to be permanently part of my Steam account - a nice 'gift' from Bethesda!]

Battlefield 1 - DirectX Error "GetDeviceRemovedReason" [Workaround]

At first, because of the phrasing of the error, I thought it might be Hardware, namely my GPU (Graphics Processing Unit, the Videocard); but since that was working fine with literally, all other games - playing in longer gaming sessions even [and I know for sure that I wasn't actually physically pulling out my videocard while playing ...I think] - I omitted that possibility (for now) and focused on a potential Software approach, which meant checking configuration...

Looking at the Settings for the game then, I tried reducing everything down to the Lowest Possible Settings; to reduce the load on the GPU and the load in the processing of the game itself. (With lowered settings, there would be less data being streamed from the game, less being extracted from the compressed/encrypted files of the game, less being calculated and drawn, less everything). If there was a problem with how game data was being handled, this might being it to light [note: an issue with integrity of the files would not be detected this way, this is more of a data handling troubleshooting step; integrity of the game files can usually be checked/verified with a Repair/Verify through the game client or if that doesn't help, a Reinstall of the game usually assures accurate game files (barring Drive/RAM file handling (Hardware) issues - which is another tangent/issue altogether, heh) - screenshot of where to run a Repair/Verify of the game files for BF1, below].

Example of the Location of where to Repair the game files in the Origin Game Client, showing Battlefield 1 in 2017
(Click to see Full Size)

Nope. Crash. Error [which I lost the clean Screenshot of, of course - but a version of it is in the Header for this posting - I will add a clear Screenshot of the error window to this post when I can capture it again, if it occurs]. Hmmm.... Since it was a DirectX error (and I am 93.33-repeating-percent-sure that I did not "remove the video card" while playing..), I tried one last thing. Instead of swapping out the GPU to try with something else (a GPU from a friend's PC, for example), which is approaching a Hardware type issue; I tried something else: I changed the DirectX level in the game from DirectX 12 to DirectX11 [this may not have been solely 'my idea' - although I am sure I would have eventually arrived at it as a troubleshooting step, I looked up this error and found many, many locations and sources of others stating they have this issue and encountered this error and I may have read it somewhere, for it to have come up - merely mentioning because I just don't want to take sole credit for something I may not have come up with entirely by myself...].

Example of where to 'Disable DirectX 12' and 'Enable DirectX 11' in the Video Settings, in Battlefield 1
[Hmm, this is more of a Workaround than a 'Fix' for this issue...]
(Click to see Full Size)

Success! I played a good couple of hours this way, with no crashing, closing, freezing, or errors at all - great! After trying it after re-opening the game, rebooting and playing some more, testing it the next day or two after as well, it seemed 'solidified'; changing the DirectX level/version from 12 to 11 seemed to 'solve' the issue [for me, for now].

I think this is more of a 'Workaround' than a 'Fix', since it doesn't solve the issue permanently... there is still something in the game engine or how it communicates with DirectX/Windows/theGPU, which is causing something that is not 'fixed' by this step; but, since it does work to get past the issue, I thought I would share, to help others that may be running into this seemingly-popular problem ('popular' judging from the queries I found about this issue on both the Battlelog forum and EA Support Forums, spanning a few years now..). I hope this works for you, dear reader, as it seems to have done, for me.


[Since this is not a true 'fix' (I do not know if this is permanent nor do I know the actual source/nature of the issue, therefore I cannot say this is a 'fix', imo); I will post this with the title "workaround"...]

Addendum:

Other helpful tips/steps that can possibly help, if the above step does not work (and some additional information), can be found in multiple places on the Battlefield and EA forums, such as this list by a helpful poster named STEEiL:

https://forums.battlefield.com/en-us/discussion/54605/directx-function-error-amd-getdeviceremovedreason-error-in-battlefield-1

Good Luck - I hope it gets working for you soon - and See You In The Game!

It's Not Just You™ - GTAV Launcher Crashing Right After Starting? Here's What Worked For Me... [Notification]

Just a quick notification about GTAV (Grand Theft Auto Five) and how it seems to be crashing after the Launcher downloads an Update of some sort (and after looking it up a bit online, it looks like it's not just me). I'll quickly share some Tips I found from others and which one worked for me in the end - if your GTAV Launcher is crashing every time you try to play the game - don't worry, It's Not Just You™...

The thing that was happening.... oh I don't know maybe
EVERY SINGLE TIME I TRIED TO START THE GAME

Things I tried:

1. Rebooting
2. Copying d3d9.dll (eventually trying all of the d3d Libraries, copied to the game folder)
3. Updating GPU Drivers and Windows Updates (all was Latest already)
4. Updating RTSS (Rivatuner Statistics Server to Version 7.0.0 (Beta), part of MSI Afterburner)
5. Download latest Social Club installer and (Re)Install (to the same Location I had it already)

Quick Tip: Fallout 4 - TAB Key Stopped Working And Not Bringing Up The Pip-Boy? Here's A Possible Fix [Text-Only]

I have been having a ton of fun playing Fallout 4 lately [again, building up my Settlements too much and ignoring the Main Storyline!] and ran into a 'small-but-game-stopping' issue where the TAB key appeared to stop working. "Hitting TAB wasn't bringing up the Pip-Boy anymore..??"

After doing some Troubleshooting and paying attention to what I was doing and pressing... it turned out to be a very simple issue - the TAB key was 'locked' out because of how I had used it in the Console.. Let me explain briefly:

And More: Corel's VideoStudio - Crashing When Using 'Open With' To Import Clips Into VideoStudio [Fix/Workaround]

Just last Month, I picked up version 20 of Corel's recently-updated video editing suite "VideoStudio" (nomenclature "X10") and am having a lot of fun learning what it can do and how to do it all (coming from mainly editing videos with Sony's Vegas 'Movie Studio' line of products [now taken over by MAGIX]). However, I quickly ran into a little issue with importing clips using the "Open With" option in Windows and wanted to share what I found...

Normally, in Windows you can 'right-click' a video file and mouse-over the menu option "Open With..", which brings up a sub-menu of known applications, to 'send' the file to ('opening the file with the chosen application'). Doing this, whichever application you select will startup and the file will be sent to it to work with.

However, doing this with a video clip and VideoStudio x10 I found, every time the program would open up, it would immediately 'crash' (close/stop/etc). Hmm... time for some Troubleshooting! I double-checked that the file in question was not corrupted excessively by playing it, testing it in a couple of video/media players, and even tried a few other clips that were 'known good' (that VS worked with before). Each time, using "Open With...", the Splash Screen for VSx10 would show up and then just as the program itself looked like it was opening, the entire thing would crash and show this message:

Example of the "Corel VideoStudio has stopped working" Error Window Pop-Up
when trying to import a clip into VideoStudio X10 utilizing the "Open With" shortcut in Windows

It's Not Just You™: AMD's Crimson Drivers, Radeon ReLive Not Working At First [Possible Fix]

Just a quick post before I go to bed here, that I wanted to share about the AMD Crimson Drivers that I got notified about just a bit ago, which included AMD's "ReLive", their new Game [and Desktop] Recording utility - 'built-in' to their 16.12 Drivers... For those who couldn't get it working right away (I see posts about it already in the Official AMD Forums), I couldn't either... And although I eventually did, I wanted to let others know, if you are having issues with it: It's Not Just You™

I was already starting to get tired when I saw a notification of the Driver Update - and I had no idea there was a nifty Game Recording 'app' incoming with it [I haven't been reading much lately, I have another Cold for pete's sake!]. For AMD GPU owners, waiting patiently to see if AMD was going to come out with their own Game Recording utility - it's here! The future is now!

Check out AMD's Video on their ReLive edition of Radeon here: 

https://www.youtube.com/watch?v=nRSm12lwRe4

[I really wanted to start Testing it all out tonight, running Benchmarks and collecting Data for a TestRun or a Quality Test with it; but my sleepyness is actually building and getting the better of me, so I better go soon - I wanted to share what I did this evening though, to get it working (for me), before I go...]


Without going over the few things I tried first that didn't work (setting configuration, testing with different games, etc), here's the steps to take that finally got it running, for me:

• Download the Latest AMD Drivers via their main Website (http://support.amd.com/)
• Uninstall the main AMD Drivers via the Control Panel > Programs > Uninstall/Change Program
• Reboot
• Install AMD Drivers via the Download from their Website
• Reboot

That's it!

After that, even though I have a 200 Series* AMD GPU at the time of this writing**, I was able to get ReLive up and running, even playing a little bit with the configuration and making a couple of short test recordings, before I came here to write this quick 'tip' of what might help get it going for others... It's a larger 'step' (messing with Drivers, as opposed to just messing with Configuration/Settings); but I always like to Troubleshoot from the smallest steps first (eg. changing some settings) to larger steps (eg. re-installing software) to huge steps (eg. OS reinstallation, hardware changes). Thankfully, it started working just fine after only a bit of a 'larger step' taken.

Although with the most recent versions of Windows you don't always have to Reboot it when making changes, it helps to get everything 'in order' in the background, re-initializing all hardware and Drivers fully - which is why many installers/software still get you to do it through their installation programs.

I plan on putting the Game Recorder through it's paces, working on a TestRun and a QualityTest, to come in the future here at The Blog - for now though, hopefully ReLive can get up and working for you, too - good luck, and if you are having troubles with it, remember - It's Not Just You™!






* The AMD page on ReLive at their main website (http://www.amd.com/en-us/innovations/software-technologies/radeon-software/gaming/radeon-relive) shows only 400 Series GPUs as 'Officially Compatible'. Although it does not state 'it will not work with earlier Series', it is unknown 100% at this time if it is possible, hence my mentioning it above


** Disclaimer and Personal Veracity Statement: Although I currently own an AMD GPU, I have owned NVIDIA GPUs in the past and will do so in the future. I have no personal preference between the two, purchasing one or the other as Upgrades depending on my needs at the time and my financial limitations at the time I choose to Upgrade. I have not and will not receive any compensation for mentioning or talking about either companies' products. I am merely an enthusiastic user (of both).

Quick Tip: Getting ACTION, Dxtory, FRAPS and More Working With Battlefield:Hardline [Fix/Workaround]

I have been doing some Recording Tests over the past while with Mirillis' ACTION - for those who aren't familiar with it, ACTION is a game recording application, similar to MSI's Afterburner, Bandicam, Playclaw and others - and I was reminded that it does not automatically "work" with Battlefield: Hardline [that is, 'hook onto it' or 'detect-it-and-get-ready-to-record']. I actually remember running into this issue during the Beta, but at the time I merely used another recording program and didn't think much of it since. To find out more about this issue recently (since reminded of it) I dug around a bit and did a few tests, trying to find a solution and/or conditions it did work under - and wanted to share my few findings as a 'Quick Tip' for others, here.


Looking around, I found out that this is still an ongoing issue with Battlefield: Hardline - and before that, it was to some extent with Battlefield 4, even causing BF4 to 'crash' on Startup for some people. I also found out that these issues occurred not only with ACTION, but also with other similar programs, such as FRAPS and Dxtory, according to the Battlelog Forums and the main Mirillis Forum. In many places, I found the same solution stated again and again by helpful posters... So, I tried it out - and it worked perfectly! I repeated testing with it a few times - and once I was satisfied it solved the issue and was repeatable (for others to use), I wanted to share it here, with you.

Here are the steps of what to do [with a shortcut I figured out, to type it in faster/easier, near the end of this post]:

• In the game, hit the Tilde key ("~", which looks like a 'squiggly' line - the key is in the upper-left of Standard keyboards, to the left of the Number 1 and above the Tab key), which should bring down the Console. In here, you can type in commands for the game.
• Type the following in one line:
  
  RenderDevice.PresentAsync 0
  
  (That is, "render device dot present async", then a space, then a "zero")
• Hit enter and then you can close the Console by hitting the Tilde key (~) again.

That's it!

As long as that is all you want to do in the Console (you don't want to enter in any more commands), you can then just close it, as it is done - those are all the steps to do. You should then see the HUD (indicator) for ACTION pop up on the screen in the corner you chose in the "HUD Settings" section, in ACTION.

Note that this may not always be needed... For example, if you launched BF4 in Windowed or Borderless modes, it may not be required. In Battlefield: Hardline, it seems to be needed no matter what mode you run the game in [for the interface of these programs to be shown and able to record without issues]. For example, I just started up Hardline in Windowed mode a couple of times as a test - with ACTION and FRAPS - and those steps were still needed to get these ready to record (their little hud/ui/interface did not show up at all until the above command was entered. 

Another way I saw suggested in Forums, was to enter in the command via a User Configuration file (User.CFG), created in the game directory. For those who don't know, a User Configuration file is simply a text file that the game will 'run' when it starts up - and this text file can have commands listed in it, so that you don't need to manually type the command each time you play the game.

Although even a Battlelog Moderator suggested it at one time, here, it seems it is possible that this process can be "detected" or "seen as" a hack - and you can effectively be Banned, Blacklisted from Ranked Servers, and other negative actions taken against you - as seen in this thread at the Mirillis' Forums, here... Although I am sure there are many people out there using this command in a Configuration/Startup File without issue, as it has happened to some people in the past...I personally would suggest against going this route, for now, and merely type it in whenever you want to use ACTION/Dxtory/FRAPS/etc to record your gameplay in Battlefield games.

On my own, I figured out a faster way of typing this command into the Console and wanted to share it here - apparently the Tab key will try to 'guess' at the terms you are typing in (much like the Command Line or Terminal in Unix, Windows, and other operating systems [black box screens that you open to enter commands]) and by using the Tab key, you can quickly enter the command above by using these steps, after opening the in-game Console with Tilde (~):

Hit "r" then the Tab key

Hit "d" then the Tab key again

Hit "p" then the Tab key one more time

Hit "0" (zero) and hit Enter

That's it! 

R-tab-D-tab-P-tab-Zero. Done! Now, the same command as above has been entered even faster and you should see the HUD/indicator for your preferred recording program pop-up on the screen - and you can now record your battles once again. Here is an example/reminder GIF of using the Tab input method for this command, in Hardline:

GIF Example/Tutorial/Reminder of How To Get ACTION, Dxtory, FRAPS And More to Work With Battlefield:Hardline
(Click to see Full Size - Save and Share with others!)

Hopefully the above gets these programs working with Hardline for you too, dear reader, as easily as it did for me.


See You In The Game!

[Personal Log TwoZeroOneSixPointSix: I could not find the 'original' bearer of this wonderful information, to give Credit to them - and to find out "why" it solves the issue with these few recording programs (as I am not a programmer, the reason is not immediately obvious to me) and I always like to try and share the "why things work" of solutions I present, to others as well. I eventually assumed it was a developer at some point in time, but in the vast posts of passed-on knowledge, their name has become lost into the aether... Regardless, I want to say 'thank you' to whomever this helpful dev is - and I want to pass on that thanks to all the other anonymous sharers of this tip [about this issue with Hardline] on Forii everywhere. This QuickTip is merely a culmination of, or passing on yet again of, this great bit of information on this issue with these few game recording programs and Hardline. Enjoy]