Sorry, I can’t see an option to quote on this.
Some folks on Steam are reporting the same thing.
https://steamcommunity.com/app/440900/discussions/0/1735469327937823097/
I can understand it to be rare, and as I said, not a game breaker. I know full well how complex a project like this is.
I noticed something else.
I wanted to just admin build a bit and thus went to singleplayer…
I spawned a felt mile away from some (to me until now not known spot) meteorites and when I flew there, those nodes where still there. (The kind of distance they wouldnt have “spawned” for me on official.)
So eighter that issue got fixed yesterday or today OR it only seems to happen for me on official servers as singleplayer is just fine? Can others say wether thats the same for them?
Though remember - the nodes are actually there even if one hasnt been present at that spot which then causes one to not see and harvest them (and yields nothing on attempted harvest) which is being seen by running through the mist the nodes leave behind.
My issue cleared up over the weekend as well. Right after the hotfix for the door issue was implemented.
Strange how that may have been related.
My experience is the same.
If you are within what appears to be “render range” of the meteors when they strike the ground, you can successfully see them and mine them.
When you are outside of render range when they fall, you will see the smoke where they hit, but they do not show up on your game client. Further info: if you try to walk at or through the smoke spot, the game client will hitch or rubber-band at the meteor spot.
As Nuria describes, for your best chance at success, position yourself in the middle of a spawn impact zone prior to the timing of the spawn for the best results.
What this tells me is that the game client is getting information about the smoke trail location, but it is not getting a reconcile / render update for the actual meteor node itself. When you try to walk through the space (game client shows no obstructions / collisions), you begin to bounce and rubber-band because the game server does have a collision flagged at that location. As such, the game client allows you to go there, checks with the game server, and then bounces you back because the game server cannot place you there - and provides that update to the game client, pushing you back…
I had hoped that this “invisibility” to the game client would not prevent harvesting. When you swing a pick at the smoke motes, there is no harvesting of the node on the game server. There is something on the game client side of the equation that is preventing this.
This seems to have to do with the game client’s rendering and derendering, memory space, etc. There have been times when I was in the spot of a spawn, died, respawned at a bed roll outside of render range but not TOO far away, and I could come back to the nodes that were still present and harvest them. If you respawn too far away, the meteors will be invisible / gone upon your return to the area.
I hope that this detail is helpful for improving the spawning and the event.
And that become abit problematic whit the system, insted of play as normal and when on a random time on a random plase you have to abor what you do and tryto find it you now hawe to just stop playing and camp the spot on exact time to harvest.
Make it the oposit so you have to run to the spot insted and not on the Clock on the sape spot every time,
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.