Jump to content

DayDreamer

Members
  • Posts

    822
  • Joined

  • Last visited

Everything posted by DayDreamer

  1. Of course, I'm not anonymous. Neither is Arthmoor. We just use a sobriquet and a pseudonym (respectively) as a handle. Your (rather old) quotation was not relevant to this discussion. As to the former, that may be the Roman view. However the British view seems to be that none of EU law was incorporated in the agreement that was not explicitly specified in the agreement. Notably leading to recent arguments about sausage. Yeah, I'm not sure infinite was the best legal term (as opposed to the more usual perpetual and irrevocable). Presumably they have consulted legal counsel. In either case, that seems to me it obviates the parlor model, as there is no possibility of taking their toys home. Arthmoor seems to be (correctly) splitting the difference, keeping the community-based mods at Nexusmods, and retaining his personal mods here. Although personally I'd have preferred he had left Bring Out Your Dead, as one of the folks who searched for missing burials. I'd always thought of that as a community effort.
  2. IANAL. However, I've briefed and argued pro se up to the state supreme court, and at the federal district and circuit. My areas of expertise have been FOIA, landlord-tenant, political redistricting, tax law, among others. I've been following US copyright issues for over 40 years, due to personal involvement in the Unix wars as a *BSD and Linux kernel contributor, and served as a subject matter expert in several cases. I'm also the former head of standards for Red Hat, and have spent much of my life discussing intellectual property law. Please re-read my earlier comment about the Parlor model. The transaction was from the modder to the distributor, who has rights to copy. Note that the EU has a contrary decision on the same subject. Now that UK is not part of the EU, we don't know the British status.
  3. This is not correct. See 17 U.S. Code ยง 109. Just "copy". Any "copy". We'd all granted a nonexclusive perpetual license to distribute copies. We knew that the distributor Nexus was paying for its infrastructure by ads and subscriptions. Once we've done that, there's no "recall" provision in the Act. Normally, an artist who wants to retrieve all the copies of their work has to pay to collect them, at the current going rate. There are plenty of extant examples. Nexus was generous enough to give notice of changes in their distribution model, and allow folks to rescind their license to distribute without cost. Again, this doctrine is US, and I'm US, but Nexus is British. If somebody has a good grasp of British copyright law, that might be interesting.
  4. Thanks for posting the link. I'd been awfully confused about usage here of "Cathedral", as I'm a long-time Open Source participant (45+ years, since before the term "Open Source"). We have used Cathedral differently, as in The Cathedral and the Bazaar (see https://en.wikipedia.org/wiki/The_Cathedral_and_the_Bazaar). I've always been a little uncomfortable with Nexus. My early Skyrim hosting was Steamworks (built-in the CK) and Dark Creations. But folks were re-posting my stuff on Nexus with somewhat different names, so it seemed best to use Nexus too and get ahead of the problem. Then Dark Creations went away, and the migration seemed fortuitous. Nexus added Donation Points. Folks have re-posted various things with Donation Points turned on, even though I'd explicitly selected "You are not allowed to earn Donation Points for your mods if they use my assets". The most egregious is where they combined my nif changes with SMIM mesh and texture changes, even though both of us don't allow Donation Points for derivatives. There's no good enforcement mechanism. On the other hand, I'm not sure that the "Parlor" model is even legal under the "first sale doctrine". But that's an Americanism, and Nexus is British-based. I've given my modding contributions to be available to the general public for free. I'm irked when somebody tries to profit from bundles that include my works. But I'm also at end of life, so don't have a lot of fight leftover for this issue.
  5. https://elderscrolls.bethesda.net/en/article/REybYU3Gy2InVlHmus4UC/skyrim-10th-anniversary-fan-celebration https://www.theverge.com/2021/8/19/22633130/skyrim-next-gen-upgrade-update-anniversary-special-edition-bethesda We'll need a new topic section.
  6. I agree that the stories could be moved to their own category. I do like reading them from time to time. It brings back some of the feel of Andalay Bay's sites. Many of us have a story in mind as we progress. It's nice to see some written down. But posting them in General Discussion means they dominate the recents. When I'm looking in on a Sunday evening, I'm just trying to see all the recent topics at a glance.
  7. It is very sad that so many console players are willing to buy a game where the world gradually becomes perpetually bare and desolate, NPCs don't leave their homes, weapon racks and other activities don't work, many quests don't run properly, and the save games bloat so that eventually the game won't play anymore. If I'd known about the vast number of bugs, I'd never have bought the game. Because of the press reported bugs, I'd delayed buying the game until Feb 2012, expecting that the bugs would be fixed by then -- never imagining that Bethesda would actually add more bugs breaking things that already worked.... To be honest, if I'd not invested so much time into US*P, I'd not still be reporting and fixing bugs. At some point, responsibility to the community became more important than the game itself. Someday, I hope to finish a run-through of the game. The last best try died after 500+ hours and 8901 saves. So far, 220 hours and 6326 saves.
  8. There is Ysolda forcegreet dialogue, so it helps to have a forcegreet package to make that happen. She is essential (since official patch 1.5). There are dependencies in cleaning up the Markarth temple that depend on the Rorikstead stages. Likewise, there is Ennis dialogue conditioned on speaking to Ysolda that makes no sense in any other order than Rorikstead -> Whiterun -> Rorikstead. The quest stages are intended to be mostly linear, within an open world where they can happen partly out of order. The mistake in US*P is that the forcegreet package is missing a condition that you've talked to Ennis. Ysolda should not be telling you that she's tired of waiting for payment until you've been pointed to her by Ennis. Otherwise you get dangling objectives and leftover persistent objects. US*P is supposed to be only bug fixes: vanilla seemingly intended by the developers as revealed by underlying data. That's why the Alto Wine is replaced by Holy Water. The developers had made a quest Alias_DA14HolyWater, and the note explicitly says "Holy Water". There's an unused potion called Holy Water. My guess is that during development somebody stuck alto wine in the holy water alias as a placeholder until the graphics folks made them the holy water item, then forgot to update the alias. Call it a QA failure. Skyrim without US*P isn't worth playing.
  9. This is a US*P change. Particularly jarring for those who have married her. Vanilla, she doesn't change behavior, instead you have to find her. Should this be reverted? Moira is created as you talk to Isolda. Vanilla, Moira remains forever until killed, and you are supposed to return her ring to Isolda. Isolda says "Don't forget you still owe me!". But there is no way to return the ring after the quest is over, which is a bug. US*P, if Isolda tells you about Morvunskar, Moira is disabled again and replaced by a generic hagraven. That fixes the bugs.
  10. There isn't any Alto Wine. The Wine alias is actually filled with "Holy Water", as is the Water alias. No problem, other than you have to carry 1 extra encumbrance. The Giant Toe was originally intended to be a Giant's club. It is annoying that they stack with non-quest toes, but that's a game engine issue. There are other items (such as follower bows) that have the same name, yet do not stack. There are no feathers. They are merely mentioned in the quest note. That is kept in the DA14Start quest. It is supposed to be copied into DA14 quest at the latter start. If the alias doesn't fill due to engine timing issues, you can end up in a radiantly selected Inn. (Has not happened to me, but it looks like the possible explaination.)
  11. Retrospectively leading the goat requires a minor script change to DA14SammyScript !GetOwningQuest().IsStageDone(75) && !GetOwningQuest().IsStageDone(85) The DA14SammyFollow package is a bit odd, testing for >= 65 and <= 75. There isn't a 65, so == 75 would be sufficient. But in the interest of minimal changes, I've left it alone.
  12. To make it work retroactively, copy the StageDone style conditions from the US*P Ysolda changes into the earlier Ennis dialogue and packages, so they operate similarly. Fairly straightforward. Found an error in the US*P Ysolda forcegreet package conditions. The result of the forcegreet dialogue is stage 100, not 130; 130 is later, transient, and immediately sets stage 135 (which is already correctly checked). Likewise, the forcegreet dialogue conditional should be stage 100, not 150; 150 is the end of the sequence. We really don't want repeated forcegreets. They are flagged as Once, but we know that doesn't always work.
  13. Turns out the USKP Ysolda changes also broke the cleanup in the temple via stage 50 script fragment (begin talking to Ennis), and various giant issues. An easy fix is to condition the USKP Ysolda package and dialogue >= stage 84, instead of stage 10. Now to figure out how to make this work retroactively mid-quest.
  14. That's another potential bug. I'll look into it. You are supposed to be returned to where you talked to Sam. Another bug is that the "drunken night of revelry that crossed all of Skyrim" takes no time at all. It should take at least 24 hours. That looks like the original intent. USKP made it more parallel, adding a forcegreet package to Ysolda. That's what broke Ennis and the goat. The conditions are wrong. Ysolda shouldn't talk to you about this until you have talked to Ennis. Also, Ysolda hangs around outdoors until you complete the quest. That's not the original design, and a bit odd. Moreover, apparently Moira isn't even spawned until you talk to Ysolda (stage 100). While more parallel makes more logical sense, as all the events have happened "across Skyrim" at quest start, there are a lot of vanilla linear conditions. The current US*P approach is haphazard, and didn't handle all of the possible transitions.
  15. https://en.uesp.net/wiki/Skyrim:A_Night_To_Remember The progression is wonky. It seems to be logically parallel; once started, all the background events have already happened and could to be investigated individually. Instead, some of the quest stages are linear or forgotten. Arriving at Whiterun before Rorikstead causes Ysolda to forcegreet, but disables part of Rorikstead. Then, going to Rorikstead has no forcegreet, but you still have the objective. It actually makes no sense to ask about a goat, as you've never had the forcegreet about the goat. Yet asking still doesn't clear the objective. Looking at the other setstages, there are similar problems with Witchmist Grove, because you can skip it by pursuading Ysolda, whereas pursuading Senna and Ennis doesn't skip the next step. There are 2 ways to fix this, and the objective bugs. Force it to be more linear? (Ysolda doesn't talk until after Senna and Ennis.) Allow Senna, Ennis, Ysolda, and Moira to proceed in parallel? I'm in favor of #2, although it is a bit more work. Currently, there isn't a good way for Morvunskar to happen without doing some of the others. Ysolda is a bottleneck. That could be fixed by having everything be created at the start. The dialogue hints that it should remain live until you've returned the ring, even after persuading Ysolda to tell you about Morvunskar. So the Witchmist Grove objective needs to stay in the journal until the end. Currently it disappears after persuading Ysolda. There are other inconsistencies mentioned in the UESP notes. They could be cleaned up as well. Which should it be: more linear or more parallel?
  16. Thanks, this is important to know. I'm wondering how many other places are affected by this "multithreading".... It does make it very hard to follow, and violates the usual teaching on structured programming and object methods. No wonder that we had such problems getting the weapon rack scripts to work. Running two parallel scripts was bad enough. If they could in turn be split into threads without any thread locking or coordination method, what a mess! Thanks also for printing out each retroscript running. In December, I'd reported the 4.2.4 variable changes in the log; the kind of thing that I've always checked. Never knew to check that a retroscript was running multiple times. Also, idempotency. Sometimes it seems to me that Bethesda didn't hire anybody with compiler or kernel experience. Back in the day (mid-1970s), we all took a semester systems programming class (multiprocessing scheduler), and a full year compiler class. As time went by, those became graduate level specializations. Nowadays, my colleagues complain kids just want to learn Rudy on Rails to get a job. Anyway, want to thank whomever SenorCorruptedSave might be (you really don't need to hide your name around here). Excellent detective work.
  17. If Papyrus allows out of order parallel processing within a single function, then a lot of scripts aren't going to work. Could you cite an example? Calling the same function 3 different ways isn't a good programming practice. Invoking the serial sequence of functions as subfunctions just builds up the stack, another poor programming practice. All those redundant stage checks aren't good practice either. If it is required to make Papyrus work, then it needs to be better documented.
  18. It's very sad to learn that this wasn't a Bethesda issue after all (other than it shouldn't crash on saves). This was a USSEP issue, now described in https://www.afkmods.com/index.php?/topic/5806-updating-from-ussep-422-to-424b-causes-new-retroscripts-to-run-everytime-you-load-a-save/ My 500+ hour savefile corrupted. Nearly a year of my own "spare" time.
  19. That's an odd bit of coding. For one thing, there are two tests for Are those supposed to be ElseIf? Running version USSEP 400, upgrading to 424. Doesn't this require running every Process() in the list? Why is it better to have 406 Process() call 407 Process() call 408 Process() et cetera?
  20. Rather than Flora Respawn Fix, I'm running https://www.nexusmods.com/skyrimspecialedition/mods/43532?tab=description Scrambled Bugs. It is under active development. But running a 3rd game engine patch does make game loading rather slow.... I wish they'd combine efforts.
  21. Then this forum package must be really easy to setup. A basic locked down version of wikimedia isn't that hard. As Bethesda did for Creation Kit. It's the backend multiuser multiwiki enhancements that add complexity and security issues. Bethesda didn't do them, so the Creation Kit wiki is very slow. UESP did a better job, but they also added a lot of specialized templates and name spaces. While I'm a former developer (and still on the tech list), the codebase has changed a lot in 15 years. So I'd not be of much help. Still, this forum package gets the job done. Just treat the OP as the Main page, and the rest as Talk page subsections, as is the practice for the big U*P releases and many of the mod releases.
  22. See old https://afktrack.afkmods.com/index.php?a=issues&i=17351 and new https://afktrack.afkmods.com/index.php?a=issues&i=31330 @BlackPetehad attempted to fix the predators. I've discovered that also the prey have a Z problem. The 3 prey have a preferred path to town, so it is clear developers intended predators to follow prey into town. There is also dialogue mentioning animal attacks in town. This seems to slow the predators down somewhat, as they have prey to attack first. I've added a second patch that may help get the patrol in place sooner. No reason for all the patrollers to start in a block near the water. Please check that USSEP [000A4491] isn't a stray edit. I've found no log entry for it.
  23. Over all these years, I've never gotten very far in Skyrim. Since Feb 2012, I kept finding bugs, gave up for many months to play something else (Northgard this past year, No Man's Sky the year before that, Civilization going back to version 1 and the board game in 1980s), and eventually start over. The only character I've ever tried is always a Breton named Cormac or Camroc. My long-time persona Cormac an t-aislingeach is/was a bard in the Society for Creative Anachronism since 1976. As I'd discovered picking flowers in my earliest Skyrim run, the first innkeeper encourages me to use their lab, and the bard directs me to the Bards College, I've always played an alchemist-bard who is dependent on followers for help. He doesn't really fit in any of the main factions, but is willing to be recruited by any of them for a time. My goal is legendary alchemy and speech.
  24. Could you place a warning at the top of the cleaning pages here? I didn't know, and only recently noticed obvious problems that caused me to search and find the warnings. This needs to be prominently documented somewhere. Reload after death is probably important. Personally, I'm a rather tediously cautious role player, and rarely die. Simply by not doing a quest as soon as it is offered. By rule of thumb, wait at least 10 levels after it is offered. Unfortunately, there are some severe surprises, such as opponents that are always 1.2 or even 1.5 times your level. That's small at levels 5-10, but often insurmountable by level 30. So UESP warnings help, too. In my case, I've been frequently reloading in the same cell. I'm a "completionist", and like to hear what alternative answers they've recorded. Then pick the most interesting one. [I've changed the title to reflect that this is the most likely culprit, at least from my testing process.]
  25. I've tested with the bAllTargetsInTrigger unchecked and the disable after enter checked. Because it's in an interior, there's no significant difference, other than now cleaning up the trigger itself afterward. The package order and trigger box seem to be organized so that this wouldn't trigger with the occupants sleeping. But they don't lock the door. That's a bug. All that seems to happen is they are standing in different places, yet still allow you to buy/sell immediately anyway. You can enter in the middle of the night and be invited to step up to the counter. That's another bug. The problem turns out to be their aliases in DialogueMarkarth. The packages are duplicated there. By adding a 8x16 schedule to the packages, they can fall through to their sleeping and eating packages. https://afktrack.afkmods.com/index.php?a=issues&i=31301
×
×
  • Create New...