Showing posts with label solution. Show all posts
Showing posts with label solution. Show all posts

Thursday, January 21, 2021

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


Saturday, September 30, 2017

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

Sunday, July 16, 2017

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)


Monday, June 19, 2017

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:

Friday, June 17, 2016

And More: Color Differences When Opening or Importing Images with PaintShop Pro X8 [Fix/Workaround]



I am just finishing up a Trial for Corel's PaintShop Pro X8, an image editing program which I enjoyed testing out - and while it had very few issues or problems [for me personally], I did run into one where, upon importing (opening or pasting) an image, the colours seemed altered/changed (looking like they had been 'reduced' perhaps) as can be seen by this brief comparison I put together for uploading to a forum:

In the example comparison above, the difference can be seen mainly in the lower-left portion, the darker area - which seems 'blotchy' and the image appears to have less colour, but the palette [the amount of colours the image holds] shows RGB/16bit


I mentioned this on the Corel User Forum to see if anyone had any ideas... Perhaps it was a setting somewhere in X8 I missed [I thought to myself]. I Disabled the 'Automatically Convert Colour to 8bit' (changing it to Prompt instead of Automatically convert) but that did not seem to have an effect [it is usually only used for certain needs anyway, such as Animated GIF images, as it reduces the palette down to 256 colors, but I thought it was worth a shot in case it 'triggered' something else in the program].

I did not run into this issue/problem with PaintShop Pro X7, a great image editing application that I continue to enjoy to this day - in fact, all the images on this Blog and other places I share them - I do a Final create/compile with either PaintShop Pro or GIMP (which is a versatile Open Source Image Editing Program with an interface similar to Photoshop). 

[Note: I am not affiliated with nor do I receive any compensation in any form from Corel for talking about or using PaintShop Pro - I am merely an enthusiast user of the program for image editing purposes and wish to share my own discovered information with other like users of the program]


