Forest object bugs...

mmm-kay now, I've reported this before, but I'm reporting this AGAIN. YES it's a bug. It's VERY annoying.

If I make a road kit of some 50 pieces. I start placing them, experimenting with some slopes, to see which one is best, and I decide to only keep one of the three pieces, each one there's only a single unit of in the map, I cannot delete the last anything of a forest object.... so if I make a mistake, I have to undo, otherwise, I CAN NEVER DELETE THE ERRONIOUS PIECE.
This has been around since y'all have redone the forest stuff around 0.8 ~ 0.9. It's not me. I am also not entirely sure WHICH object it is, and there's literally dozens of objects like this in my city map that I CANNOT DELETE (well, they delete fine but when you restart the map, they're back!), among the thousands of objects I wish to KEEP.

I'm not trying to be rude, or condescending or otherwise MEAN, but c'mon, this one's a real ball-buster (if I that's offensive please edit it out), and it grates on one's sanity after a while. I love this simulator but it HATES me.

Help?

To recreate:
Add a new forest object into the forest brush (so that it makes it's own file entry under /forest DIR)
without un-doing creating it, go ahead and select it if it's not already, and try to delete it. Place a few NEW things one by one, and try to delete them (they may appear to delete fine). Good luck, they will be back upon restart, as it can't seem to delete the very last entry. I don't know why that is, but I don't think there's code for how to remove an item, if it's the last item of it's kind which involves deleting the entire item file for it.
Otherwise, I have to add all my forest entries together as that's the only way I know how to do this, and that's going to take a *LONG* time.
Please give me some feedback on this (when I mentioned it before, I was told to delete the text entry, well before there were too many to timely figure out which entry from which file it was, now I REALLY don't know, otherwise my city is going to be plagued by floating rogue objects, some of which refuse to even save movement).

 

Hey,

thanks for getting in touch! I was able to reproduce the issue using the steps you provided and could fix the problem of deleted items re-appearing upon map reload despite all instances of their respective type having been removed. Until the release is updated, you can manually get rid of leftover .json files corresponding to the type whose last entry you have deleted. If, for example, you deleted all "dri_rock_a" brush elements, you can manually remove the "forest/dri_rock_a.forest4.json" file from your level to prevent them being reloaded until the fix is rolled out. Hope that helps.

I could not reproduce the bolded part, however. As long as items of a certain type are present, their data (including positions) should be exported upon save. Do you have steps to reproduce that not happening?

Cheers,
Siggy

 

Some pieces in my private beta of my city map refuse to be moved. I don't know why it's happening. I manually removed the last one about two months ago, using the method you mentioned. That works IF you know exactly which piece it is. I have an 825 piece city infrastructure kit (though bug happens with much less than that). Some pieces as I mentioned, could not be moved, they are the same ones that couldn't be deleted, normally (I tried burying them inside the terrain, they moved around just fine - when I could select them), but if I re-loaded, many would be back to their old spot on-top the terrain. I don't know what's causing it, it's as if it's losing track of what is where, and it's not really to-do with how many pieces there are in the forest brush, as I'm not that far along with this map.

When I do my next upload within the next 10 days for backup, and I can 100% reproduce this bug on various pieces (that refuse to be moved and save movement, upon reload), I will hit you up with a link and take a screenshot of where it is & it's name.
It's happened dozens of times (not just the deletion bug), so I'll hit it in the next couple of days for-sure.

Do I need to save all my logs as I work on my map, to help you figure out what caused it, before I notice the error?

Will get back to you after I try to reproduce that bug 100% with the movement not saving, I think I know just which pieces are buggered. I forget which ones were doing it at the moment as it's been a bit.

P.S. Is it me or if when I move a piece up and down (while pulling the mouse just sideways during movement vs just up and down when I nearly have the object lined up), it moves a tiny bit allowing for adjustment. If this is a new feature, thanks, my modeling program does that, and it's lovely when it works, especially on big pieces. If it's been in a while, well, I just noticed it.

 

It can't hurt to keep some. They aren't huge. The deletion bug you mentioned wasn't visible from logs alone, so they don't work 100% of the time, but better than nothing.

Okay, will keep an eye out

Cheers,
Siggy