-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not working Minecraft Android Versions #48
Comments
1.16.100.50 just hangs. |
1.16.20.03 is broken again. See #129 |
1.16.100.04 hangs randomly, mostly when game is quit |
I know the launcher is unstable on some devices, but here an overview about the current status:
|
I would like to politely mention that while the launcher says that lack of support for 1.16.210 is not a bug but a feature request, the inability to use 1.16.210 basically prevents some of us from playing with our family and friends any more, as some devices auto-update and it seems universally true that they block older clients from connecting. |
I won't want be rude, you get what you want immediately minecraft-linux/mcpelauncher-versiondb#11 ...the ability to craft in 1.16.210 prevents basically some of us from playing survival at all see MCPE-117105. I still recommend to back up your worlds before starting 1.16.210. |
@ChristopherHX Wow, thanks! I tested it this weekend and it works great with Realms for me. |
Here an overview about the current status of 1.16.230. I will upload fixes in the next update no eta.
|
Minecraft bedrock version numbers are getting out of hand, I hope this doesn't go to 1.16.2000.05... |
So far, I didn't encounter the crafting bug... |
Then you are likely only using the arm version of this Launcher, it seems to only affect Android x86(_64) devices incl. x86(_64) Versions of this Launcher. Most Users of this Launcher don't use the arm version, I use / test arm seldom. I was the first one who began to provide prebuilds for armv7 and armv8, just to make it complete or to complex for noobs to install it (Imagine running the x86_64 version on raspbian (armv7) and wonder why it creates a text file on the desktop, no joke). |
True, I do use the arm version of the launcher, well, thanks for building for different architectures! |
What versions do work exactly? I am looking to test my OG Mac Pro running El Capitan, and all the x86 versions I've tried are blocked by the latest launcher. |
I prefer you would open an issue here: https://github.com/minecraft-linux/mcpelauncher-ui-manifest/issues
For EI Captain 32bit game, should be Minecraft 1.1-1.16.10 (x86) . I never tested it on EI Captain.
This might be a bug, which appeard after I introduced "Block launching unsupported Minecraft Versions completely"
Workaround 1:start the
Go to settings->Dev enable show unverified Versions, you will be able to run it anyway. Workaround 2:Delete the Minecraft version completly, and reinstall the version, if still blocked open an issue https://github.com/minecraft-linux/mcpelauncher-ui-manifest/issues Workaround 3:Get the old version of the Launcher until fixed, only basic 1.16.210 support was added. In the changelog: If you are not trying to run a beta version and you find the version in https://github.com/minecraft-linux/mcpelauncher-versiondb/tree/v0.1-beta-20 it is the bug I can confirm, I'am going to fix it with the next release. No sound for game 1.16.20 or newer on 32bit macOS, might be implementable |
When it says that 'baron cannot fabricate Classloader class' is this a blocking bug, or a bug in some legacy part of the loader? |
Well I've just bought the game on the Google Play store, and I don't have this issue anymore. I am able to play 1.16.210 just fine, no sound effects and all. The crafting system doesn't look to be difficult to use. The game runs fantastically, just like Java edition does since I upgraded the system starting in 2015 and is almost done as of last year. Just needs the CPUs upgraded to dual 3 GHz Quad core Xeons. |
The latest version, 1.16.220.02, is preventing me from getting on my realm on my mac. When will the new update be added. |
When it says that 'baron cannot fabricate Classloader class' is this a blocking bug, or a bug in some legacy part of the loaderNot blocking for me, I would say it is optional. It might be possible to fix by just implementing missing c++ funcions called via jni. I'm not willing to update the Launcher as frequently as last year, it is very time consuming. If someone tells me the crafting and / or texture bugs are fixed by mojang the next update might happen earlier.
|
Do I just need to update my launcher to get it? |
no, sorry this is still being worked on. |
|
this applys to .31 as well. |
This is taking a lot of the developers time and energy to fix this just give them some time they are humans too yk. |
yes. |
It's still quite unacceptable, I was never given the task to respect any of the developers I just want to play the game the developer's jobs are to fix It which I doubt they have been "working on a long time" since It's been nearly three weeks already. So no |
The level of entitlement displayed here is insane. You are not paying these people. They are providing their limited spare time free of charge to solve what is clearly an insanely difficult problem (if that were not the case, you would have solved it yourself). The only thing unacceptable here is the above comment. Being frustrated with Microsoft and the industry in general for not providing support for Linux is one thing. The original game developer, after all, generally has the resources to do this... and more importantly, you compensated the original developer. |
No excuses, If you want to be upset with my feedback then fine but don't sit here and make something up to make yourself look like the good guy. If one or two people decide to make a public project and after a while just abandon It because there Is too much difficulty then I'm not going to presume that they will fix It within a short amount of time. I have a 99% chance of thought that right now nobody Is doing anything to increase the speed of when this bug will be fixed. |
Ok ill agree with him now the last update we had on this project was 3 days ago and it was a line suggested by another user. He is giving feedback and they seem to be slowing down instead of speeding up, some of this can be pinned on Mojangs render dragon engine but they could spend a little more time on this. |
It's clear you are not a developer yourself so let me explain; the number
of lines committed or changed has very little to do with how much work is
being poured into a project - Christopher could've poured in hundred of
hours trying to debug the issue, but until he finds a solution that will
amount to 0 committed lines. So it is not a useful metric, and even if he
had decided to take a week off - then what? What screwed up universe do you
live in where you think that you are entitled to demand how other people
spend their free time? If it bothers you that much then download the source
and start doing some work yourself.
…On Wed, May 4, 2022 at 2:33 AM CrypzM ***@***.***> wrote:
This is taking a lot of the developers time and energy to fix this just
give them some time they are humans too yk.
It's still quite unacceptable, I was never given the task to respect any
of the developers I just want to play the game the developer's jobs are to
fix It which I doubt they have been "working on a long time" since It's
been nearly three weeks already. So no
The level of entitlement displayed here is insane. You are not paying
these people. They are providing their limited spare time free of charge to
solve what is clearly an insanely difficult problem (if that were not the
case, you would have solved it yourself). The only thing unacceptable here
is the above comment.
Being frustrated with Microsoft and the industry in general for not
providing support for Linux is one thing. The original game developer,
after all, generally has the resources to do this... and more importantly,
you compensated the original developer.
No excuses, If you want to be upset with my feedback then fine but don't
sit here and make something up to make yourself look like the good guy. If
one or two people decide to make a public project and after a while just
abandon It because there Is too much difficulty then I'm not going to
presume that they will fix It within a short amount of time. I have a 99%
chance of thought that right now nobody Is doing anything to increase the
speed of when this bug will be fixed.
Ok ill agree with him some what the last update we had on this project was
3 days ago and it was a line suggested by another user.
—
Reply to this email directly, view it on GitHub
<#48 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABRSMJMEOIKJ3BMZQQQ5QHTVIHAVVANCNFSM4K7F6QJQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
woah this just popes up in my email. jeez! |
wow, cool, you are being so rude! |
Remember that the folks working on this are not Microsoft or Mojang developers. This is a project done out of the goodness of their heart, and they have no obligation to fix anything. "Demanding" anything from them is counterproductive. Your options are:
Complaining solves exactly zero issues, and actually causes more when the devs, who are people like you, get frustrated from the negative reactions to something you're not paying them for and stop work. |
Ok let me explain what im getting at. Im just saying we can get a couple more updates to this and like i said this is not your guys fault its mojangs they were the ones who put in render dragon and that seems to be the main issue and if i had to guess you guys are leaving a bit of code in still using the old renderer and sense that is no longer in mojangs code i would remove it and replace it with the render dragon code. If already done so then this is a lost project because render dragons code might be exclusive to mojang. |
yes i agree completely! |
This is a public free project created by people that love minecraft enough to try and support the bedrock edition on Linux. They do this with free time and passion. If they don't play anymore or don't have enough time, then too bad for us, but it's a public project, just fork it and fix it yourself and support the other members of the community. The only thing I ask is that you stop those rude comments. When a community gets entitled like you are, then that will demotivate the devs to ever want to touch that project again. Now say you're sorry and wait in line like the others. |
yea |
There's no rule stating that I must respect anybody here, I'm not entitled to telling the complete truth. I would love to see any form of progress, besides people just posting random codes that do literally nothing. Once you can provide some form of evidence that these devs are actually doing something I will admit that I'm entitled and I will apologize. |
Check again, there are actual rules here: I would argue that complaining that a pro-bono tool hasn't been updated fast enough for you is instigating conflict as the above conversation shows, and has resulted in discussion not about the bug, but about entitlement. It's unlikely you'll get banned, but your bad behavior is recorded publicly and if you ask for something in the future and folks see it they will weigh it when thinking about assisting you. So if they don't update the bug, what then? You'll take away your zero dollars you paid ChristopherX for this? ChristopherX and others, some of us are happy you do what you can for us. The trolls may be louder, but we're still here. This issue was closed forever ago, no need to keep even discussing here. |
i mean it is a good place to discuss the new version bugs. |
I was trying to say that there might be some left over code of the original renderer in just replace it with the new render dragon. |
note: the original developer(s) have basically given up on the project, we are just community members poking around looking for a fix, we aren't experienced in this project in any way. (I am not sure about the we part, but this is the case for me) This will obviously take some time, since I have school work and many other things to do. 3 weeks is not even a lot of time, so relax and wait, there are other ways to play minecraft bedrock on linux you can rely on right now. |
the code is written in c++ and is passed through a compiler, the resulting machine code is unreadable to humans, so we have to resort to using a decompiler. Decompilers are only good at producing assembly code, which is basically machine code in human readable form, which is useless (since the .so file is massive and there's the problem that most of us here can't read or comprehend that in any way). Considering these factors, it is impossible to search through it, so our best bet is just trial and error. (or a rewrite) |
I have a feeling they will remove render dragon. There is so much backlash against it. |
This issue is locked now. New bugs in 1.18.20+
New bugs in 1.18.30.04
New bugs in renderdragon
|
1.18.30 / 1.19.30 public developer preview You have to clone minecraft-linux/mcpelauncher-manifest ng or qt6 recursive and pull the latest version of the mcpelauncher-client, mcpelauncher-core, libc-shim submodules from the master branches. This issue is locked goto and subscribe minecraft-linux#691 for further updates |
This Project has been suspended by me since 2021/11/1, further changes or bug fixes are requiring Pull Requests to github repositories of minecraft-linux See #48 (comment)
FAQ
and depends on this issueI just don't want see bug reports of beta versions, it is not something I want to support.
Because something magically worked sometime, it doesn't mean it will always work.
I never told you that you can play on realms with this Launcher and do not support it.
I do not use it and don't want to invest time fixing it.
The following versions haven't known to work yet.
0.0.0.0 - 0.11.99.99
1.13.0.9 - 1.13.0.17
1.16.0.67+ (works in ng)
1.16.210, 1.16.220 (Known issues)
1.16.230-1.17.0 (Known issues)
Please post exact version numbers which aren't working.
Crashlogs would pollute this Issue.
The text was updated successfully, but these errors were encountered: