Indeed, though now that I think on it, perhaps it has something to do with the "experimental" nature of the data pack. I forgot to mention that I'm using it and yes it is the latest one posted on the snapshot changelog.
I was told that my issue is a duplicate of this, so I thought I'd include the pic I took. MC-172852
Thanks for the reply! It does seem that you are correct, this is a world generation issue.
I created a new world with the seed I mentioned in creative mode. Then I teleported to the location, and watched the villager suffocate (that always happens). I added a villager spawn egg to my first inventory slot and had it in my hand to place. I right-clicked on the bed, but that just set my spawn point, it doesn't let you spawn a villager on a bed. So, I right-clicked on a block of the wall next to the bed, this block is one block high, sitting on top of the floor, pretty much. This caused the issue I reported, the villager spawned on the bed and suffocated. I then right-clicked on the floor next to the bed and the villager spawned correctly. I then changed the time to midnight and the villager went to bed. I then changed the time to day and the villager got out of bed correctly.
So, I think maybe the villager in the bug I reported wasn't spawning on the floor, but the wall. Maybe during spawn it dropped on to the bed which pushed the villager up a block or even just high enough to suffocate in the ceiling. I think this, because when teleporting to the coordinates I gave, I kind of fell to the spot, but safely, this isn't unusual, I was using the block coordinates from the F3 menu instead of the XYZ coordinates. I created a video showing what I did, but it's too big to attach here, so you can view it at https://youtu.be/f9V8Q-bUmRc.
Thanks again for your help, I greatly appreciate it!
Thank you, I've done as you've asked. https://bugs.mojang.com/browse/MC-166612
I just loaded 1.15 Pre-Release 1. I was testing an issue I had with the last snapshot where some villagers would not go to bed at night. I teleported to a snow village and instantly watched a villager die by suffocation, it's head was in the ceiling above or near the bed. You can see this in the screenshot I've attached. I've also included a fresh copy of the world (named Pre-Release1) created with seed#7333969029456169764. I have "cheats" enabled so you can quickly type in "/tp -502 70 -643" or "/tp -507 70 -642" to get to the point in the screenshot. (There are a lot of duplicates of similar behavior and I accidentally reported this in the Switch bug tracker at first. This seems to be the correct place to report it.)
Oh! I see now, I did overlook that this was the Switch version. Sorry about that.
Thanks Swekob. I found what you were referring to. In that post, a moderator commented that it relates to another ticket, which is labeled as "Works As Intended," so I deleted my previous comment here. Thanks for helping by pointing me in the right direction. I appreciate it.
This sounds like MC-157494 which is now solved as of 1.15 Pre-Release 1. I just tamed a wolf, used "/kill" and it teleported to me when I respawned. This ticket is still open and I thought it was similar, so I thought I'd provide some recent feedback.
I tamed a wolf and used "/kill" and it teleported to my spawn point. So, this works in 1.15 Pre-Release 1 for Java, but could we please also get it to work for Bedrock Edition? I'm using Beta 1.14.05.1, which is pretty much equivalent to Java 1.15 Pre-Release/Snapshots. I realize this belongs in the Bedrock section, but similar Bedrock issues are linked to similar Java issues.
I'm playing Windows 10 Bedrock Edition version 1.13.1 and I feel like this is happening to me, too. I've created pens for some of my animals, specifically sheep and cows. I'm absolutely sure I've bred them multiple times, but when I went to check on them last time, I only had two cows and one sheep. The game has crashed a few times, so I think this ticket fits the issue I'm experiencing. I didn't test to see if these animals were on chunk borders. That might also explain why I can't seem to find the iron golem that used to be in the village I live near. I may have to do more testing and get a screenshot of how many animals I have now and if it changes, I can provide that.
Ok, so I attached two screenshots. One shows you my tamed horse in the pen, the other shows you that my horse disappeared. The game did crash in between these pictures, maybe a crash log could provide more information, but I'm not sure where that might be. Also, I bred some more cows, the game saved, then crashed, but my cows didn't disappear. I'll see what I can find out about the game crashing. I know it does this sometimes if I minimize the window. Perhaps I should save and quit instead of minimizing the window.
-I just loaded 1.15 Pre-Release 1. I was testing an issue I had with the last snapshot where some villagers would not go to bed at night. I teleported to a snow village and instantly watched a villager die by suffocation, it's head was in the ceiling above or near the bed. You can see this in the screenshot I've attached. I've also included a fresh copy of the world (named Pre-Release1) created with seed#7333969029456169764. I have "cheats" enabled so you can quickly type in "/tp -502 70 -643" or "/tp -507 70 642" to get to the point in the screenshot.
Sorry, added to the wrong bug tracker.
In 1.15 snapshot 19w46b I found one village where only two villagers went to bed. I tried replacing a door and a bed and I think I managed to get one to go to bed, but I'm not sure if it was because of the door or the bed. I just found a new village and almost every villager went to bed, except for two or three. In my attached screenshot you'll see a villager out at night and behind it in the background is a house that contains an empty bed. I opened the door so you could see.
Sorry for the big picture. I know moderators know how to get a screen shot to show as a small thumbnail, but I haven't figured out how to do that yet. If you're a moderator and know how us regular users can do this, please comment and let me know. I was able to resize the picture by clicking on it and dragging a corner down, maybe that's how it's done.
[media]After some testing and troubleshooting, I resolved my issue. The issue for me was an application called Razer Cortex. It's part of the Razer software I use for my keyboard and headset, although Cortex is not necessary. It has a feature to "auto-boost" your games, supposedly freeing up resources and such. Once I disabled this, the game ran so well that my CPU and GPU were barely being utilized. LOL I even turned off VSync and saw over 200+ FPS. 🙂
Debug info
[media][media][media]Testing snapshot 19w46b in Windows 10 installed on an SSD (both game and OS are on it) with a GTX 1660Ti and i7-8700 and 16GB RAM. Up to date NVidia driver and Windows 10 contains all updates as of today. I have attached screenshots of my settings and performance in-game. My resolution is 1920x1200@60hz. The game has been running for a few minutes. I just looked at it and the FPS (with Fullscreen off) was what I expect it to be (about 59), but then I switched to Fullscreen and looked around which caused the FPS to seriously drop. I tested this out in 1.14, but had no issues with that version of the game. There is an integrated GPU in my CPU, but I have verified that it is disabled in BIOS. I looked at the Nvidia Control Panel and changed the default option of OpenGL Rendering GPU from Auto-Select to the only other option, my Geforce GTX 1660Ti. At one point it seemed like this fixed it, but I tried again and couldn't replicate the seemingly success. I am not using any mods or resource packs with this snapshot, nor was I using any when I test (successfully) in 1.14. Also, while testing HWMonitor shows 0 to less than 10% GPU utilization. Also, it seems the first two cores of my CPU are working pretty hard, anywhere from about 50% or slightly less all the way to 100%.
[media][media]I installed Optifine and found the vignette setting. When I changed that setting to Fast, the issue went away. Thank you for helping me understand this issue and finding a way around it. I greatly appreciate it!
Thank you for the support, I greatly appreciate it!
That's not a bad observation. I saw that and overlooked it without watching the included video. When I initially noticed it, the technicality of what was stated was beyond my understanding of the game, so I quickly overlooked it. After actually watching the video included in that bug report and watching mine, I think I can agree this is a duplicate, though I think it sounds faster in my video.
Thanks for the input, both of you!