There are for sure some things I missed. The tool deleted too much in your case. Taking a look at the delete list can help. You can uncheck files you know they are needed. The only way to debug the problem for me would be with your original map. But you can try the map cleanup in the world editor.
Thanks a lot for your reponse. I will surely take a closer look if time is available and will let you know. I wonder what missing file(s) can lead the game to crash while loading the map. At that point I gave up for the moment. Btw. the map I want to shrink is an update for my "Barbent's Gambling Zone". In extreme case I will delete as many files as possible manually before publishing. But it would be that cool if a one click shrink could succeed and this would be more efficient I believe. How do you think about the new cleanup tools like "find unused assets" in the world editor? Could you gain some experience with them? Are they propper? (I distrust any BNG algorithm since the camera path editor created a folder in the object tree with ~250.000 copies of a wall object leading to 0.001fps! No lie! I was shocked afer 2 hours of debugging. Brute memory overwrite! Well, we know it's alpha). Anyway thanks for your fine work and help!
There was an error that the tool deleted cubemaps which are not referenced by missiongroups. Some cubemaps in BeamNG are loaded by convention from the gameengine I guess and therefore have no reference in the map itself. The cubemaps folder is now excluded from shrinking.
What do you all think? Should I allow to select a folder of an unzipped level to start with any functionality of the tool? My worries are that someone uses it by accident on his single working project folder shrinks the project to hell and then hates me forever, haha. For me it is no problem because I use git for version control, but who does?
I would like to select unzipped folders because it's an additional task zipping. Espacially if you have to do it several times. But I do understand your fears. My idea would be to aquire the BeamNG user folder path - if possible (?) and do not allow changes in there (hence on the current working version).
That's a good idea! The userfolderpath is not written in the registry and not mentioned in any of the BeamNG config files (or I miss something). I guess it is always by convention: <Windowspath to userfolder>\AppData\Local\BeamNG.drive\<installedVersion> I must check where I get the installed Version from or build my own logic But I will try that. Thanks! Alex
Hi ! could be simply <Windowspath to userfolder>\AppData\Local\BeamNG.drive\*.* I don't think someone works in old version's user folders (?). So could be restricted in any case no matter of the version... Barbent
A small update is out because I start copying assets to my wip map now and the actual process of zipping my project all the time I want to copy an asset is stupid. Version 1.1.2 (2024-06-02) - Copy Assets: You can now choose a folder for your target map (makes the process quicker) - Fix: Update Imagesharp dependency because of vulnerabilty Already downloaded versions of my tool ask for an update. https://github.com/alexkleinwaechter/BeamNG_LevelCleanUp/releases/tag/1.1.2
A small update again: I'm very happy that I can support Barbent Servo GT with the preparations for the upcoming initial release of his outstanding map Barbent's Homerange. Testing my tool, especially the shrinker, with the map showed some errors which are fixed now. Additional there is a new experimental utility for changing the height position (z-axis) of all objects in your map (I forgot the skybox here, comes with a later update). Best! Alex
WOW! Thanks a lot "AlexKidd77". Your tool (and you) are a golden help for my project. The "Z-axis lift all" option made it possible to finaly use ships all around the map, cause there was a problem with some kind of border. Lifting everything a few meters was the solution. I never could have managed this task by hand. Also the shrink functionality is a must have not only for bigger maps, and last but not least, to have a deep proof of all paths, dependencies and detailed information if something is problematic. Great tool! Great work! Great update! Thanks "Alex"
Absolutely LOVE this tool. It is such a life saver, and you are an absolute legend for making it; however, I have a question. Would it be possible to add an X/Y offset in the same way you have a Z offset? It would be very helpful in expanding my existing maps or combining some of my maps into one mega map. I don't want to request too much work if it is more complicated than just changing some parameters with the existing Z offset. So, no worries if it is more complex than I understand it to be.
I just deployed an update. You can change all axis now. I just did a small test on west coast usa and it looked good. It would be great if you could test the functionality since I have almost no time at the moment.
I just changed the stupid behaviour of the copy assets selection which was deleted when using the search. Selection is now retained when using search filter.
Hello! as of .35 everything works expect it doesn't bring textures over when copying assetts, it does the material just not the texture.
