Blue Screen Fix Worked!
#101 posted by Virto on 2018/04/03 01:05:21
Just tried it- works perfectly now! Great work!
@virto
#102 posted by Baker on 2018/04/03 01:21:40
Great! Glad to hear it! We're batting 1000% again.
My greatest fear on release was the diversity of the Android platform from models to Android versions to processors.
/Mega-thanks to ericw! It could have been weeks before I came across that kind of information!
Sepulchre Support?
#103 posted by Qmaster on 2018/04/03 01:24:04
I suppose your support implementation differs than Quakespasms, because I still can't play aristical's map in dm4jam because it is greater than 80000 verts. I haven't actually tested AD itself yet though.
#104 posted by Baker on 2018/04/03 01:28:15
I didn't go full dynamic. I want to see if a minimal skinny implementation worked first. I'll go full dynamic next version so there is effectively no cap.
@qmaster
Neither Mark V nor QuakeDroid can load Artisitical's map. We even put a "this map requires Quakespasm" warning in the dm4jam start menu before the teleporter to this level.
I Know
#106 posted by Qmaster on 2018/04/03 06:33:21
I just wanted to test it after Baker added sepulchre support to QuakeDroid, something MarkV doesn't have yet either.
I'm trying to get my Gunter badge for the month ;)
Bug Report V2.0
#107 posted by oGkspAz on 2018/04/03 09:28:15
Just downloaded the new version this morning and reinstalled. It did update as the console now has an underscore.
I am still getting the lines on transparent water mentioned in posts #60 and #85.
Samsung J5 Prime still running Android 6.01
Congrats On The Release!
#108 posted by brassbite on 2018/04/03 14:28:17
On my phone, the Huawei P9 lite Quakedroid works perfectly fine.
I wondered if my Kindle Fire HD tablet from 2012 could handle Quake, and the shareware downloaded perfectly fine, then it just got stuck on a white screen. Don't really bother about, only maybe. I bet you can find issues more important, I bet it will lag the hell out of the Kindle (1.2 Ghz Dual-Core, 1GB of total RAM)
@brassbite
#109 posted by Baker on 2018/04/03 20:59:30
I'm glad it works well on your phone!
should run on any Android phone made in the last 5-6 years
For the 2012 Kindle, it might not have enough RAM or might be out of storage space. It could also be that the version of Android is too old. Also it is my understanding that Amazon rolled their own (outdated) Android especially on older Kindle Fire tablets.
Thanks for letting me know about the 2012 Kindle Fire. I think I know someone with one of those sitting around and I might be able to get ahold of it in a few weeks (at a minimum to satisfy my curiosity to see if I can get it to run).
You might be able to free up some space on it and still get it to work.
I'm Fine On Storage
#110 posted by brassbite on 2018/04/03 23:05:36
Got at least 10GB of free space. Of the 1Gb RAM, it should still have 400 Mb free. Maybe. Just guessing, cause Amazon patched out the task-view. I can run a N64 Emulator though
@brassbite
#111 posted by Baker on 2018/04/03 23:49:01
Yeah, sounds like you are fine on storage. My Android phone, storage is more of an issue (4 GB) and during testing I managed to run myself out of space a few times.
If you posted Quakeid1qconsole.log off your device folder pic via USB, I might be able to learn something useful about the crash.
(You usually need to restart the device first to see the file. Android uses MediaStore to keep track of files and rescans on boot, Quake doesn't have a good way to update MediaStore because it is a low-level native C application.)
1) You might try the APK for Virto I made in post #100 to see if that works. It tells the device the desired color format.
2) Seems from your description that video works (download flashes the screen, changing the shading as it downloads) and that download works.
Barring that, I have a friend of friend who I know had a 2012 Kindle Fire, but it won't be quick to get ahold of it.
@oGkspAz
#112 posted by Baker on 2018/04/03 23:53:00
I'll have to play around. I'm hoping it isn't "luck of draw" depending on screen resolution. I modified the algo but apparently on some resolutions the draw stretches favoring certain columns more of liney look on the transparent water.
@Baker
I am pretty sure I have a 2012 Fire. Will confirm with you. This project is so cool I want to help out where possible. I can also test on other models. I have access to a Pixel and a 1st and 2nd gen Moto X. I'll report back.
@dumptruck
#114 posted by Baker on 2018/04/04 00:23:28
Could you check if your 2012 Fire has the problems that brassbite does?
@Baker
Yep. Will report back this evening.
I Have An Old Fire Too
#116 posted by Qmaster on 2018/04/04 02:02:23
Can't revall the year, 2013 maybe 2012.
@Baker
Unfortunately, my Kindle is from 2011 and gave the error: There is a problem parsing the package. Most likely the OS is way too old.
My wife has a much newer model. I will steal it and report back if I have any luck.
Have A Log File
#118 posted by brassbite on 2018/04/04 09:16:36
And Another One
#119 posted by brassbite on 2018/04/04 09:21:23
@brassbite
#120 posted by Baker on 2018/04/04 09:33:50
Looking at the log, it appears the engine thinks everything loaded ok and it proceeds to start playing the demo.
Does it make sound in the background and just show a white screen while doing it?
Either way, I'll try to eventually get my hands on a 2012 Kindle Fire from a friend I know, just to satisfy my curiosity and see if I can get it to work.
Suggestion
#121 posted by ICARO on 2018/04/04 14:03:59
@Baker fantastic job, but would it be possible in the next release to rise The step left / right icons at the same level of the fwd icon. In my opinion this would lead to an increased playability. What do you think?
@brassbite
#122 posted by Baker on 2018/04/04 14:51:42
I'm about 80% I know what's up with your Kindle and can fix it if it is playing the sound. I saw something in the log you posted that made me think.
@icaro - Thanks! I tried to make it very nice. Yeah, the controls need some tuning and it'll come. I've got a little bit of a queue at the moment.
#123 posted by Gunter on 2018/04/04 19:09:18
ICARO is right about the position of the move icons -- at least util a better control option comes along.
But while we're still using the current setup, I'll also mention, in addition to my previous preference for:
Jump
Attack
Change
that the buttons along the right could be positioned like:
. . . . . . Jump
Change Attack
with the buttons grouped around the bottom right corner. That still puts all buttons close to the Attack button for easy access.
Seconded
#124 posted by Qmaster on 2018/04/04 19:20:52
Sorry, I'm A F K Until Friday Afternoon
#125 posted by brassbite on 2018/04/04 22:28:15
Away from Kindle
Have fun with other issues meanwhile
|