BASIC

Recent Posts

Pages: [1] 2 3 ... 10
1
im have not have the issue here. just dont use more number of mouse you can use. on Windows, most player use keyboard and joypad, if its that such a game.
2
Bug Reports / Re: SHOEBOX does not work on ANDROID
« Last post by spacefractal on Today at 06:18 pm »
btw you can try to force a DOESDIREXISTS, which Android will copy all files from that folder to the internal memory first and try to acess the shoebox after that. Also sometimes you need to use full path on Android.
3
removed Android TV scaling stuff.... its effected this issue, mostly im did set a scalling max in y 1560 resolution. this happens easy in portrait mode. Then its try to scaling it.... but the code did not take system button area at all, but returned as its was full screen. Then mousestate returns wrong.

Also Android TV stuff do require Landscape anyway.
4
Bug Reports / Re: SHOEBOX does not work on ANDROID
« Last post by spacefractal on Today at 06:12 pm »
filesystem on Android is crap...... on IOS, you have direct file access to the files, that is not on on the case with the Android.

Im recommend you to use folder based files instead to access your file and perform a function to that.

Currectly its a issue that wont been fixed in near feature, and its a hell on Android really.

This is why im newer used them. its really dont give any mean at all on Android, since you dont have direct access and require some "hacking" to that.

The media files is also copied to the main document folde ron Android before access. Howover the file might get deleted before its try access. im can take a look here, because the deleting should not do that on shoebox files really, but stay it. here the deleting of tiles happens in the Java file too. "EDIT". Just checked, its should not do that really. So its can been a bug, but its much more compliced here. Android is here very strange.
5
Bug Reports / Re: SHOEBOX does not work on ANDROID
« Last post by adaz on Today at 03:19 pm »
Thanks spacefractal. The file exists, I already used DOESFILEEXISTS(), but LOADSPRITE still cannot access the sbx, or even doesn't try to access it, I don't know. All my levelpacks and graphics are based on this, so I'm very despondent if it really won't work on Android :-(

By the way, here is the _logview.bat's result when LOADSPRITE failed to load from the sbx:

Quote
02-19 15:31:48.309  5757  5757 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
02-19 15:31:48.310  5757  5757 F DEBUG   : Build fingerprint: 'HUAWEI/VTR-L29/HWVTR:7.0/HUAWEIVTR-L29/C432B151:user/release-keys'
02-19 15:31:48.310  5757  5757 F DEBUG   : Revision: '0'
02-19 15:31:48.310  5757  5757 F DEBUG   : ABI: 'arm'
02-19 15:31:48.310  5757  5757 F DEBUG   : pid: 5688, tid: 5728, name: SDLThread  >>> com.adaz.antirock <<<
02-19 15:31:48.310  5757  5757 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x7fffffff
02-19 15:31:48.310  5757  5757 F DEBUG   :     r0 ce17ea1f  r1 7fffffff  r2 80000000  r3 00000000
02-19 15:31:48.310  5757  5757 F DEBUG   :     r4 ce17ea54  r5 008000ff  r6 00000001  r7 00000000
02-19 15:31:48.310  5757  5757 F DEBUG   :     r8 00040a74  r9 00000000  sl 7fffffff  fp ce17ecfc
02-19 15:31:48.310  5757  5757 F DEBUG   :     ip 20000000  sp ce17e1b0  lr e51042e0  pc ee9c15cc  cpsr 80030010
02-19 15:31:48.311  5757  5757 F DEBUG   :
02-19 15:31:48.311  5757  5757 F DEBUG   : backtrace:
02-19 15:31:48.311  5757  5757 F DEBUG   :     #00 pc 000175cc  /system/lib/libc.so (memcpy+196)
02-19 15:31:48.311  5757  5757 F DEBUG   :     #01 pc 0009f2dc  /data/app/com.adaz.antirock-1/lib/arm/libmain.so (_ZN12OPENGL_IMAGE12LoadImageBMPEPKcm+340)
6
Spacefractal, YOU ARE A GENIUS!!! It's working!!! I cannot say how happy I am! This SDLActivity.java resolved this problem. I don't know what you did, but you did it!
So what did you do? :)
7
GLBasic - de / Re: Laufwerke
« Last post by D2O on Today at 09:06 am »


Gesendet von meinem HUAWEI RIO-L01 mit Tapatalk

8
Bug Reports / Re: SHOEBOX does not work on ANDROID
« Last post by spacefractal on Today at 08:44 am »
This is due file copy issue on Android. ALL files from the APK files require to been copy to the internal memory, before its can been used.

What you can try to do is do a DOESFILEEXISTS() before any file checking. That command make sure the file got extracted from the APK file to internal memory before uses.

Also a file copy from Android APK to internal is required for ALL files when used on Android. This is just a bit crappy design, but nothing im can do. So Shoebox can been fiffly on Android. Sorry about it.

So this is a issue im will not fix.
9
Im have in this morning removed all AndroidTV scaling code, so its dont interfere normal devices, actuelly forced 720p is only happens on Ouya and GameStick. Android 5 devices TV is normally quite much faster than Android 4 consoles anyway.

Im have updated the Android update thread in the top. here only the java file is requried update. Howover its wont fix the issue in the bottom about system buttons, as im wrote due system.

Howover im will not support the Immersive Android 4.4, you need to have the system buttons, which is also pretty normal way.

Make sure to make a proper use of the back button eventuelly.
10
This topic has been moved to Bug Reports.

http://www.glbasic.com/forum/index.php?topic=11136.0

This is really more a bug. so moved to there.
Pages: [1] 2 3 ... 10