IL-2 Sturmovik: Cliffs of Dover Plugin 2.0.0.1

Still is not working can you walk me through game engine for setup for il2?

How is this written out? secondly found the missons and the .cs file curious as to why you did not use the deviceLink in il2 cliffs of Dover.

[Console]
IP=127.0.0.1:20002
IPS=127.0.0.1
LOG=0
LOGTIME=0
LOGFILE=logs.txt
HISTORY=128
HISTORYCMD=128
WRAP=1
PAUSE=1
PAGE=20
LOGKEEP=1

I am just testing the game connection at the moment to see if it is reading the telemetry of the game when flying the mission. when I go into fly nothing is reporting back to the game engine.

Don't give up Harry. It took me ages to get things working at first. Your path for the patch is correct. At first only Free Hunt missions work, but earlier in this thread Prilad explains about adding a .cs file to missions created using Full Mission Builder. Telemetry is not available for multiplayer. My 5 dof motion platform has been working well since early 2014. What motions have you available?

@hugso one thing I do not understand is the get parameters can also draw it directly from the game why just a script with mission and not entire game? Secondly ran a server and wrote many and copied many a .cs file so I caught that. Last the flight sim I have put on hold till now is a 3 degrees of 360. I was testing the game connection to the software is all and still not getting that to work. I would just like to see the axis output getting the info and moving and that is not happening. What am I missing?

So I am looking at the game manager and it says connected. I am looking at the game engine under axis output and then connect to game in window mode. Fly mission with Script and nothing is registering. Before I get to the next step I was hoping to see if the game plane telemetry is being register with the software. Have step motors ready to roll just trying to find the right driver. Right now I have a cnc board with kmotion software C++ going tp try and make it work. if it does not looking to invest in a proper motor driver and board. cockpit design is stuck at getting the game connected to high torque step motors. All other fabrication is just about finished.

Last the game is sending info for an x and Y axis and is has been hook up to other PC or tablets. Their has got to be a easier way to make the connection to get info with program and relay it to the step motors in my case. I put this project on hold for 4 years then bumped onto this page and am FIRED UP LOL!!! I would like to knock this out of the park. I was going to work with one of the programer at Fight illusion and lost contact with him. Anyway that is my simpit story.

I am inspired to give CLoD a go again.....

