torcs-users Mailing List for TORCS - The Open Racing Car Simulator

Bernhard Wymann wrote:
> Hi All
> 
>> The in-game function for making screen shots by pressing F12 doesn't 
>> work. I use torcs 1.2.2 in Windows XP. I only get a small blue png 
>> file with the right resolution.
>> In the old 1.2.1 release it was possible to make screen shots only in 16
> 
> 
> Interesting, so you are sure that 24 and 32 bpp did not work? Was your 
> screen at 16bpp?

Here are some detailed results:
Desktop bpp  torcs bpp  Fullscreen/Windowed  Screenshot-Function
16           32         FS                   OK
32           24,32      FS                   blue picture
32           16,24,32   W                    OK

Other modes are not playable here.
> 
>> bpp mode. This mode is not playable in the new version.
>> It's still possible to make screen shots with Print key, but it is not 
> 
> 
> Does the in game track map and the rear mirror work under these 
> conditions (from your former bug report I guess yes)? Is your Windows 
> desktop setting 16 bpp? If you run TORCS in a window instead of 
> fullscreen, does the capturing work then?

The in game track map and the mirror are working.


bye, Eugen

Hi All

> The in-game function for making screen shots by pressing F12 doesn't 
> work. I use torcs 1.2.2 in Windows XP. I only get a small blue png file 
> with the right resolution.
> In the old 1.2.1 release it was possible to make screen shots only in 16

Interesting, so you are sure that 24 and 32 bpp did not work? Was your 
screen at 16bpp?

> bpp mode. This mode is not playable in the new version.
> It's still possible to make screen shots with Print key, but it is not 

Does the in game track map and the rear mirror work under these 
conditions (from your former bug report I guess yes)? Is your Windows 
desktop setting 16 bpp? If you run TORCS in a window instead of 
fullscreen, does the capturing work then?

Loud thinking:

I suspect that glReadPixels has a problem with the front buffer. 
Reasoning: Very similar techniques are used to create the track map and 
the rear mirror view, the main difference is that the screenshot and 
movie capturing use the frontbuffer instead of the backbuffer.

I also suspect there is a connection to the weird colors and slow 
operation of 1.2.2 in 16bpp @ 16bpp display. If you look at the colors 
it seems like the red component has gone, like somthing has cut down the 
24 or 32 bit to 16 bit instead of converting it to 16bpp (565 rgb or 
5551 rgba). Is is possible that the automatic OpenGL format conversion 
is somehow messed up through the new initialization? But it seems to be 
broken in a different way on 1.2.1.

The difference between the backbuffer and frontbuffer might be that the 
backbuffer is stored in the "real" format (e. g. 24 bit RGB), while the 
frontbuffer sits on the 16bpp framebuffer and needs conversion on write 
and read.

/Loud thinking.

bye, Bernhard.

-- 

visit my homepage http://www.berniw.org

Hi Eugen

> PS: The new FAQ (well done) says, problems should be reported here, so i 
> did. Don't you use Sourceforge bug section anymore?

If you are SURE you have found a bug it is perfect to report it in the 
bugtracker (your previous reports are good!), but some users filed 
"bugs" which were not bugs but installation problems, I wanted to 
prevent that. The "real bugs" are welcome in the bugtracker, the 
exterminator is waiting...;-)

bye, thank you for the reports,

Bernhard.

-- 

visit my homepage http://www.berniw.org

Hi all!

The in-game function for making screen shots by pressing F12 doesn't 
work. I use torcs 1.2.2 in Windows XP. I only get a small blue png file 
with the right resolution.
In the old 1.2.1 release it was possible to make screen shots only in 16 
bpp mode. This mode is not playable in the new version.
It's still possible to make screen shots with Print key, but it is not 
very comfortable.

Thanks for this great game.

Eugen

PS: The new FAQ (well done) says, problems should be reported here, so i 
did. Don't you use Sourceforge bug section anymore?

Am Donnerstag, 26. Februar 2004 22:53 schrieb Eric Anderson:

> Could be using the nvidia version of the glx module for Xfree86,
> which breaks GLX on a radeon card.  Remove all old nvidia related GLX
> modules, and find the radeon ones..
>
> That's all I know..

