TorcsDotNet WIP: Difference between revisions

From SpaceElevatorWiki.com
Jump to navigationJump to search
(New page: = TorcsDotNet WIP = The aim of the task is to build a C# core for Torcs. We were creating new C# plugins for a C++ engine, which had to communicate through layers of C# <-> C++ conversio...)
 
No edit summary
Line 1: Line 1:
= TorcsDotNet WIP =
== Aim ==


The aim of the task is to build a C# core for Torcs.
The aim of the task is to build a C# core for Torcs.
Line 16: Line 16:


Initialize OgreDotNet graphic plugins to display the track : WIP.
Initialize OgreDotNet graphic plugins to display the track : WIP.
Load cars / physics engine.


Decide whether we'd like to load C++ drivers or if we're happy with just sharpy's one.
Decide whether we'd like to load C++ drivers or if we're happy with just sharpy's one.


Load the driver, make it run a car.
Load a driver, make it run a car.


Make a GUI designed for our needs (load a track, evaluate drivers, run simulation in background, ...)
Make a GUI designed for our needs (load a track, evaluate drivers, run simulation in background, ...)

Revision as of 14:34, 4 December 2008

Aim

The aim of the task is to build a C# core for Torcs.

We were creating new C# plugins for a C++ engine, which had to communicate through layers of C# <-> C++ conversions.

I'd like to build a next generation core in C#. For fast development purpose, it first will be able to use current C++ plugins.

C# plugins will be used without the C++ interface, thus allowing to take full advantage of C# design.

Current core relies on plib and other oldness, let's remove all of this!

Plans

Load a complete track using C++ plugin : DONE.

Initialize OgreDotNet graphic plugins to display the track : WIP.

Load cars / physics engine.

Decide whether we'd like to load C++ drivers or if we're happy with just sharpy's one.

Load a driver, make it run a car.

Make a GUI designed for our needs (load a track, evaluate drivers, run simulation in background, ...)