I am not an IT guy. All I know is that the way the game is made is such that telemetry is only available in Training and Single (not on-line) Missions. This should show up as action in both Output Testing -> Virtual Axis and in the Tuning Center (R click on Game Engine in Task Bar. If things are working here, you can copy any of the .cs files and rename it the name of your mission so it will then work with Full Mission Builder missions also. That's about the extent of my knowledge, I'm afraid.

Sorry, to further clarify: the only missions which provide telemetry from the start are Training and Quick Missions (Free Flight). The Single Missions will need you to add the .cs file.

Question on the .cs files are they in the Documents folder 1csoft or in steam main? Last if you help me get this rolling I can fix the issue with a server allowing you the info. I was thinking about setting one up again with a favorite squadron mission file I have and will add the .cs file to it and will begin testing that side of it but when I launched the game into window still no reg. in Tuning Center or the virtual Axis.

PS this should work to get the telemetry from the game constant and not through missions.

sing System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.IO.MemoryMappedFiles;

namespace DeviceLinkServer
{
public class GameCommunications
{
private MemoryMappedFile m_MemoryMappedFile;
private MemoryMappedViewAccessor m_MemoryMappedViewAccessor;
public enum ParameterTypes
{
Nil,
M_Random,
M_Shake,
M_CabinDamage,
M_CabinState,
M_NamedDamage,
M_SystemWear,
M_Health,
C_Steering,
C_Brake,
C_Throttle,
C_Trigger,
C_Pitch,
C_Mix,
C_WaterRadiator,
C_OilRadiator,
C_RadiatorAutomation,
C_PitchAutomation,
C_Compressor,
C_Afterburner,
C_BoostEnabler,
C_SlowRunningCutOut,
C_Magneto,
C_Feather,
C_CarbHeater,
C_HatchDoor,
C_HatchJettison,
C_Timer,
C_Timer1,
C_Aileron,
C_Elevator,
C_Rudder,
C_AileronTrim,
C_ElevatorTrim,
C_RudderTrim,
C_TailwheelLock,
C_LandingFlap,
C_LeadingEdgeSlats,
C_Undercarriage,
C_UndercarriageEmergency,
C_BombBayDoor,
C_Airbrake,
C_FuelTankSelector,
C_TelepirometroElettrico,
C_AltimeterPinion,
C_AnemometroPinion,
C_BombSight,
C_Sight,
C_Bombenabwurfgerat,
C_KraftstoffSelector,
C_LiquidGauge0,
C_LiquidGauge1,
C_PriLights,
C_SecLights,
C_SightLights,
C_PitotHeater,
C_Handpumpe,
C_RadTXRX,
C_RadPriNav,
C_RadSecNav,
C_Kurssteuerung,
A_Steering,
A_Brake,
A_Aileron,
A_Elevator,
A_Rudder,
A_AileronTrim,
A_ElevatorTrim,
A_RudderTrim,
A_Undercarriage,
A_UndercarriageShock,
A_UndercarriageWheel,
A_HatchDoor,
A_BombBayDoor,
A_ImpellerAngle,
A_ImpellerAngularVelocity,
A_ImpellerUnfold,
A_LandingFlap,
A_Airbrake,
A_EngineAirRadiator,
A_EngineWaterRadiator,
A_EngineOilRadiator,
A_LeadingEdgeSlat,
Z_Coordinates,
Z_Orientation,
Z_Overload,
Z_AltitudeAGL,
Z_AltitudeMSL,
Z_VelocityIAS,
Z_VelocityTAS,
Z_VelocityMach,
Z_AmbientAirTemperature,
S_ElectricVoltage,
S_ElectricIncandescingRatio,
S_ElectricAmperage,
S_ElectricPrimaryPitLight,
S_ElectricSecondaryPitLight,
S_ElectricSightLight,
S_FuelReserve,
S_HatchDoor,
S_UndercarriageValve,
S_PneumoContainerPressure,
S_PneumoLinePressure,
S_HydroPressure,
S_HydroReserve,
S_Sturzanlage,
S_GunOperation,
S_GunReserve,
S_GunClipReserve,
S_BombReserve,
S_Fenster,
S_PitotHeater,
S_Bombenabwurfgerat,
S_Turret,
M_Reserved000,
M_Reserved001,
M_Reserved002,
M_Reserved003,
M_Reserved004,
M_Reserved005,
M_Reserved006,
M_Reserved007,
M_Reserved008,
M_Reserved009,
M_Reserved00A,
M_Reserved00B,
M_Reserved00C,
M_Reserved00D,
M_Reserved00E,
M_Reserved00F,
M_Reserved010,
M_Reserved011,
M_Reserved012,
M_Reserved013,
M_Reserved014,
M_Reserved015,
M_Reserved016,
M_Reserved017,
M_Reserved018,
M_Reserved019,
M_Reserved01A,
M_Reserved01B,
M_Reserved01C,
M_Reserved01D,
M_Reserved01E,
M_Reserved01F,
I_Timer,
I_AmbientTemp,
I_EngineRPM,
I_EngineManPress,
I_EngineBoostPress,
I_EngineWatPress,
I_EngineOilPress,
I_EngineFuelPress,
I_EngineWatTemp,
I_EngineRadTemp,
I_EngineOilTemp,
I_EngineOilRadiatorTemp,
I_EngineTemperature,
I_EngineCarbTemp,
I_Pitch,
I_VelocityIAS,
I_Altitude,
I_Variometer,
I_Slip,
I_MagneticCompass,
I_RepeaterCompass,
I_Peilzeiger,
I_FuelReserve,
I_LiquidReserve,
I_Voltamperemeter,
I_Voltmeter,
I_Amperemeter,
I_HydroPressure,
I_HydroEmPressure,
I_Turn,
I_AH,
I_DirectionIndicator,
I_SlavedCompass,
I_Suction,
I_AFN,
I_ADF,
I_RDF,
I_RMI,
I_FLRC,
I_Kurssteuerung,
I_BombSight
}

public GameCommunications()
{
m_MemoryMappedFile = null;
m_MemoryMappedViewAccessor = null;
}


private void OpenMMF()
{
try
{
m_MemoryMappedFile = MemoryMappedFile.OpenExisting("CLODDeviceLink", MemoryMappedFileRights.Read);
m_MemoryMappedViewAccessor = m_MemoryMappedFile.CreateViewAccessor(0, 10000 * sizeof(double), MemoryMappedFileAccess.Read);
}
catch(Exception e)
{
return;
}
}

public double GetParameter(ParameterTypes ParameterType, int SubType)
{
if (m_MemoryMappedFile == null)
OpenMMF();

try
{
return m_MemoryMappedViewAccessor.ReadDouble((((int)ParameterType * 10) + SubType) * sizeof(double));
}
catch (Exception e)
{
return -99999.99999;
}
}
}
}
Enjoy!

zAnother help info to make a full game link!!!

Try-
#region Parameters - Machine Spatial
/// <summary>
/// [Misc.: Machine Spatial Coordinates]
/// <para>Indicates machine position in world coordinates.</para>
/// <para>Subtype 0 shows X-coordinate;</para>
/// <para>Subtype 1 shows Y-coordinate;</para>
/// <para>Subtype 2 shows Z-coordinate.</para>
/// </summary>
Z_Coordinates,
/// <summary>
/// [Misc.: Machine Spatial Orientation]
/// <para>Indicates machine orientation, angles are in degrees.</para>
/// <para>Subtype 0 shows yaw (0 degrees point E);</para>
/// <para>Subtype 1 shows pitch (nose-up is negative);</para>
/// <para>Subtype 2 shows roll (right roll is positive).</para>
/// </summary>
Z_Orientation,
/// <summary>
/// [Misc.: Machine Overload under Acceleration]
/// <para>Indicates overload in m/s/s.</para>
/// <para>Generic subtype (-1) shows accelerometer, being 0 under normal conditions;</para>
/// <para>Subtype 0 shows acceleraton along machine's X axis;</para>
/// <para>Subtype 1 shows acceleraton along machine's Y axis;</para>
/// <para>Subtype 2 shows acceleraton along machine's Z axis.</para>
/// </summary>
Z_Overload,
/// <summary>
/// [Misc.: Machine Altitude AGL]
/// <para>Indicates machine elevation above ground level in meters.</para>
/// </summary>
Z_AltitudeAGL,
/// <summary>
/// [Misc.: Machine Altitude MSL]
/// <para>Indicates machine elevation above 0.0 Z-plane.</para>
/// </summary>
Z_AltitudeMSL,
/// <summary>
/// [Misc.: Machine's Velocity in Air]
/// <para>Indicates machine's aerial velocity.</para>
/// <para>Generic subtype (-1) shows velocity length;</para>
/// <para>Subtype 0 shows aerial flow along machine's X-axis;</para>
/// <para>Subtype 1 shows aerial flow along machine's Y-axis;</para>
/// <para>Subtype 2 shows aerial flow along machine's Z-axis.</para>
/// </summary>
Z_VelocityIAS,
/// <summary>
/// [Misc.: Machine's Velocity in World Coordinates]
/// <para>Indicates machine's absolute velocity.</para>
/// <para>Generic subtype (-1) shows velocity length;</para>
/// <para>Subtype 0 shows machine's speed along world's X-coordinate;</para>
/// <para>Subtype 1 shows machine's speed along world's Y-coordinate;</para>
/// <para>Subtype 2 shows machine's speed along world's Z-coordinate.</para>
/// </summary>
Z_VelocityTAS,
/// <summary>
/// [Misc.: Machine's Mach Factor]
/// <para>Indicates machine's aerial velocity devided by sonic speed.</para>
/// <para>Generic subtype (-1) shows velocity length;</para>
/// <para>Subtype 0 shows aerial flow along machine's X-axis;</para>
/// <para>Subtype 1 shows aerial flow along machine's Y-axis;</para>
/// <para>Subtype 2 shows aerial flow along machine's Z-axis.</para>
/// </summary>
Z_VelocityMach,
/// <summary>
/// [Misc.: Ambient Temperature]
/// <para>Indicates air temperature around machine's location, in K.</para>
/// </summary>
Z_AmbientAirTemperature,
#endregion

Here are 3 pics showing info:
http://i1024.photobucket.com/albums/y305/harry_king2/pic2_zps9jgliqh4.jpg
http://i1024.photobucket.com/albums/y305/harry_king2/pic1_zpse1gxwbwz.jpg
http://i1024.photobucket.com/albums/y305/harry_king2/Pic3_zpslofyosvo.jpg
Not sure if I am doing this right but here ya go!

Blimey! That's amazing. All way beyond my capabilities to deal with, but maybe I could pick your brains about how to use that data if you get it working? All I know is that the .cs files are all identical and you just need to rename one of them to the same name as your mission name and put it next to your mission in the My Missions folder. These are all in Documents etc. Do keep posting how you get on.

Copy that was easy seeing that script, my goal is to take it one set further so that you can directly connect to this particular game. I just wish I could get the thing to work so I can see the Tuning reading the GAME mission .cs info. that would jump start my next expenditures.