0 of 0
File information
Created by
vurt and MarcuriosUploaded by
vurtVirus scan
Some manually verified files
Notifications
2767 comments
My new grass mod is out, works well with WFO
A Wasteland in Bloom<- Click
...also available Groundcover Overhaul and Improved Plants
Issues? Read the post by RogerLibiez2 below;
What I did was set the "bModifyDirectXBehavior" line in New Vegas Tick Fix .ini to "1" instead of "0" and set my GPU to performance mode on New Vegas exe.
To generate the Tree LODs for this mod you can use XLODGEN
Vurt on Youtube
This way you will be able to generate proper tree lod.
One, is the latest version the same as the fertile version? Because I want fertile, more trees.
Second, can someone walk me through generating LOD like a literal baby?
I tried on my own and have ended up having to do a complete reinstall because I'm so confused. The LOD I generated was all messed up. I had building lod on tree lod, looking very strange, and cliff lod looking very strange too, all messed up. I would prefer not to have messed up LOD again.
I followed instructions as far as I'm aware, including using the other lod resource mods as suggested in the description, plus one lod resource mod for NMCs. The one thing I think I did different was select all the world spaces? Because I'm using the HH stuff too and didn't know which worldspaces to have selected. I just now read the comment that suggests LOD Fixes and Improvements, maybe I needed that?
EDIT: I am currently trying out the LOD Guide from Viva New Vegas to see if it helps.
As far as I know, it makes some pretty useful and significant changes to your mod.
Have you considering these fixes as a future update to the main mod?
Well, or at least discuss it with Inthegrave.
That is because some LOD is treelod, which was not supplied in vanilla BSA files, but was enabled on vanilla forms.
That in turn means that if you supply the treelod assets on vanilla game, you get LOD up close errors.
if for some reason i have the will to make all LOD 3DLOD (static) in the future, those flags could be re-enabled, but not right now.
Also, there are no dirty edits, the edits made in WFO are made with a specific reason.
And if there would be ITM's, that would mean i haven't been checking my file, and i don't think that is the case, i always check my file with xEdit before saving it. And making the mod a ESM gave us crashing problems in the past, and it prevented people from putting it last in the load order, which means that if you have another mod that touches the placement of a vanilla tree that was deleted (disabled) in WFO, it will again give you the LOD up close problem, So if you want to use that patch, be my guest, but don't come crying to us if you have LOD up close because another mod re-enables vanilla forms, or your game starts crashing without obvious cause.
Not everything is what it seems, and sometimes you have to do things in a way that is not generally recommended.
So no, we won't incoorporate these "fixes", cause they arent fixes as far as i'm concerned.
Also, i don't see why we would need to discuss this with InTheGrave if we should want to make these edits.
If these edits would have been neccesary, i would have made them long before he did, but i didn't cause they would mess up the mod for many people that don't know how to fix errors themselves that could come from using these edits, or this patch.
The reason the mod is like it is, is to make it as noob friendly as it can be, so long as the follow the given instructions to put it last in the load order.
Also there is a reason a lot of the modding community is moving towards ESM. ESPs increase memory usage and save file size
because you are forcing all the placed REFs (including the disabled ones which should not have been disabled but swapped for the new records you added) to be forced into memory at all times.
If even just the mod was flagged as ESM (file extension doesn't need changed) I would hide my mod as I feel like the most major issue
would have been addressed. Rest of the issues would be fairly minor at that point.
To extend an olive branch, if either of the authors of this mod want me to takedown my patch then I will do so just say the word.
But I would hope the changes are made because they still should be done (Flagging as ESM, removal of dirty edits and brand new
placed REFs removed and the old disable ones reenabled and swapped instead) or even just esm flagging at the very least.
i have like 100+ games that i wanted to try out so, having fun with that.
Took a break from modding (and gaming), now all i do is 3D printing + painting what i print
Chatgpt does agree with me that there's quite a lot of cacti in southern nevada, also google images does agree with it, but you're right it seems like other parts might have more perhaps.
Again, i don't really see how its important to represent today's Nevada when the game is 1) not even taking place in this universe, FO is an alternative universe of earth. 2) it's taking place in the far future. 3) scenario is after a nuclear blast and nature is reclaiming itself, we already know for a fact that this affects nature in a very profound way, from e.g looking at Chernobyl, and that was not many hundreds of years ago.
Not meant as a diss... maybe it can help you with the immersion.
If you want to edit the cacti's sure, quite a complex task since it would involve LOD editing. You can likely find tutorials for lod editing on e.g youtube for NV. but apart from that its easy, you'll just need to copy a small bush or whatever, name it like the cacti you want to remove, done, the game will now show bushes instead of cacti's, but you'll have cacti in the distance unless you edit the LOD's .
And clean up the deleted references after removing the static with a xEdit filter.
If you don't know how to do that, send me a PM and i'll fix a file up for you.
It's so easy to mess this up, so even after years of modding, i get very, very nervous about the whole procedure.
Could you please tell me if this is the correct order to install these mods?
1 NMCs Textures
2 NMC New Vegas Patch for ALL Sized packs
3 Ojo Bueno Texture Pack
4 FNVLODGen Resources
5 LODadditions
6 Much Needed LOD
7 WFO Medium Resolution version
8 A Wasteland in Bloom
And then generate LOD?
This mod, along with NMC's Texture Packs, and the 4GB Patch... are causing siginificant performance issues that result in black screens, flickering textures, missing textures, invisible textures... and extremely poor FPS... and random crashing to desktop.
I tested this by completely deleting every mod I've used, wiping out my entire game installation, including all save games; and re-installed a fresh clean copy of the game, then reinstalled the mods one at a time, launching the game after each one.... and the only other mods I have are NV Script Extender, and NV Mesh Improvement mod.... and I only have NVSE because I was thinking about installing the updated version of Nevada Skies, but haven't yet.
Anyway, as I installed this one, I experienced flickering textures, and poor performance with FPS dropping down to 5 - 10... Removing all mods, and running this one solo, the problems persisted.... but only multiplied and got worse as either NMC's Texture Packs, or the 4GB Patch were installed with it...
Once these three mods were removed, I experienced smooth gameplay at 90+ FPS and no more crashing.
I refuse to update my drivers as long as i hear that people have problems with it.
Knowing AMD that could take quite some time, they usually take a few years to fix thing that they don't find all that important.
AMD drivers will not handle the textures very well with current versions, but this fixed it for me.
I only got a 32MB file, maybe another upload can fix this?
i hope he can upload it again.
EDIT: i just reuploaded (it actually did not entirely reupload but merely finalized in the other browser, something it didn't seem to be able to do in Firefox yesterday) and it works fine on my end in MO2.
So it should be good now.
This problem of "the files are being processed" hanging forever is a long standing one on Nexus it seems, i read a topic that stated that it was supposed to be fixed in 2023, but it seems that it isn't fixed when you upload in Firefox, (just mentioning this for myself so i will remember in the future)
MO2 users should download the file manually and then use the "install mod" option in MO2.
the main download manager link is for NMM or Vortex, i do not use either of them so let me know if that still doesnt work, cause than i might need to add a script for NMM and Vortex to work correctly.