SMB92
-
Posts
2304 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by SMB92
-
-
The best way to deal with a "Merged patch" approach is to generate with all those mods loaded, at once. I started a project doing something like this but it's far more work/upkeep than I care to commit. You will need to keep on top of mod updates, and be prepared to edit and regenerate locations that cause problems for previs (loose example, trees in front of windows might cause a noticeable occlusion pop in/out). You will get far more consistent results this way, but it's a lot to maintain as said. From there you can consider using that xEdit script that optimises the generation.
RE version control, you may want to look into that for CK, but it might just be easier to keep manual backups of the plugin and generations. In fact I seem to have a lot of drama with previs gens with VC enabled (seems to hang a lot, probably due to network setup), not that I've bothered to solve it though.
-
Generally persistent and disabled objects aren't included in the generation. Didn't know objects with emittance were excluded, so that's cool to know.
I'm a little confused over the usefulness of these commands. The previs command seems to be non-precombined from our limited testing. Doesn't seem to be any command for precombined previs in the CK EXE strings. I'm guessing that's why you end up with 2 plug-ins. I'm thinking these were for some kind of quick testing purposes, without wrecking the master.
What I was hoping was this command would let us generate previs on a world scale reliably. Suppose it still is, if one were keen on disabling precombineds at the plugin level, and then marking all the relevant objects in the game as scrappable, leaving the rest for occlusion. Still, performance would be much worse so yeah, probably not viable. But it's something.
-
Man y'all must really love this new premium advert/interruption. Y'all ought to apply for staff member status or join the marketing and pr team. Y'all must of seen that ad for the first time and been like, "man, what a great addition to the nexus experience this is, never have I seen such a glorious wonder. Surely I will champion this for all the days to come".
Stuff the dictionary definition, people paying for supporter status shouldn't have that forced down their throat. That is such poor form. At the very least it should be made much less aggressive for the supporters.
-
I think it's a sign of greed personally.
The Nexus promotes its offerings to bring in revenue to keep the lights on and reward mod authors.
The users who have free accounts want everything for free without interruptions, distractions, or limitations forever - damn the costs!
Who's greedy again?
You liked my donut story but you clearly missed the point.
Oh I totally get the point, despite a few flaws in its relevance to this debacle. I think you read too far Into that first line and not paid attention to anything else I have said. I get the business standpoint, and I get the folks that are upset about this (even if they can't quite quantify what it is they expect is the fair solution to their problem, or in some cases, what the problem even is). I've offered at least some empathy where others seem to simply want to argue. Really quite tiresome.
But let me reiterate and be more specific about that particular line. I think it's greedy because I find this tactic to be one of coercion, by way of annoyance. A lot of mobs are doing it. Some of them are really quite bad, like YouTube for example. If you like this tactic and want to champion it, you go right ahead and keep wondering why the response is mostly negative. But hey, all good if it brings in the money, who cares how it came. Speaking of which the fact they are doing it to paid supporters is really pathetic. I find that to be a greedy decision.
But let's stop right here and propose an ultimatum. Why not just lock the site behind a pay wall? As it was mentioned above, nexus could be charging for everything. Let's not beat around the bush then aye. Let's start charging like a bull out of a gate, as per the mandate of the majority of companies as of late. Surely it's inevitable. Wouldn't that be a great solution? Wall the peasants off so all you champions of business and capitalism can revel in your splendour? What a utopia that could be. Oh no wait, that would be paid modding of sorts. Hmm, best we just coerce the users into buying a membership then.
-
Well said, Steve
-
Functionally, the "download nag" page is obtrusive in nature. I really doubt the website devs thought for a second anyone would be happy about it. It's a tad annoying, but I'm not about to take up arms about it.
Speaking from experience, I've found most people - myself included - tend to express genuine concern in overly dramatic ways.
I think it's a sign of greed personally. I don't think the nexus was doing so bad for itself prior to this move. Like I said, make no mistake it's a commercial operation, get used to it. It's not just the nexus, it's everywhere. I know people are tired of having to fork out for everything (especially when they previously didn't have to) and it doesn't help. I paid for me lifetime membership at a time I had a lot of coin. I would most certainly be annoyed right now if I was being served with the same pop up ad (and yes it's an ad) about the membership, especially if I was a supporter (that's just non sense IMO).
I also have some concern the lifetime membership will disappear and become subscription. From a business angle, I get it, but no one will like it.
Vote with your wallet and your mods. That's all you can do.
-
Arguably, the membership and Vortex "ads" are Public Service Announcements, not commercial advertising.
Â
KEK, no its an advertisement, through and through.
-
I really like that donut paradigm, @fireundubh
Significant amount of energy spent in this thread. Wowee. A few things come to mind when I think of this dilemma. I was thinking of posting something longer and perhaps rational, but I find that I dont even care enough any more to bother. This scene has gone down the drain.
I'll say this. I don't think I like the idea of this subject being turned into another "inclusiveness" debate/argument. Getting tired of that angle. But make no mistake, Nexus is a commercial operation. It's not a charity. It's not going to get any better for the free users, pretty much ever.
-
That is correct MageBlade. Likely the Discord will be the only download location as well.
-
Fair enough. On a side note I did see some settings related to engine management at high/low fps, haven't looked much further as to what gets controlled there yet.
-
Rofl 25 grids. Most if not all the rendering is still single threaded though, worth noting (doesn't reflect accurately in total usage stat). And Lol that 750 isn't doing so badly.
Interesting your finding with the keyboard lag. Is that with the prerendered frame buffer (usual cause for that sort of thing) set to 0/1?
-
Zzyxzz, causes vary for these symptoms, depends how your system is setup. I take it you used the fps cap instead of vsync, so possibly in your case frame times were wildly inconsistent when not at max? Not withstanding any hardware level issue (I'd expect such issues when IMC/RAM is unstable or even CPU throttling). Anyway that's a rabbit hole I won't go much further into, such a case specific thing.
My experience with this game, I conclude the CPU is more important overall, not just for the rendering factor but the sheer amount of data to process, particularly when modded (think, AI, Papyrus, inventory etc). Faster RAM is a help all the same (particularly for Ryzen as is known).
Here's a little comparison for you on the GPU front with ones I've owned, for trivial sake. With game maxed to Ultra, various high quality mods installed (note that I generally choose wisely, no 4k door knobs etc etc lol) and reasonable INI settings.
HD7970 1100mhz 1080P: Be happy if ever gets 30fps let alone 20. Unplayable at this setting.
Intel iGPU (8700k) 1080P: Amazingly gets up to 3-5 fps
Intel iGPU (8700k) 1440P: 1 frame per every other second or so, lmfao
RX580 Strix 1080P: very playable but hangs around the mid 40s a lot (Boston worse). Radeon enhanced sync brings mad stutter, found vsync best (144hz screen = 72fps sync for F4, locked to 60 with Riva, smoothest experience IMO).
RX580 Strix 1440P: Generally not playable, not unlike the 7970 at 1080P.
980ti 1080P Gsync: Very comfortable, except the typical trouble spots on the CPU downtown and elsewhere. Observed VRAM always maxed at 4.5 or so gig. Weird since 1080ti happily eats it's 11GB in F4 for me.
980Ti 1440P Gsync: Runs like the RX580 in 1080p, but a bit worse perhaps. Generally didn't like to play at this res with it.
1080Ti 1080P Gsync: CPU only bottleneck now, some places downtown take a dive when waiting on CPU to draw as usual.
1080ti 1440P Gsync: As above, although I expect fps to hover 60 to 100 in most places not Boston (rather than be maxed, although they still often are). Some of those fps hitting places I mentioned may sink me down to the 30s and 40s.
I have to imagine oldmate with the HD6500 was running some fairly low settings.
Anyway trivia/hardware rant over hahaha
-
Wanderer, glad you were able to get through those initial troubles. Crashing at generating PC has been a rare experience for me (usually something mod specific, e.g didn't like a mesh),
Vis on the other hand is usually always memory (RAM/page file). This process will eat memory alive. I have been told this is due to the way that it loads every texture for every processed object into memory (this may also relate to why Bethesda says they had memory concerns in making this runtime generated perhaps). Usually I grant the CK 64GB of page file and its fine, but I have been told one can remove textures from the data folder as well, and then run the generation without concern for memory.
-
Generally any object that has a recipe for building or marked as "initially disabled" won't be included/incorporated in your PC meshes. And yes moving a piece that was baked in PC will break it for that cell, the system will turn off for that area when that cell is loaded in game.
Haven't taken the the time to play with the script yet, so can't help you there. What problems are you having exactly? Vis not generating properly?
-
I think the previs/precombine optimization systems are far more of an extremely yucky, itchy, nasty compromise than a solution; Probably just there to get things going on sub-sub-par hardware (and to appease the "ZOMFG!!!! 50FPS IS UNPLAYABLE!!!!!!!1!!!!!!" crowd). I've ran without any of them on my old Radeon HD6500 and I still do so with a 1080Ti.
After having looked into Umbra tech a bit further, I've shifted my tune a bit. The precombined system as well. Both are great ideas, you could call them lazy man's systems, but then if you were a Dev you'd want to automate as much as possible too.
Fallouts implementation is quite good, compared to some games I've seen using Umbra now where I see things pop in and out on certain camera angles, I see it far less in F4.
It's just not exactly a modding friendly solution, thats why it sucks in most people's eyes. What sucks twice as bad is that Beth hasn't really optimized a lot of the busier scenes (i.e Boston) if not outright over trashed them, and hidden this behind said system.
-
Can't recall when it was, might have been earlier this year, lol. Haven't been playing with cells much, only the odd regen for myself.
Yeah bad business that with NIFSkope, hopefully one day dude will return.
Just snuck in a look at XPRI before bed, good general description for what that field includes would be: "animated objects (i.e containers) + furniture + some movable statics (even when doesn't make sense like an odd tire) + light emitting statics/probably other types + some really random stuff like a hazard or xheading marker O.o". Maybe you could term it as "non-mundane things with a chance of an erroneous inclusion" XD
-
That is a good point, I've seen that with CK myself. I've had some weird ones though, such as a tree by a window, a staircase near a door and a tree cluster by a larger tree would always fail to have collision (and be prone to flickering) until I moved them a bit. On the whole these cases a rare, can't say I go looking for it either. Seen some other folk mention similar things.
I'll go back and revisit some files I did regens for and see what it listed for XPRI, see if can make some sense out of it. There was a conversation on this in the xEdit server a while ago I think, not sure if research is still on going there, but I heard the NIFSkope guy has left the scene.
-
@VlitS
Thanks for the answer. I deleted the vis files for both cells and regend precombined vis only. That worked. As general rule of thumb, as probably all cells have precombined. Should one only use precombined vis? Or when to use the normal vis
One option is for cells without precombineds, the other with.
Also, I had an understanding the physics refs were for collision and possibly animation. It appears at times during runtime, when previs isn't calculated/generated properly, collision may not load for some objects.
-
Not sure I understand that last reply.
Anywho, been a long while since I started this project. I lack this level of enthusiasm anymore, lol.
NV has come such a long way now, this is fairly redundant. I'd recommend not necro posting here any more.
-
The Papyrus section if the INI should only be for enabling debug logs, and some setting which are really not recommended to change.
I doubt this part of it has anything to do with your companion problems.
-
AFAIK there is NO way to modify and persist changes on base records in the game, at least not in this category.
There are ways you could achieve this but none of them would be pretty. You'd be better off making the changes in a plugin and calling it a day.
-
Set a 32GB page file in Windows, should fix it unless you have some other weird thing going on. Avoid having Monsignor plaza loaded as well, or if you do disable the rogue occlusion box hidden in the building. Or you'll have flickering previs everywhere
-
Cool. Nothing really wrong with what you were doing, but I'd say you're probably covering the same 3x3 grid over and over on a number of those cells. Ain't nobody got time for that XD
I did the whole of Cambridge once. I think 11 or 13 grids squared. Consumed all 32GB of my Ram, all 11GB of my Gpu and a further 30GB+ of page file (the latter seems to matter more to the CK, at least in my experience). I was only trying to cover a number of spread out cells for Beantown, however I found the performance in Cambridge was better across the board, better average frametimes etc etc. Bethesda has missed a bunch of stuff, no doubt. However, our CK generator is not without its flaws, it will fail to include or link physics to some objects and in some cases produce really bad previs (but this is mostly just Umbra/calculation being imperfect) among other odd things from time to time, and may differ per generation.
-
@Mycenia - If I were you and those 14 cells you wanna regen are all in one main area, I'd set the ugrids value high and find the middle cell that would cover all them cells and regen that way. You might even end up catching stuff from vanilla that may not be done by default. This does require a decent computer to do however, namely a lot of RAM/page file.
Really I wouldn't worry much about it, if you now have conflicts just put your file last or resolve by hand etc etc. Is this something you want to release?
Fallout 4 Optimization and Performance Systems Explained
in Creation Kit and Modders
Posted
Be careful you didn't pick up that hidden occlusion box in Monsignor Plaza. It'll break the generation in this fashion. You'll need to find it and disable it. It's in the top of a building that had a cracked roof. Don't have a pic handy sorry.
I'm not familiar with that mod so I won't comment beyond that.