Welcome to Black Liquid Software

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

Trasd

Members
  • Content count

    30
  • Joined

  • Last visited

Community Reputation

61 Bright

About Trasd

  • Rank
    Worker
  1. Yes, I also found, with new video cards, on some games, DirectX 11 runs a bit faster. This makes sense because of the newer, faster hardware algorithms, if the software takes advantage of it. When I get back around to the manual, I'll note your findings.
  2. I finally finished my Settings' Guide: Some of it may help with crashes....
  3. Banished Video Settings Quick Guide for Windows Please note that the document pasted in with a good attempt at the formatting, but missed! I will fix it later, please be patient. This short layman's guide provides a brief explanation of Banished's video settings. Some of these settings will have a large impact on how well Banished runs and some will help with "out of memory" crashes. I will approach each setting's explanation with these two particulars in mind. Our goal is to have Banished run as fast (and stable) as possible with little or no video degradation; a happy median. Even if your system seems to run fine with all the game's settings maxed out, I still recommend you review your choices as these can greatly impact other aspects of Banished, like modding and map size, for example. Before I get into the explanations, I have some general advise on keeping your game running as efficient as possible: 1. Make sure you are running the latest Banished retail version; see the first entry. 2. If you are experiencing crashes, report them to Shining Rock Software support (see the bottom of the linked page) after reading the FAQ to verify that your error is not already addressed. 3. Make sure your machine is in the best game-running shape that you can! This subject is much too broad to cover here, but there are many tweaking sites and free programs available to help. A few items to keep in mind are: · Make sure your hard drives are defragged on a regular bases. There are a lot of free defragging programs available (including the one packaged with Windows), but I use Puran because it allows the targeting of specific directories, boot time defrag, and more. · Keep the number of background tasks to a minimum. This is an expansive subject and I will not attempt to touch it here, but this is one of the main causes of poor performance on capable systems. Puran also offers free, a whole suit of utilities (some to help streamline the number of background tasks); please note, if you use the full suite, Puran Defrag does not need to be downloaded separately. Many people use CCleaner instead, which has been around a long time. 4. Beware of quick solutions, like editing your registry, unless you've fully researched the problem and solution and, you know what you are doing. 5. Remember, large maps can crash the game on any system, as stated on the official Shining Rock Software site: "...at some point very large maps will crash the game due to out of memory, or textures failing to be created." Banished Video Settings Graphic quality is subjective, there can be no doubt, but many of the standard graphic settings in today's games are unnecessary. For example, antialiasing was used on lower resolution screens to minimize pixelization (it softens pixel hard edges), but isn't necessarily needed on today's HiRes monitors. Turning off this setting alone can greatly improve performance, decrease resource demands, and help alleviate certain problems. Please be aware: · If you don't like the visual outcome of lowering a particular setting, feel free to change it back, but remember, there are consequences. Carefully weigh the visual gain against the benefits of performance, and in some cases, stability. · Hardware and or driver settings can (and usually do) affect your options and, in some cases, will override them. Hardware and or driver settings are beyond the scope of this guide. Renderer: The renderer option lets you set your DirectX version for the game to either DirectX 9.0c or DirectX 11. For the purpose of this guide, I'd recommend going with DirectX 9.0c. 9.0c requires fewer resources and is more stable, but it does not have all the features of version 11. With a game like Banished, the differences should be virtually unnoticeable. Adapter: The adapter option allows you to select which video card and or driver to use with Banished. Most computers will have only one video card, but may still offer two choices, one usually being generic. It's hard to point you to the correct option because this depends upon your hardware, but I can tell you what not to choose! Stay away from generic options, such as: Generic PnP Display, Standard VGA Graphics Adapter, etc. Generic choices typically utilize a built-in Windows VGA driver whereas most video card manufacturers will supply a much better choice. Two very popular gaming cards are ATI and Nvidia, but other valid option may be Intel, ASUS, and a few others. If your choices are still ambiguous, the best way to choose the proper adapter is to identify what you have, but even these steps can vary depending upon which Windows version you are running. You can try looking here, or Google "identify windows video card" and append your OS version (i.e. "identify windows video card windows 10"). Resolution: The resolution option has a very big impact on performance, but you should generally stick to your monitor's native resolution. If you choose anything but the native resolution, the pixels will not be one-to-one with the game's rendering, but approximate, which means your graphics will be blurry, especially text. Most newer, standard monitors are 1920x1080 (if you use an HDMI connection, it is 1920x1080). Generally, the native resolution will be the largest of your choices and at the top of the resolution list. If in doubt, Google your monitor's model number. As a last ditch effort, if your game's performance is still unsatisfactory, you can lower the resolution setting, but make sure this is the last thing you try. Quite frankly, if you have to resort to lowering this setting, it might be time to update your system! Refresh Rate: Refresh rate is the number of times the monitor is refreshed per second. In most cases, you'll stick to 60Hz, which is pretty standard nowadays. This setting generally does not affect performance (see VSync below), though some people claim they can see 60Hz refresh rates (if your monitor appears to strobe, you are one of these folks). If your eyes are this sensitive, you can increase the refresh rate if the option is available with your hardware. Personally, I could see strobing on the old CRT monitors at 60Hz, but never had this problem on modern LCD monitors. VSync: The Refresh Rate described above determines the number of times the monitor is refreshed per second, but in most cases, this does not correspond to the number of times Banished redraws its screen, which can vary significantly. When on, VSync assures that Banished does not redraw its screen while the monitor is in the middle of a refresh. If this happens, you may notice a "tearing" of your graphic screen (only part of the scene is redrawn resulting in a horizontal line somewhere on your screen, but only for a split second or, 1/60th of a second, to be precise). If VSync is on, your scenes should never "tear," but in most cases, you will never display more than 60 fps (frames per second). Unfortunately, turning VSync on can result in stuttering (skipping, dropping frames, etc.) if your system cannot keep up with the monitor's refresh rate. Without getting too technical, I suggest leaving VSync turned off (not selected) unless you notice a lot of "tearing." Fullscreen: I recommend running all games in full screen for a number of reasons, most importantly of which is performance. Most video cards are tweaked to run in full screen because they can write directly to the graphic system without going through a Windows' buffer. In window mode, all screen output is filtered through a Windows' buffer and will always result in a slowdown, though in some cases, the performance hit is negligible (on fast systems). Another reason is CPU resources, which are spread thinner when running programs windowed. Antialiasing: Pixels are aligned in a grid. With this technique, drawing a curve or diagonal line will result in jaggedness, or pixelization. Antialiasing is a method used to help diminish this jagged effect. But, as previously stated, today's HiRes monitors have very small pixels compared to their brethren of yesteryear, so antialiasing has become superfluous, in most cases. My recommendation is to set the option to None. If you are still unconvinced, change the setting and judge the difference for yourself. Just remember, with antialiasing on, at a minimum, the neighbors of over 2 million pixels (1920x1080) have to be examined, judged, then redrawn, ~30+ times per second. This, alone, is a huge resource drain, even with hardware optimization. Texture Filtering: You can think of texture filtering as antialiasing on steroids! I don't have the room to properly explain this here, so I will direct you to Wikipedia, if you want a better understanding. Just remember, texture filtering, in most cases, will have the largest impact on quality versus performance and, it also has the largest impact on the amount of video RAM used. In other words, if you are having bad performance and or crashes with Banished, you can lower this setting to help with both. Again, I cannot simply tell you which setting to choose, but I would start with the lowest (Bilinear) and work your way up (I use Bilinear on my laptop and am happy with the results). Keep in mind, texture filtering is not the only determining factor of graphic quality. Many times, a lower texture filtering setting can be compensated for by adjusting Banished's other settings. In other words, if the Bilinear setting doesn't look as good as you want, don't just choose a higher setting, try tweaking Banished's other settings first. Shadow Resolution: Shadows, in a game, can compensate for other graphic shortcomings, but at the expense of resources. Even so, from a purely visual point of view, I'd recommend keeping this setting as high as possible. If, after lowering other settings, you are still having performance problems, you can think of lowering shadow resolution or simply turning shadows off (see Shadow Quality below). Shadow Quality: Unlike Shadow Resolution, Shadow Quality can have a significant impact on graphic resources (performance and memory requirements). With this setting, I recommend you start with the lowest setting (excluding None) and work your way up, stopping on the lowest acceptable setting. I find Low does what I need. Reflections: Reflections can help compensate for graphic shortcomings, but can also significantly deplete available video resources. I consider reflections eye candy. But, if you can afford the overhead, I suggest you keep it set for Terrain, at a minimum. If you've lowered other setting and are still having trouble with performance and or crashing, you can simply turn reflections off. Quick Video Settings The following table is a summary of my recommended settings, depending on whether you are after performance or stability. If you are crashing, there is a good chance you are running out of resources, so my recommended settings are just a starting point (with trial and error, you should be able to minimize crashes, if low resources are indeed the cause). You will need to contact Shining Rock support once you narrow down the problem. See this guide's description for clarification of the recommendations below. Setting Performance Diagnosing Renderer DirectX 9.0c DirectX 9.0c Adapter Manufacturer Driver Manufacturer Driver Resolution Your Monitor's Native Resolution Your Monitor's Native Resolution Refresh Rate ~60Hz ~60Hz VSync Off Off Fullscreen On On Antialising None None Texture Filtering Lowest Acceptable Bilinear Shadow Resolution High Low Shadow Quality Low None Reflections Terrain None Quick Settings' Table If you find any problems (grammatical or technical) in this document, please let me know. I will let the guide simmer awhile before releasing it as a PDF, if a PDF is requested. This document is Copyright © 2017 by Troy A. Dalton and permission is given only to link to it from other sites, but not to reproduce it electronically. It may be printed for personal consumption. The only reason for the copyright notice is document control, so if you find this on any site other than Black Liquid's, please let someone know.
  4. @KevinTheCynic, thanks, that was a straight forward, very informative answer! Maybe I'm too optimistic, but I think I can fix this for her (even considering my bad start), or at least, help determine the problem but, it won't be a quick fix. Especially, if her problem is unique. She will have to work closely with me though, and it might take quite awhile (as we've both said, not happening to our games makes it hard to diagnose). I've been doing this for more years than I care to remember (my first computer was in 1979, before the PC was released). I will approach her again after she returns. I know she loves the game and I enjoy these challenges. In the meantime, I will continue with the guide. Thanks.
  5. Yea, I know @rejectedegg has stated that she won't post more of her game problems in this thread, but @KevinTheCynic, I thought you were saying others had the problem too. Are you saying this problem is unique to rejectedegg? I found a few others reporting this error, but not on these forums. I'm not getting feedback, so I cannot properly diagnose the problem. It looks like @Paeng has already done a lot of research on this error, which means I'm spinning my wheels (especially with no real feedback pointing me in the right direction). Basically, I'm new to the game, so I'm playing catch up, whereas you guys have been playing for years. Should I even continue with my Video Settings Guide?
  6. @Paeng is exactly and totally correct! This is why I hate jumping into a situation without doing the proper ground work. I erroneously believed the link was to the official Shunning Rock Software forums. [The forum that has the Known Issue post is the link supplied by the official Shining Rock site, but I guess it hasn't been kept up to date - or, has it? The mysteries of the internet!] I was in too much of a hurry. Now, instead of doing the proper background work and researching the problem, I'm playing catch up and correcting errors I made in my statements. Unfortunately, when trying to give technical advise, this is an easy trap to fall into and, it creeps up on you before you realized what's happened! So far, I feel I've caused more problems than I've solved and, I apologize. If I was a moderator, I'd remove all posts after @KevinTheCynic's original. As I cannot do this, I will refrain from more armchair recommendations until I've had a chance to study the problem in greater detail. In the meantime, I will work on the video settings short guide I've been working on. I may put a short retraction at the top of my other posts. My only advise right now would be to submit a bug report to Shining Rock Software support. Forever your servant.....
  7. Sorry guys, it's been a long day. I'm sure I probably meant antialiasing, not anisotropics (this is usually a driver setting\customization)! I'll load the game tomorrow and check the actually game settings. By now, you'd think I would have learned not to go by memory (yea, I'm that old)! My theory is that it's a memory problem with the video. I'll try to put together a little guide on each of the settings and what they do. The idea would be to get the best possible graphics with the lowest memory consumption. If my theory is correct, it will not alleviate the fatal access errors, but it will certainly minimize them. If it doesn't help, I know I'm barking up the wrong tree! Give me a few days (holidays and all plus, we have a wedding and graduation in the family, before Christmas!)....
  8. LOL See, I'm under the impression everyone can code! I could never understand why people can't!
  9. You'd be surprised what the uninitiated can accomplish! The problem I have is I'm no artist.
  10. First, @rejectedegg, it is (probably) not your system, it is the game. Too many people are reporting the same issue. An access violation has many causes that are not related to a specific system. This can be anything from a null pointer to improper memory management. It's not even necessarily the programmers fault, it could be the compiler or even the OS. Also, if you look at Shining Rock Software's known issues, you will see there are a lot of problems, many (many), unresolved. For number 2 above, there is a modder's version of the game that is different than the "release" version. This is a special version that exposes more for programmers, like BL. The more I dig into this, the less likely I think it can be resolved (without Shunning Rock's involvement - typo, or not ). The reason it didn't crash when you did the same thing from your saved game is because the exact same conditions were not met. To us, mere humans, it seems random, but it probably isn't. I believe, looking at the known issue list, the game should not have been abandoned by its creator so soon. Maybe we can talk him into releasing the code as open source, but I doubt he would.... For now, try cutting back on the graphic settings. Use bilinear textures with no anisotropics. Modern computer monitors are so hires nowadays, anisotropic is rarely even needed anymore. I have a crappy laptop (I haven't loaded it on my desktop as I can't sit at it very long without hurting) and I don't get crashes (yet?)! I play large maps, but haven't gotten near as far as you guys. Many of my settings are set to medium, or below. It still looks good, though. Let me know how this goes....
  11. OK, I didn't expect all this, so quickly! As @KevinTheCynic said, there have been reported crashes because of audio, as well. There is a lot to sift through, but first, a few questions: 1. Does the game crash on any other map size (with all mods installed) than (what is it?) extra large? 2. Are you running the modder's version? Does it crash on the release version (non-modder's version)? Doesn't the modder's version offer a running log for diagnosing purposes (I haven't looked into this yet)? 3. Have you tried clearing texture (shader) cache? 4. How often are you crashing? I'm still thinking it is probably the texture\shader handling (corrupt file, multi-threading GPU problem, etc., but audio is still something to consider). Fortunately for me, I'm not getting the error, but like I said, that makes it very difficult to diagnose. Can you repeat your system specs on this thread so I don't have to jump around? Also, I'm watching my 4 year old graddaughter while her mom is picking up my mom! I will be entertaining until after the holidays.... Either way, this may take awhile and, since others (really knowledgeable folks, I would think) have looked into this, there may not be a simple answer. In other words, unless the author gets Involved, it will not be a quick fix or, may not be fixable. Plus, I'm great at diagnosing to a certain point, but I am no guru! I do, however, have years of programming, troubleshooting, and diagnosing experience. I'll give it my best! I don't want to get hopes up only to disapoint.....
  12. Well, OK, after a bit more reading, I've come to the determination that folks are getting their errors mixed up (not here, it seems, but other reports out there)! After deciphering a few, it might be that the access violations are happening on unmodded games. I need to see a dump.... The swap advice still stands, but right now there may not be a need to look at the modding (though it does simplify things). My guess is it is a problem with video memory and or texturing, but guessing can be dangerous at this stage. There is a possibility that old installs with a number of updates has corrupt something somewhere. DDO does this to me at times. The way I fix it without loosening data is to rename the install directory, then reinstalled the game. I then copy all config and custom files to the new install (saves with Banished, too). After upgrading (I guess it can be called an "upgrade") to Window 10, DDO (and others) lost write permission to their data directories! OMG, really? I used the same technique as described above (not reinstalling, but with the data directory), but copied all the data over to my manually created data directory. It worked fine. Anywho, if someone wants to try the rename-reinstall-copy method above, you should be safe (if you are somewhat computer savvy and have a backup), but I'd be surprised if that fixit it on its own (though it may buy you some time). One of the best and easiest fixes is to clear texture cache. This works if some of the cache is corrupt (which can result in an access violation). Like I said, these problems can be very difficult to diagnose from afar! Again, I'll need to see some dumps.....
  13. Access violations may occur for a number of reasons. A quick Google search showed me that this problem doesn't seem to be tied to specific hardware, and generally appears on heavily modded games (again, this was a quick search). I've read a number of supposed fixes, everything from removing Banished registry keys to disabling specific mods. Without this problem happening on my system, it could be difficult to diagnose. There is a chance, of course, the problem is in the code (only triggering with certain conditions) and nothing short of a hack-patch will fix it. My recommendations would be to rule out mods first. This is a lengthy process and would require removing all mods (don't just disable them, move the mods to an un-associated directory), then reenabling them one at a time only moving to the next one after each has been thoroughly tested. Obviously, large-map mods have to be active if the problem only happens with out-side-the-box maps. Run the game for awhile with only the large map mod and see what happens. The unfortunate chances you take with the trial and error method is that the specific set of conditions may not happen. It would appear to be fixed, but wouldnt be. Can someone point me to the error dump? Also, make sure Windows is managing your swap file, for now. If you have more than one hard drive, make sure the non-system drive is enabled for swapping. If someone tries this, let me know the results. For those having the problem, can you post a summary of your system here?
  14. I'm playing vanilla right now and will work my way up to CC. But, this stuff I've already figured out except, I'm too new to be cocky! As a rule of thumb, I try to keep a close eye on that stuff and, sometimes returning to basics yields results! That's when you slap yourself on the head and say, "damn, I cannot believe I missed that!" Thanks for quantifying the "ground rules."
  15. I plan on sticking to 1x, at least until I know the game much better. 1x leaves me time to experiment. I have nothing against the higher speeds, but feel I'll be cheating myself of learning interactions if I go that high, right now.