I found it. In /usr/include/GL/ gl.h and glx.h still pointed to the no 
more existing NVIDIA versions in /usr/doc/NVIDIA.foo
Luckily there still were gl.h.old and glx.h.old, which I simply renamed. 
Then the compilation went fine.

Thanks to you all!

Cheerz Lars

Hi all

Eric Espie wrote:
> As I'm not a "radeon specialist" I forward this problem to
> the torcs-users mailing list with the initial mail too,
> I hope that someone can solve your problem.
> 
> Lars Behrens wrote:
> 
>>> Am Donnerstag, 26. Februar 2004 21:25 schrieb Eric Espie:
>>> Hi Lars,
>>>
>>> Your problem is not glut, but OpenGL itself...
>>>
>>>
>>> Lars Behrens wrote:
>>>
>>> Hi Eric,
>>>
>>> just wanted to install Torcs on Slackware 9.1, but the compilation 
>>> stopped with
>>>
>>>  "configure: error: Can't find GL/glut.h"
>>>
>>> although I have glut-3.7-i486-1 installed:
>>>
>>> -----------------------------------------------------------------------
>>> bash-2.05b# ls -l /usr/include/GL/glut.h -rw-r--r--  1 root  root  
>>> 20844 1998-08-08 02:18 /usr/include/GL/glut.h
>>> -----------------------------------------------------------------------
>>>
>>> I have attached config.log.
>>>
>>> Cheerz Lars
>>>
>>> In file included from 
>>> /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/include/GL/glut.h:70,
>>>                  from configure:2069:
>>> /usr/include/GL/glu.h:35:19: GL/gl.h: No such file or directory
>>>
>>> You have to install the includes for OpenGL too. and be careful that 
>>> your glut.h in:
>>> /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/include/GL/glut.h
>>> is not in conflict with the one in:
>>> /usr/include/GL/glut.h
>>> just in case...

I agree. What is a bit funny is the path of your glut.h, are there also 
the other headerfiles, like gl.h, glu.h, etc.?

>> Thaks for your quick response!
>> Phew, this goes a bit over my horizon... Don't know how this happened. 
>> I switched from NVIDIA to Radeon recently, maybe that's the reason 
>> why. How do I fix that? Maybe you can help me?

