As @nevir says, that is the Testing beta which only has a single spawn region.
Switch back to the Live version to join the main universe. (The Testing and Live universes are separate.)
The Testing and Live binaries are currently identical so best to explore the Live version. But it seems like the game current triggers a shader compiler issue, we’ll not be able to explore this until next week when the team is back in the studio.
I’ve had this happen once as well, when making glass. I did change to an alt shortly after starting it off though, and the other alt didn’t have the skill to create glass, so not sure if that had anything to do with it.
It has gotten to the point where my framerate is so bad I have to set all my settings to the lowest as possible just so the game is playable, I’ve even had to turn per-pixel lighting off, I can’t even tell what blocks I’m looking at anymore… but ~20fps is better than 6fps… I used to get over 30 before the meteorite update with full settings.
I’m running a 27" imac from late 2012 on 10.12.6 Sierra,
3.4 GHz Intel Core i7 processor, 16GB DDR3 ram,
and NVIDIA GeForce GTX 675MX 1024 MB graphics card.
[edit] Ok wow, even after changing all my settings to the lowest possible, i am still having spikes when my frame rate drops to about 6-10, i’m mining for coal near lava and using the grapple, but it dropped before I even shot the grapple, when i was looking around for a place to shoot it… I could start counting my frames per second manually… it’s still averaging higher with these low settings but it still drops down to a countable level. to me that is definitely not playable
A strange graphics bug I randomly noticed. When the torch is in a certain kind of view (only notice it like this) it shoots narrow flame streaks downwards. It was hard to capture since it’s kinda sporadic and fast. I captured this right as it was about to disappear.
first of all, whenever I walk over a flower, there is a good chance Ill somehow get stuck at that location until I destroy the flower, or the terrain below me; this is especially annoying since wildstock and spitters like to spawn in plains, where flowers like to go.
Second of all, I cant seem to cancel crafting a recipe without breaking the crafting machine, leading in to…
And third…Crafting machines eating Items when the crafting machine is broken, not just one, but every recipe of it’s type; I lost 13 hard-earned small fossils (copper progression) because I forgot I could craft them in bulk
This probably has to do with the way the devs set up the enemy AI script. There is a periodic invisible sphere that is cast around the enemy that will recognize player positions if they fall into the sphere. Then an invisible ray is cast to each position that was within the sphere. If the ray hits an object with a collider (a block) it will recognize that the player is not in sight. It seems that some mobs do not have this second ray cast or will at least go in to a hostile state with it. This is most likely on purpose and Is ultimately up to the devs how they want the enemies to react.
The intention (obviously) is that it is possible to place single blocks with max attributes. I balanced it to be as fast it can be whilst still being able to place singles, but maybe I’ve over done it a bit. I can bring that back a notch.
I still want to split tool speed from block placement speed (it was an earlier suggestion)…
I want full speed when mining block, but then i place block so fast that it ends up all over the place.
That’s a bug / omission / **** up – with the name change to Condition it should have also reversed the number and bar as you describe. The whole point of changing the name was to make it a value that goes down rather than one that goes up. We’ll get that fixed.
Just to check, was there already a beacon plot in that area where the creature spawned?
Did you see it attack any other players before you encountered it? The expected behaviour from a Spitter is that if it cannot get to you, it will stop pursuing you but will still be represented as a red dot on the compass. However, it does look like that it doesn’t go into its attacking behaviour after you walked into its line of sight, so I’ll have a look to see if I can reproduce this situation.
I can’t reproduce the issue in some of the suggested locations. Do you have any other examples of where this is likely to occur a lot of the time?
Also, @brook-monroe are you able to upload the video again?
It depends how some parts are beaconed. Creatures can walk into beaconed areas or that some parts of those areas are not beaconed. As long as creatures are not spawned inside beaconed areas to begin with, then it should be working as expected. Having said that, I can check the excavated beaconed area if you can provide coordinates and a screenshot so I can check that this is the case.
It’s currently a known issue. Incidentally, @OmniUno did this occur after you switched characters?
Are you experiencing framerate issues even when there are no meteorites landing nearby?
Thanks for the bug reports. These have been logged.
You can’t cancel an item that currently in the process of being crafted, if that’s what you meant.
I’m somewhat confused when you said that you lost 13 small fossils because you didn’t choose to bulk craft them. Can you clarify what you mean?
Also, when a crafting machine is broken, crafting is temporarily halted. Did you try repairing it with a spanner?
Welcome to the team of sad owners of macs… Can’t play too here on my iMac with 10.11.6 version… I’m hoping that this new year brings us a new update that solves this situation … it is sad to pay 31$ for a game that you can not play …
Iv had the same issue with my 2017 MacBook Pro with the same specs and unfortunately haven’t found anything to resolve it on the forums or elsewhere, the only semblance of a reason was from a Dev who said “the issues seems to be with the graphics card” after having a look at the crash logs.
But Mac’s and this game are pretty much incompatible atm, My wife and I have had some success on our iMac and MacBook air by reducing all graphics to their minimum, turning off V-sync and by playing the game on a smaller window as opposed to Fullscreen, and it does seem the smaller the window the better the performance.