The Corel User To User Web Board (Corel's Support Forum, they can still be contacted directly for problems) was once again very helpful with information on what was going on here...

Apparently, there is an issue with Color Management that many people seem to be having, with PaintShopPro version 18 (X8), which does not occur in X7 (which turned out to be the exact issue I myself was running into!).


The solution/fix was to Disable the Color Management in X8, by going to

File > Color Management > Color Management

and Uncheck the checkbox in that window to Disable the management system in PaintShop Pro.

Example of what the Color Management window looks like and the simple solution
to the color issue/problem in Paintshop Pro X8 (Click to see Full Size)


Although I do not know the details of why the problem itself is occurring in X8 (and the exact details were not given at the Forum at the time), the fix/workaround did in fact work for me and I no longer experienced this issue of color reduction/loss in X8 - and I wanted come here to share it with everyone in the hopes that it works for others experiencing this problem, too!

If I had to summarize Color Management, I would state it is a way of matching up colours from different sources, such as making sure that an image taken with a camera will be reproduced correctly on a printer, etc. While the average home user does not really have a need for this, professional photographers, publishers and printing houses appreciate these options (which has a list of various devices, like printers, monitors and so on, so that 'what they see is what they get', which is something they really want).


[The original Thread where I asked about this issue at the Corel User Forum (with the helpful answer by Kathy_9, an advisor at the site), can be found at: http://forum.corel.com/EN/viewtopic.php?f=56&t=59642&p=328249  ]

Hopefully this fixes the problem for you too, dear reader, if you run into it - enjoy!



Sunday, July 26, 2015

Diablo II - Getting Ladder-Only Runewords Working In Single-Player Mode, Without Any Addons [Updated for Patch 1.14d]


[This post is currently being uploaded as Text Only for now - I may add images and some screenshots to it Soon™]

[Update 2016-06: As of Patch 1.14, where the save game information is kept has changed. I have tested this process and all changes are noted within**, including relocation of Runes.txt placement. This process still works as of this Patch.]

[Update 2016-07-03: As of Patch 1.14d, the save game information has been reverted by Blizzard 'back' to the 'older' instructions. The section at the bottom, talking about creating the Subfolders and Runes.txt in the 'Windows User' location is not needed in 1.14D - the steps talking about creating Subfolders and the Runes.txt are still required overall though, but work once again for the 'Game Installation' location itself - tested this as of this Update ...date.] 


[Personal note at end †  certain Runewords are not working?]



I recently re-installed Diablo2, ready to once again enjoy days gone by of Monsters, Magic and Loot... I wrote an article last year, about getting the scroll-wheel to work for switching spells/skills (the 'Right Mouse' Secondary Skill functions) in D2, in Windows. That post is located here:
http://gametipsandmore.blogspot.ca/2014/06/diablo-ii-getting-scrollwheel-to-work.html

After setting up the mouse-wheel once again, I started up a Single-Player game and made a character for it [a Necromancer, as I love Summoners]. I had collected some Runes for Runewords in the past, archiving them for SinglePlayer with The Hero Editor, a small utility that can save items found in Single Player Mode, by Exporting them to files on a local system/disk (as Diablo 2 Item [.d2i] files), which can then be Imported at a later time, into a future Character in Single Player Mode [only] through the same utility [which was "written mainly by Shokaku and ZonFire99" according to the ReadMe file for it].

Using the Hero Editor, I imported past runes and gems into my new character, using the Horadric Cube to create higher Runes I needed, for creating some Runewords. After trying to create an Enigma armor, I found that it was a Runeword that was not craftable in Single Player Mode (when trying to create it, the item simply fills up with the Runes used and utilizes the bonuses from the single Runes themselves, not creating the 'Special Item' that the Runeword would normally create, in an online, BattleNet game).

Searching online for some clues as to what could be done, I found in a few forums, mention of Addons that could possibly be used to create Ladder-Only Runewords in Single Player games. For now, I went looking for ways to craft Runewords in D2 without Addons. What I found, were various instructions to create a Text file in a created Subdirectory of Diablo2, where the Single Player game would use it as a source for Runewords... great! The only issue was that there seemed to be some variance for how the Subfolders should be created/named, to make the Text file work (there were multiple versions of information on what the subfolders should be).

Experimenting on my own then, I found the path of folders that would need to be created within the Diablo2 directory, in order to get this Text file to work. Just to summarize again, what this will do is:

» Allow Diablo II to use Ladder-Only Runewords in Single Player games, by reading Runeword information from a Text file (with no outside Addons or Mods needed to do so)


To do this, here is the working folder structure to create in the Diablo II directory:

<D2 installation folder>/Data/Global/Excel/Runes.txt


The steps to create the above folder structure are:

  • in the Diablo II directory, create a New Folder called Data
  • in the newly-created Data folder, create a New Folder called Global
  • in the newly-created Global folder, create a New Folder called Excel
  • in the newly-created folder called Excel, place the Text file from my PasteBin here:
    http://pastebin.com/xGLWhmZ1(If you do not feel comfortable Downloading anything at all for this procedure, simply copy and paste the text from that website and paste it into a text file, one that you create in the Excel folder, within the Diablo II directory structure you just created via the above - be sure to name the text file Runes.txt)
  • lastly, add "-direct" and "-txt" to the Shortcut Properties for the "Diablo II.exe" file that starts up the game. The quotation marks aren't added, only the commands, such that the Target line in the Shortcut should then look like this:
    "C:\Program Files (x86)\Diablo II\Diablo II.exe" -direct -txt
    (the above line assumes that it is installed into the C: drive of the system. If you installed Diablo2 into a different drive/partition, the first letter would be whatever your drive letter is of where D2 is installed - the main part to match is the end portions, the "-direct -txt" added to the end, which allows usage of the Text file used in this process)

That's it!

What should occur in theory is, Diablo2 will use the Runeword information from that text file, allowing Runewords to now function within the Single Player game mode (even ones that are "Ladder Only")!

After "cubing-up" some new Runes that I did not have [using a Hero Editor to save/import the ones I had], I created an Enigma Runeword armor. Then, to specifically test the procedure above with a "Ladder-Only Runeword", I attempted to create an Insight for my Merc - and it worked! Hopefully, this will help you utilize Runewords in Single Player, too.


Note: Although I talked about a utility called Hero Editor within this post, it is not a required aspect of the steps above [ie. I use it for Item saving, not Runeword creation]. Also, although an "Excel" folder is created, neither Microsoft Office nor Excel or any other Spreadsheet-type of application need be present on the system - only a simple Text file and a few New Folders created are all that is needed.




** Update for Patch 1.14:

The file structure has changed, for where the game saves your character files, as of this Patch.

While I am not a developer for Blizzard, looking at the effects this Patch will have with Windows, I assume this was done to create a maintainable save game system for people upgrading from Windows 7/8/8.1 to Windows 10, as upgrading Windows [or reinstalling the game itself, if needed] will then not affect your save games in any way and they can then still be found by Diablo 2 (Single Player, etc) [by using this new directory setup implemented in 1.14].

As of Patch 1.14, your save game information is now located at:

C:/Users/<YOUR USER NAME>/Saved Games/Diablo II/

Your saved games, maps and characters are all now within that folder above [assuming C: as your Windows Installation Drive/Location, or where Windows and Saved Games can be found].

To continue using Runewords in Single Player with Patch 1.14, simply create new folders within (the Data folder may already be present), so that your file structure looks like this:

C:/Users/<YOUR USER NAME>/Saved Games/Diablo II/Data/Global/Excel/Runes.txt

Placing the Runes.txt folder within the Excel folder, as shown above, will then allow you to continue using Runewords in Single Player with the new file structure utilized in Patch 1.14 [personally tested as of 2016-06-06].


Tip: Don't forget to add "-direct" and "-txt" to the Shortcut Properties for the "Diablo II.exe", if needed, so that the end of the Shortcut Target line looks like this:
... \Diablo II\Diablo II.exe" -direct -txt


Enjoy - and See You In The Game sometime on BattleNet!



[Personal Log, Regarding Addons, Mods and Utilities: Just a quick mention of my remark regarding 'without any addons' above - I have used Addons, Mods and Utilities in the past, with games, and will likely do so in the future - however, mostly for security reasons, I normally do not and usually advise others against them at first. I realize that most of them are safe, hence my own usage of addons, mods and utilities at times; but because of the chance to encounter security risks, I usually advise against them initially, if people ask me for input. In the end though, most Addons, Mods and Utilities for most games are Safe and offer great functionality, the result of many hours of hard work that their creators have poured into them (if you use Addons or Mods or Utilities for games and you liked them, let their creators know, if you can)]


[Because this post is over a year old now, I have made a newer one (here at the blog, in June/July 2016) talking about this process again, with a bit more detailed instructions (a few screenshots showing the process) - along with my experiences of installing/playing D2 in Windows 10 - if it's not on 'the front page' anymore, that article can be located by going direct to the blog posting here.]


† [It seems that certain Runewords were not working for some people, according to various forum posts, using Add-Ons and other methods. For example, the Runeword EDGE, did not work for some. I have personally created INSIGHT and other Runewords, so this was puzzling. I investigated this potential limitation and found that it may be due to either limitations in the Add-On/Program being used, or the Runes.txt file itself containing Commas, which can occur if the file is opened in a Spreadsheet application (which may turn the file into a Comma-delimited format (using Commas to separate sections)) - be sure to utilize my methods above and the text direct from my Pastebin source (copying it into a Text file or downloading it as a Text file), or use the text I re-pasted into a 'Code' area at my newer article on this, here, copying it in to a Text file and placing it into the Data/Global/Excel subfolder. As of 2016-07-06 I personally tested the Runeword EDGE and it worked using these methods. I hope it works for you as well!] 


Wednesday, August 06, 2014

Quick Tip: The Sims 3 - Game Recording Is Slightly Darker Than The 'Normal' Colours Of Regular Gameplay [FIX]

Just a Quick Tip for those of you recording The Sims 3 and finding that your videos are looking 'darker' than the original gameplay itself - a problem that has been around for some people for over a year now... It's not that the game isn't recordable (although for some people they got nothing but 'blank/black screens' a few years ago) it's that the recordings are coming out, what looks like, a few shades darker than what the game really is.
I was recently seeing a spike in the number of people talking about this problem again and decided to see if I could find a fix, or at least a workaround, for it; and what I found was something that everyone can do for now (at least until AMD/NVIDIA or Maxis/EA makes an update that fully fixes the issue) and that is simply: to run The Sims 3 in Windowed Mode.

Whether you are using Dxtory, Bandicam, Afterburner or most other game recording programs (even NVIDIA's Shadowplay has the same issue for some people), the fix [more of a workaround] that I found for now at least allows you to record your Sims 3 gameplay with proper colours, as you can see in these frames extracted from a couple of game recordings, below:

Comparison between the display modes and the colours when recording (Darker vs. 'Normal') for the recording issue with The Sims 3, showing that the workaround works [at least for now] in two extracted frames from two game recordings (one in Windowed Mode and one in Fullscreen Mode). [In the right half, the camera has been 'zoomed in']


Have fun recording your Sims 3 gameplay once again, if this problem has made you stop - and
See You In The Games!


Friday, March 14, 2014

And More: The EULA Keeps Popping Up When Starting Sony's Vegas Video Editing Applications (FIX)


Since the most popular answer on the ongoing poll I have running here at the blog ("what type of posts would you like to see more of in 2014" [top right, it will run until the middle of the year]) is "Tips And Tricks Of Video Capturing And Editing", I thought I would start more of these types of requested posts by sharing this fix for a problem that seems to pop up intermittently with Sony's Vegas line of products.


Whether you have just re-installed it or whether it has been on your system for a while, 'something' is causing the EULA (End User License Agreement) to pop up and require you to agree to it, even if you have already done so and/or Registered the program. This question comes up once in a while on the Sony Creative Software Official Forums and I have seen it elsewhere. I was recently reminded of it again because it is also something that just happened to me on my system! I didn't re-install Vegas or make any large changes related to Vegas, yet this little guy started popping-up every time I started up Vegas Movie Studio HD**:
The popup that comes up for some people, every time they start Vegas

The fix is a simple one, originally suggested by a Sony Forum Moderator and quoted/forwarded frequently on the official forums, to those who come and ask the question there. Although it seems more like a 'workaround' than a 'fix [in my opinion], it works just fine and since it is officially supported by Sony and I just tested it for verification myself [that it does indeed solve the problem], so now I share it here with you:

  • To stop the EULA popping up every time you start Sony Vegas, simply open Windows Explorer and navigate to the folder where you installed it on your system. 
  • Then, find the file that is titled, simply, "eula". There will be no Extension showing, even if you have the Windows option to 'Hide Extensions For Known File Types' turned off. 
  • Rename (or delete) the file. That's it! 
Now the EULA cannot pop up anymore and won't, every time you start up Vegas to edit your game captures.

**Although this example shows steps for the Movie Studio version of Sony's Vegas Video editing line, the EULA 'fix' is the same steps for Vegas Pro, Vegas Edit or other versions of Vegas

Enjoy popup-free video editing once again - and See You In The Games!

Saturday, December 28, 2013

Quick Tip: Medieval II Total War - 'Fatal Graphics Error' [Possible Fix]




I first bought this great game as a DVD Retail Box and then later on purchased it through Direct2Drive [when Direct2Drive was around, then that service became GameFly (2015 Edit: and now it's D2D again)]. I also have it on Steam as a backup digital download source - it's too hard to resist those really cheap Steam Sales! Recently, I was Re-Installing M2TW, to begin conquering the world once again... However, I was surprised to see nothing but an error message (on Windows7):

The "Fatal Graphics Error" message, when starting MTW2


I personally found this error humorous, as it complained about Graphic Settings - and I couldn't even start/get into the game to change or even set them in the first place! So, I started Troubleshooting....

Apparently, a lot of people, on many forums, have been getting and asking about this error - and still are - so here is a great chance to share this Quick Tip on a simple 'fix' for it I eventually found, simply by playing with the Shortcut Properties:

Right-Clicking on the Shortcut for the game and editing the Compatibility Tab to match these settings,
is how I fixed the Fatal Graphics Error problem when I played M2TW recently. Try it out!
Click image to see Full Size

After making these changes to the Shortcut that runs the game (adding two quick checkmarks in the checkboxes shown above), after launching it should show a black screen [detecting settings?] momentarily and then load up the game properly (you may have to click on the icon in the Taskbar [Windows] to bring it up a second time) but that's it!
Hopefully that works for you all, as it did for me.

See You In The Games!


Sunday, June 23, 2013

Game Tip - Planetside 2: Missing Terminal Panels/Displays with Anti-Aliasing Enabled (Fix/Workaround)

Just a quick tip for Planetside 2 that I meant to post a while back: If you have Enabled AA through the Control Panel of your Video Card (NVIDIA or AMD/ATi) and can no longer see the display screens of the Vehicle/Resupply Terminals or other transparency effects (and if you want to keep AA enabled and see them), all you have to do is go into the in-game 'Graphics' Settings and adjust the 'Render Quality' - even just knocking it down from 100% to 99% will allow them to show up again - a screenshot example of the setting and the result is below
Have fun and See You In The Games!