TORCS getting closed when try to run default car

[Mario Alberto Alvarado Galindo]

I'm getting TORCS closed by it self when I execute the command "python torcs_jm_par.py" to run a car, here are the steeps followed:

• Installed python 3.14
• Click Race
• Click Quick Race
• Click Configure Race
• Selected track
• Selected driver (scr_server 1)
• Selected laps (3)
• Click New Race
• Execute in other terminal -> python torcs_jm_par.py

Get the message "start invalid enumerant" and get TORCS closed

I'm using Windows Server 2019

Logs messages:
Waiting for request on port 3001
!identified
initCars: start invalid enumerant
loadCars: start invalid enumerant
Load: grLoadPngTexture start invalid enumerant
loadcar: end invalid enumerant
loadcar: start invalid enumerant
loadcar: end invalid enumerant
loadcar: start invalid enumerant
loadcar: end invalid enumerant
Disabling Sound: OpenAL initialisation failed: Could not open device
refresh: start invalid enumerant

[Bernhard Wymann]

Ah, this got forwarded to me, I answered by mail, here part of my reply:

So for whatever reason OpenGL reports the errors "invalid value", after that "invalid enumerant", which must be happened at some point beforehand (OpenGL 1.x has internal state). I have never seen this, but if I had to guess:

If you look at the other robots, the texture format is the SGI RGB format (with alpha channel), so maybe png does not work for robots, because it was not done before
Maybe it would work, but there is something wrong with the PNG (e.g. dimensions not a power of 2, no alpha channel, whatever)
Does SCR allow to sumbit on initialization a texture via network, maybe there yould something go wrong too

Steps to analyse:

Just run a non scr bot like a berniw, do you see the message too (Expectation -> no)
Now take the same robot, but convert the texture to PNG with an alpha channel, delete the rgb texture, and place the png one in the robots directory instead
    Does it still get picked up
    Do you see the same error ->
        if yes, TORCS does somehow not support png textures for robots yet, at least in your version
            workaround -> convert your png to the SGI RGB format with alpha Channel (e.g. with GIMP), use SGI RGB textures for robots
        if everything is still fine it must be the texture itself somehow
            Place the texture which causes this into the berniw robot (with proper naming etc.), see if you get the same error
                If yes -> it is something wrong with the texture itself, check dimensions (power of 2) and that it has all Channels (RGBA)
                If no -> the submission of the texture in the SCR-Patch must screw up something