beloko

Huh, this suggests the log is huge, does it work if you press it while on another engine? Try waiting for a bit longer while loads. I need to fix it so loads large logs in pieces.

Did you know about the 'View last log' button in the app? It should show you the full last log generated by the engine which may help?

Yeah I plan to add the other lightmodes back, they operate differently so I need to figure out how they work. I noticed the mirror issue actually, not sure what I broke but I think it basically tries to the draw the entire level seen from the mirror. I think it's something to do with the clipping planes I broke, not sure yet.

Yes that usually works, but then how will you connect to the pc at the same time? Bluetooth mouse should also work!

Mouse should work, but you need to connect it to your phone, is the moue still connected to the PC and the mouse data is going over the USB cable?

Oh great! Yes wait though, I'll make a branch with a couple of changes to use, otherwise the Pi will try to use GL3 context with some sort of emulator (that's what my Ri Pi 3 did anyway)

Thanks for the link! Very interesting to see the results when they come in and how the modification translates to PC platforms and if they help or make it worse. Actually I tried the build on a Raspberry Pi 3, definitely helped in a speed but still wasn't playable running at 15-20 FPS which long pauses when loading new shaders. May work on Raspberry Pi 4, I'll give it a try when I get one. Also did a few updates, interesting one is now 'Fixed color map' is working again, this fixes the black and white 'invulnerability' screen mode. It doesn't use a second pass, instead performs the color fragment operation in the main render pass - this mostly works but currently looks bad with transparent objects. New code is now in this branch: https://github.com/emileb/gzdoom/commits/master

I think it's possibly the updating of the vertex data which uses a very old method in the GLES2 code. There is a common extension to GLES2 to allow the use of glMapBuffer, I'll be adding that in as an option which might make a difference for larger maps.

(Full menu options) Display Options- > Hardware Renderer ->Sector Light mode: Change to something else, some of them are broken

If you pc is only 3yrs old and runs doom 2016 at 180 fps there is a good chance this won't help you out (and may be worse) , but just try and see what happens. I did an update which should fix the texture filtering modes, make sure you have downloaded the new 0.2 version. Let me know if it still doesn't work.

No need to apologise for anything. Will it be faster? Well I don't know, you just need to give it a try. There seems to be so many variables which effect it. If you don't have trouble with performance on Gzdoom just use that, it has more features and is gaureteed to work. If you have a really old GPU and low average frame rate is it possible the binary I posted may help.

Tnx. Yep don't use SW mode I have broken it (there is no point anyway as it won't be any difference even if it did work).

OK I have not touched the Vulkan engine so it will play exactly the same as before (except if I have broken it by accident). You need to run the binary I posted with OpenGL selected otherwise nothing will change! It still may not make much difference but you HAVE to select OpenGL mode if you wanna try it out :)

Appreciate the update! Are you saying you are using the binary I posted with Vulkan?