@MX Duke Just tried your test world. The doors and ore icons seem fine on my machine. Do I need to do anything to reproduce the issues?

I just turn on the ore detector, and after about a min, things stop rendering. In all honesty, the more I mess with it, the more I think I've just found the limit of keens engine. I think its just process load confusing the game engine.

Funny thing is, I get no clipping, Sim speed is always 1.00 - 1.02. But its pushing my 4.5 gig overclocked Coffee Lake Cpu to the max. I'm just going to have to drop a mod to make this work.

Even though I've got my Cpu cranking at 60 deg Celsius to run this world, and warm my house, game runs smooth as butter. I really think the game engine is eating itself.

And I dled my test world off steam and loaded it. It loaded a save from before I even built the ore detector. I've updated it here:

https://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?id=1663437537

It's definitely server load causing the issue. I played that save a bit before uploading it, killing wolves and marking rocks before I saved. As I opened the wolf inventories, the icons for the wolf meat took 10 seconds or so to load in.

https://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?id=1663448831

screenshot from the world I just posted. The x97 in my inventory is nato magazines. I stared at them for about 5 mins, the icon never rendered.

If you can't reproduce it. I'm going to chock it up to Keens engine and call it good.

I was able to reproduce it. There appear to be more issues with Procedurally Generated Ores, too.

The cause is ore detection range. The mod author marked the one you were using with the 2.5km+ range as Space Only, presumably because things can be unstable if used on planets. In my testing, it appeared to cause memory leaks which would explain the issues persisting even after you exit to the menu and start a new world. The game engine was likely not designed to process so many voxels for ores. A 250m detection range needs to check 19,6349m^2 of voxels while the 2.5km range must check 1,9634,954m^2.

As for why it is worse with Procedurally Generated Ore, I suspect this is because the ore patches it adds are typically sparse with disconnected tiles. Keen has likely optimised how they process ores for the vanilla shapes where the patches are contiguous. I'll try pumping out some procedural ores with contiguous patches to test this at some point.

I'm just glad I'm not nuts. Until then I'm just going to have to put on my big boy britches, build a rover, and scout with a 500m detector, instead of trying to do it the easy way.

In a side note, a patch for Dr's Vanilla Voxels would probably be a good idea, for you. He has 4000+ subscribers, so its a very popular mod.

Haha, good luck! I found that I needed wing mods/low cost aircraft to find anything early on. That was just with vanilla detectors though.

Fair enough, I'll look into making a compatibility patch mod :)

I had previously found a iron boulder that decided it wanted a sex change because now its full of silicon.

@HUNGARY 4 KABOB

Seems boulders might be doing strange stuff of late. Shall have a look.

Thank you.

@Lemmiwinks
Any update on boulders issue?

As @Gertz said ... Almost everytime when I find some boulder it is ok, until another player comes to certain range. Then it seems that another boulder with different ore is generated at the same location and merges with original one, or completely replaces original.

On top of that... When is mined, voxels of boulder do not change and texture is static for one of the present players.

Is boulder generation client-side/per player? (dedicated server)

Boulder spawning is pretty weird in this game. It's possible that the issue is because of a config this mod adds to replace existing boulders with an ore which should spawn on the planet. Removing it would mean that there's no control whatsoever over boulder spawns. Doesn't seem to be working too well anyway so Keen must've changed how they work.

@Lemmiwinks
I found out that, if you drill the boulder, than ore is replaced by modded one (not always). After that its ok and it does not change after that. So its possible to "check" for ores that way. Just don't belive first ore you see.

Thats what Ive been doing. Find a boulder>drill a hole into the ore>then just mark it for later and continue scouting.

Hi,
I started a game with your mod some weeks ago and it worked fine. Since today I can load my savegame anymore and getting the following error in the log file. If I deactivate your mod, the savegamne is working again. I tried to reassign the mod, but this had no effect. Any ideas? I like the mod and would like to continuing playing with it.

2021-01-23 08:49:28.498 - Thread: 1 -> MOD_ERROR: Procedurally Generated Ore
2021-01-23 08:49:28.498 - Thread: 1 -> in file: P:\Spiele\Steam\steamapps\workshop\content\244850\1649218738\Data\PlanetGeneratorDefinitions.sbc
2021-01-23 08:49:28.498 - Thread: 1 -> Resource not found, setting to null. Resource path: P:\Spiele\Steam\steamapps\workshop\content\244850\1649218738\Textures/Models/Environment/Sky/EarthFarClouds.dds
2021-01-23 08:49:28.498 - Thread: 1 -> MOD_ERROR: Procedurally Generated Ore
2021-01-23 08:49:28.498 - Thread: 1 -> in file: P:\Spiele\Steam\steamapps\workshop\content\244850\1649218738\Data\PlanetGeneratorDefinitions.sbc
2021-01-23 08:49:28.498 - Thread: 1 -> Resource not found, setting to null. Resource path: P:\Spiele\Steam\steamapps\workshop\content\244850\1649218738\Textures/Models/Environment/Sky/Landsky_texture.dds
2021-01-23 08:49:28.498 - Thread: 1 -> MOD_ERROR: Procedurally Generated Ore
2021-01-23 08:49:28.498 - Thread: 1 -> in file: P:\Spiele\Steam\steamapps\workshop\content\244850\1649218738\Data\PlanetGeneratorDefinitions.sbc
2021-01-23 08:49:28.498 - Thread: 1 -> Resource not found, setting to null. Resource path: P:\Spiele\Steam\steamapps\workshop\content\244850\1649218738\Textures/Models/Environment/Sky/Landsky_texture.dds
2021-01-23 08:49:28.499 - Thread: 1 -> MOD_ERROR: Procedurally Generated Ore
2021-01-23 08:49:28.499 - Thread: 1 -> in file: P:\Spiele\Steam\steamapps\workshop\content\244850\1649218738\Data\PlanetGeneratorDefinitions.sbc
2021-01-23 08:49:28.499 - Thread: 1 -> Resource not found, setting to null. Resource path: P:\Spiele\Steam\steamapps\workshop\content\244850\1649218738\Textures/Models/Environment/Sky/Landsky_texture.dds
2021-01-23 08:49:28.501 - Thread: 1 -> MOD_ERROR: Procedurally Generated Ore
2021-01-23 08:49:28.501 - Thread: 1 -> in file: P:\Spiele\Steam\steamapps\workshop\content\244850\1649218738\Data\PlanetGeneratorDefinitions.sbc
2021-01-23 08:49:28.501 - Thread: 1 -> Resource not found, setting to null. Resource path: P:\Spiele\Steam\steamapps\workshop\content\244850\1649218738\Textures/Models/Environment/Sky/AlienSky.dds

...

it goes on like this