FreeGameDev

MTres19 {l Wrote}:Actually on Windows everything should work except H.264 encoding. Sorry for the confusion, but the wiki has to cover all the platforms.

Thanks again, but it seems a bit complicated. I was looking for something simpler like a red "record" button.
My PC has a GT 730, but the NVIDIA Experience doesn't records Supertuxkart and I'm tired of the low fps rate of webinaria. I will look for an alternative.

Pressing Ctl+PrntScr on your keyboard should record without having to enable artist debug mode.

QwertyChouskie {l Wrote}:Pressing Ctl+PrntScr on your keyboard should record without having to enable artist debug mode.

I've tried and nothing happened.
I discovered two softwares (CamStudio and OBS Studio), so I will try to record using one of them.

Hi ¿did you fix the track crash bug?
this:
---------------------------
SuperTuxKart crashed :/
---------------------------
SuperTuxKart crashed!
Please hit Ctrl+C to copy to clipboard and signal the problem
to the developers on our forum: viewforum.php?f=16

Call stack:

RegisterProcTableCallback
RegisterProcTableCallback
RegisterProcTableCallback
RegisterProcTableCallback
RegisterProcTableCallback
RegisterProcTableCallback
RegisterProcTableCallback
asFreeMem
asFreeMem
asFreeMem
asFreeMem
asFreeMem
asFreeMem
asFreeMem
asFreeMem
BaseThreadInitThunk
RtlSubscribeWnfStateChangeNotification
RtlSubscribeWnfStateChangeNotification
---------------------------
Aceptar
---------------------------

Unfortunately it is hard to tell from just that. Your best bet is to install the new version and see for yourself.

deve {l Wrote}:

ace960 {l Wrote}:Thank you for the game and now also for the android release.

I can see that the android release requires android 4.4 (or above). Unfortunately, I have a device running android 4.3 without option to upgrade. I believe it is powerful enough to run SuperTuxCart. It is HP SlateBook 10 x2 PC, with Processor NVIDIA T40S 1.8-GHz processor (4-plus-1, quad), Chipset NVIDIA Tegra 4, ARM Cortex-A15 MPCore, 2 GB RAM, FullHD 10" display, detachable physical keyboard. We are primarily running the game on Windows PC. We would be happy if we can take it with us on our tablet pc.

Would it be please possible to install and run it on this 4.3 device? I would not complain if anything appears to be problematic.

Are you able to compile it yourself? Current version compiles fine for Android 4.3. You only need to change these lines in make.sh:

export NDK_PLATFORM_ARMV7=android-19
export SDK_VERSION_ARMV7=19

to

export NDK_PLATFORM_ARMV7=android-18
export SDK_VERSION_ARMV7=18

Or I can provide unofficial builds for android >= 4.0 after final release, because I need it for my phone anyway. Actually the modifications are available here if someone needs it: https://github.com/deveee/stk-code/tree/android-4.2

I can see that final 0.9.3 was released few days ago. I checked the provided github location and found newer apk there: https://github.com/deveee/stk-code/blob ... -api14.apk
I installed it on my older device (mentioned above) and here are the results:
1. The game indicates that my device/gpu does not meet gles 3.0. That is true as tegra 4 is gles 2.0 gpu.

2. There is missing some graphics in the game menu and in the the game too.

3. The performance is poor (evene on the lowest graphics details). To be honest, I expected a bit more based on the GPU specs (except no gles 3.0 support). FYI, I recently tested Doom 3 port on this device and it performed quite good (not expected).
4. The physical keyboard of the device works well so it can be controlled like on standard computer.

I am not complaining. I thank you for the effort. I just wanted to provide a feedback. I know that android 4.3 is really old. The device serves well. It's HP who do not support its product at all.

This apk is gles 2.0 only, because it was compiled for android >= 4.0 (api14). Gles 3.0 is available since api18. So it will always work with gles 2.0 renderer.

And the black images are because of npot textures. I see the same under emulator with gles 2.0. I think that there was a code in STK to solve the problem with npot textures, but currently there is no solution that is ready to use.

OK. Thank you for the explanation. I appreciate it.