Weird Blocks Spawning
-
Ok so yesterday I decided to fuck my game up lol (the saying don't fix it if it isnt broken applies well here). I was extremely happy with how I had my graphics mods set up. But I was having some game crashes which I was thinking was being cause by NVR (when the clouds spawn in after changing weather). So i decided to update which included updating VisualV as well, I updated both by OIV, and noticed the game STILL crashing. I uninstalled both VisualV and NVR, now the problem is these weird ass blocks appearing in my game. Kinda spooked me out at first. Here's some screens, anyone know what might be causing this?
-
@westcoastsosa Are you using an old version of Map Builder? Apparently this was an issue back in the days but has been fixed in a newer version: https://forums.gta5-mods.com/post/51170
-
@Unknown-Modder I think I removed it not too long ago since I wasnt using it, maybe i forgot to delete some of the files, ill have a look thanks.
-
@Unknown-Modder said in Weird Blocks Spawning:
@westcoastsosa Are you using an old version of Map Builder? Apparently this was an issue back in the days but has been fixed in a newer version: https://forums.gta5-mods.com/post/51170
Those are definitely Map Builder props. For some of those to just spawn randomly, though, I can't begin to fathom how severely ff-ed up that mod must have been then, as it's supposed to be just a ytyp dbase + props.
-
@westcoastsosa said in Weird Blocks Spawning:
@Unknown-Modder I think I removed it not too long ago since I wasnt using it, maybe i forgot to delete some of the files, ill have a look thanks.
I currently use Map Builder 2.08 CE now, btw: and it's the first time it's rock stable.
-
@meimeiriver @Unknown-Modder It's weird. I removed everything that was in the download but they still spawn. I even updated to the newer version (which didn't fix it). So I uninstalled again with no difference
-
@westcoastsosa said in Weird Blocks Spawning:
@meimeiriver @Unknown-Modder It's weird. I removed everything that was in the download but they still spawn. I even updated to the newer version (which didn't fix it). So I uninstalled again with no difference
It should suffice just to remove the map_builder DLC from your mod's dlclist.xml file. If the objects persist, are you sure you didn't also install map_builder in 'main' at some point?! If all that fails, use OpenIV search, and try and find ancient_rock.ydr, for instance (there are 2 of those in your picture). It's gotta be somewhere!
Also, it still totally baffles me how the Map Builder author managed for the objects to randomly spawn. A ytyp file doesn't normally spawn objects (unless it had a CMloArchetypeDef instance defined in it, somehow, which got instantiated elsewhere: the chances of that happening here are as good as 0, btw).
So, I can only imagine that the old Map Builder DLC must have a horribly fubarred setup2.xml or something. Still...
-
@meimeiriver Ok so i did what you said by searching for ancient_rock.ydr. Came back with 0 results found, so I went in game and used menyoo to highlight the blocks. I think the problem is I installed a no trash mod, and i think these models replace the trash because they're named after trash files (ng_proc_paper_01a, ng_proc_food_burg02a) I'm going to look in openiv and see if that's the case
-
@meimeiriver @UnkwnModder THAT'S IT! It's the no trash mod causing them to show up. This can be marked as fixed
-
@westcoastsosa said in Weird Blocks Spawning:
i think these models replace the trash because they're named after trash files (ng_proc_paper_01a, ng_proc_food_burg02a) I'm going to look in openiv and see if that's the case
Glad you resolved it!
And it explains perfectly why those props were spawning randomly (as I assume trash spawns randomly too).
Still, what would have possessed the author of Map Builder to do something so horrendeously stupid as to use existing prop names?!? (Probably, I think, because, at the time, he may not have known how to create his own ytyp entries, resorting to just overwriting stuffz)
It's all in the past now, and he apparently came to his senses, so it's all good.
Map Builder, not too long ago, was using duplicate names from mpapartment too, which caused havoc on those interiors affected. Tl;dr: never use names already defined in game! Give them like your own tag, like I append '_meimei' after the name of each prop for my own, private, addon props DLC. Cuz the game really trips badly over duplicates prop names!
-
@meimeiriver Yea i noticed that when I was making my house mod, i would replace a model that was in the house with a custom prop, just to find out that the prop spawns in multiple places around the map. I'm slowly fixing this, but wish I knew the right way to do things back then lol. Anyway thanks for your help, I was tempted to start with a fresh mods folder
-
@westcoastsosa said in Weird Blocks Spawning:
@meimeiriver Yea i noticed that when I was making my house mod, i would replace a model that was in the house with a custom prop, just to find out that the prop spawns in multiple places around the map. I'm slowly fixing this, but wish I knew the right way to do things back then lol. Anyway thanks for your help, I was tempted to start with a fresh mods folder
When I first started out with ymaps, I replaced an existing painting, and was very proud of myself.
That -- apart from being dumb -- really, literally only works on things like replacing an 'artwall' object or something (else the object's bbMin/bbMax values will be wrong, and the object will either be invisible, inside a ymap, or cut out of scope under certain angles).
Soon enough I figured out that just rolling my own addon props DLC was much easier, and much cleaner. Glad you came to the same conclusion.
As to how much you replaced, might actually not be a bad idea to just restore the old files (aka, simply remove the files from your 'mods' folder -- provided you didn't make other changes in them, of course), and build your own custom addon props DLC too. It's a lot easier than ppl think, really. If it was just a few props you replaced, then it may indeed be faster just to undo the damage manually.