Can I get some clarification on why the verified version of the app is set as (Android: https://play.google.com/store/apps/details?id=com.gabrielecirulli.app2048) when all current runs have been run on (2048 - https://play.google.com/store/apps/details?id=com.tpcstld.twozerogame)?
I ask because the version suggested in the rules tab runs like crap, has ads, and slows to a crawl while recording. I'm running on a Oneplus 3T, and bench marks has it as still a top 40 phone, so I can't imagine anyone else would be able to run that much better than I can, which could severely affect how many new runs are posted in the touchscreen section.
Could a moderator take a look at that, and consider changing the suggested app to the one most used? I have new recorded runs that I've saved up for when someone eventually beats my current record, but they are useless now with the app change.
I can do the times again, but the new suggested app simply doesn't run as well while recording.
The apps that are allowed for runs are the original game and a select few that also use the original game's code. We want everyone on an even playing ground.
If your phone slows down while using on-board software to record, I suggest trying an external method.
Not sure why you're sandbagging your runs. Generally, that's frowned upon.
I have atrocious internet, and uploading 300mb takes hours and hours at times. No reason to upload a new best time if no one is even beating my current one, you know?
Plus if I widen the gap to a minute between first and second, that will lower the chances anyone will even attempt.
As for an external option, I'd think video capture would be much better than someone recording the run over my shoulder.
That, or buying a TV or second device to stream my screen to(which I'd imagine would also cause slow down), and attempting to record using other software. This would also necessitate turning on developer mode to activate touch view, or perhaps another third party program to do the same thing. Kinda seems over complicated when the goal should be to keep things as uncomplicated as possible to grow the community.
The gap between places shouldn't have any bearing on whether or not someone runs the game. When I said an external option, I meant a device that captures the screen, not a person hovering over you with a camera. As stated in the rules, showing touches is required.
And again, you're over complicating things.
If my phone is struggling to run the app you've suggested, and the best screen recording software on the app store at the same time, than 90% of all Android users are going to run it even worse than I am.
Is suggesting that the best option be to find a way to externally record the screen really a fix?
Most phones and tablets don't have mini HDMI out.
Most users don't have casting capable tvs, or networks.
The only realistic option for most users is having someone else record using a secondary camera, which would require a huge time investment as 99% of run attempts end in failed runs.
Again, this is restricting the potential of the running community and I don't think it's realistic. You can't exclude the larger portion of the community because their phones can't run the needed software, or make use of external recording setups.
Between my posts yesterday, and today, I did test runs with the three most downloaded screen recorders on Google play.
DU Recorder: 50m downloads AZ Screen recorder: 10m downloads Screen recorder - Free no ads: 1m downloads.
I did runs while recording, using the app suggested in the rules, and using the app that the current top two runs used.
For all three recording programs, there was stuttering, slowdowns, and in one instance an outright hard reset(Screen recorder - Free no ads).
Using the version I've been running on, I had mild slowdowns using DU, but not bad enough that I'd say that the speed the game is running is affecting how long it takes to reach 2048.
With AZ, it ran as I expected it to, which is about 95% of normal speed.
I skipped screen recorder - free no ads for this one as it just doesn't run all that well to begin with.
For reference, this was done on a OnePlus 3T, which GSMArena.com has as 38th strongest phone, one point away from the Samsung Galaxy S9+, within 100 points of the Note 8, Note 8+, Pixel 2, and the S8 Active.
As I said above, if my phone is stuttering, so would just about most of the Android market, unless they bought a brand new phone this year. Which most people won't, and didn't.
2048 is a simple game, with simple programming. Forcing the community to only use a version that is slow, has ads, and a wonky timer because it's the original version stifles it.
I think the ads thing can be fixed by turning off wi-fi and data but regardless of that, if the original app is so buggy that no phone can run it correctly, a better alternative with the same source code should be available which I don't know if that's the case with the select few other apps that are allowed.
Oh believe me, it's worse than that. The ingame timer starts the moment the ad finishes playing on startup, but we're expected to time from our first input. Which is meant to give us a moment to consider how to start the run. A strategy moment.
So either we need to run our own on screen timer, or we need to ignore the ingame timer completely and remember the exact moment we started actually playing. Again, a feature only seen in the newly required app version for runs.
I really don't mean to complain, but as it is, barely anyone runs touchscreen. I'm pretty sure at this point, that it's just me. I'd like competition. I'd like people to run against. And right now, if I can barely run the required version, and record at the same time, how can I expect someone with a $1000 super phone to decide that 2048 is their new thing, and run against me? Especially since every counter point I have above is valid. I want an open community, and the current app is stalling that.
Requiring touches to be visible is a great idea. Stops people from using a Bluetooth keyboard, or controller.
Requiring video of the run from start to finish is super obvious.
Requiring players to use a specific app that no one has tested(other than me?) under recording conditions seems the exact opposite of a good idea.
A quick Google search yields multiple results for free solutions to record your Android device with your PC. You don't need to cast to a TV, you don't need someone else to help you, and you don't have to spend hours uploading video because it is recorded directly to your PC.
https://nathantah.github.io/2048-timer/
If you don't like the original version, feel free to use this version that Nei has written. It's primarily geared towards being used on desktop so it isn't as aesthetically pleasing on mobile, but still functions correctly. He has plans to make it more mobile friendly when time allows.
38th strongest phone doesn't exactly sound like a powerhouse.
Which do you imagine is easier?
Using one of the many well tested, well reviewed apps on the market, a.k.a what most people coming into speed running would try, or, downloading 3rd party software on their PC, plugging their phone into it, turning on USB debugging, running that program, hoping your drivers are compatible with the program, and then finally recording using that program? Because that's what your link leads to. A list of steps and a program to download. 2048 is a casual game, and I'd imagine that when someone looks to speedrun a game like 2048, they aren't going to be jumping through hoops.
It's an obvious answer, I think.
But hey, what do I know? I'm just the only person actually running 2048 on touch screen.
Also, as far as my phones ranking goes:
My phone is 38th out of over 2000 phones. It is equal in strength to top of the line phones from the biggest makers, which a quick Google tells me makes up less than 12% of the Android market. The other 88% is made up of lower line versions from different makers.
Which again, means if it's stuttering on my phone, means it's stuttering on others phones as well.
What you're doing, is gatekeeping.
Choices given are:
Use the app you chose, which is crap. Use third party PC programs to record, which is a massive hassle that obviously came with zero community input. Get a top of the line $1000+ phone to maybe run the game at close to top speed while locally recording as usual.
You're blocking out 99% of potential runners because you'd rather be right, than accommodating.
Which is cool. You're super mod, so your word is final.
But next time you want to start posting links to free results on how to record your phone's screen, you should instead consider how many people are going to go through the effort to do it.
It runs perfect on my Galaxy A5, which is a high-ish mid range phone, while recording at 1080p, 60FPS. I honestly think it's just an issue with your specific phone. Allowing versions which run different to the original should obviously not be allowed if the original works fine for pretty much everyone.
You going to link to a video there?
Because benchmarks has your phone as a '555' compared to my own phones '3328', which leads me to believe otherwise. Even the benchmarks X score, which is used specificaly in regards to gaming, has a difference of over 20k between our phones.
This leaderboard is for the 2048 game developed by Gabriele Cirulli. The list of verified versions only include the three official releases by Gabriele Cirulli (Browser, Android, iOS), as well as two mods of the browser version that only add timers for convenience. I'm happy to add more versions to the list if it can be proved they contain the same source code as one of the three originals.
