

beloko
Members-
Content count
248 -
Joined
-
Last visited
About beloko
-
Rank
Junior Member
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
Oh yeah I forgot there is a bug, you need to put the iwads on the Primary location (Android/data/...). The problem is it uses relative paths to search for the iwad.
-
I got it working ages ago here, maybe instructions might still work: https://www.doomworld.com/forum/post/2427057
-
Which doom engine and version? Playing with mods? Usually tapping the screen should work. Have you modify any default key binds?
-
Select it to bind then press back button and it should clear
-
Are you playing with mods or vanilla Doom? Gzdoom 4.8?
-
Apart from the mobile change its the same, should have the same mod compatibility.
-
Any mods which include a .DLL file will not work unfortunately, they modify the gameplay with a library file which can not be used by Android. Mods need to be built in the app to work, I have not included Hard Corps yet as I need to make a new layout for it to be playable. What setting are you trying to change in-game? Instead use the app settings where you can change resolution also (that won't work in game) What phone is it?
-
The GLES 3.2 mode essentially is OpenGL mode, it has very little change from the original code. The problem is there is only GLES on Android (except Vulkan) and the driver on the device is the thing loading the shader, there is not anything you can do to fix this except fix the shader. You MIGHT be able to make something which automatically tried to fix simple shader issues but I think this would be very unreliable.
-
Ah ok thanks, I will look into this. It must be searching for the file only on the current workimg folder (which is the primary location)
-
Hi it's using this: https://github.com/emileb/gzdoom/tree/mobile_4.7 (Minus the Strife fix from last week) It it based on official 4.7.1 GZDoom, that text is wrong as I need to manually update it and often forget!
-
For the standard actions the touch input (and gamepad) inputs such as use, jump, attack etc don't use 'keyboard keys', they inject directly to the relevant game action. You should use the 'custom' touch or gamepad inputs, these map to standard keyboard key inputs which can then be bound in-game, or using the console to any actions you want. Let me know if you need any more info
-
Do you have a link to a music mod which doesn't work? Is this a new bug in the new release I just did or did it never work? Lastly does it work on Gzdoom 1.9.1?
-
It is probably because you have Swiftkey installed as your soft-keyboard? The keyboard you have active on your device will actually intercept the keys from the physical keyboard and modify them. Swiftkey modifies printable keys which means apps will not receive separate UP and DOWN events of the key, this is why they don't work for movement. Unfortunately the only way to fix it is not use Swiftkey, try enabling GBoard and then see if your keyboard works
-
They should run great on any new high end device like that.