I mean that the portal didn’t do anything. The blocks turned colors and I broke them and the portal was just gray. And when I try to walk throughit I just went right through and not get ported. So I tried telling it to port to a safe place but nothing would change.
Not saying you are, I am just inquiring. I just found it super odd that it wouldn’t open. Again I wasn’t really going to mention it until I lost 1k coins to it and it trapped me in another world lol.
@vdragon posting here since it goes along with the smart stacking thing. It would also be great if you could just smelt the entire smart stack and not have to start smelting each ore individually.
You would only get charged if you walk through the warp into another world. It could be possible that the world was rendered at that moment as @Stretchious suggested . Do you remember if that was the case?
Both times that this happened I lost 1k coins. All I really recall is that I chose my destination and the blocks turned orange, once I broke them all I saw was a gray wall. Because the destination is rather dark I just thought that is what it was looking like and I walked through, just to fall into the water in the temple area. I did notice I lost the 500 coins both times. I am thinking the problem might have been on my end? Maybe the world were there and did render but maybe my connection or something just didn’t properly load the process to transfer? Not really sure what to suggest since I am not sure how the teleporting system works.
I have mined out the interior to find nothing but dirt. it is however a very old plot and has at different times been attached to multiple beacons. I would like to keep the plot next to it.
If any one has any incite please help or if a dev could see if its bugged that would be swell to.
Sounds like you managed to replicate a bug I had back in release 149. I too had multiple beacons attached to this plot. That must be a key to replicating the bug.
[quote=“james, post:10, topic:6094, full:true”]Please try Testing 31 and read the details here.
[/quote] Hey, James: For what it’s worth, I’ve run this patch (152) on a Windows system (high-end specs, 1080 GFX, 32GB RAM, Windows 10, etc.) using the exact same LAN/Internet connection as the iMac, the same account, and visiting the exact same locations. The result is absolutely zero of the rubber-banding/camera-snap-back that I am seeing on my iMac. Not even the tiniest little hiccup or hesitation.
I am not in any way expecting an iMac (even the highest-end 5K Retina iMac) to compete with a high-end Windows gaming system in any meaningful way; I am just providing an additional data point for you. I am not sure how this plays into your theory on chunk size strangling bandwidth for user-related processes, but I thought it was worth reporting to you.
I can try test patch 31 on that same Windows system but I am guessing that, based on the results with the alpha 152 release, that won’t show me anything different. Let me know if you think that would be valuable.
One additional data point: running release 31 on the iMac, I found the setting to reduce the chunk size in the options, I reduced it one step, and noticed no difference in the rubber-banding/camera-snap-back effect. It’s still happening, and happening in the same places under the same conditions. I will try to reduce it one step further to see if that helps.
First, I am confirming that what you described in the first two points is correct: two different hosts sitting on the exact same LAN (in fact, both are physically connected to the same physical 1GB switch, no WiFi in play here), both are running 152, using the same Steam account and, therefore, in the same place, and the iMac exhibits the rubber-banding/camera-snap-back while the Windows PC does not. One clarification: I am not using both machines at the exact same time: I will run on the iMac, then I will close down on that one and run on the Windows system and then close that down and going back to the iMac. If it won’t violate anything (license, multiple simultaneous logins, etc.), I’d be happy to run on both systems simultaneously to see if the description above still applies while both are actively playing (will need a friend to help me test that).
Second: Just to be clear (and I apologize if this is a dumb question) when you say “debugging information”, do you mean pressing the period (".") key and all the information appears overlaid on top of the game screen, or are you referring to some other log or output? Let me know.
Btw - you’ll not be able to run the game twice. Steam will not allow it.
Yes. Press “.” a few times to bring up the details. And share screen shots when the Mac is lagging and when Windows is not. Try and let them both run for the same period of time, say 5 minutes.