mojira.dev

Cole Roberts

Assigned

No issues.

Reported

No issues.

Comments

It broke again somewhere around 1.16.221

After further testing, it is not the execute command, it is the teleport command. I will open a new issue later.

Request to reopen this, I am afraid that this exists once more in 1.16.221. I made a dummy armor stand in the nether, and tried to teleport a villager to it from the overworld, it only teleports them to the coordinates not the dimension. For players, however, it works.

That only happens if your computer is using enough memory, and if the memory leak takes the rest of the free memory it will crash your pc.

Ignore those upper comments, it is working now in beta 1.16.230.50. Only problem, dunno if this is just me, but it seems that the versions vr mode might have a memory leak? Maybe look into it

[media]

Ok, so, after observing the crash dump a little, it seems to "encounter a breakpoint" at this integer, here is the modules.

[media]

From what I have been seeing, it didn't work even to this extent until steamvr updated. Possibly something in steamvr is causing incompatibility?

Odd. It boots now, but crashes while loading, no error however. Ill do some peeking file wise.

If your talking from a behavior pack perspective, yes.

The TARDIS is a entity and by setting the demat to belowname I can't see it and it still works

Can confirm, making a TARDIS addon and the demat is used via scoreboard. it only works when visible

I actually found a partial solution to this, at least a workaround for AMD users, update drivers to the latest, make sure you have all the latest windows updates, and run it again. However the downside to this is it crashes, (at least for me) after a few minutes. For any AMD user that doesn't know how to do this, go to this site and download first "Download Now" button, then, when you are in the application, click the alternate download, it was released on the 4th of December if that helps. When all that is done, reboot and give it a shot. If it doesn't work for you, sorry, I don't know how else to help.

Same problem here, hopefully this gets fixed in the next update.