Jump to content

jjc71

Premium Member
  • Posts

    91
  • Joined

  • Last visited

Posts posted by jjc71

  1. [sOLVED]

     

    After following the fantastic info provided by @dubiousintent and @Mktavish, I have fixed my problem. I followed all the helpful hints and tips, many which I'd already implemented previously. I moved my game folder away from C:\Program Files(x86)\ to another partitioned drive. I updated my 4gb patcher, NVSE, stutter remover, ini tweaks and shader package 13, but still the problem persisted. I landed up at the TTW performance page and stumbled across http://www.nexusmods.com/newvegas/mods/61265 which replaces the old ogg vorbis .dll files and hey presto.

     

    I'd basically given up at the point of replacing the ogg vorbis files so I was bloody amazed. I'd have never pinpointed it as being related to audio.

     

    Thanks again to dubious and Mktavish.

  2. I wonder if this old dusty tweak guide might be of use ?

    http://www.tweakguides.com/Fallout3_1.html

     

    The part about triple buffering ... err maybe I'm thinking backwards on that.

     

    But also ... since your problem is about what's loaded into memory ... makes me think you could possibly step up the cell depth to the next level (How many cells around the player is loaded) Which that should me mentioned in the guide also.

     

    IDK just a stab in the dark worth a mention I thought.

     

    That is a good shout. I remember using that tweak guide many moons ago. It might be worth a revisit.

  3. The drop occurs every 15 seconds? This is called "stuttering" or "lag".

     

    Re: Stuttering or "micro-stutters". All visual stuttering problems are caused by the video stream having to wait for the "art assets" required to render the display OR the game writing something to disk (such as a save game file or logging). Mostly these are due to the hard disk drive being orders of magnitude slower than VRAM, with System RAM (e.g. "ENBoost") and "solid state drives" (SSDs) being in between. Keep in mind that this game was designed for older PC and XBox console systems, and it is now possible for your new "latest and greatest" gaming machine to be faster than it can handle. There are internal design choices that cannot be overcome. The following are "mitigations" that have been found to help some people.

     

    Please see the following entries under the 'Solutions to Performance problems' section in the wiki Fallout NV Mod Conflict Troubleshooting" guide if you haven't already.

    * 'Issue: "Full screen mode" exhibits CTDs and stutters or micro-stutters'

    * 'Issue: Lag or "micro stutters" even with "New Vegas Stutter Remover" installed'

    * 'Issue: Win10 Screen tearing in "Borderless Windowed Mode"'

    * 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu' for other settings that can indirectly affect micro-stutter.

    * There are also some NVSR configuration suggestions under the 'Issue: Game in slow motion' and entries.

    * The 'Issue: What's with these Solid Green billboard signs in the distance (LOD)?' entry under the 'Solutions to Mesh (Red "!" icon) or Texture (solid color) problems' section can also help if your problems started after you installed VWD/LOD texture packages.

    * If you are using CASM or some similar "auto-save" mod to manage your save game files (recommended), try increasing the "time between saves" set in the "save frequency"; and reducing the number of occasions it saves to the minimum (e.g. disable most "Autosave Events" in CASM) and see how that impacts the game seeming to freeze temporarily.

    * If you have "NVSE logging" enabled (see the 'Checklist Item #4' entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide), disable it until actually needed.

     

    Reading from or writing to disk for any reason is the slowest thing the game does.

     

    As you can see, there are a number of things that can underlie your problem. If one of these doesn't fix it, I would be interested to hear about any eventual solution that does.

     

    -Dubious-

     

    Thank you so much for such a detailed reply. I really appreciate it. You have given me plenty to go on. I couldn't have asked for more. I'll report back if and when I crack this problem.

     

    If anybody else has experienced anything similar, I would appreciate any feedback.

     

    Thanks again Dubious

  4. The Problem: During the end of my last play through of Tales of Two Wastelands (New Vegas/Fallout 3), I began to notice I was dropping about 20 fps every 15 seconds. The slow down would last for about 15 seconds and then it would go back to normal. I initially thought it must be a broken quest script or something. I decided to do a fresh install and new game with no mods, and low and behold, the problem was still there.

     

    I'm wracking my brain at this point. My hardware is high-end so it is not that. If anyone can shed any light or give something to go on, I'd be eternally grateful.

     

    Thanks

     

    JJ

  5. As a front-end developer for many years, I applaud @Dark0ne and the staff at Nexus for the fixes and updates they have made to the new design. It has certainly improved BUT, in terms of HCI (Human Computer Interaction), it remains flawed. The new design is not as good as the old design and this must be worrying for the Nexus team. If it does not worry them, then I am worried for the future of the Nexus.

     

    In my humble opinion, the new design in its current state will cost the Nexus to lose a section of its LOYAL fanbase. That is a very dangerous game to play.

     

    It has been established what is disliked about the new design: Visual overload, poor use of colour theory, not intuitive, doesn't flow, too much scrolling etc. These are school boy errors BUT, they are trying to remedy those problems.

     

    It appears to me that the UI developers have tried to copy the current trends for web design instead of just building on the strengths of the the old design and augmenting those features.

     

    The old saying 'You don't throw the baby out with the bathwater' certainly rings true in this instance.

     

     

  6. In response to post #55305648. #55306153, #55309998, #55314643 are all replies on the same post.


    VulpesHilarianus wrote:

    Did some searching using a couple of different metrics. According to Alexa, SimilarWeb, and Quantcast Nexus Mods had a major traffic decrease when the website redesign launched. Also according to Alexa and Quantcast only 44% of users are switching to the new layout. Many are choosing old.nexusmods.com to use the site. For the Wayback Machine in the months of October and November the most popular saved versions were the old Nexus layout, with less than 1/3 being the new layout. People don't like it. I urge you, please, delay the launch of the redesign until the usability issues are sorted out. The massive amounts of wasted space, lack of contrasts, abhorrent element sizing, and focus on mobile for a PC-centric website are making people uncomfortable and having them avoid the site.

    EDIT: Also the forums are screwing up and not letting me post the entire comment.

    pacfish wrote: I'm one of the 44% that are using the new site and don't like it. But I'm trying to make it better with feedback. I also want to point out that the old site is the default. "nexusmods.com" is the old version and doesn't force the user to switch. There is an annoying button at the top that even the old.nexusmods.com has plastered on it.

    I don't think they'll release an unfinished product, they don't have a publishing company racing to make a return on the investment... But then there's Fallout 4 which took 5 years and is plagued with bugs, Starcraft 2 which is mostly bug free but has a limited game engine (supporting very small files in comparison to other games) and took 10 years, and HalfLife 3 which according to a Fallout 4 cartoon, is still in development in 2077.
    HomicidalGrouse wrote: Pretty much all links spread all over the internet lead back to the normal nexusmods domain.

    Of course the vast majority of people who visit the site will be using that one, and not the rd domain used to preview the new site.
    Dark0ne wrote:
    According to Alexa, SimilarWeb, and Quantcast Nexus Mods had a major traffic decrease when the website redesign launched


    Uh...? I'm looking at Alexa (which you take with a big pinch of salt as it only tracks people who have installed their toolbar), where there's been a steady decline since January of this year and SimilarWeb (whose tracking code we don't use, so is wildly inaccurate) is showing an uptick in September and October compared to previous months.

    Of the three, Quantcast is the only one that tracks accurately and the tracking code for Quantcast isn't tracking the redesign site right now (seriously, check the site source code. No tracking code on rd.nexusmods.com for quantcast). As such, anyone using the redesign is not being tracked on Quantcast, which is a lot of traffic. So yeah, there's going to be a downtick compared to previous months.

    Inspite of this, October 2017 still had 18m page views more than October 2016 according to Quantcast, despite declining traffic on the back of Fallout 4 getting older and despite the fact RD isn't being tracked on Quantcast yet.

    So when you say "major traffic decrease" I don't know WTF you're talking about, but it renders everything else you're saying as moot when the stats you're basing it off are just plain wrong.


    You're wasting your time bro. Don't you know the customer is always wrong?
  7. I love embracing new things, and usually embrace new things very quickly. I'm afraid that in my humble opinion, the guys at Nexus have dropped a huge clanger with the new design. I hold a degree in Web Design and Development, and simply put, this design does not flow, and is far from intuitive. It just looks a complete mess. The new design will put me off visiting the site. Sorry guys.

     

     

  8. W

    Check out the fTimeSpan variables in the Gameplay>Settings menu. Set them all to the desired time of day.

    Wouldn't that chage it for all vanilla worldspaces and not just the custom one?

     

     

    It would yes, so you would need to create a script to control these variables.

  9. Crashing right after the Bethesda screen is highly likely to be caused by a missing .esm (master file). One of your .esp files is looking for a masterfile that isn't there. I'm not familiar with all the mods you have so you will have to check their dependencies.

     

    EDIT: I've just noticed this regarding SFO - Expanded Diversity.esp. BOSS notes: Uninstall old version of Skyrim Flora Overhaul if using SFO - Expanded Diversity.esp. You have Skyrim Flora Overhaul active as well. That might be worth checking.

  10.  

    It appears some people interpreted "I'm retiring," as meaning, "I'm DONE! Yeah, I'm leaving NOW, so if there's any problems, they're not mine! HA-HA!"

     

    In that case, I'll go redownload COT 2.1 and hold onto the other new files for later. Good tidings with your fix, JJ!

     

    Well, it did kind of sound like that. :blush: (Either because it's happened to people before with other mod authors, or they would have taken that attitude themselves.)

     

    Though, I'm thoroughly embarrassed by my own lack of rationality in my reaction, and I regret ever saying anything at all (which is why I eventually deleted my comment). I'm sure others do, too.

     

    If anything, interpret it as people really, really liking the mod and taking JJC's decision to retire perhaps a little too seriously. Maybe in some back-handed manner, that denotes a level of respect. I dunno. The internet makes people reactionary and short-sighted for some reason. (Myself included.)

     

    My strong hand phrasing in relation to my retiring was probably more for my benefit - just so I understood it loud and clear. :)

     

    But in all seriousness, I can understand how people could become irrational if they think the rug is being pulled from under them. Sometimes, observing human behavior on here can be more interesting than the mods themselves. But, everything will be resolved. I shall retire in earnest once I know I'm leaving everything in working order.

  11. It appears some people interpreted "I'm retiring," as meaning, "I'm DONE! Yeah, I'm leaving NOW, so if there's any problems, they're not mine! HA-HA!"

     

    In that case, I'll go redownload COT 2.1 and hold onto the other new files for later. Good tidings with your fix, JJ!

     

    Very true, but that is human nature I suppose. I didn't spend 12 months of my life just to walk away when I was most needed. I'm sure there is a song lyric in there somewhere... :)

  12. It was brought to my attention that the files were loaded into older versions of TESVSnip. Probably 4.2 or 4.3.x. Notes were added to the BOSS list. I have loaded at least one file, and I am looking at others. I can confirm that the file I have looked at was saved with TESVSnip and therefore there is no way to know what kind of corruption has or has not occurred The author should not have used those versions of Snip with the files and I support the BOSS warnings.

     

    The file version is 0.85 which is an old TESVSnip bug. This means the files were not loaded into any version of the official CK from Bethesda, prior to being released to the public. The file version number is not simply a small over site it's an indication that the files was made with TESVSnip 4.2 or 4.3.x. Those versions do not use Zlib compression which is what the community believes Skyrim uses. TES5Edit used Zlib as well as the dev version of TESVSnip.

     

    I was going to provide the author with fixed files but the file has been hidden and he no longer accepts PMs. If someone knows the Author please have him PM me I would appreciate it. It will probably only take me a few short hours to look at all the files and have updated versions ready to be used.

     

    Hi Sharlikran

     

    I've messaged you.

     

    JJ

×
×
  • Create New...