lagomoof
- lagomoof
- lagomoof
- Europe/London
- Yes
- No
MCL-21450
MC-47683
Please, refer to his answer and let us know if the work-around provided by lagomoof is working for you.
Temporarily closing the ticket as "Awaiting response". This ticket will automatically reopen when you reply.
![[Mojang] Donuts1000](../../../data/avatars/users/18949.svg){kind=small}
lagomoof per my understanding, Launcher's minimum window size is 720p. The issue as written here is saying resolution of 1266 x 768 isn't fitting - and I'm assuming this means with the Launcher resolution at default & no up-scaling happening either at the OS level or within the Launcher settings.
Assuming all that is true, it should fit. Can you confirm what your OS level zoom settings & Launcher level display settings are set to?
Dark torch issue still happening in 1.8.2 full. Screenshot supplied. Left torch acted same as right torch until the block above was removed. World is new.
Further to previous. Still happening for me in 1.8.3. Additional testing seems to show that opaque blocks above the torch still make for darkened torch flame, but an otherwise opaque light/chest-blocking "double slab" block does not darken the torch in the same way!
Note that all of this only applies to torches on the side of a block and underneath another block. Upright torches (on top of blocks) do not seem to be affected when a block is above them.
OS is Windows 7 64-bit. Graphics card is NVidia GeForce GTS 450 with latest drivers. Java 1.8. I had been using Optifine on 1.8.1, but clearing out the .minecraft directory and starting afresh has had no effect.
No change by making NVidia driver aware of minecraft.exe specifically.
Switching on the beta mode doesn't appear to make any difference.
I checked my notes from the time I happened to tweet about this a while ago (in retrospect I should have submitted a bug at the time, but I kept the launcher open), and at that time, the logs said that no update was needed, but then it proceeded to download the update twice* anyway!
Running tests with the beta mode enabled results in one of three outcomes in the logs:
1) It decides that it wants to downgrade, like the previously provided logs.
2) It decides that it wants to upgrade (switch the versions in the above), because the previous download apparently succeeded.
3) It detects that it has a version it likes and that no change is needed, but then proceeds to download something anyway.
All three have happened during my further testing today.
In answer to the first question: Yes. Once the launcher finally loads, it's possible to use it properly and play Minecraft just fine.
(It's fortunate I'm not on a connection where I pay per data, because this might have been getting expensive)
Coming in from 21450; later duplicate of this issue.
Can confirm that manually replacing /opt/minecraft-launcher/minecraft-launcher with the tar.gz version from the 'Other' option on the downloads page stops the repeated updates.
The .deb package (that would otherwise work on my computer) is detected as being an older version than is currently installed (because of automatic updates, somewhat ironically), so I could not use that to perform the more standard installation / upgrade.
Since the manual installation workaround required root access and the automatic updates generally don't, that would explain why the automatic updates don't, or perhaps can't, fix this error.
On Linux, the current minimum size for the launcher is 1280x720.
There is absolutely no reason that it needs to be this large.
On most screens there is conspicuous vertical and horizontal empty space, suggesting this choice was made arbitrarily without reference to the internal layout. I'd be willing to bet that it would be usable (if cramped) even at 640x480, were that allowed.
My interest here is that I have an old 1024x768 monitor that I used to be able to put the launcher on, in maximised mode, but now it won't fit.
It even removes the "maximise window" icon from the launcher's title bar to prevent my trying to get it to fit that way, should I move most of the launcher over to that monitor. In my book, that's just plain rude.
If that wasn't enough, Minecraft itself works just fine on that monitor. Why does the launcher need more resolution than the game itself?
> We recommend you set your system to scale not beyond 100%
System scaling, for me at least, is 1:1 and regardless of what it is set to, it is not the cause of this problem.
Indeed, since this cryptic comment might have been a reverse hint, I did try to run the launcher with alternative scaling, but the hard-coded minimum size in the launcher still takes effect and the window will not resize below 1280x720 actual, physical pixels on my monitor.
Flipping this on its head and turning scaling the other way, elements in the launcher window become larger, and yet the launcher works just fine, proving that the hard-coded limit is unnecessarily large.
We could, of course, change our entire OS scaling and then scale everything else but the launcher back the other way, but that's a horrible workaround.
There is a 1280 somewhere in the launcher code pertaining to resizing that should ideally be a 1024 if that minimum limit is to exist at all (and I'm not sure it needs to). That is the only change that is needed.
My secondary monitor is, or rather was, 1024x768, and though I have had the good fortune to be able to upgrade, I may not be the only person with a monitor of that size. It remains my backup monitor if something is to go wrong with my current ones.
The other point I made back in March is that the game itself will run at a lower resolution than 720p. That the launcher won't also do this doesn't make sense.