Engine agnostic interface for communication between game engines and simulations systems

1. A method for communicating between a simulator and a game engine, the method comprising steps of:

providing an agnostic interface mechanism coupled between the simulator and the game engine;

receiving a first simulator specific object from the simulator via a specific protocol of the simulator;

translating the first simulator specific object into a first interface object;

translating the first interface object into a game specific object and to transmit the first game specific object to the game engine; and

providing a core control coupled for controlling the communication of objects between the simulator and the game engine;

wherein the agnostic interface mechanism provides the first game specific object to the game engine through a direct application programming interface (API) call;

generating a second game specific object at the game engine;

translating the second game specific object generated by the game engine into a second interface object;

translating the second interface object into a second simulator specific object in accordance with the simulator specific protocol; and

providing the second simulator specific object to the simulator;

wherein the first game specific object, the first interface object and the first simulator specific objects are corresponding data objects; and

wherein the second game specific object, the second interface object and the second simulator specific objects are corresponding data objects;

generating a third interface object in the core control; translating the third interface object into a third game specific object; and transmitting the third game specific object to the game engine; wherein the second game specific object is a control object.

2. The system recited in claim 1 , wherein the core control generates the third interface object to manage multiple instances of the game engine.

3. The system recited in claim 1 , wherein the third interface object is selected from the following group of control objects: creating the game engine, starting the game engine, stopping the game engine or destroying the game engine.

4. A communication system, the system comprising:

a computer;

a simulator;

a game engine; and

an agnostic interface mechanism coupled between the simulator and the game engine, the agnostic interface mechanism comprising:

a first interface configured to receive a first simulator specific object from the simulator via a specific protocol of the simulator and to translate the first simulator specific object into a first interface object;

a second interface configured to translate the first interface object into a game specific object and to transmit the first game specific object to the game engine; and

a core control coupled between the first interface and the second interface for controlling the communication of objects between the simulator and the game engine; wherein the core control through the second interface provides the first game specific object to the game engine through a direct application programming interface (API) call;

wherein the second interface is configured to translate a second game specific object generated by the game engine into a second interface object, and wherein the first interface is configured to translate the second interface object into a second simulator specific object in accordance with the simulator specific protocol and to provide the second simulator specific object to the simulator;

wherein the first game specific object, the first interface object and the first simulator specific objects are corresponding data objects; and

wherein the second game specific object, the second interface object and the second simulator specific objects are corresponding data objects;

a third interface in the agnostic interface mechanism configured to translate a third interface object into a third game specific object and to transmit the third game specific object to the game engine; wherein the second game specific object is a control object.

5. The system recited in claim 4 , wherein the core control generates the third interface object to manage multiple instances of the game engine.

6. The system recited in claim 4 , wherein the third interface object is selected from the following group of control objects: creating the game engine, starting the game engine, stopping the game engine or destroying the game engine.

7. A computer program product comprising a non-transitional computer usable medium having control logic stored therein for interfacing between a simulator and a game engine, the control logic comprising:

first computer readable program code means for causing the computer to receive a first simulator specific object from the simulator via a specific protocol of the simulator;

second computer readable program code means for causing the computer to translate the first simulator specific object into a first interface object;

third computer readable program code means for causing the computer to translate the first interface object into a game specific object and to transmit the first game specific object to the game engine;

fourth computer readable program code means for causing the computer to provide a core control coupled for controlling the communication of objects between the simulator and the game engine; and

fifth computer readable program code means for causing the computer to provide the first game specific object to the game engine through a direct application programming interface (API) call;

sixth computer readable program code means for causing the computer to generate a second game specific object at the game engine;

seventh computer readable program code means for causing the computer to translate the second game specific object generated by the game engine into a second interface object;

seventh computer readable program code means for causing the computer to translate the second interface object into a second simulator specific object in accordance with the simulator specific protocol; and

eighth computer readable program code means for causing the computer to provide the second simulator specific object to the simulator;

wherein the first game specific object, the first interface object and the first simulator specific objects are corresponding data objects; and

wherein the second game specific object, the second interface object and the second simulator specific objects are corresponding data objects;

ninth computer readable program code means for causing the computer to generate a third interface object in the core control;

tenth computer readable program code means for causing the computer to translate the third interface object into a third game specific object; and

eleventh computer readable program code means for causing the computer to transmit the third game specific object to the game engine;

wherein the second game specific object is a control object.

8. The computer program product recited in claim 7 , wherein the ninth computer readable program code means generates the third interface object to manage multiple instances of the game engine.

9. The computer program product recited in claim 7 , wherein the third interface object is selected from the following group of control objects: creating the game engine, starting the game engine, stopping the game engine or destroying the game engine.