Jump to content

m1sf1t711

Premium Member
  • Posts

    11
  • Joined

  • Last visited

Nexus Mods Profile

About m1sf1t711

m1sf1t711's Achievements

Rookie

Rookie (2/14)

  • Dedicated
  • Collaborator
  • First Post
  • Conversation Starter
  • Week One Done

Recent Badges

3

Reputation

  1. I am finding both the UI and the colour scheme hard to look at and it's putting me off browsing the site at all. I am only logging in to check my notifications. Please change it again to something without the black background, which makes everything harder to look at and take in. And as somebody else has commented, the new style feels cold and impersonal and less reflective of a playful community.
  2. Well I can report that everything ran smoothly with SSELODGen with no seasons mods and it installed smoothly with Vortex. DynDOLOD also ran very smoothly but Vortex again failed to install the Output zip with the following errors. I have also found that Vortex has been unusually unstable this evening, crashing whilst trying to deploy mods, notification messages not clearing after they're resolved, e.g. for managing conflict rules, and flashing during some operations. So I do feel that Vortex itself is part of my problem but I obviously can't back that up with anything factual. Just leaving it here in case it matches with any other reported user expereinces with the current version.
  3. Yeah that's what I thought I think my next step is to try removing all my seasons mods and rerunning SSEDLODGen and DynDOLOD after that, when the file load should be significantly smaller. Perhaps that will help and the problem is that I've just let my mod addiction go too far I will report back if it does help or if I dioscover anything else. Thank you for your patience Pickysaurus.
  4. Sorry also, is there a way I can test the files in the output for corruption so I can narrow down if it's happening during DynDOLOD generation or during the zipping process? Apologies if I'm straying too far from appropriate support queries for Vortex itself. I'll understand if that's the case.
  5. Thank you for the suggestion. I have tried that and still had the same problem but interestingly 7.zip crashed on the first attempt to zip the folder so now I'm wondering if I have a CPU problem Very disappointing if that proves to be the case as I only bought this PC in August. EDIT: some testing and basic research seems to imply that my CPU health is fine but it does hit max 100% usage when Vortex is trying to install the DynDOLOD Output zip. Is that normal?
  6. Sorry one more update. I closed and tried to reopen Vortex again after my last post and got an error message saying that my Vortex installation was corrupted. So I have updated to the 03.12.2024 release (which I hadn't realised had dropped) and tried to install the same DynDOLOD output zip again. I had another error message: So there are sometimes overlaps of files appearing in the error messages but always some differences. If my Vortex installation got corrupted then I'm thinking that something on my PC may be interfering with it. Can you point me towards anything you know of that might be causing it? I don't have any virus protection running during this other than Windows Defender as I know that can sometimes cause problems. My Windows 11 is up to date with the latest available updates. I have added an exception in Windows Virus security for the Vortex installation folder but this hasn't had any effect.
  7. Sorry to be returning but I am starting to wonder if my problem could actually be related to Vortex struggling to install very large files? I have rerun DynDOLOD Alpha 3 without problems, used it's own option to zip the files at the end, and then tried to install the Output zip. I have tried 4 times and each time Vortex has had an error at a different point in the process or with different files: Attempt 1: Attempt 2: Attempt 3: Attempt 4: I closed and restarted Vortex between attempts 3 and 4. I'm not a coder or any kind of expert in anything so if you can give me any ideas of how I might be able to get around this I'd be grateful.
  8. Yes I understand. I'm now having the same problems with DynDOLOD where it appears to generate ok (after a few attempts where it fails to generate some parts) but then when I try to install the zip file Vortex reports corrupted files. I've tried using DynDOLOD's own zipping option at the end of the run and using 7zip. But I appreciate this isn't your remit to troubleshoot for me, it just seems that maybe Vortex is more sensitive to, or aware of, corrupted files than in the past as I've been rerunning DynDOLOD regularly for years and not come across this particluar problem before. Nothing that I'm aware of has changed on my PC but that doesn't mean that nothing has lol ... and I appreciate that this is probably something unique to me. Thanks for taking the time to look at my posts. If I discover anything concrete I'll give another update in case it's helpful to anyone else.
  9. A further update ... I reran SSELODGen again making sure absolutely nothing else was open and the absolute minimum apps were running in the background and I have now successfully completed that and installed the output through Vortex. So I am delighted to report that the problem is entirely on my end and I appreciate that Vortex can so clearly identify problem files for me
  10. I realised that I'm not 100% certain those are the files relating to the message I posted so I have just updated Vortex to today's release version and tried again with that SSELODGen Output. This is the error message and I've attached the specific files DLC2SolstheimWorld.4.44.0.btr DLC2SolstheimWorld.4.44.56.btr DLC2SolstheimWorld.4.44.56.SPR.btr DLC2SolstheimWorld.4.44.56.SUM.btr
  11. Hi Pickysaurus Thank you for looking. Here's the zipped SSELODGen Output https://drive.google.com/file/d/1eIUWhooFGP3bhZbCQ_BhXn13l_45Z0KR/view?usp=sharing
  12. I keep getting the error message, below, or similar, when trying to install SSELODGen output or DynDOLOD Alpha 3 output. I even tried reinstalling an old SSELODGen output that it had successfully installed previously and had the same problem. I've tried reinstalling Vortex but this didn't resolve the issue.
×
×
  • Create New...