Re: (no subject)
Bernhard Wymann <[email protected]>
| Newsgroups | gmane.games.torcs.general |
|---|---|
| Organization | wytec |
| Message-ID | <[email protected]> |
Hi There is just the robot tutorial, chapter 1 (www.berniw.org, follow the links). This might give you an insight (->what are the inputs/interpretation/ranges). Basically you do not need to worry about a lot of stuff in human.cpp, because loads of code there just handle various input sources. What hepls me when digging into unknown projects/sources is to just roughly map the big blocks and hold myself back in wasting time with trying to understand details which are not required for my task;-) This way even huge projects can start to look handy;-) Best regards Bernhard On 10/02/2013 08:42 AM, khushali modi wrote: > Hello Bernhard, > > We started reading code in human.cpp and client project, we are able to > navigate the code faster but still we are facing a lot of problems > understanding everything in the code. Can you provide a bit > documentation on these files which may guide us. > > Best Regards, > Khushali > > > On Tue, Oct 1, 2013 at 3:38 PM, khushali modi <[email protected] > <mailto:[email protected]>> wrote: > > ok.!! Thanx!! > > > On Tue, Oct 1, 2013 at 12:40 PM, Bernhard Wymann <[email protected] > <mailto:[email protected]>> wrote: > > Hi Khushali > > HID, just see here: > http://en.wikipedia.org/wiki/__Human_interface_device > <http://en.wikipedia.org/wiki/Human_interface_device> > Usually your USB mice, keyboard, joystick, gamepad, steering > wheel, etc. talk this way to your PC. > > It is not needed to be used, but it could make sense, because if > you change TORCS directly (which is perfectly possible) then > your work can used be only in TORCS, if you would implement it > as HID device, then you could use it potentially in any racing > or other game/experiment. > > I guess you can use the Emotiv API's directly for TORCS, but I > suggest a minute of thinking what architecture makes most sense: > 1. Build it directly into TORCS, you can only do experiments > from TORCS > 2. Build some device driver to make your input accessible to any > application without requirement for having the source code > (disadvantage, device drivers are operating system dependent) > > Best regards > > Bernhard > > > On 10/01/2013 04:39 AM, khushali modi wrote: > > Thanks Bernhard!! > Your response is quite effective that I got the Idea how I > can do this > task, but I don't know about the HID drivers. I am totally > new to it. > Can you tell me about it in some detail so that I can > understand it? And > why it is needed to be used? Can't the torcs take the inputs > without > "hid" driver implementation? Can't I use Emotiv API's to > give the input > to the torcs? > > > On Wed, Sep 25, 2013 at 2:02 PM, Bernhard Wymann > <[email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>>> wrote: > > Hi > > The most important thing is to use a development > environment which > can list/follow references and has a good debugger, I > use under > Windows (I guess you are under Windows because of the > "26" projects) > VS2008 with "Virtual Assist X" to navigate code faster, > maybe VS2010 > or later can do this equally good, I do not know. Under > Linux I use > usually an editor or IDE which supports "ctags" or a > similar technology. > > For your case I recommend the following: > - Read the TORCS FAQ, the researchers section > (ReOneStep), have a > look at the simulation timestep > - Have a look at the file human.cpp, this is the > "driver" which is > driven by user input. > - Have a look at the input setup, files are in > src/libs/confscreens, > I guess this is in the "client" project IIRC > - Build a debug version, set breakpoints and inspect > the callstack > - You can generate some documents under Linux with > "make doc", an > old version is available here: > http://www.berniw.org/aboutme/____publications/api.tar.bz2 > <http://www.berniw.org/aboutme/__publications/api.tar.bz2> > > > <http://www.berniw.org/__aboutme/publications/api.tar.__bz2 > <http://www.berniw.org/aboutme/publications/api.tar.bz2>> > > Your project sounds interesting, please post a link to > the result > then (if public available). > > Depending on your architecture you will not need to > modify TORCS at > all, e.g. you could consider writing a "hid" driver for > your input > device (you will need the Microsoft Driver Development > Kit/SDK, but > Universities have those things usually available), so > it would > appear to TORCS as any other input device, then you > could use your > interface as well for any sort of application (other > racing games, > jump and run, whatever...). > > Best regards > > Bernhard > > > On 09/25/2013 07:05 AM, khushali modi wrote: > > Hello All > > I am working in torcs for my final B.Tech Project. > I am using > the emotiv > neuroheadset to drive the car using our mind. > Actually, I need > to make > emotiv to be able to communicate with torcs. Emotiv > will send > the data > to torcs to drive the car. I need the > documentation of source > code to > understand all the 26 projects and to understand > how the torcs > works. I > am getting lost whenever I read the code to > understand it. Can you > suggest me how can I do it? > > > > ------------------------------____----------------------------__--__------------------ > > October Webinars: Code for Performance > Free Intel webinars can help you accelerate > application performance. > Explore tips for MPI, OpenMP, advanced profiling, > and more. Get > the most from > the latest Intel processors and coprocessors. See > abstracts and > register > > http://pubads.g.doubleclick.____net/gampad/clk?id=60133471&iu=____/4140/ostg.clktrk > > <http://pubads.g.doubleclick.__net/gampad/clk?id=60133471&iu=__/4140/ostg.clktrk > <http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk>> > > > > ___________________________________________________ > Torcs-users mailing list > [email protected].____net > <mailto:Torcs-users@lists.__sourceforge.net > <mailto:[email protected]>> > https://lists.sourceforge.net/____lists/listinfo/torcs-users > <https://lists.sourceforge.net/__lists/listinfo/torcs-users> > > > <https://lists.sourceforge.__net/lists/listinfo/torcs-users > <https://lists.sourceforge.net/lists/listinfo/torcs-users>__> > > > > > > -- > Khushali modi > B. Tech. 3rd Year CSE > IIT Mandi > > > ------------------------------__------------------------------__------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application > performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. > Get the most from > the latest Intel processors and coprocessors. See abstracts > and register > > http://pubads.g.doubleclick.__net/gampad/clk?id=60134791&iu=__/4140/ostg.clktrk > <http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk> > > > > > _________________________________________________ > Torcs-users mailing list > [email protected].__net > <mailto:[email protected]> > https://lists.sourceforge.net/__lists/listinfo/torcs-users > <https://lists.sourceforge.net/lists/listinfo/torcs-users> > > > > > > -- > Khushali modi > B. Tech. 3rd Year CSE > IIT Mandi > > > > > -- > Khushali modi > B. Tech. 3rd Year CSE > IIT Mandi ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk