beloko

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.

Did you bind the extra gamepad buttons to the 'Custom X(GZ)' buttons first in the apps gamepad setup?

Nice! Might be worth feeding back your shader fix into Doom CE if you can, would be usfull for others. When in GLES mode it will load from shaders_gles, it fixes the path internally just before loading them so possibly the original path is printed out, is that why you thought it was loading from 'shaders'? Very soon, just fixing up last small issues this week. Retro is updated to latest v4.4.4

Humm should work, but that does sound like what would happen if it ran out of GFX mem. I just checked and it's taking 0.8GB RAM on my Note 20.

What device do you have? It might be running out of RAM, but the textures don't look that huge. How does it fail when you try and run it?

OK I got it working, I bought Doom 64 and ran the doom64-install.bat file to generate the files. Then copy DOOM64.CE.ipk3 and DOOM64.IWAD to the 'Delta' folder Then copy the other PK3 files to 'Delta/mods/D64/' Then select the PK3 in the correct order ( I got the order from running on the PC and looking at the console. Should be like this: Then select the IPK3 file to launch, should look something like this:

There are two ways to show the console: 1. Add the console button to touch screen buttons at the top, it is hidden my default. See the built-in tutorial about enabling hidden buttons (Press the green help icon to see tutorials) 2. Bring up the keyboard and hold down the 'Q' button (This is like pressing the tilde key on a keyboard)

It is due to Google stupid 'Scoped Storage' enforcement on Android 11. All access to files outside of the apps data storage location go through a shit load of code and IPC calls which has made opening files, or accessing the file system insanely slow (can be over 100ms to list a directory). Go to the apps 'Files' settings and enable 'Scoped storage' mode at the top right, then select your old "/OpenTouch/Delta" folder using the instructions shown in the app. I have put is LOTS of caching of the filesystem and cache and reuse file descriptors so it brings the speed back up, it won't as fast as before but will be a lot quicker than it is now.

Yes I've been meaning to add this but haven't had time. I started one here: https://github.com/emileb/ZandronumBrowser It reads and displays the servers from the master server but needs a load of work to get the UI up and interfaced to the app. I'll try and make some time to take a look again.

I could have a look.. Does that port purely add these new features? Will people who are not interested in the demo stuff be negatively affected do you think, or it will behave the same?

It changes the way some of the render data is handled. It might change performance up or down but will look the same.

Vulcan is not enabled in the app, I found it much slower than Opengl on mobile. Which GLES version are you running, 3.2 or 3.0?