What exactly are growth blocks? They don’t look like anything to me .-.
Given the name, and that they are being placed as decorations (on top of substrate layers) - my hunch is that they’re supposed to modify the blocks underneath them (nasty evil growths on the land)
1 Like
Reminds me of Zerg Creep.
3 Likes
Boundless now quits correctly on Mac after this latest update! Thank you!
5 Likes
We fixed it 
@Combatman12 can you post the log from from the loader (not the game log) ? %LOCALAPPDATA%\Turbulenz\boundlessloader_win\boundlessloader_log.txt.
That error code looks like its saying it could not connect to a server. Trying again may work.
INFO …\src\steam\steam.cpp:997 (turbulenz::SteamServices::GetUserID) --> ENTERED FUNCTION
INFO …\src\steam\steam.cpp:1004 (turbulenz::SteamServices::GetUserID) user id: 76561198077867826
INFO …\src\steam\steam.cpp(turbulenz::SteamServices::GetUserID) <-- LEAVING FUNCTION
INFO …\src\steam\steam.cpp:884 (turbulenz::SteamServices::GetAuthSessionTicket) --> ENTERED FUNCTION
INFO …\src\steam\steam.cpp:915 (turbulenz::SteamServices::GetAuthSessionTicket) Got auth token (240 bytes)
INFO …\src\steam\steam.cpp(turbulenz::SteamServices::GetAuthSessionTicket) <-- LEAVING FUNCTION
INFO …\src\steam\steam.cpp:809 (turbulenz::SteamServices::UserStatsReceivedCB) got stats
INFO …\src\steam\steam.cpp:966 (turbulenz::SteamServices::GetAuthSessionTicketResponseCB) --> ENTERED FUNCTION
INFO …\src\steam\steam.cpp:947 (turbulenz::SteamServices::AuthSessionTicketMakeCallbacks) --> ENTERED FUNCTION
INFO …\src\steam\steam.cpp:952 (turbulenz::SteamServices::AuthSessionTicketMakeCallbacks) making callback (true) …
INFO …\src\steam\steam.cpp(turbulenz::SteamServices::AuthSessionTicketMakeCallbacks) <-- LEAVING FUNCTION
INFO …\src\steam\steam.cpp(turbulenz::SteamServices::GetAuthSessionTicketResponseCB) <-- LEAVING FUNCTION
INFO …\src\browserfeatures\httprequest.cpp:772 (turbulenz::HttpRequest::PerformSyncRequest) !! curl error: schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.
INFO authentication\authentication.cpp:401 (turbulenz::authentication::GetAuthenticationToken) Failed to signin with embedded credentials: schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.
INFO …\src\browserfeatures\httprequest.cpp:772 (turbulenz::HttpRequest::PerformSyncRequest) !! curl error: schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.
INFO …\src\browserfeatures\httprequest.cpp:772 (turbulenz::HttpRequest::PerformSyncRequest) !! curl error: schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.
INFO …\src\browserfeatures\httprequest.cpp:772 (turbulenz::HttpRequest::PerformSyncRequest) !! curl error: schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.
INFO …\src\browserfeatures\httprequest.cpp:772 (turbulenz::HttpRequest::PerformSyncRequest) !! curl error: schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.
INFO …\src\browserfeatures\httprequest.cpp:772 (turbulenz::HttpRequest::PerformSyncRequest) !! curl error: schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.
INFO …\src\browserfeatures\httprequest.cpp:772 (turbulenz::HttpRequest::PerformSyncRequest) !! curl error: schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.
INFO …\src\browserfeatures\httprequest.cpp:772 (turbulenz::HttpRequest::PerformSyncRequest) !! curl error: schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.
INFO …\src\browserfeatures\httprequest.cpp:772 (turbulenz::HttpRequest::PerformSyncRequest) !! curl error: schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.
INFO …\src\steam\steam.cpp:150 (turbulenz::SteamServices::Shutdown) --> ENTERED FUNCTION
INFO …\src\steam\steam.cpp(turbulenz::SteamServices::Shutdown) <-- LEAVING FUNCTION
Same happened to me some times on the JS build and I think that is just rubber banding.
It is a server connection issue. If it is still failing check that both boundless.exe and boundlessloader.exe are being allowed through your firewall. Also are other online Steam games working for you?
I still can’t get it to work, I’ve allowed it through my fire wall and TF2 works fine for me.
Here’s a video of the OS X Bug:
4 Likes
You mean cool flash multiple background feature! 
1 Like
That’s what my Mac has been doing since the c++ update.
1 Like
A few more bugs:
Sometimes when I hit esc to open the menu, it stays on the screen for half a second and then closes. This seems to occur most often after I teleport somewhere and it only does it the first time I open it.
This next one may be a specific graphics issue on my Mac because I don’t have a monster system. Most of the time when I break a block, it appears that the block behind it takes a fraction of a second to load and I can see through it, all the way through a dungeon deep in the earth.
Lots of trees in the new build with no trunks. Is that intended to test regen, or something else going on?
Here ya go 
1 Like
In the latest build, Healing/Ember blocks can not be crafted.