Mahamatan
- mahamatan
- mahamatan
- Europe/Stockholm
- Yes
- No
MC-30158
When 'maximizing' a Minecraft window, my framerate drops to a consistent 15 fps when I'm otherwise able to run at around 60fps in most other situations.
Steps to Reproduce:
1. Start Minecraft
2. Hit f3 to bring up the stats display
3. measure fps.
4. 'Stretch' the window so that it's almost maximized, but not quite. Measure fps.
5. 'Maximize' the window via the windows maximize button or double-clicking the title bar. Measure fps. Note the massive drop.In the screenshots below, I've posted examples of what this looks like. In the first, 2013-09-06_15.44.56.png, it's the little bitty window that Minecraft always starts with. 58 fps. This is on the new 'amplified' world setting, just after I've created a new world, so it's working pretty hard.
In the next, 2013-09-06_15.46.01.png, I've stretched it out so that it's not quite maximized. 60fps
In the third, 2013-09-06_15.46.19.png, I've 'stretched' the display across two monitors. 59 fps.
In the last, 2013-09-06_15.46.34.png, I've moved the display back onto the main monitor (powered by the GT430) and simply maximized it so it's slightly larger than the 2nd. Drop to 15fps.
So something about 'maximizing' the window is arbitrarily limiting the FPS there, especially if I can drag it across multiple displays for a larger total pixel count.
When 'maximizing' a Minecraft window, my framerate drops to a consistent 15 fps when I'm otherwise able to run at around 60fps in most other situations.
Steps to Reproduce:
1. Start Minecraft
– Edit: Set Render Distance to 'Normal'. –
2. Hit f3 to bring up the stats display
3. measure fps.
4. 'Stretch' the window so that it's almost maximized, but not quite. Measure fps.
5. 'Maximize' the window via the windows maximize button or double-clicking the title bar. Measure fps. Note the massive drop.In the screenshots below, I've posted examples of what this looks like. In the first, 2013-09-06_15.44.56.png, it's the little bitty window that Minecraft always starts with. 58 fps. This is on the new 'amplified' world setting, just after I've created a new world, so it's working pretty hard.
In the next, 2013-09-06_15.46.01.png, I've stretched it out so that it's not quite maximized. 60fps
In the third, 2013-09-06_15.46.19.png, I've 'stretched' the display across two monitors. 59 fps.
In the last, 2013-09-06_15.46.34.png, I've moved the display back onto the main monitor (powered by the GT430) and simply maximized it so it's slightly larger than the 2nd. Drop to 15fps.
So something about 'maximizing' the window is arbitrarily limiting the FPS there, especially if I can drag it across multiple displays for a larger total pixel count.
As of 14w07a, Villagers show nowinterest in breeding when they should
So, I thought I noticed this in the last snapshot but wasn't sure. I spent some time testing the issue a couple different ways this evening.
1. In survival mode, I found an existing NPC village and added several buildings with many doors (Mostly 4 x 4 with 8 doors). I took care to make sure that their 'cover' spaces were not overlapping. The villagers will walk around the village and even enter the new bulidings during daytime, but never show any interest in breeding. They never get any hearts or produce any new villager young.
2. In creative mode, I built two 6x6 buildings with 16 doors each for a total of 32 doors. The two are built diagonally from each other so as not to 'overlap' at all. Then I opened 2 villager eggs near by. The villagers will enter the buildings, but show no interest in each other. They don't get hearts or produce little villagers.
It's sad, really. It's like they've taken too much redstone prozac and have lost their reproduction drive.
_Attached screenie is of the two villagers not having sex.
As ofAs of 15w39c, villagers are once more North-West obsessed.
As of 15w39c, Villagers are once more clustering in the north-west corner of their villages. This was not the case in the 15w38 builds.
Note in the attached screenshot, I'm standing 'one building away' from the NW corner of the village. Behind me are roughly 30 buildings.
– Edit –
2 Months later and this bug has still not been acknowledged, let alone addressed. It'd be really nice to see some attention to this issue since it's a regression bug and one that was a real pain before it was fixed the first time. I understand that bugs need to be triaged and prioritized, but I'm really starting to worry that this regression is going to make it to the release build.
As of 15w39c, Villagers are once more clustering in the north-west corner of their villages. This was not the case in the 15w38 builds.
Note in the attached screenshot, I'm standing 'one building away' from the NW corner of the village. Behind me are roughly 30 buildings.
– Edit –
2 Months later and this bug has still not been acknowledged, let alone addressed. It'd be really nice to see some attention to this issue since it's a regression bug and one that was a real pain before it was fixed the first time. I understand that bugs need to be triaged and prioritized, but I'm really starting to worry that this regression is going to make it to the release build.
– Edit –
Behavior is still present in 15w49b
I've noticed this in 1.4.7. I've made a huge village and they all crowd into the same 3 houses in the far north/west corner of the village.
My suggestion for changing this in villagers... we know that village population is tied to the number of wooden doors in a village, so that must mean that all doors are counted or indexed in some fashion. Each villager should be given an attribute that is a 'favorite' door he prefers to walk towards when idle, hiding from the dark, or when running from zombies. This favorite door should be a door that is not another villager's favorite, if possible.
These screenshots were taken just before I forced the crash. One is at the tiny 'starting' resolution and the other is 'maximized', but not full-screen. This is a different world than the other screenshots, created with normal settings.
Chris, my experience is that the following behavior exists:
Play at any resolution windowed other than 'maximized' in Windows and you get full FPS, up to the capabilities of your machine.
Play at any resolution fullscreen and you get full FPS, up to the capabilities of your machine.
Play at any resolution 'maximized' in Windows and you are arbitrarily limited to 15fps.
Can you confirm that's what's happening with your setup?
I hurt for your driver woes. Sounds like you've got a beefier rig than I do, though!
Your results are pretty consistent with what I'm seeing, although, I'm getting lower FPS all around, simply due to a less beefy rig.
Mrs. had her PC unused this evening, and she has a MC account/install on it, so I tested on hers. It's a slightly less beefy rig than mine. CPU is an AMD 7750, dual core 2.7ghz with 3 gb of Ram and an nvidia 9400GT.
On 'Far' render distance, I got the following FPS:
Tiny: 59fps
Near Maximized: 30fps
Maximized: 30fps
Full Screen 33fps
On 'Normal' render distance, I got the following FPS
Tiny: 60fps
Near Maximized: 60fps
Maximized: 30fps
Full Screen: 40fps
So, yeah, it definitely pops up with the 'Normal' render distance moreso than the 'far' render distance and will attempt to edit my original reproduction instructions to include setting render distance.
I forced a crash report, JIC.
Attached are screenies of the missing chunks near my tower base... ie, they're in my 'active' area most of the time.
After falling back to 15w36d, the villagers IMMEDIATELY started to spread back out to the rest of the village.
As of 15w40b, villagers are still drifting North-west, ignoring and/or forgetting other buildings.
The familiar 'cramming' behavior from before the 1.8 series is back.
as of 15w43c, the villagers seem to spread out to occupy parts of the village, but not the entire village, even giving them time to explore and 'pushing' them to the unexplored edges. They still seem to prefer the north-west quadrant.
I can confirm that this is still an issue in 15w45a
As of 15w47c, Villagers are still 'cramming' in the NW-most building.
Confirmed present in 15w47c, single player survival, minecarts. Behavior is usually in the form of you drift out into the 'empty' until the chunk pieces around you disappear. At this point, you have to quit and restart and are usually stuck 1 block down at the chunk boundary where stuff should have been loading but wasn't.
Confirming still broken on minecarts as of 15w49b. 49a was too crashy for me to get a reasonable test scenario going.
I took the doors off the most north-west building in 15w49b just to see what the villagers would do. They 'crammed' into the next most north-western buildings, going so far as trying to climb the walls and shoving each other north-west in a building that had a west-facing nook.