I don't know how Slackware is packaged, but if you download a stock 
nvidia driver, then you get also OpenGL header files. If the Slackware 
people install them with the driver, they get also uninstalled with the 
driver, so it is possible that you have lost your header files with a 
driver change. Now you need probably (I'm just gessing!) to install 
something like XFree86-devel or glx-devel.

In case you face after that a runtime problem with GLU, have a look at 
this here:

http://sourceforge.net/tracker/index.php?func=detail&aid=870201&group_id=3777&atid=103777


bye, Bernhard.


-- 

visit my homepage http://www.berniw.org

Could be using the nvidia version of the glx module for Xfree86, which 
breaks GLX on a radeon card.  Remove all old nvidia related GLX modules, 
and find the radeon ones..

That's all I know..



Eric Espie wrote:
> As I'm not a "radeon specialist" I forward this problem to
> the torcs-users mailing list with the initial mail too,
> I hope that someone can solve your problem.
> 
> Lars Behrens wrote:
> 
>>> Am Donnerstag, 26. Februar 2004 21:25 schrieb Eric Espie:
>>> Hi Lars,
>>>
>>> Your problem is not glut, but OpenGL itself...
>>>
>>>
>>> Lars Behrens wrote:
>>>
>>> Hi Eric,
>>>
>>> just wanted to install Torcs on Slackware 9.1, but the compilation 
>>> stopped with
>>>
>>>  "configure: error: Can't find GL/glut.h"
>>>
>>> although I have glut-3.7-i486-1 installed:
>>>
>>> -----------------------------------------------------------------------
>>> bash-2.05b# ls -l /usr/include/GL/glut.h -rw-r--r--  1 root  root  
>>> 20844 1998-08-08 02:18 /usr/include/GL/glut.h
>>> -----------------------------------------------------------------------
>>>
>>> I have attached config.log.
>>>
>>> Cheerz Lars
>>>
>>> In file included from 
>>> /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/include/GL/glut.h:70,
>>>                  from configure:2069:
>>> /usr/include/GL/glu.h:35:19: GL/gl.h: No such file or directory
>>>
>>> You have to install the includes for OpenGL too. and be careful that 
>>> your glut.h in:
>>> /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/include/GL/glut.h
>>> is not in conflict with the one in:
>>> /usr/include/GL/glut.h
>>> just in case...
>>
>>
>> Thaks for your quick response!
>> Phew, this goes a bit over my horizon... Don't know how this happened. 
>> I switched from NVIDIA to Radeon recently, maybe that's the reason 
>> why. How do I fix that? Maybe you can help me?
>>
>> TIA
>>
>> Cheerz Lars
>>
>>
>>
>>
> 
> Eric.


-- 
------------------------------------------------------------------
Eric Anderson     Sr. Systems Administrator    Centaur Technology
Today is the tomorrow you worried about yesterday.
------------------------------------------------------------------

As I'm not a "radeon specialist" I forward this problem to
the torcs-users mailing list with the initial mail too,
I hope that someone can solve your problem.

Lars Behrens wrote:
>> Am Donnerstag, 26. Februar 2004 21:25 schrieb Eric Espie:
>> Hi Lars,
>> 
>> Your problem is not glut, but OpenGL itself...
>> 
>> 
>> Lars Behrens wrote:
>> 
>> Hi Eric,
>>
>> just wanted to install Torcs on Slackware 9.1, but the compilation stopped with
>>
>>  "configure: error: Can't find GL/glut.h"
>>
>> although I have glut-3.7-i486-1 installed:
>>
>> -----------------------------------------------------------------------
>> bash-2.05b# ls -l /usr/include/GL/glut.h -rw-r--r--  1 root  root  20844 1998-08-08 02:18 /usr/include/GL/glut.h
>> -----------------------------------------------------------------------
>>
>> I have attached config.log.
>>
>> Cheerz Lars
>>
>> In file included from /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/include/GL/glut.h:70,
>>                  from configure:2069:
>> /usr/include/GL/glu.h:35:19: GL/gl.h: No such file or directory
>>
>> You have to install the includes for OpenGL too. 
>> and be careful 
>> that your glut.h in:
>> /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/include/GL/glut.h
>> is not in conflict with the one in:
>> /usr/include/GL/glut.h
>> just in case...
> 
> Thaks for your quick response! 
> 
> Phew, this goes a bit over my horizon... Don't know how this happened. I 
> switched from NVIDIA to Radeon recently, maybe that's the reason why. 
> How do I fix that? Maybe you can help me?
> 
> TIA
> 
> Cheerz Lars
> 
> 
> 
> 

Eric.
-- 
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
                        TORCS
             The Open Racing Car Simulator
         AKA The Other Release Coming Soon (Skin'r)
                  http://torcs.org
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=

-- 

visit my homepage http://www.berniw.org

the previous torcs and even cvs used to work great, but now I have:

Visual Properties Report
------------------------
The minimum display requirements are not fulfilled.
We need a double buffered RGBA visual with a 16 bit depth buffer atleast.
GLUT: Fatal Error in torcs-bin: visual with necessary capabilities notfound.


when I start torcs.. :-(

I'm with 16 bits and other OpenGL games work fine.

Any hints? :\


Ps.: Please CC me

Am Freitag, 20. Februar 2004 23:18 schrieb be...@bl...:
> Hi Dirk
>
> >After download, compile and install the start of torcs 1.2.2
> >
> >fails:
> >> torcs
> >
> >/root/.torcs created, copying/linking game data
> >/usr/lib/torcs/torcs-bin: relocation
> >error: /usr/lib/torcs/lib/libtgfclient.so: undefined symbol:
> >_Z15GfParmWriteFilePKcPvPc
>
> Seems like the symbol has not been exported, weird. Did the compilation run
> without errors (make >& error.log, then look up in error.log). Which
> operating system, compiler and hardware do you use? Do you have an old
> TORCS version lurking around?
>
> bye, Bernhard.

I found some old libs in /usr/local/lib.

After deleting them everything works.

Dirk

-- 

visit my homepage http://www.berniw.org

Hi Bernhard

>    I tried the new version of TORCS on a older 500 MHz machine and besides a
> problem with some plib applications(TORCS also) and my sound card when using
> ALSA as driver(which doesn't occur if I use the OSS driver) on Kernel 2.6,

Marks problem was a mix up of several alsa components versions, I think, 
finally he could resolve it.

> Most tracks worked fine, but the Road Tracks CG 2 and CG3 had problems with
> background flipping in the front, the car possibly jumping below the street,
> - it was possible to drive these but not very nice. Looked like the depth
> buffer handling in the driver could be buggy somehow(But TORCS is the only
> application which shows an error so far).
> 
> The bug disappeared when I started torcs with the options -s and -m
> together, one of the two options alone didn't suffice.
> 
> Bernhard
> 
> PS: Sorry that I don't have more detail right now, I'll get some glxinfo -l
> when I'm back at this machine.

This will be interesting.

> PPS: It could be nice to have a 'easy' mode for graphics drivers(as an option)
> by default and allow people with better cards/drivers to turn on multitexturing 
> and the other option in the Display config menu where you can change the screen
> size and window/fullscreen, there torcs gets restarted anyway.

bye, Bernhard.

Offtopic: How can I fix (SuSE 8.2, kernel 2.6.3) the problem of wrong 
reported failing services at startup (startproc/rc.status problem?, 
somebody suggested to insert a sleep 0.2 in the init scripts).

-- 

visit my homepage http://www.berniw.org

Hi Jonepet

> OpenGL renderer string: Mesa DRI Intel(R) 852GM/855GM 20021115
> OpenGL version string: 1.2 Mesa 4.0.4

Ok, you use an old Mesa/DRI version, you should upgrade. Those was 
reported to work (altough with an R7200):

OpenGL renderer string: Mesa DRI Radeon 20030328 AGP 1x 
x86/MMX+/3DNow!+/SSE TCL
OpenGL version string: 1.2 Mesa 5.0.1

>   visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
> id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
> ----------------------------------------------------------------------
> 0x22 16 tc  1 16  0 r  y  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
> 0x23 16 tc  1 16  0 r  .  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
> 0x24 16 tc  1 16  0 r  y  .  5  6  5  0  0 16  8  0  0  0  0  0 0 Slow
> 0x25 16 tc  1 16  0 r  .  .  5  6  5  0  0 16  8  0  0  0  0  0 0 Slow
> 0x26 16 tc  1 16  0 r  y  .  5  6  5  0  0 16  0 16 16 16 16  0 0 Slow
> 0x27 16 tc  1 16  0 r  .  .  5  6  5  0  0 16  0 16 16 16 16  0 0 Slow
> 0x28 16 tc  1 16  0 r  y  .  5  6  5  0  0 16  8 16 16 16 16  0 0 Slow
> 0x29 16 tc  1 16  0 r  .  .  5  6  5  0  0 16  8 16 16 16 16  0 0 Slow

I think the TORCS code is right, but either your driver or glut lies 
about the capabilities of the graphics board (e. g. 0x22 should work). 
As a temporary workaround you can replace your screen.cpp and recompile 
and reinstall torcs.

You should:
- switch to 24 bpp -> report if that succeeds.
- upgrade your DRI/Mesa to a recent version -> report if that succeeds.
- try an alternate glut (freeglut) -> report if that succeeds.
- as last resort you can try an alternate src/libs/tgfclient/screen.cpp 
(replace the file, recompile and reinstall torcs), have also a look at 
the g550 thread.

bye, Bernhard.

-- 

visit my homepage http://www.berniw.org

-- 

visit my homepage http://www.berniw.org

Hi all,

   I tried the new version of TORCS on a older 500 MHz machine and besides a
problem with some plib applications(TORCS also) and my sound card when using
ALSA as driver(which doesn't occur if I use the OSS driver) on Kernel 2.6,
I also had problems with the ATI FireGL driver(latest XFree86.org driver):

(guess trying OSS could also help Mark Baas with his plib problem, a
 possible suspiction could be an interrupt/ACPI issue with the ALSA driver, I
 will test a different sound card eventually, it's some CS4248 or so there now)

Most tracks worked fine, but the Road Tracks CG 2 and CG3 had problems with
background flipping in the front, the car possibly jumping below the street,
- it was possible to drive these but not very nice. Looked like the depth
buffer handling in the driver could be buggy somehow(But TORCS is the only
application which shows an error so far).

The bug disappeared when I started torcs with the options -s and -m
together, one of the two options alone didn't suffice.

Bernhard

PS: Sorry that I don't have more detail right now, I'll get some glxinfo -l
when I'm back at this machine.

PPS: It could be nice to have a 'easy' mode for graphics drivers(as an option)
by default and allow people with better cards/drivers to turn on multitexturing 
and the other option in the Display config menu where you can change the screen
size and window/fullscreen, there torcs gets restarted anyway.

Bernhard Wymann wrote:

> Hi
>
>> [jonepet@localhost jonepet]$ torcs
>> Visual Properties Report
>> ------------------------
>> The minimum display requirements are not fulfilled.
>> We need a double buffered RGBA visual with a 16 bit depth buffer at 
>> least.
>> GLUT: Fatal Error in torcs-bin: visual with necessary capabilities not
>> found.
>>
>> My video-card:
>> Intel 82852/855GM using i810 driver.
>>
>> [jonepet@localhost jonepet]$ uname -a
>> Linux localhost.localdomain 2.6.3 #10 Mon Feb 23 10:19:27 CET 2004 i686
>> i686 i386 GNU/Linux
>
>
> Could you please post the output of "glxinfo -l" and XFree86.0.log? 
> You should also try to start TORCS with -s, and you could try 
> different color depths. What is also very important that you use a 
> recent DRI/OpenGL driver.
>
> bye, Bernhard.
>
[jonepet@localhost jonepet]$ glxinfo -l
name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
client glx vendor string: SGI
client glx version string: 1.2
client glx extensions:
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
GLX extensions:
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
OpenGL vendor string: Tungsten Graphics, Inc
OpenGL renderer string: Mesa DRI Intel(R) 852GM/855GM 20021115
OpenGL version string: 1.2 Mesa 4.0.4
OpenGL extensions:
    GL_ARB_imaging, GL_ARB_multitexture, GL_ARB_texture_env_add,
    GL_ARB_texture_env_combine, GL_ARB_transpose_matrix, GL_EXT_abgr,
    GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_func_separate,
    GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_clip_volume_hint,
    GL_EXT_convolution, GL_EXT_compiled_vertex_array, GL_EXT_fog_coord,
    GL_EXT_histogram, GL_EXT_packed_pixels, GL_EXT_polygon_offset,
    GL_EXT_rescale_normal, GL_EXT_secondary_color, GL_EXT_texture3D,
    GL_EXT_texture_env_add, GL_EXT_texture_env_combine, 
GL_EXT_texture_object,
    GL_EXT_texture_lod_bias, GL_EXT_vertex_array, GL_IBM_rasterpos_clip,
    GL_MESA_window_pos, GL_NV_texgen_reflection, GL_SGI_color_matrix,
    GL_SGI_color_table
OpenGL limits:
    GL_MAX_ATTRIB_STACK_DEPTH = 16
    GL_MAX_CLIENT_ATTRIB_STACK_DEPTH = 16
    GL_MAX_CLIP_PLANES = 6
    GL_MAX_COLOR_MATRIX_STACK_DEPTH = 4
    GL_MAX_ELEMENTS_VERTICES = 3000
    GL_MAX_ELEMENTS_INDICES = 3000
    GL_MAX_EVAL_ORDER = 30
    GL_MAX_LIGHTS = 8
    GL_MAX_LIST_NESTING = 64
    GL_MAX_MODELVIEW_STACK_DEPTH = 32
    GL_MAX_NAME_STACK_DEPTH = 64
    GL_MAX_PIXEL_MAP_TABLE = 256
    GL_MAX_PROJECTION_STACK_DEPTH = 32
    GL_MAX_TEXTURE_STACK_DEPTH = 10
    GL_MAX_TEXTURE_SIZE = 1024
    GL_MAX_3D_TEXTURE_SIZE = 128
    GL_MAX_TEXTURE_UNITS_ARB = 2
    GL_MAX_TEXTURE_LOD_BIAS_EXT = 4
    GL_MAX_VIEWPORT_DIMS = 2048, 2048
    GL_ALIASED_LINE_WIDTH_RANGE = 1, 3
    GL_SMOOTH_LINE_WIDTH_RANGE = 1, 3
    GL_ALIASED_POINT_SIZE_RANGE = 1, 255
    GL_SMOOTH_POINT_SIZE_RANGE = 1, 3
glu version: 1.3
glu extensions:
    GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess

   visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
 id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
----------------------------------------------------------------------
0x22 16 tc  1 16  0 r  y  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x23 16 tc  1 16  0 r  .  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x24 16 tc  1 16  0 r  y  .  5  6  5  0  0 16  8  0  0  0  0  0 0 Slow
0x25 16 tc  1 16  0 r  .  .  5  6  5  0  0 16  8  0  0  0  0  0 0 Slow
0x26 16 tc  1 16  0 r  y  .  5  6  5  0  0 16  0 16 16 16 16  0 0 Slow
0x27 16 tc  1 16  0 r  .  .  5  6  5  0  0 16  0 16 16 16 16  0 0 Slow
0x28 16 tc  1 16  0 r  y  .  5  6  5  0  0 16  8 16 16 16 16  0 0 Slow
0x29 16 tc  1 16  0 r  .  .  5  6  5  0  0 16  8 16 16 16 16  0 0 Slow

XFree86.0.log is _huge_.
-s made the same error.

Jozef Riha wrote:
> hello,
> 
> would it be possible to make individual sound-set for each car? there 
> are plenty of them included within zipped car models intended to be used 
> w/ racer (www.racer.nl). i wonder if they can be extracted and bundled 
> w/ torcs (license?) and/or if it is possible to convert car models racer 
> uses to torcs.

I don't follow the racer's life very much ;-) but the models file format
seems proprietary.
The sound samples license is problematic because it is generaly
not clearly indicated. The best would be to find someone able to generate
samples...

> 
> thank you.
> 
> cheers,
> 
> -- joe
> 

Eric.
-- 
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
                        TORCS
             The Open Racing Car Simulator
         AKA The Other Release Coming Soon (Skin'r)
                  http://torcs.org
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=

Hi

> [jonepet@localhost jonepet]$ torcs
> Visual Properties Report
> ------------------------
> The minimum display requirements are not fulfilled.
> We need a double buffered RGBA visual with a 16 bit depth buffer at least.
> GLUT: Fatal Error in torcs-bin: visual with necessary capabilities not
> found.
> 
> My video-card:
> Intel 82852/855GM using i810 driver.
> 
> [jonepet@localhost jonepet]$ uname -a
> Linux localhost.localdomain 2.6.3 #10 Mon Feb 23 10:19:27 CET 2004 i686
> i686 i386 GNU/Linux

Could you please post the output of "glxinfo -l" and XFree86.0.log? You 
should also try to start TORCS with -s, and you could try different 
color depths. What is also very important that you use a recent 
DRI/OpenGL driver.

bye, Bernhard.

-- 

visit my homepage http://www.berniw.org

[jonepet@localhost jonepet]$ torcs
Visual Properties Report
------------------------
The minimum display requirements are not fulfilled.
We need a double buffered RGBA visual with a 16 bit depth buffer at least=
.
GLUT: Fatal Error in torcs-bin: visual with necessary capabilities not
found.

My video-card:
Intel 82852/855GM using i810 driver.

[jonepet@localhost jonepet]$ uname -a
Linux localhost.localdomain 2.6.3 #10 Mon Feb 23 10:19:27 CET 2004 i686
i686 i386 GNU/Linux

hello,

would it be possible to make individual sound-set for each car? there are plenty of them included within zipped car models 
intended to be used w/ racer (www.racer.nl). i wonder if they can be extracted and bundled w/ torcs (license?) and/or if it 
is possible to convert car models racer uses to torcs.

thank you.

cheers,

-- joe



________ Information from NOD32 ________
This message was checked by NOD32 Antivirus System for Linux Mail Server.
http://www.nod32.com

 
> I'm currently updating the user's manual.
> The way to configure the controls is to go to the
> "player's config" menu, you select a player then you
> go to the "controls" screen configuration.
> Then, click on the "left arrow" text facing the "steer left"
> and turn you wheel or joystick to the left or move the mouse
> to the left if you want to use the mouse to steer.
> 
> After, that you'll have to calibrate the joystick.

That did the trick :) Many thanks.
Now I'll be busy playing so hopefully I 
won't need to bother you for a while. Yipee.

__________________________________
Do you Yahoo!?
Yahoo! Mail SpamGuard - Read only the mail you want.
http://antispam.yahoo.com/tools

Amartyo Banerjee wrote:
> I built and installed both torcs 1.2.2 and the latest cvs checkout, 
> but in neither case is my joystick recognized or any screens shown to
> configure or use the joystick. 
> The 'js_demo' program which is part of the 'plib' example programs recognizes
> my joystick correctly.
> The 'jstest' and 'jscal' programs also recognize my joystick (Logitech Wingman Extreme Digital
> 3D).
> Any help with getting torcs to recognize my joystick would be greatly appreciated. :)
> One possible cause may be that the 'configure' script, both version 1.2.2 and in cvs, 
> does not check for 'libplibjs', although it does check for the other plib libraries. 
> Nor is there any flag in the makefiles containing '-lplibjs'. 
> I have created 2 tarballs containing the output on the terminal of  
> './configure, make and make install' and of  the command 'torcs', 
> for the latest stable version (1.2.2) and the cvs version respectively.
> The first tarball also contains the configuration screens shown by torcs.
> These screens are identical for me in both versions.
> The tarballs are about 350Kb and 19Kb in size. Please let me know if it 
> would be useful in helping to solve my problem and where is the appropriate 
> place to post it. Unfortunately I don't have web space available.
> Thanks
> 

I'm currently updating the user's manual.
The way to configure the controls is to go to the
"player's config" menu, you select a player then you
go to the "controls" screen configuration.
Then, click on the "left arrow" text facing the "steer left"
and turn you wheel or joystick to the left or move the mouse
to the left if you want to use the mouse to steer.

After, that you'll have to calibrate the joystick.

I hope that'll help,
Eric.
-- 
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
                        TORCS
             The Open Racing Car Simulator
         AKA The Other Release Coming Soon (Skin'r)
                  http://torcs.org
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=

I built and installed both torcs 1.2.2 and the latest cvs checkout, 
but in neither case is my joystick recognized or any screens shown to
configure or use the joystick. 
The 'js_demo' program which is part of the 'plib' example programs recognizes
my joystick correctly.
The 'jstest' and 'jscal' programs also recognize my joystick (Logitech Wingman Extreme Digital
3D).
Any help with getting torcs to recognize my joystick would be greatly appreciated. :)
One possible cause may be that the 'configure' script, both version 1.2.2 and in cvs, 
does not check for 'libplibjs', although it does check for the other plib libraries. 
Nor is there any flag in the makefiles containing '-lplibjs'. 
I have created 2 tarballs containing the output on the terminal of  
'./configure, make and make install' and of  the command 'torcs', 
for the latest stable version (1.2.2) and the cvs version respectively.
The first tarball also contains the configuration screens shown by torcs.
These screens are identical for me in both versions.
The tarballs are about 350Kb and 19Kb in size. Please let me know if it 
would be useful in helping to solve my problem and where is the appropriate 
place to post it. Unfortunately I don't have web space available.
Thanks



__________________________________
Do you Yahoo!?
Yahoo! Mail SpamGuard - Read only the mail you want.
http://antispam.yahoo.com/tools

Hi Mitchell

>I see that there is a Windows executable, but what about being able to
>compile a new robot, and then test it against other robots.  Can a
>Windows user do that?

Yes, of course (but you need vc++ 6.0). There is simply no specific tutorial
for that available. The easiest way to start with windows is the following:
- Download the TORCS source and manage to compile and run it.
- Download e. g. the bt robot package, it is a little enhanced version of
the robot developed in the tutorial, so there is good documentation available
to understand it.
- Copy the sources into a new directory, e. g. when you choose the name "myrobot"
create a directory /src/drivers/myrobot.
- Copy all the bt files into the myrobot directory.
- Now rename all "bt*" files into myrobot*.
- Edit myrobot.def and also change all bt strings into myrobot.
- The same for myrobot.dsp, .xml, perhaps more, you get the idea.
- Change the "bt" module entry point in myrobot.cpp to myrobot, also make
the strings for the robots names and description match with those in myrobot.xml.
- Add the myrobot project to TORCS, open the project with vc++ and try to
compile it.
- If you want to deploy the files you have to do that manually, create a
directory in "runtime" where the other robots are and copy the required files
there (myrobot.dll, .xml, setup subdirectories etc.).
- Now TORCS should pick up you robot. 

>Is this the right place to ask, or should I use a forum?

Yes, IMHO this is the right place. The forums are not read really frequently,
so it can last quite long till sombody answers. 

bye, Bernhard.