Marcus S Aurelius
- maurel
- maurel
- Europe/Stockholm
- Yes
- No
MC-3202
Stereo sound stage is incorrect with packaged openal32.dll but correct when OpenAL32 version 6.14.357.24 is installed from http://connect.creativelabs.com/openal/Downloads/Forms/AllItems.aspx .
Example using jukebox playing a record: sound volume decreases too much when player turns more than about 100 degrees from source. Volume also mutes at certain positions when looking directly at the jukebox.
Tested using vanilla 1.4.4 Creative mode with jukebox and skeletons.
Problem first noticed in 1.3.2 survival with noise from skeletons in water.
Maybe relevant: also noticed lag spike when moving 16 blocks away from sound source - no spike with OpenAL32 version 6.14.357.24 .
Installing OpenAL32 version 6.14.357.24 from openal.org and removing (or renaming) %APPDATA%\.minecraft\bin\natives\openal32.dll fixed this problem (and the lag spike). Restoring the original openal32.dll restores the problem.
Keywords: openal, openal32, sound, stereo, openal.org, version 6.14.357.24
Edit to explain attachment 2012-11-16_21.58.54.png : this shows a central jukebox with four wooden plack "listening" positions; stand at any of these positions and rotate the player and note the volume severely mutes in the directions of the raised wood blocks; at extreme right is darker wood block where the volume also mutes when looking directly at the jukebox.
2015-12-27_22.29.36.png
Music volume drops to almost zero when looking in direction of cross hairs, but rotate about 15 degrees and volume rises to near maximum.
I can confirm this happens with 1.4.5 in single player survival on HARD and Normal mode. Caveat: I use Optifine but no other mod, and my save is a 100% vanilla world I created in Beta 1.8.
In 1.4.5 the total entity count never exceeds 20, and hostile mobs, bats and squid hardly spawn at all, - maybe about 1 every 10 minutes.
If I copy the whole save folder to a 1.4.2 minecraft install (I have seperate .minecraft folders for each update for the purpose of tests such as this) then hostile mobs spawn as usual - in both the overworld and the Nether.
However, I found the End world is not affected by this 1.4.5 bug - the endermen spawn at their usual rate with a cap around 80.
Things I tried to get mobs to spawn in 1.4.5:
1. exit world, exit minecraft, restart minecraft, reload world - this sometimes caused 1 or 2 new hostiles to spawn and then none more
2. travel far enough to cause chunks to unload and return - either had no effect or just 1 new mob spawned
3. travel in the Nether to get to overworld locations seperated by more than 512 blocks - same effect as 2.
The following report prompted me to try returning to 1.4.2 :
http://www.minecraftforum.net/topic/1584168-no-hostile-mobs-spawning/
Follow-up from my 10/Dec/2012 comment : I cannot reproduce the "no-hostiles" issue in a fresh vanilla 1.4.5 installation - I copied my singleplayer world to the fresh install and after a minecraft day, the hostile mob spawning returns to normal.
However I can reproduce the issue in a separate Minecraft folder modded with OptiFine_1.4.5_HD_U_D3 - if I set Terrain Animated to OFF, new hostiles stop spawning (or spawn at only 1 or 2 every 10 minutes). I switch Terrain Animated to ON and new hostile spanws return.
I tested this several times over several hours in both vanilla and modded 1.4.5.
I confirm the Bad Login issue is affecting many players using 1.6.4 trying to connect to multiplayer servers running 1.6.4.
1.7.2 servers are not giving this problem.
I will attach my detailed tests, but meanwhile,
please see reports at http://www.minecraftcc.com/index.php?threads/bad-login.6124/page-2
and at http://www.minecraftforum.net/topic/2141011-bad-login-error-often/
From several months to two days ago I have never seen this problem on my various vanilla clean installs of minecraft. Now I see it on two different PCs, one Vista the other Windows 8. Nothing has changed on either machine since the last time minecraft was working. The Vista machine has been kept running since the last successful multiplayer connection, now it reports Bad Login for 1.6.4 servers. The Windows 8 machine has been restarted several times, the router has been restarted, all to no avail.
Detailed tests:
1. Download a fresh minecraft.exe from https://minecraft.net/download
It's SHA256 is fc0cf7896c32791501d5864b7b639d0ce36fd3430088c00b0a15a9960b3ce434
https://www.virustotal.com/en/file/fc0cf7896c32791501d5864b7b639d0ce36fd3430088c00b0a15a9960b3ce434/analysis/
2. On Windows 8 PC create new folder F:\data\mc164\ and copy Minecraft.exe to it
3. Create batch file goexe.bat with these four lines:
@echo off
set APPDATA=%CD%
Minecraft.exe
pause
4. double click the file goexe.bat to launch Minecraft, login and wait for the install
5. Test it works on 1.7.2: click Play, click Multiplayer, click Direct,
type "minetime.com", click Join Server, and you will join the server.
6. Press Escape and click Disconnect, click Multiplayer, click Direct,
type "play.lichcraft.com", click Joine Server, and again you will join Ok.
7. Repeat step 6 for several of the 1.7.2 servers listed on https://minestatus.net/
Most will login, none will report Bad Login.
8. Press Escape and click Disconnect and click Quit Game.
9. Relaunch the goexe.bat file but this time click New Profile, name it 164,
under "Use version" select "release 1.6.4", and click Save Profile.
10. With the profile now showing "164" click Play. Minecraft 1.6.4 should launch.
11. click Multiplayer, click Direct Connect, type "mc.ecocitycraft.com",
click Join Server, and you will very likely get
Connection Lost
Failed to login: Bad login
12. repeat step 11 for any 1.6.4 server and most of them will fail.
I tested several times:
play.minecraftcc.com - this worked two times out of 24 attempts
mcb.skyprison.net - this worked one time
mc.ecocitycraft.com - this worked one time out of 6 attempts
198.23.247.55 (Iceymon) - this failed one time out of one
13. Prior to this clean install test, I had tested about eight 1.6.4 servers
using cleanly installed 1.6.4 minecraft in separate folders,
and on two PCS. Windows Vista, and Windows 8. Each machine had never given
Bad Login errors before today. I had already tried the advice in
https://help.mojang.com/customer/portal/articles/1218708-error-bad-login
(router restarted, Windows Firewall disabled, PC restarted several times).
14. My conclusion is there is some problem affecting the communication
between server and client for many people around the world (I talked to a few!)
and it only affects 1.6.4 not 1.7.2 servers.
Nothing is going on apparently. After maybe 40 attempts at connecting to a 1.6.4 server I am able to connect.
Pity we cannot vote on resolved issues. Is there a way to word a bug report that mojang will accept? Maybe
"client reports unexpected Bad Login error message when the cause is not bad name or bad password"?
EDIT: Ok, I created a bug report that might get mojang's attention, please see https://mojang.atlassian.net/browse/MC-40809 .
Screenshots showing misleading error message from minecraft when running with 1.6.4 profile attempting to connect to 1.6.4 servers. First two screenshots show twitter reports showing problems affecting people worldwide.
What is that meant to mean?
Is minecraft 1.6.4 not being supported any longer?
Please see attached screenshot showing the problem is affecting many people today.
More reports from around the world, yet MojangSupport still unaware that the fix they point to does not work: https://twitter.com/search?q=mojangsupport&src=typd
Please tell us HOW to report this to the right place.
Reproducible missing lighting updates in Survival 15w51b and 1.8.8. To reproduce, create new world with this custom preset expected to produce a uniform light level 8: 3;minecraft:bedrock,54*minecraft:stone,minecraft:iron_block,minecraft:stone,minecraft:log,2*minecraft:dirt,minecraft:grass,6*minecraft:air,minecraft:lit_pumpkin;1
An easier way to reproduce this issue in survival (also see screenshot 2015-12-27_22.29.36.png ) is to create a new world using custom presets. For example this preset should produce light level 9 over the superflat world:
3;minecraft:bedrock,57*minecraft:stone,minecraft:log,3*minecraft:dirt,minecraft:grass,4*minecraft:air,minecraft:lit_pumpkin;1
and this one should produce lightlevel 8 (the one used in screenshot using seed 000188):
3;minecraft:bedrock,54*minecraft:stone,minecraft:iron_block,minecraft:stone,minecraft:log,2*minecraft:dirt,minecraft:grass,6*minecraft:air,minecraft:lit_pumpkin;1
In survival the player will spawn on top of the lit_pumpkin ceiling; to see the black spots the player should break the pumpkins and fall the 6 blocks to the grass, there they will see a reproducible pattern of zero-light areas. Move over to each dark area and F3-debug will show light 0 and sky 15. Some areas are light 0 and sky 0. Placing and removing blocks or light sources on the ground will update the light level but not the sky level. Placing and removing blocks on the ceiling will correct the zero sky levels.
The issue also exists on the lit_pumpkin ceiling itself, but is harder to see: occassional hostile mobs will spawn on the rare zero light level blocks. The issue occurs in both 1.8.8 and the latest snapshot. My PC is Windows 8 and I use the standard launcher from minecraft.net with the built-in java runtime.
EDIT to note that the zero sky level (not the zero block level) blocks can be seen in my screenshot as a slight shade (not black) on the lower left.
1.8.8 Minecraft vanilla creative showing zero block light level where level 14 was expected. A creeper was found to have spawned on that block. This world was generated using a custom preset to generate a layer of lit_pumpkin.