PDA

View Full Version : TF DeviceLink like interface



Pages : [1] 2 3

ATAG_Colander
Mar-20-2013, 22:14
Just another goodie in the TF release. A "DeviceLink" like readonly interface.

- It accepts the same parameters as the "GetParameters" function for missions.
- Only the data available in instruments for the airplane being flown will be available. This means, for example, that if you the plane you are flying does not have an altimeter, you will not receive values for the altimeter.
- It has not been fully tested so it might have some bugs (i.e. missing information which is available in instruments).
- Run it in a timer to get periodic updates.
Those who know programming will know what can be done with it :thumbsup:



using 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)Param eterType * 10) + SubType) * sizeof(double));
}
catch (Exception e)
{
return -99999.99999;
}
}
}
}


Enjoy!

ATAG_Colander
Mar-23-2013, 17:34
Is any one using this? :confused!:

ATAG_Lolsav
Mar-23-2013, 18:36
To my knowledge its usefull to those who have panels.. i only have what i see on my monitor. Not even a G15 keyboard with display.. those could have some use. Althought maybe it could have some use to X52 Saitek MDF display, but theres a bug with 64 bit drivers, does not display characters correctly, they get scrambled, so, getting readings its more like a guess game.

DK_
Mar-23-2013, 19:14
Would be nice to set up some engine/flight instruments on another screen or tablet device (wifi, bluetooth, usb, etc).

I have seen some things like this in racing sims but it is way beyond my abilities to set up.

Pikas62
Mar-27-2013, 08:13
Nice feature. Thats what I have waited for since the release of CLOD :D. Now I hope that CLOD will be beimplemented into HELIOS or to the nice USB devices that have been anounced in that threat: http://forums.eagle.ru/showthread.php?t=100076.

Ree2
Apr-22-2013, 15:10
Good job:)

Could you please explain to me what is the meaning of the prefixes (M, C, A, Z, S, I)?

Thank you.

Silver
May-27-2013, 04:38
i am also interested in using this to display some of the gauges (airspeed, altitude, engine temp etc) on a 2e small monitor or tablet type display, but i have no clue on how to use the data values you just provided

thanks anyway to provide the information output from the game, hopefully some of the more tech savvy CoD folks will know how to take it to the next step :) (there have been a number of threads at the old 1C forum asking for this)

Knight
Jun-07-2013, 10:28
Need help with a program to send UDP packets to a step motor driver. I am looking for some one to write a program like UDPSpeed (il2 1946) Artificial Horizon for X and Y axis and compass Z axis for step motors for a full motion cockpit.

I know it can be done if UDPSpeed works by sending data to another computer it could send that same information to a step motor driver.

Any Help or advice would greatly be appreciated.

Knight

Flyingblind
Jun-07-2013, 17:04
I am not sure if this is any use although it is something I will be looking into myself. There is a forum called X-Sim. This is a community devoted to DIY motion platforms for flight and racing sims. They have free software that extracts output data from a sim as it runs and exports it to HID devices, Arduino boards and all manner of similar goodies. I do not know if it works with CloD but I understand it works with IL-2 1946 by utilizing Device Link although this meant it has limited use online.

Knight
Jun-07-2013, 19:11
Sorry double post!

Knight
Jun-07-2013, 19:37
GREAT Website, however does not use step motors. I am looking at bypassing a motor controller board and going with UDP direct to stepper motor driver on Ethernet more accurate. The best place I have been to is Flight illusions and there gauge setup for attitude and compass using stepper motors. however the driver board they are using is not powerful enough or I would be DONE.LOL
Anyway I am still moving forward and I know that many of the guys at ATAG know about getparameter script. I just don't know how to create a program to use this script to send the data to the stepper motor driver hook up on Urse Data Protocol.

My final phase will be ready to go by Christmas this year.


Knight

lowca
Jun-15-2013, 12:05
Super ..
i use vb net and arduino for tests.. ;)


3084

What about compass value .. always get 0 ..

Greetings

bolox
Jun-15-2013, 15:41
I believe compass value has a problem- which parameter are you trying to read as there are several possibilities.

Looking through some old scripting I used I seem to have used
aircraft.getParameter(part.ParameterTypes.I_Repeat erCompass, 0);
rather than the magnetic compass value.

Cool you can program something to use this:thumbsup::thumbsup::thumbsup:

Tomsk
Sep-14-2013, 11:37
So I tried to use this to write a bridge app that would allow UDPSpeed to work with IL2CoD ... however, most of these parameters do not seem to work properly. I tried all the I_* params and I_MagneticCompass and I_EngineRPM, do seem to work ... but that was about it. For example I_VelocityIAS, I_Altitude, I_Variometer, I_Slip etc. all report 0 in all 10 sub-params. Which is a shame, because being able to use UDPSpeed with IL2CoD is something I'm sure many people would be interested in :)

ATAG_Colander
Sep-14-2013, 15:48
Maybe because of this:

- Only the data available in instruments for the airplane being flown will be available. This means, for example, that if you the plane you are flying does not have an altimeter, you will not receive values for the altimeter.

Tomsk
Sep-14-2013, 17:02
Sadly not, the airplane definitely did have an altimeter and an airspeed indicator. Unless I'm mistaken and I'm not using the right parameters, I wasn't entirely sure what the I_ C_ Z_ etc stood for ... but I_ seemed to be instruments to me, so I'm guessing I_Altitude and I_VelocityIAS should work ...

ATAG_Colander
Sep-14-2013, 22:45
Try I_VelocityIAS with -1 as the parameter.

Tomsk
Sep-15-2013, 09:53
Try I_VelocityIAS with -1 as the parameter.

Okay yes that works. That's pretty odd, some of the parameters are accessible at 0 index ... some at -1. Why not put all of them starting at index 0?

So the only other issue is that I_VelocityIAS (and many of the other parameters) change units depending on what plane you are in. So in a Bf109 I_VelocityIAS gives kmph, in a Spitfire it gives mph. This makes compatibility with UDPSpeed complicated, because IL2 DeviceLink always uses the same units irrespective of the plane. Since you don't know whether the numbers from CoD are in mph or kmph you can't automatically convert them to the right values for the DeviceLink protocol.

IMO there are quite a lot of advantages to using fixed units for the parameters. It's generally very easy to adjust a gauge to display in mph even if the input data is kmph, but without fixed units it's impossible to make a set of generic gauges that are usable for every plane. Not having fixed units also makes compatibility with existing tools and protocols difficult, as all of the protocols I know are built around fixed units.

bolox
Sep-15-2013, 10:05
I agree having different units makes things slightly complicated, however it appears that the units of measurement are based on nationality - so it would 'only' require a set of RAF gauges and a set of Luftwaffe gauges- the RAF ones just needing some 'conversion' in the UDP ini's for the relevant gauge sets.

For users of physical gauges, motion cockpits etc things are more difficult

ATAG_Colander
Sep-15-2013, 10:46
What this is returning is the data available for the plane's instruments.
Because of this, the values will be in the instruments UOM (and if there's no instrument, there's no value).

I guess you can assume that there are only 2 UOM (metric and imperial) and make a "switch" to change between A and B.

Propnut
Sep-16-2013, 18:44
Hi, I am not a programmer so I might be reading this incorrectly but; you can get flight telemetry from this such as roll, pitch, heave and yaw is that correct?

The reason I ask is that, like Knight, I too have a motion platform but I do not need to talk directly to my motor drivers. I am using a program called SimTools (free, check it out at XSimulator.net). If I can find out the method of extracting telemetry from the game I can get help over there in making a plugin for Simtools which will allow me to have motion with Cliffs.

As I understand it; I would need the memory map locations for each of the data sets I mention above. Plugins for Simtools can be made from Memory map locations, memory hooks, UDP, DLLs, etc.

As I mentioned, I am not a programmer but if I do the leg works I know someone that is a flight sim enthusiast, a programmer, and developer with Simtools that is willing to create plugins for the sim motion community.


Thanks

bolox
Sep-17-2013, 10:53
Hi, I am not a programmer so I might be reading this incorrectly but; you can get flight telemetry from this such as roll, pitch, heave and yaw is that correct?
correct- Colander has done is mapped he instrument readings.- ie if the olane doesn't have the instrument the data will not be able to be read.
It is also possible to use a script to output data from a greater variety of possible types- but this requires a script for each mission (offline).

A programmer should be able to make sense of the parameters in the first post

ATAG_Bliss
Sep-17-2013, 10:59
correct- Colander has done is mapped he instrument readings.- ie if the olane doesn't have the instrument the data will not be able to be read.
It is also possible to use a script to output data from a greater variety of possible types- but this requires a script for each mission (offline).

A programmer should be able to make sense of the parameters in the first post

Yep - with the reasoning behind this is anyone using a device link type setup still won't be able to have an unfair advantage online as anyone else.

But all the other information (don't know about telemetry) could be scripted into SP missions to see an assortment of just about any type of information you wanted.

ATAG_Colander
Sep-17-2013, 11:21
I'm thinking I might add Rx, Ry and Rz rotations to it.
I don't think they could give any advantage to any one. Thoughts?

ATAG_Bliss
Sep-17-2013, 11:31
I'm thinking I might add Rx, Ry and Rz rotations to it.
I don't think they could give any advantage to any one. Thoughts?

Eh.., in English please :D

Is that like the game telling you how much control input you are doing (pitch, roll, rudder)?

If so there are programs out there that can overlay and give you the same type of information already. So I don't see how that would give someone an unfair advantage. If that's not what you are talking about you'll have to explain it a bit more :D

ATAG_Colander
Sep-17-2013, 11:41
No, I'm talking about the position in space of the plane....

For example:
Roll 30 degrees
Pitch 10 degrees
Bank -5 degrees

The data that the 6DOF cockpit people needs.

ATAG_Bliss
Sep-17-2013, 11:45
No, I'm talking about the position in space of the plane....

For example:
Roll 30 degrees
Pitch 10 degrees
Bank -5 degrees

The data that the 6DOF cockpit people needs.

Ah - that's pretty cool. I have no idea how that could be used as an unfair advantage at all. Hell, I have no idea how that is advantageous in the 1st place :D

bolox
Sep-17-2013, 14:31
Only advantage I can see is that planes without artificial horizon (eg 109) could have a graphic representation on a separate screen.
Doesn't bother me personally, but I know some people get massively upset if there is a one in a billion chance someone could theoretically cheat with it

ATAG_Colander
Sep-17-2013, 15:09
That's what I'm afraid of.

Propnut
Sep-18-2013, 08:22
Wow, I forgot to subscribe to this thread and so did not see the responses. Thank you all for replying to my request.

I had completely forgotten the "anti-cheating" issue from way back when until Bolox reminded me of it in my thread on this topic. You are correct though, it is a huge issue that would adversely affect those of us who are building out of the box so to speak. Reminds me of the music video created by David "Tolwyn" Shaw called "Flying for the First Time". One of the lyrics was "Anyone better than me must be cheating". A refrain you used to see often on Hyperlobby.

I did pass on the code in the first post and hopefully someone will be able to incorporate it into a plug-in for Cliffs, and I am trying to learn how to program. I am starting with Visual Studio Express 2012 and C# but I doubt I will be in a position to do anything on my own for a very long time. Regardless it is fun to learn.

Thanks for carrying on the conversation and tossing ideas around.

matweich
Sep-18-2013, 14:09
4381438243834384
http://rusfolder.com/38084518

ATAG_Colander
Sep-18-2013, 14:46
Nice Mat!

Tonester
Sep-18-2013, 18:58
4381438243834384
http://rusfolder.com/38084518

Is there somewhere one can download this...thats the thing i miss most about il2... having gauges on a separate screen with udp speed...would be great to have in CLOD

ATAG_Bliss
Sep-18-2013, 19:08
Is there somewhere one can download this...thats the thing i miss most about il2... having gauges on a separate screen with udp speed...would be great to have in CLOD

Here you go Tonester.

He left a download link in Russian and I somehow was able to navigate through it :D.

See attached:

4387

ATAG_Bliss
Sep-18-2013, 19:09
4381438243834384
http://rusfolder.com/38084518


Awesome!!! :thumbsup::thumbsup:

:salute:

Tonester
Sep-18-2013, 20:50
Awesome...thanks mate!

ATAG_Colander
Sep-18-2013, 20:59
I'm glad some one is finally doing something with this!

Skoshi_Tiger
Sep-19-2013, 01:50
Unless being able to read the compass in a Spitfire is considered a "Cheat", I think this looks really great!


Many thanks Matweich!

Tomsk
Sep-19-2013, 03:18
What this is returning is the data available for the plane's instruments.
Because of this, the values will be in the instruments UOM (and if there's no instrument, there's no value).

I guess you can assume that there are only 2 UOM (metric and imperial) and make a "switch" to change between A and B.

Yup that's possible, but ultimately I'd really like to integrate support for Cliffs of Dover into Helios (http://www.youtube.com/watch?v=v15E1JZe9es). Then next version of Helios will apparently support creating new interface plugins.

That would be much easier if I can find a way to get standardized units out of it. Otherwise I'd either have to create two different interfaces into Helios, one for imperial units and one for metric ... or all the gauges would need to be units specific.

What I was wondering is whether you'd be able to expose another parameter value which tells you whether this is an axis plane (metric units) or an allied plane (imperial units)? Then I'd know which units are being used and can automatically convert into a standardized set of units. Is that possible?


One the subject of creating an artificial horizon in planes that don't have them, well the Z_Orientation parameter seems to work well enough for that purpose already. As for this being cheating, well creating a sim-pit with real instruments, or even using a second screen to display the instruments does give a slight advantage. But it can also increase immersion hugely.

In the end I think the question you have to ask is not "Does this allow one player to gain an advantage over another?" but instead "Does this give the sim pilot a big advantage that a real pilot wouldn't have had access to?". An artificial horizon, IMO, is mostly only useful for flying in very poor visibility, good luck getting any real advantage out of it in combat. Artificial horizons are also something that sim pilots rely on much more heavily than real pilots, because providing the plane is relatively unloaded a real pilot can generally feel the pull of gravity, telling them which way the plane is oriented. To my mind, it doesn't give an unfair advantage ... although others may disagree.

Tonester
Sep-19-2013, 06:08
So is this useable online?...im confused

ATAG_Bliss
Sep-19-2013, 06:44
So is this useable online?...im confused

Yep - That's why the interface was made like it was.. Essentially the only information you can get is the same exact information your cockpit gives you in game of that particular plane.. Use away!

Skoshi_Tiger
Sep-19-2013, 08:42
I can get the raw data application to run ok and read values from COD but when I run the virtual cockpit and choose the Spitire Mk IIa I get an error in the right hand panel saying "'0,01' is not a valid floating point value" and the gauges screen does not display.

Any ideas gents?

ATAG_Colander
Sep-19-2013, 09:31
I can get the raw data application to run ok and read values from COD but when I run the virtual cockpit and choose the Spitire Mk IIa I get an error in the right hand panel saying "'0,01' is not a valid floating point value" and the gauges screen does not display.

Any ideas gents?

, is not a decimal separator in english.

Tomsk
Sep-19-2013, 10:55
, is not a decimal separator in english.

Wow Matweich, I'm impressed, this is awesome! To my mind this renders my efforts to convert UDPSpeed as unnecessary, good work! :thumbsup:

The only problem I've had is the same as reported by Skoshi_Tiger: on startup it complains "0,01 is not a valid floating point number". The reason for this is that some of the ini files (although not all) are using comma (,) as the decimal separator. Using comma as the decimal separator is common in Europe, but doesn't work for all locales. It's very likely the problem is that the code is parsing the numbers using the users current locale. Which means 0,01 will parse fine if your locale has ',' as the decimal separator, sadly my UK English locale only accepts dot so "0,01" doesn't parse.

So .. for those other users who are getting this problem, here is an updated version that works with English locales. All I've done is change the .ini files so that they use dot (.) rather than comma for the decimal separator. It may well work with all locales, as I think '.' is a very standard decimal separator that is nearly always supported.

http://www.shackell.org.uk/files/VC-English.zip

I'm also going to work on a Bf-109 cockpit, the ini format looks easy enough to fathom.

Skoshi_Tiger
Sep-19-2013, 11:16
LOL!

I just spent the last half hour chasing commas in the .ini files then came back here to find the update already posted!

Once the .ini files are set to the appropriate separator it works great!

It runs a lot smoother than I remember UDPSpeed running (I haven't run original Il2 for a long time!)

Thanks for posting this, I'll try it out in Multiplayer Next time I'm on!

A few years back I was playing around with devicelink on the original IL2, sending and receiving UDP packets, It would be very interesting to see the source code at some time to see how to talk to CoD.

Cheers!

matweich
Sep-19-2013, 17:03
Hi all!
Glad you found this program useful.
Sorry for "international" problems with download and commas.
This version
http://www.mediafire.com/download/gm585mlg8d6mm3f/VC.zip
accepts both points and commas as decimal point separators.

PS Thanks Colander for DeviceLink and Team Fusion for their work.

Skoshi_Tiger
Sep-19-2013, 18:47
Thank you!

Propnut
Sep-22-2013, 09:57
A HUGE thank you to everyone who commented on extracting telemetry for motion platforms and especially to Team Fusion for their TF Devicelink code.

A Simtools community developer has come up with a working (Roll, Pitch and Yaw at least so far) plug-in for motion.

It is of course only for single player missions, which means that I will be spending my future flights offline unfortunately. :(

Any other ideas please do share them, if you want to further improve access to telemetry (especially for online mode) please please please share, lol.

Thanks again.

Simtools and the Cliffs of Dover plug-in can be found here:


XSimulator.net


So yes Colander, to answer the original question from this thread: We are using it! :)

Skoshi_Tiger
Sep-22-2013, 10:08
I spent the night using the virtual cockpit on line and it worked flawlessly.

I particularly liked the Gun sight indicator highlighting the aircraft wingspan in a table.

Very Cool!

wingflyr
Sep-23-2013, 13:30
Hey M8s,
for my first post I first would like to say Team Fusion, Awesome site, Brilliant work on the upgrades. Cliffs of Dover stepped up to the plate and is preforming nice. All you folks rock.Thanks.I been flyin IL2 since its demo release eons ago.

The reason Im posting here is that ever since device link was introduced to IL2, Ive built a very detailed sim pit with Dastardlly' gauges and then Bolox' wonderful set of working gauges. Hoping that the D-link would be continued on with Clod, the TF DeviceLink like interface is an exciting step forward. Big thanks to Matweich this is an awesome program!
The program works great on the PC system with the game installed with 2 monitors,
my question is can it be setup to link gauges fron a 2nd PC on its monitor like the old way
for example conf.ini
[DeviceLink]
port=21100
host=192.168.0.106
If so how do you set it up.


Also is there a posiblity that the program can allow changing the graphics to more realistic looking gauges textures.

Again Guys a Millon Thanks. Cheers Wingflyr.

bolox
Sep-23-2013, 14:09
Hiya, good to see you around:thumbsup:

Yeah, I'm asking myself the same 2 questions..... would love to have a crack at CoD version graphically.

wingflyr
Sep-23-2013, 14:19
Hiya, good to see you around:thumbsup:

Yeah, I'm asking myself the same 2 questions..... would love to have a crack at CoD version graphically.

Thats wonderful news my friend, just loved your work with all the D-link Sim pits you've made.

Skoshi_Tiger
Sep-23-2013, 20:13
Hey M8s,
....
The program works great on the PC system with the game installed with 2 monitors,
my question is can it be setup to link gauges fron a 2nd PC on its monitor like the old way
for example conf.ini
[DeviceLink]
port=21100
host=192.168.0.106
If so how do you set it up.


Also is there a posiblity that the program can allow changing the graphics to more realistic looking gauges textures.

Again Guys a Millon Thanks. Cheers Wingflyr.

From my understanding the program does not use UDP to communicate with COD like devicelink in the original Il2. Instead it uses .net memory mapped files. (Those in the know please correct me if I'm talking crap here!) so it would be restricted to a single PC.

To communicate to a second PC you might need to do like TomsK mentioned and create a program that sits between COD and your simpit software to read from the memory mapped file and then broadcasts the the info using UDP.

I'm not sure how bad the latency would be.

wingflyr
Sep-23-2013, 23:15
Thanks for the reply Skoshi_Tiger,:salute:
maybe one day soon. Il2 of old was always full of suprises which is still a wonderful game to today.
Cheers Wingflyr :thumbsup:

Zisi
Sep-28-2013, 20:12
This is really well done, is the source around somewhere?

Thanks

hugso
Sep-29-2013, 06:50
I am delighted to read that getting telemetry out of CoD is becoming easier. I see we can get instrument readings which will be a great help for me use to drive my pneumatic motion platform. The most important information I need is the g levels to drive the heave motion. Is it likely this will be available? My system works at present with IL-2 using DeviceLink. And a huge thank you to Team Fusion for the fantastic work they are doing.

Maltloaf1
Sep-29-2013, 19:09
Wow,

This is fantastic, a serious upgrade. I use trackir and try to watch my gauges all the time but to be honest it is fairly difficult in cockpit. I down loaded this tonight and despite the fact that my set up is far from user friendly yet (second monitor balanced on books),this was amazing. Not only did I navigate properly for the first time since leaving IL2 1946 because I could actually read the damn compass but when I cooked my engine over Calais I glanced at the gauges and sure enough I was well in the red (130!). Normally I would have cursed the thing and assumed the game was wrong. Because I could instantly and clearly see my dials (realistic, not cheating!) I realised I had screwed up. Next time I should be able to keep out of trouble. Clear and constant realistic instruments, bloody fantastic! Thanks!

Cheers!

Robusti
Oct-16-2013, 07:38
Does this/will this have server/client capability? Edit. Never mind, I see the answer is no.

Also, can the gauges be moved to different locations, separately? Ie. multiple monitors.

matweich
Oct-16-2013, 10:52
Does this/will this have server/client capability?
Not now. May be later.


Also, can the gauges be moved to different locations, separately? Ie. multiple monitors.
Yes. See "ControlPanels" section in Cockpit.ini.
Sample here: 4911.
49124913

Robusti
Oct-16-2013, 12:31
Not now. May be later.

That would be awesome for my two computer system, then I could spread the gauges over my client pit monitors.:ilike:


Works great! Needed to use "Pseudo" fullscreen setting to get it to work.

Skoshi_Tiger
Oct-19-2013, 09:11
One of the benefits of having the gauges on a second screen is that I have actually managed to do a level bombing run in the Blenheim! Flying on instruments has allowed me to keep the old bird level and flying in a straight line!

Cheers!

9./JG52 Hans Gruber
Oct-21-2013, 21:45
Is there a 109 version?

Skoshi_Tiger
Oct-21-2013, 22:16
Is there a 109 version?

I'm not sure, but you can use the spitfire guages with all aircraft, it's just any 109 specific instruments will not be shown.

All the config files for the SPitfire can be opened and inspected, so I expect that someone could make up a set for the 109. All it would take is someone with the time and will to do it.

San
Oct-22-2013, 09:02
Very good job!

I have been watching the config files and I am wondering how can I display a image as background instead black color.
Do you have any documentation about the format you are using and the classes you can instance?
Regards

Tomsk
Oct-22-2013, 09:55
Is there a 109 version?

You can use mine if you like: https://dl.dropboxusercontent.com/u/8624040/Bf109.zip

It's for a 1280x1024 screen, unlike the spitfire one which is 1420x770 ... but hopefully someone finds it useful.

I haven't quite finished it yet, there are a couple of gauges I still want to do like landing gear indicator ... but it's got all the main flight instruments.

E69_Korrea
Oct-22-2013, 13:27
I love this new feature. I'll use to my motion cockpit:

5187

Thanks!

matweich
Oct-22-2013, 16:07
I have been watching the config files and I am wondering how can I display a image as background instead black color.
You can use Background and Foreground value for any item like this:
Class = Radial gauge;
Caption = Altimeter;
...
Background = metal1.bmp; // Only 32 bit BMP in ARGB order
BackgroundFitMode = Center; // NoFit, Center (default), Stretch, Scale, Fill
Foreground = FG.bmp;
ForegroundFitMode = Center;

Inputs{
Alt10000Ft{
ParamType = I_Altitude
...

Also you can use Bitmap value for needles:
...
Needle{
Bitmap = Needle.bmp;
Width = 10;
CenterY = 60;
Length = 70;
}
...

5194
But FPS will not be good because it does not use hardware acceleration.
On my i3 with all spitfire gauges using bitmaps it was completely unusable.


Do you have any documentation about the format you are using and the classes you can instance?
No documentation, sorry. My English is not good enough for that.

matweich
Oct-22-2013, 16:11
You can use mine if you like: https://dl.dropboxusercontent.com/u/8624040/Bf109.zip

It's for a 1280x1024 screen, unlike the spitfire one which is 1420x770 ... but hopefully someone finds it useful.

I haven't quite finished it yet, there are a couple of gauges I still want to do like landing gear indicator ... but it's got all the main flight instruments.

Good job! I especially liked your slip&turn indicator.

9./JG52 Lopp
Oct-22-2013, 16:22
Great work guys. Thank you for sharing!!

Tomsk
Oct-22-2013, 16:46
Good job! I especially liked your slip&turn indicator.

Thanks that one did take quite a bit of fiddling to get it right :)

1lokos
Oct-22-2013, 18:09
I love this new feature. I'll use to my motion cockpit:


Only after see in ES69 (http://www.escuadron69.net/v20/foro/index.php?/topic/57655-exportar-instrumentos-a-segundo-monitor/) I understand what you were talking about. :doh:

Your Spitfire "seat" make movements! Very nice.:thumbsup:

Sokol1

San
Oct-24-2013, 06:30
You can use Background and Foreground value for any item like this:
Class = Radial gauge;
Caption = Altimeter;
...
Background = metal1.bmp; // Only 32 bit BMP in ARGB order
BackgroundFitMode = Center; // NoFit, Center (default), Stretch, Scale, Fill
Foreground = FG.bmp;
ForegroundFitMode = Center;

Inputs{
Alt10000Ft{
ParamType = I_Altitude
...

Also you can use Bitmap value for needles:
...
Needle{
Bitmap = Needle.bmp;
Width = 10;
CenterY = 60;
Length = 70;
}
...

5194
But FPS will not be good because it does not use hardware acceleration.
On my i3 with all spitfire gauges using bitmaps it was completely unusable.


No documentation, sorry. My English is not good enough for that.

Ok, I have done a workarround. I have created a pannel with with Helios with a cockpit texture with transparent holes in the gauges. You can see your window as background integrated with the cockpit and I can add other pannels.
Thank you very much

hnbdgr
Oct-24-2013, 07:29
Hi,

I'm looking for a cheap digital readout solution much like the arduino LCD display seen earlier. I'm technical, but have no previous experience with this sort of thing. Could anybody point me to some tutorials, etc. to build/"ready buy" such a device and use it with the readouts in CloD?

I thought about using the little utility mentioned above, but even though my monitor is a dual setup and due to space issues it's not feasible to have them above or below the main monitor which is why the little arduino type lcd would come in incredibly handy....

Can anybody help?

Many thanks:salute:

1lokos
Oct-26-2013, 23:47
"iDisplay" allow use one Tablet/Smartphone as second monitor to show VC.

http://www.getidisplay.com/

Tested with PIPO M9 by Maquina on ES69: http://www.escuadron69.net/v20/foro/index.php?/topic/57655-exportar-instrumentos-a-segundo-monitor/#entry859155

Sokol1

hnbdgr
Oct-28-2013, 05:24
thanks sokol, I'll try that out, let's hope it works fast and wirelessly

superman
Oct-30-2013, 04:25
Hi

I have put together a quick and dirty Tiger moth cockpit. It needs more tweaking to be perfect, but it works for me :-) resolution is 1024*768 to be used on my Ipad with Idisplay. All credit to the one who made the excellent spitfire cockpit in the first place.

Feel free to use it if you like

5462

avidflyer
Nov-03-2013, 14:32
Thank you for this great Tool, now I am able to use Clod with my Simpit.

But unfortunately Iam not able to bring the instruments in the size to fit:-) behind my bezels - so is anyone out there who can make them resizeable and moveable?


http://theairtacticalassaultgroup.com/forum/images/smilies/geek.gif[/url]

But in any case i like to thank you.

best regards

SG1_sandokito
Dec-02-2013, 08:34
Hi all, this is my first He111 Template.

When i finish the template, y go to put link to dowload.

6073

SepiaX
Dec-08-2013, 07:49
You can use Background and Foreground value for any item like this:
Class = Radial gauge;
Caption = Altimeter;
...
Background = metal1.bmp; // Only 32 bit BMP in ARGB order
BackgroundFitMode = Center; // NoFit, Center (default), Stretch, Scale, Fill
Foreground = FG.bmp;
ForegroundFitMode = Center;

Inputs{
Alt10000Ft{
ParamType = I_Altitude
...

Also you can use Bitmap value for needles:
...
Needle{
Bitmap = Needle.bmp;
Width = 10;
CenterY = 60;
Length = 70;
}
...

5194
But FPS will not be good because it does not use hardware acceleration.
On my i3 with all spitfire gauges using bitmaps it was completely unusable.


No documentation, sorry. My English is not good enough for that.

It can achieve a transparent background? If you please help.
Thanks
"Pardon my English"

AKA_Sully
Dec-10-2013, 13:43
NP .....Got it sorted .....

Fehler
Dec-15-2013, 04:23
Has anyone made one for the Blenheim?

AKA_Sully
Dec-15-2013, 11:17
The only two I've seen are for the Spit and the 109 ..... The spits works for the Hurri as well. S~

skunk160
Dec-18-2013, 01:54
this is awesome:thumbsup:, I just wish I could get it running.

I can get it to run on a 2nd screen in test mode, but not in game

anyone care to explain? or is there a read me anywhere

thanks

I'm in the middle of a rebuild :)

6300

Fehler
Dec-18-2013, 02:23
Skunk,

I never found a readme file either. All I did was start the program, select the profile (Spitfire IIa) and then start the game. Once it recognizes CLoD running, it populates the data.

skunk160
Dec-18-2013, 11:49
user error and too impatient :IAG:

works so well, no fps overhead

Flappie
Dec-18-2013, 13:21
Hello. I'm desperately trying to use the leds of my G940 to display some CoD info (booster on/off, gear out/in, lights on/off, engine on/off...). I think I could make good use of this tool. Is there a way to collect more info ? Like boolean things ?

EDIT: I found the C_Undercarriage info, but it doesn't show what the cockpit displays. It equals 2,0 when I start opening the gears, but its value doesn't change once the gear is fully opened. So, is there a way to get the exact info that makes the cockpit to display one, then two green lights, or one then two red lights ?

EDIT2 : found it, A_Undercarriage, with its two values (1,00 = gear out, 0,00 gear in)

Fehler
Dec-18-2013, 19:23
EDIT2 : found it, A_Undercarriage, with its two values (1,00 = gear out, 0,00 gear in)

If I am not mistaken, the planes that have a neutral position for the undercarriage (Hurricane for example) have three values; 0, 1.00, and 2.00. That's the reason why the graphic doesn't display the Hurricane properly when the Spit IIa template is used.

I am trying to figure out how to rectify that, but there is a great deal to this programming I do not understand.

Fehler
Dec-25-2013, 08:24
OK, did a little work on the Hurricane pit. Here is a link: https://www.dropbox.com/s/sbgucsn5mbr4ywb/Hurricane.rar

I made the fuel gauge and undercarriage indicator to look and act like the ones in the Hurricane cockpit. I also added a couple of the minor "Hurricane only" features. All this was based off the original Spit coding.

Oh...

If anyone knows how to turn the polygons in the Undercarriage Indicator to rounded rectangles, let me know. I am not the best at coding this stuff...

I have started work on the Blenheim and I'm about 40% done. I will get that out to your guys as soon as it's done.

Cheers!

9./JG52 Ziegler
Dec-27-2013, 10:59
Can I use a laptop for second monitor with the idisplay app or is it only for "mobile devices?

Fehler
Dec-29-2013, 05:48
OK, here is the Blenheim.

There is one issue: For some reason, the RD_IL2CloDTF30.exe file does not read the bomb sight data when you first start up the plane. You will see a couple of errors. But after you cycle through the bombardier seat, the errors go away, and the data appears correctly. That way, you can increase or decrease your bomb data from the pilot seat and get a readout. It helps a lot! Also, when you cycle your cowl flaps, the RD_IL2CloDTF30.exe file only reads one flap, so make sure you visually inspect your airplane's cowl flaps or risk blowing your engine.

If you find anything else that needs fixing, let me know. I am still looking forward to someone explaining how to turn a square polygon into a rounded rectangle... :grrr: :-)

http://i640.photobucket.com/albums/uu125/JV44Fehler/Blenheim2.jpg

Here is the link to the file. Just drop it into your "Cockpits" folder... https://www.dropbox.com/s/ebz0eo2usupe5ew/BlenheimIV-v1.rar

Skoshi_Tiger
Dec-29-2013, 17:58
Fehler, Thank you very much!

Have downloaded and will try it out today.


Cheers!

Fehler
Dec-31-2013, 21:06
Hey, no problem Skoshi!

I think I will start on the BR20 next, but I have to actually learn to fly it first! LOL

maquina
Jan-11-2014, 06:24
Excuse me Fehler, I'm Maquina, the one who tried vc in his Pipo M9.

It seems that the links to your hurricane and blenheim cockpits aren't ok.

Could you do something? I'm really interested. Could't fly Cod without Vc anymore!


By the way, I've a second Cod installation for the "MALTA" mod, but as it is not 4.0 patched VC doesn't work.

Does anybody knows if VC will work with the stock version of the sim in the future?

Thanks to everybody!

Fehler
Jan-11-2014, 12:51
Excuse me Fehler, I'm Maquina, the one who tried vc in his Pipo M9.

It seems that the links to your hurricane and blenheim cockpits aren't ok.

Could you do something? I'm really interested. Could't fly Cod without Vc anymore!


By the way, I've a second Cod installation for the "MALTA" mod, but as it is not 4.0 patched VC doesn't work.

Does anybody knows if VC will work with the stock version of the sim in the future?

Thanks to everybody!

There seems to be something wrong with the Dropbox service right now. They posted about it on their web site, and hopefully it will be back up and running in the next day or two. In the mean time, if you shoot me a PM with your email address, I can send them to you directly.

Also, unfortunately, VC will not work with the game if it is not patched to 4.0. I have no idea if Team Fusion is going to make previous patches compatible with this, but I seriously doubt it. They just have way too much on their plate right now.

Anyways mate, shoot my a PM and I will EMail those pits to you. :)

maquina
Jan-12-2014, 04:04
Wow, thank you very much Fehler!

56RAF_klem
Jan-12-2014, 07:54
Hi Guys,

This is really cool but I wonder if anybody can help me and save me a lot of time digging into this as I have a lot of stuff on just now.

I have a Samsung Note 8 and want to display the instruments I have picked off of Mattweich's display. I don't now if its possible to have a - and + button just above each compass so I can set them by touch but that would be really nice. The attached image is dimensionally accurate, well it was when uploaded, the Tablet has a screen 6.75" x 4.25" (8" diagonal).

I will be getting the 'iDisplay' or 'Air Display' App for it.

At last I could have a full size cockpit view and a glance-down instrument panel :)

EDIT: Please see next post (2 down)

ATAG_Bliss
Jan-12-2014, 09:34
Sorry klem,

No help from me :D

But I did find this which has some download links from a Spanish squadron. Looks like they've been hard at making several templates.

See here: http://translate.google.com/translate?hl=en&sl=es&tl=en&u=http%3A%2F%2Fwww.escuadron69.net%2Fv20%2Fforo%2F index.php%3F%2Ftopic%2F57655-exportar-instrumentos-a-segundo-monitor%2F&anno=2&sandbox=1

(http://translate.google.com/translate?hl=en&sl=es&tl=en&u=http%3A%2F%2Fwww.escuadron69.net%2Fv20%2Fforo%2F index.php%3F%2Ftopic%2F57655-exportar-instrumentos-a-segundo-monitor%2F&anno=2&sandbox=1)

(http://translate.google.com/translate?hl=en&sl=es&tl=en&u=http%3A%2F%2Fwww.escuadron69.net%2Fv20%2Fforo%2F index.php%3F%2Ftopic%2F57655-exportar-instrumentos-a-segundo-monitor%2F&anno=2&sandbox=1) http://imageshack.us/a/img34/3359/rblu.JPG
http://imageshack.us/a/img811/8888/o6i7.jpg






(http://translate.google.com/translate?hl=en&sl=es&tl=en&u=http%3A%2F%2Fwww.escuadron69.net%2Fv20%2Fforo%2F index.php%3F%2Ftopic%2F57655-exportar-instrumentos-a-segundo-monitor%2F&anno=2&sandbox=1)

56RAF_klem
Jan-13-2014, 03:38
EDIT!

Dooohhhhh!

I didn't see the 'Select Monitor' drop down and Start buttons. I never looked beyond selecting a cockpit from the list. All the 'instructions' I found said start each App, start the game and voila!
:smash:

Working ok now, just got to resize a few instruments to suit.

56RAF_klem
Jan-15-2014, 07:32
Well I spent more time than I should have but here's a Spitfires Mk I & II VC for an Android 8" 1280 x 800 resolution. Can also be used for Hurricane. See attached piccies. Zip file attached. Add it under VC\Cockpits or VC-English\Cockpits.

NOTE it is the English version, i.e. decimals as . not ,

It should scale ok to 7", 9" and maybe even 10" if the original is VC too large.

I based it on the VC_English but I have changed some of the instruments to be more visible on the small screen (some Font sizes and colours, all needles are white).


EDIT2: New file attached with Brakes Gauge and Fuel Selector. Still like to know how to code touch buttons for adjusting Compass, Altimeter, etc.? Also how to set foreground for my Panel overlay with instrument cutouts (.png or .gif? .bmp doesn't seem to retain the cutouts)

TWC_SLAG
Jan-15-2014, 18:43
Is there somewhere one can download this...thats the thing i miss most about il2... having gauges on a separate screen with udp speed...would be great to have in CLOD

Do the checked boxes mean I can uncheck some, and just have those I want to display on a second monitor?

badfinger

OverDhill
Jan-15-2014, 21:10
Hey guys... love what you are doing. I also would love to see a UDP Speed type app for a networked PC. I use UDP Speed with Helios for my IL-2 1946 touchscreen now. Would love to get something like it for CLOD.

6907

Skoshi_Tiger
Jan-15-2014, 21:41
If anyone has made a Brakes gauge for the Spits I'd be interested in getting it.
The original Spitfire IIA gauges has a brakes guage. It's defined in the file _PCP file ( Pneumo container pressure)

6908

Can you cut and paste the config from there?

TWC_SLAG
Jan-16-2014, 08:37
Do the checked boxes mean I can uncheck some, and just have those I want to display on a second monitor?

badfinger

Clarification:

I guess those aren't checked boxes in the zip files (my old eyes again).

But, the question is still: can I delete those instruments I don't want? Are there any that must remain in order to have any show up on a second monitor?

badfinger

Skoshi_Tiger
Jan-16-2014, 08:56
Clarification:

I guess those aren't checked boxes in the zip files (my old eyes again).

But, the question is still: can I delete those instruments I don't want? Are there any that must remain in order to have any show up on a second monitor?

badfinger

If you want you could go into the cockpit file for the aircraft you want and comment out the entry for the instruments that you don't want.


Items{
/* MagneticCompass{
Left = 610;
Top = 520;
#Include(_MagneticCompass.ini)#
} */
Altimeter{
Left = 425;
Top = 310;
#Include(_Altimeter.ini)#
}
DirectionalGyro{
Left = 635;
Top = 310;
#Include(_DirGyro.ini)#
}
SlipTurn{
Left = 845;
Top = 310;
#Include(_SlipTurn.ini)#
}
IAS{
Left = 425;
Top = 100;
#Include(_IAS.ini)#
}

In the items section there is a block of code for each instrument displayed. If for instance I wanted to remove the magnetic compass I'd find the entry and place a start comment marker /* before it and place a close comment maker */ after the block of code as shown above.

Make a copy of the file first incase of problems.

All the best

TWC_SLAG
Jan-16-2014, 09:00
If you want you could go into the cockpit file for the aircraft you want and comment out the entry for the instruments that you don't want.


In the items section there is a block of code for each instrument displayed. If for instance I wanted to remove the magnetic compass I'd find the entry and place a start comment marker /* before it and place a close comment maker */ after the block of code as shown above.

Make a copy of the file first incase of problems.

All the best

Great.

Thanks,

badfinger

56RAF_klem
Jan-16-2014, 19:00
The original Spitfire IIA gauges has a brakes guage. It's defined in the file _PCP file ( Pneumo container pressure)

6908

Can you cut and paste the config from there?

Thanks Skoshi, I missed that.

I've replaced my original zip file with one including brakes and fuel lever. Now trying to place an overlay with instrument cutouts (png or gif) or else change background to same but then I'll have to add a black background to all instruments : (

OverDhill
Jan-18-2014, 10:02
Wow Matweich, I'm impressed, this is awesome! To my mind this renders my efforts to convert UDPSpeed as unnecessary, good work! :thumbsup:

The only problem I've had is the same as reported by Skoshi_Tiger: on startup it complains "0,01 is not a valid floating point number". The reason for this is that some of the ini files (although not all) are using comma (,) as the decimal separator. Using comma as the decimal separator is common in Europe, but doesn't work for all locales. It's very likely the problem is that the code is parsing the numbers using the users current locale. Which means 0,01 will parse fine if your locale has ',' as the decimal separator, sadly my UK English locale only accepts dot so "0,01" doesn't parse.

So .. for those other users who are getting this problem, here is an updated version that works with English locales. All I've done is change the .ini files so that they use dot (.) rather than comma for the decimal separator. It may well work with all locales, as I think '.' is a very standard decimal separator that is nearly always supported.

http://www.shackell.org.uk/files/VC-English.zip

I'm also going to work on a Bf-109 cockpit, the ini format looks easy enough to fathom.

Hey Tom any chance you could make your UDP Speed code available so maybe someone else could finish it. We really do need some client/server method and it seems a shame not to take advantage of the UDP Speed gauges that are already there and working. Thanks

TWC_SLAG
Jan-18-2014, 23:13
The readme doesn't say much.

Could someone give me the file string showing to where the zip file should be downloaded?

I have Airdisplay working on my iPad, after a" little" help from their support guy.

Thanks,

badfinger

56RAF_klem
Jan-19-2014, 02:51
The readme doesn't say much.

Could someone give me the file string showing to where the zip file should be downloaded?

I have Airdisplay working on my iPad, after a" little" help from their support guy.

Thanks,

badfinger

You can keep the VirtualCockpit folders anywhere you like, there is no 'install' process. Just Unzip it to somewhere then right-click VirtualCockpit.exe and 'Send' it to Desktop (makes a shortcut).

With Air Display running and your Tablet showing as a second monitor and displaying your desktop (or at least a part of it) do the following:

Run VirtualCockpit.exe from the Desktop icon. A VC 'control panel' will open on your PC monitor and you can select which cockpit profile to use from the list on the left hand side (there is only Spitfire IIa with the basic download but there are other 'large screen' profiles in this thread like the Bf109 and I think Blenheim and He111 which you can add as folders under the Cockpits folder. Also there is my SpitfiresI-II for a smaller screen version (1280x800). They will both show on a larger screen anyway. Actually they are not very different in pixels-size but mine has had resolution changed to match my Tablet and fonts/colours altered for readability on my physically smaller 8" Tablet (6.25" x 4.25").

Next, in the VC 'control panel', you select which monitor to display the cockpit pit on (presumably #2) and Note that you can also tick 'Scale to Monitor' but I haven't tried that. Finally click the Start button. The cockpit will appear on your Monitor #2 but to start with you will only get a red background and 'No Connection' until you are in-game and in a cockpit.

If you get the process wrong and the cockpit appears on your PC screen it will have replaced the control panel and you will not be able to select screen #2 so just close the PC VC application and start again.

The second screen will 'hold onto' the last cockpit used when you exit the plane but will change when you select a different profile and go into that cockpit.

Simples.

TWC_SLAG
Jan-19-2014, 18:29
You can keep the VirtualCockpit folders anywhere you like, there is no 'install' process. Just Unzip it to somewhere then right-click VirtualCockpit.exe and 'Send' it to Desktop (makes a shortcut).

With Air Display running and your Tablet showing as a second monitor and displaying your desktop (or at least a part of it) do the following:

Run VirtualCockpit.exe from the Desktop icon. A VC 'control panel' will open on your PC monitor and you can select which cockpit profile to use from the list on the left hand side (there is only Spitfire IIa with the basic download but there are other 'large screen' profiles in this thread like the Bf109 and I think Blenheim and He111 which you can add as folders under the Cockpits folder. Also there is my SpitfiresI-II for a smaller screen version (1280x800). They will both show on a larger screen anyway. Actually they are not very different in pixels-size but mine has had resolution changed to match my Tablet and fonts/colours altered for readability on my physically smaller 8" Tablet (6.25" x 4.25").

Next, in the VC 'control panel', you select which monitor to display the cockpit pit on (presumably #2) and Note that you can also tick 'Scale to Monitor' but I haven't tried that. Finally click the Start button. The cockpit will appear on your Monitor #2 but to start with you will only get a red background and 'No Connection' until you are in-game and in a cockpit.

If you get the process wrong and the cockpit appears on your PC screen it will have replaced the control panel and you will not be able to select screen #2 so just close the PC VC application and start again.

The second screen will 'hold onto' the last cockpit used when you exit the plane but will change when you select a different profile and go into that cockpit.

Simples.

Klem,

I have it working, and saw how to eliminate the guages I don't want. Can you tell me how to re-arrange those that I do want?

Thanks,

badfinger

Skoshi_Tiger
Jan-19-2014, 19:11
Klem,

I have it working, and saw how to eliminate the guages I don't want. Can you tell me how to re-arrange those that I do want?

Thanks,

badfinger

Here is my understanding of the process

the following is an exert from the cockpit.ini file


ControlPanels{

Default{

Width = 1420;
Height = 770;
Scale = 1;

BackgroundShape{
{Class = Text; Text = Supermarine Spitfire Mk IIa; Pos = 5/5; Font{Size = 8; Color = $FF404040}}
}

Font{
Name = #Const(DefFontName)#;
Size = 14;
Color = $FFFFFFFF;
}

Items{
MagneticCompass{
Left = 610;
Top = 520;
#Include(_MagneticCompass.ini)#
}
...
...
...
...
EngineControls{
Left = 0;
Top = 620;
#Include(_EngineControls.ini)#
}
}
}
}


to change the default display size you alter the width and height variable to the value you would like for your display

Width = 1420;
Height = 770;

Inside the Items block is the set up for each instrument. you can change it's location by altering the Left and Top variable to be any location you want.

MagneticCompass{
Left = 610;
Top = 520;
#Include(_MagneticCompass.ini)#
}


The layout is based on a Cartesian coordinates with 0,0 at the top left of the screen.

For each instrument there is an Include function with the name of the ini file that defines what that instrument looks like and how it behaves. These files are stored in the same directory as the cockpit.ini file

If you want to resize your instrument go into the instrument file and at the top is a section with the width and height of the instrument.


Class = Radial gauge;
Caption = Altimeter;

Width = 200;
Height = 200;


You may have to play around with the font size parameter to get it looking proper if you resize the instruments too much.

Hope it is of some use!

56RAF_klem
Jan-20-2014, 05:36
.......................................

If you want to resize your instrument go into the instrument file and at the top is a section with the width and height of the instrument.

...............................

A quicker way is to include a Scale as in:

MagneticCompass{
Left = 610;
Top = 520;
Scale = 0.85;
#Include(_MagneticCompass.ini)#
}

That reduces the size to 85% of the original. You can also enlarge with say Scale = 1.3;

You may not like the result so you may have to go into the Instrument .ini as Skoshi says. However some instrument.ini elements include dimensions like Radius 70 (dims are in pixels). Here are a couple from the Spitfire elevator trim scale inner and outer scale lines;
Outer{
Radius = 120;
RingWidth = 2;
RingColor = $FFA0A0A0;
Markers{Count = 9; Width = 3; Height = 5; Color = $FFFFFFFF; TextFormat = }
}
Inner{
Radius = 115;
RingWidth = 1;
RingColor = $FFA0A0A0;
Markers{Count = 5; Width = 2; Height = -10; Color = $FFFFFFFF; TextFormat = }
}

If you reduce the size of the instrument from say 200x200 to 150x150 the 120 and 115 Radius of those lines may be too large for the reduced size instrument so you may have to change several dimensions too.

Try Scaling it first.

Skoshi_Tiger
Jan-20-2014, 09:52
This is what I like about this stuff! I learn something new every day! :thumbsup:

Cheers and thanks!

TWC_SLAG
Jan-20-2014, 11:34
A quicker way is to include a Scale as in:

MagneticCompass{
Left = 610;
Top = 520;
Scale = 0.85;
#Include(_MagneticCompass.ini)#
}

That reduces the size to 85% of the original. You can also enlarge with say Scale = 1.3;

You may not like the result so you may have to go into the Instrument .ini as Skoshi says. However some instrument.ini elements include dimensions like Radius 70 (dims are in pixels). Here are a couple from the Spitfire elevator trim scale inner and outer scale lines;
Outer{
Radius = 120;
RingWidth = 2;
RingColor = $FFA0A0A0;
Markers{Count = 9; Width = 3; Height = 5; Color = $FFFFFFFF; TextFormat = }
}
Inner{
Radius = 115;
RingWidth = 1;
RingColor = $FFA0A0A0;
Markers{Count = 5; Width = 2; Height = -10; Color = $FFFFFFFF; TextFormat = }
}

If you reduce the size of the instrument from say 200x200 to 150x150 the 120 and 115 Radius of those lines may be too large for the reduced size instrument so you may have to change several dimensions too.

Try Scaling it first.

Klem,

I'll try it tonight.

Thanks,

badfinger

skunk160
Jan-20-2014, 13:05
Got my new Rig 99% together and now LOVING Clod with TF4 and the external gauges are a dream come true!!

Thanks!!!

70267027

Ratcatcher
Jan-24-2014, 13:54
Hey all, first off I have to say what a fantastic addition this is, great job! However I do have a slight problem.

To begin, I will briefly explain my setup and then my problem...

I have 3x24" monitors running in eyefinity. I have an additional 4th monitor for the instruments, this is running at 1440x900. Before I start the game everything is running perfectly ( the monitors are scaled correctly and the instrument screen is centered on the 4th Monitor ).

When I run the game the 4th monitor continues to display everything centered ( so far so good! ), however when I launch a mission and actually go into the cockpit the 4th monitors displays gets "kicked" down about 4cm. Everything is working ok and the instruments are displaying the correct values, its just the display has moved down the screen leaving about 10cm of my desktop background showing on the 4th monitor before the instruments are rendered.

If I come out of the mission the 4th monitor immediately reverts back to being perfectly centered.

Any advice please?

**EDIT**
Managed to sort it. I changed my desktop resolution to match the ingame res ( from 5760x1200 to 5040x1024 ) am very very happy :)

56RAF_klem
Jan-24-2014, 15:23
Hey all, first off I have to say what a fantastic addition this is, great job! However I do have a slight problem.

To begin, I will briefly explain my setup and then my problem...

I have 3x24" monitors running in eyefinity. I have an additional 4th monitor for the instruments, this is running at 1440x900. Before I start the game everything is running perfectly ( the monitors are scaled correctly and the instrument screen is centered on the 4th Monitor ).

When I run the game the 4th monitor continues to display everything centered ( so far so good! ), however when I launch a mission and actually go into the cockpit the 4th monitors displays gets "kicked" down about 4cm. Everything is working ok and the instruments are displaying the correct values, its just the display has moved down the screen leaving about 10cm of my desktop background showing on the 4th monitor before the instruments are rendered.

If I come out of the mission the 4th monitor immediately reverts back to being perfectly centered.

Any advice please?

The original VC_Cockpit uses 1420 x 770 pixels. You are running 1440 x 900 so it is probably rendering at only 770 high, leaving 130 pixels untouched. When you open Virtual Cockpit and select the Monitor, click the 'Scale to fit monitor' checkbox. It may distort the instruments or simply move them a little.

Other options:

Go into the Cockpit.ini file and change the width and height to suit your monitor. e.g.

ID = SpitfireIIa;
Caption = Supermarine Spitfire Mk IIa;
DeviceLinkClass = IL2_CloD_TF30;

ControlPanels{

Default{

Width = 1420;
Height = 770;

Scale = 1;

Probably the instruments will no longer be centred but should have the same basic layout.
With that option you could go through the Cockpit.ini and reposition each instrument by changing the Left = and Top = pixel values. The nice thing is you can select your aircraft so as to display the instruments, hit Esc back to the map room but don't deselect the aircraft (map room eases the load on the PC), ALt+Tab to desktop where you can display the Cockpit.ini file and the VC control panel, edit the Cockpit.ini Left & Top values, click on that cockpit profile in the VC CP and the instrument display on your 'instruments' monitor will update with the new positions. Same for any changes you make in an [insrument].ini.

Another option in the Cockpit.ini is to change the Scale = 1; to = 1.014 to match the width and still have some height not covered, or = 1.17 which should solve the height but you will lose some off the left and right sides.

Play with these and see which you prefer.

Ratcatcher
Jan-24-2014, 17:55
The original VC_Cockpit uses 1420 x 770 pixels. You are running 1440 x 900 so it is probably rendering at only 770 high, leaving 130 pixels untouched. When you open Virtual Cockpit and select the Monitor, click the 'Scale to fit monitor' checkbox. It may distort the instruments or simply move them a little.
Play with these and see which you prefer.

Hi, Thanks very much for taking the time to reply.

I did sort it ( please see orginal post - edit ) but the info you have provided will be very useful for future reference.

Cheers

Rat

OverDhill
Jan-28-2014, 09:46
Still hoping to see a client/server version for my networked PC running a 24" touchscreen.

Vencejo
Jan-28-2014, 10:42
Hi,
Is´t possible to use a different language to c# for import data?

maquina
Feb-15-2014, 07:37
Still hoping to see a client/server version for my networked PC running a 24" touchscreen.

Hi OverDhill, nice to see you here!

I think it's not necessary a client/server version, because with a modern computer there is no need to use a client/server at all.

That network was necessary to use UDP Speed, though I've read it is also supported on the same computer.

If you want to use the client/server structure of your cockpit I'would try with an app like idisplay, that connects two devices (PC - tablet) and makes the tablet into a 2n virtual monitor. Surely it can be used also to engage two PC' s, one acting as a virtual display for the other :salute:

56RAF_klem
Feb-21-2014, 02:50
You can use Background and Foreground value for any item like this:
Class = Radial gauge;
Caption = Altimeter;
...
Background = metal1.bmp; // Only 32 bit BMP in ARGB order
BackgroundFitMode = Center; // NoFit, Center (default), Stretch, Scale, Fill
Foreground = FG.bmp;
ForegroundFitMode = Center;

Inputs{
Alt10000Ft{
ParamType = I_Altitude
...

Also you can use Bitmap value for needles:
...
Needle{
Bitmap = Needle.bmp;
Width = 10;
CenterY = 60;
Length = 70;
}
...

5194
But FPS will not be good because it does not use hardware acceleration.
On my i3 with all spitfire gauges using bitmaps it was completely unusable.


No documentation, sorry. My English is not good enough for that.

Hi Matweich.

I have moved away from my Tablet to a spare 1680x1050 screen. VC works just fine but I am trying to set a cockpit panel background created from a cockpit screenshot.

I have created _panel.ini as:-

======================
Class = Indicator;
Caption = Panel;

Width = 1680;
Height = 1050;

Background = SpitIIa_panel.bmp; // Only 32 bit BMP in ARGB order
BackgroundFitMode = Center; // NoFit, Center (default), Stretch, Scale, Fill
======================

The .bmp is a cropped cockpit screenshot, resized to 1680 x 1050 in Paint.net and just Saved.

It is in Cockpit.ini as:

===================
Panel{
Left = 0;
Top = 0;
#Include(_panel.ini)#
}
====================

All the SpitIIa gauges still show up but I get error message at bottom left saying

Panel: M_Random - no data available.

Any idea what I am doing wrong?

matweich
Feb-21-2014, 04:10
Hi Klem.

I think problem is here:
Class = Indicator;
Caption = Panel;

Indicator class requires input parameter (ParamType and ParamSubtype values). M_Random.0 is used when this values are not specified.
Use Panel class to solve this problem or set background for ControlPanel (in Cockpit.ini) like that:
...
ControlPanels{

Default{

Width = 1680;
Height = 1050;

Background = SpitIIa_panel.bmp; // Only 32 bit BMP in ARGB order
BackgroundFitMode = Center; // NoFit, Center (default), Stretch, Scale, Fill
...

matweich
Feb-21-2014, 04:22
Hi,
Is´t possible to use a different language to c# for import data?

Hi.
You can use any language that can work with named shared memory.
Here (http://msdn.microsoft.com/en-us/library/windows/desktop/aa366551(v=vs.85).aspx) is C++ sample (see "Second process" chapter).

hannibal
Feb-21-2014, 15:32
any word or updates about a client/server version?
im dying to run this utility on a second PC..

56RAF_klem
Feb-21-2014, 17:55
Hi Klem.

I think problem is here:
Class = Indicator;
Caption = Panel;

Indicator class requires input parameter (ParamType and ParamSubtype values). M_Random.0 is used when this values are not specified.
Use Panel class to solve this problem or set background for ControlPanel (in Cockpit.ini) like that:
...
ControlPanels{

Default{

Width = 1680;
Height = 1050;

Background = SpitIIa_panel.bmp; // Only 32 bit BMP in ARGB order
BackgroundFitMode = Center; // NoFit, Center (default), Stretch, Scale, Fill
...

Many thanks matweich, that worked just fine.

I have almost finished my Spitfire VirtualCockpit with a cockpit background - looks great, see attached :)

If I can try your patience one more time I am trying to replace the simple bitmap images for Flaps Up/Down, Magneto Switches and Fuel Lever with cockpit images. How would I display them in the instrument.ini, like the _FlapsIndicator.ini:

============================
Class = Indicator;
Caption = Flaps;

Width = 60;
Height = 120;


ParamType = C_LandingFlap;
MinValue = 0;
MaxValue = 1;

Ranges{
Down{
MinValue = 0.5;
MaxValue = 1;
>>>code to display the FlapsDn.bmpx image<<<<
}
}
Up{
MinValue = 0;
MaxValue = 0.5;
>>>code to display the FlapsUp.bmpx image<<<<
}
}
}
=================================

hannibal
Feb-21-2014, 21:30
Hey ATAG_Colander..

my C is really rusty, and i dont have a compiler...

if you know something about the code you wrote,
do you know anything about the functions TcpListner and AcceptTcpClient?
I was reading and i read about needing a TcpListener object to act as the server. The TcpListener object would listen for incoming connections on the specified port. You can use the .AcceptTcpClient method to establish a new connection.

http://msdn.microsoft.com/en-us/library/system.net.sockets.tcplistener.accepttcpclient%28v =vs.110%29.aspx

Btw, if anyone wants to try to configure this, i also suggest that you set 10.0.0.1/255.255.255.0/10.0.0.2 for the server and 10.0.0.2/255.255.255.0/10.0.0.1 for the client, because in my past experience in setting up virtual panels on a second PC on DCS World, this ip address allow the computers to connect to each other to establish a home network, any other address, it will deem the connection as "un-identified"...

hope this info helps someone... im still researching

matweich
Feb-23-2014, 07:44
Hi Klem!
Your cockpit looks great!
To use images for indicators you have to download new version of VC from here (https://www.dropbox.com/s/eczwm9lwvkpmvw0/VC%202014-02-23.ZIP) and set Bitmap and BitmapFitMode values in Range section of indicator:
...
Ranges{
Down{
MinValue = 0.5;
MaxValue = 1;
Shape{
{Class = Polygon; Color = $FF808080; LineWidth = 1; Points = 12/98, 48/98, 48/88, 12/88}
}
Bitmap = FG.bmp;
BitmapFitMode = Scale;
}
Up{
MinValue = 0;
MaxValue = 0.5;
Shape{
{Class = Polygon; Color = $FF808080; LineWidth = 1; Points = 12/40, 48/40, 48/50, 12/50}
}
Bitmap = metal1.bmp;
}
}
...
You can see Flaps indicator in included test Spitfire cockpit as a sample.

Also new version have client/server capabilities but there are some problems right now (very unstable update rate and other) so I have some work to do.

matweich
Feb-23-2014, 07:53
any word or updates about a client/server version?
im dying to run this utility on a second PC..
It's not ready yet but you can test it (see download link in previous post). Expect some bugs and poor update rate.

hnbdgr
Feb-24-2014, 04:44
Hi Gents,

I've noticed Virtual cockpit causes a noticeable fps drop for me..., is there a solution for this? also if this isn't the place to discuss this my apologies.

badger

56RAF_klem
Feb-24-2014, 06:18
Hi Klem!
Your cockpit looks great!
To use images for indicators you have to download new version of VC from here (https://www.dropbox.com/s/eczwm9lwvkpmvw0/VC%202014-02-23.ZIP) and set Bitmap and BitmapFitMode values in Range section of indicator:
...
Ranges{
Down{
MinValue = 0.5;
MaxValue = 1;
Shape{
{Class = Polygon; Color = $FF808080; LineWidth = 1; Points = 12/98, 48/98, 48/88, 12/88}
}
Bitmap = FG.bmp;
BitmapFitMode = Scale;
}
Up{
MinValue = 0;
MaxValue = 0.5;
Shape{
{Class = Polygon; Color = $FF808080; LineWidth = 1; Points = 12/40, 48/40, 48/50, 12/50}
}
Bitmap = metal1.bmp;
}
}
...
You can see Flaps indicator in included test Spitfire cockpit as a sample.

Also new version have client/server capabilities but there are some problems right now (very unstable update rate and other) so I have some work to do.

Again, many thanks matweich,

I've finished my Spitfire panels and created a complete VC folder structure to include them. It is the new folder structure from your last post to me but only contains the Spitfire panel folders to keep the file size down. Other existing cockpit folders can be added as usual. zip file attached.

It is named Spitfire IIa but can be used for any spitfires really and even the Hurricane. There are two versions:

'Hi Panel'. This is the first one I made and stretches from the bottom of the front windscreen to the bottom of the instrument panel. I had to locate the engine controls, Mag Compass and Fuel cock on the instrument panel. However, it didn't suit my personal View preferences so I made a 'Lo Panel' from it. This first one may still be of interest to some guys.

'Lo Panel'. This one stretches from just above the Flaps control/gunsight adjusters (not animated) down to below the instrument panel where the Mag Compass and Fuel cock are located. The instruments are raised quite a bit for easier viewing. I use 'Normal' cockpit view, zoomed in until bottom half of top instruments are cut off.

The following controls are animated (well, they have 2 positions):- Flap Control, Magneto Switches, Fuel cock. Also of course the original engine controls. AmpereMeter has been added.

It is set in 1680x1050 so remember to tick 'Scale to monitor' if yours isn't.

Hope some of you enjoy it.

EDIT: APOLOGIES, there was an error in the _FuelTankSelector.ini

Attachment updated but if you don't want to download it all again just paste the following into the file /Cockpits/SpitfireIIa HiPanel/_FuelTankSelector.ini to replace everything in there and /Cockpits/SpitfireIIa LoPanel/_FuelTankSelector.ini (not the ========================= lines).

================================================== ===
Class = Indicator;
Caption = Fuel Tank Selector;

Width = 60;
Height = 120;



ParamType = C_FuelTankSelector;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 1;

Ranges{
Down{
MinValue = 0;
MaxValue = 0.5;
Shape{
}
Bitmap = FuelLeverOn.bmpx;
BitmapFitMode = Scale;
}
Up{
MinValue = 0.5;
MaxValue = 1;
Shape{
}
Bitmap = FuelLeverOff.bmpx;
BitmapFitMode = Scale;
}
}

============================================

56RAF_klem
Feb-25-2014, 16:37
Forgot to add screenshots.

Vencejo
Feb-26-2014, 05:52
Hi.
You can use any language that can work with named shared memory.
Here (http://msdn.microsoft.com/en-us/library/windows/desktop/aa366551(v=vs.85).aspx) is C++ sample (see "Second process" chapter).

A big thanks Matweich :salute:

hannibal
Feb-27-2014, 00:34
It's not ready yet but you can test it (see download link in previous post). Expect some bugs and poor update rate.

Im going to try this out on a secondary PC tomorrow..

101ECV_GADGET
Mar-02-2014, 03:53
Any atempt to convert VC in a tactile screen application?
That would be rearry realy great

Fehler
Mar-02-2014, 06:56
Someone was already working on a He-111 cockpit. Does anyone know if it was ever completed? I cannot find a link for download.

I completed the Hurricane and the Blenheim pits. Another person completed the Bf-109 pit (not sure for which variant)

Hurricane:
Click Here (https://www.dropbox.com/s/sbgucsn5mbr4ywb/Hurricane.rar)

Blenheim:
Click Here (https://www.dropbox.com/s/ebz0eo2usupe5ew/BlenheimIV-v1.rar)

I have been very busy at work and not finding much time to work on fun stuff. As soon as I am able to complete the BR-20, I will post it.

hnbdgr
Mar-04-2014, 12:10
Hi All,

Does anyone else experience a FPS drop when running VC?

X-Raptor
Mar-06-2014, 14:29
Hi all, some questions and help calling to any Expert here about devicelink.

I'm a novice about CLOD and devicelink, but I'm reading with great interest about this feature to use with a TABLET in order to read better the AC instruments panel.

Now I would like to buy a TABLET (may be 8" inches display) in order to apply this feature.

My question is: I read here that I have to apply a APP to the PC named "VC", then I have to apply another APP like "AIR-DISPLAY 2" to the tablet (?) .. or into PC again (?) . then I have to connect VIA WI-FI the tablet with my modem/router PC and launch the game. is this all procedure correct?

Another 2 big doubt/questions are: which kind of O.S. does have the TABLET to use this feature devicelink: with Android O.S.? ..or WINDOW O.S. ?.. or a APPLE/mac one? and what resolution must have the display (considering a 8" screen) ?

Thank you in advance to everyone about clarification.

56RAF_klem
Mar-06-2014, 15:31
Hi all, some questions and help calling to any Expert here about devicelink.

I'm a novice about CLOD and devicelink, but I'm reading with great interest about this feature to use with a TABLET in order to read better the AC instruments panel.

Now I would like to buy a TABLET (may be 8" inches display) in order to apply this feature.

My question is: I read here that I have to apply a APP to the PC named "VC", then I have to apply another APP like "AIR-DISPLAY 2" to the tablet (?) .. or into PC again (?) . then I have to connect VIA WI-FI the tablet with my modem/router PC and launch the game. is this all procedure correct?

Another 2 big doubt/questions are: which kind of O.S. does have the TABLET to use this feature devicelink: with Android O.S.? ..or WINDOW O.S. ?.. or a APPLE/mac one? and what resolution must have the display (considering a 8" screen) ?

Thank you in advance to everyone about clarification.

I think this thread split into two topics: 1. a "device link" to connect to another PC and pass CoD instrument and controls data to it and 2. the simple question of using a second screen attached to your gaming PC to display instruments. In both cases the data comes from the same output parameters provided by CoD.

In your case you are talking about using a Tablet as a second screen. There are two ways to get a second screen on your gaming PC, either simply plug another monitor into the second video output of your video card or use a couple of applications (software) to connect your Tablet as a second monitor. So, first lets get the Tablet connected. Here is where you need the "Air Display" App on your Tablet (or "iDisplay" App for a MAC Tablet although I think Air Display works on the Mac devices too). Next you need the PC application which you will find is a free download where you buy your Tablet App from. Install the Tablet App on your Tablet and the PC application on your PC. Now start the Tablet App and then start the PC app and the PC App will find the Tablet and "connect it" as a second screen. It connects over your home network Wifi, it is not a wired connection. OK, so far you have connected a Tablet as a second screen instead of simply plugging a second monitor into your video card.

Getting the instruments onto a second screen is a separate matter. That is where you need the VC application (software) on your PC. You don't 'install' it, you just unzip it to a folder of your choice. When you start it you can select which cockpit layout you want to use, select the monitor you want to display it on (probably #2), select 'Scale to monitor' so that if the layout is for a different resolution to your Tablet/second monitor it will fit it as best it can, then click on Start. Odd messages may appear on the second screen until you are in a cockpit. Now when you go into a CoD cockpit it will display the instruments on the second screen.

Things to be aware of (I'm putting this here to save coming back again later):
1. I gave up on using my Samsung Note 8 Tablet because it kept losing the Wifi connection. Just a warning. I now use an old monitor plugged into the second socket on my video card (see attached image).
2. The cockpit selections are kept in their own folders under a /Cockpits/ folder where the VC software was unzipped to and it will already contain some depending on which download you take from this Thread. You can just add more cockpit folders into that Cockpits folder for them to appear on the list and you can get them from other posts in this Thread. You'll see what I mean when you unzip it.
3. If you 'Scale to monitor' you may get squished layouts but someone here is likely to be able to help you with that. If you don't 'Scale...' and your screen isn't the same resolution as the layout design it can either partly disappear off the screen or simply be smaller than the entire screen. Suck it and see.
4. Actually its not difficult to create your own simple layouts if you look carefully at how other people have done it.

Hope that helps.

X-Raptor
Mar-06-2014, 17:59
thank you for your detailed explanation Klem, all is quite clear, just one thing: you mentioned that you tried to use your samsung tablet but it has problem of continuos disconnections to wi-fi .. so I ask if you think is a problem of samsung or may be this is a common problem with ALL tablet?? (may be other people reading this post and using a tablet can give their feedback about.

And what about S.O. of the tablet may be better using a apple one ? or a android one? thank you.

hnbdgr
Mar-07-2014, 03:43
I found that having VC run on a tablet is a bit of hit and miss. AirDisplay seems to have a mind of its own, sometimes works sometimes doesn't.

Dropping wifi signal - this can and will happen to some tablets. It's either OS related (bad update) and sometimes there's a fault with the device on a hardware level. Remember that tablets are relatively young technology and are not as flexible when it comes to fixing(you can't poke around the tablet OS as easily as you would on Win,Mac, Linux) . Sometimes all you need is to set up a static IP on your network and it will work, other times it will keep dropping every 10 minutes no matter what. Generally you can't use a cable to stream output to a tablet, it works vice versa(connect tablet to a telly) but not into the tablet.

A small 2nd hand monitor is a good solution as it's connected directly to your GPU, go with that if you can.

Another option:

Arduino LCD or TFT module (https://www.google.co.uk/search?q=arduino+tft+lcd+screen&safe=off&espv=210&es_sm=122&tbm=isch&tbo=u&source=univ&sa=X&ei=c4UZU-6VAcKrhQfUl4GABw&ved=0CJMBELAE&biw=1920&bih=965#facrc=_&imgdii=_&imgrc=MgL8nZXtfxAlYM%253A%3BRrHdnzCvx6ZtJM%3Bhttp% 253A%252F%252Fwww.geeetech.com%252Fblog%252Fwp-content%252Fuploads%252F2012%252F04%252FIMG_3.jpg% 3Bhttp%253A%252F%252Fwww.geeetech.com%252Fauthor%2 52Fjack%252F%3B1000%3B667). I'm currently looking for a tutorial on how to make this work with a pc as a second monitor. I only need 2-3 critical systems to show (pitch, wtemp, ata) and the size is compact.

Another issue to keep in mind - fps might drop when using VC - Can people chime in please to confirm whether it has affected their performance and whether there is a solution to this?

hope this helps!

badger

56RAF_klem
Mar-07-2014, 05:00
thank you for your detailed explanation Klem, all is quite clear, just one thing: you mentioned that you tried to use your samsung tablet but it has problem of continuos disconnections to wi-fi .. so I ask if you think is a problem of samsung or may be this is a common problem with ALL tablet?? (may be other people reading this post and using a tablet can give their feedback about.

And what about S.O. of the tablet may be better using a apple one ? or a android one? thank you.

The operating system is Android 4.1.2 (according to Samsung website but I guess the version could be updated). I know nothing about iPads.

I can't say if dropped connections are better or worse with other Tablets but I can tell you that the Tablet is only 6 feet away from my wireless router. Generally I am very happy with the Tablet but browsing and reading emails is not a 'streaming' process and it may only take a momentary problem to throw the connection. Actually what happens is that the main screen suddenly switches from CoD to desktop when the Air Display is interrupted or perhaps interfered with in some way. To be honest after missing a few dead-cert 109 shots because of it and realising that I had that old monitor sitting doing nothing - and that is is a much larger screen - I jumped ship and went to the monitor. The Tablet was a Christmas present and I was full of enthusiasm to use it any way I could (and I get a lot of general use out of it) but truthfully a second monitor is a much better idea for cockpit instruments. So I wouldn't let the decision to buy a Tablet be influenced by the idea of using it for CoD.

X-Raptor
Mar-07-2014, 13:39
Mmhh.. all this don't sound well after all..:( My enthusiasm is dropping down about TABLET use as 2nd monitor.. But in the meantime I've yet ordered one (onda v813) even to use it for my busness. i'll go to try it with airDisplay when it will arrive and I eventually come here again to tell feedback about. The choice of a 2nd monitor phisically connected is really a better choice as I can understand here.. but a 19"-17" one side to main monitor is really a little bit a desktop mess IMHO.. and a little one like the "lilliput" series (10") cost as purchasing a TABLET , at least here in Italy. :goofy

avidflyer
Mar-08-2014, 11:28
Great,

now i can dedicated my Pit to CLOD with a virtual Panel. Is there the possibiltity to make the Instruments resizeable and moveable? Ardunio Support is a dream to geht real Hardware to run like LED for gear or servos for instruments or switches. Thank you for make it possible for me to switch from IL 1946 to the mor detailed Cliffs of dover.

kind regrads Christian

hnbdgr
Mar-09-2014, 11:36
Great,

now i can dedicated my Pit to CLOD with a virtual Panel. Is there the possibiltity to make the Instruments resizeable and moveable? Ardunio Support is a dream to geht real Hardware to run like LED for gear or servos for instruments or switches. Thank you for make it possible for me to switch from IL 1946 to the mor detailed Cliffs of dover.

kind regrads Christian

I just wanted to say If you happen to make an arduino TFT or LCD work with this, can you post the tutorial? Or somebody else:))? many thanks!

X-Raptor
Mar-14-2014, 22:07
Just to say BIG THANK YOU for all suggestion found here about to set up my Devicelink with TABLET :

8152

..It work like a dream!! :)

now waiting to find how to insert cockpit contours of every plane

56RAF_klem
Mar-15-2014, 04:30
Just to say BIG THANK YOU for all suggestion found here about to set up my Devicelink with TABLET :

8152

..It work like a dream!! :)

now waiting to find how to insert cockpit contours of every plane

There are several examples of other cockpits in this thread, here's one I did for the Spitfires (and you can use it for Hurricane) when I was using my 8" 1200x600 Samsung Note 8:
http://theairtacticalassaultgroup.com/forum/showthread.php?t=3887&p=86074&viewfull=1#post86074

If you open any cockpit.ini file you will see how each instrument is positioned. If you need new instruments and don't know how to create them you can "borrow" missing instruments from other people's cockpits because each one can be scaled in the cockpit.ini file to suit your screen size and the whole screen can be scaled in VC to your Tablet. You may even be able to make new instruments, or modify existing ones, by looking carefully in each instrument .ini file to see how it is made. That's how I was able to make mine, I'm not a real coder. If you do, you may find Notepad++ more helpful than Windows Notepad because it numbers code lines and indicates correct bracketing.

Good luck.

X-Raptor
Mar-15-2014, 12:26
thank you sincerely Klem!! :thumbsup: I'll follow your precious suggestion here above and report my progress.. BIG Thank you again for you ever good help about this good stuff.

Roblex
Mar-16-2014, 18:05
I have tried to get this working with an Android Tablet but when I tried to use it as a second screen all I was getting was a black screen. I knew I was connecting OK because if I set it to 'mirror mode' my tablet would show my PC desktop and allow me to manipulate it. I then saw a post on the internet that seemed to suggest that the extended screen part of Air Display does not work without Aero so I changed to an Aero theme and suddenly it worked, I could drag things off my PC screen onto my tablet and I could run Virtual Cockpit while flying and all was rosy. I then came out and installed some of the extra cockpits shown on this thread and after that I could not get Air Display to work again. It is nothing to do with the changes to VC as I am failing to get as far as running VC, I am just back with the black screen on my tablet when I should be seeing the windows wallpaper.

Any thoughts? I have tried changing from an Aero theme to a basic windows one then back to Aero and I have tried rebooting both the tablet and the PC.

56RAF_klem
Mar-16-2014, 19:42
I have tried to get this working with an Android Tablet but when I tried to use it as a second screen all I was getting was a black screen. I knew I was connecting OK because if I set it to 'mirror mode' my tablet would show my PC desktop and allow me to manipulate it. I then saw a post on the internet that seemed to suggest that the extended screen part of Air Display does not work without Aero so I changed to an Aero theme and suddenly it worked, I could drag things off my PC screen onto my tablet and I could run Virtual Cockpit while flying and all was rosy. I then came out and installed some of the extra cockpits shown on this thread and after that I could not get Air Display to work again. It is nothing to do with the changes to VC as I am failing to get as far as running VC, I am just back with the black screen on my tablet when I should be seeing the windows wallpaper.

Any thoughts? I have tried changing from an Aero theme to a basic windows one then back to Aero and I have tried rebooting both the tablet and the PC.

1. Did you accidentally turn Aero off?
2. Do you mean it doesn't even show up as a running application? (Task bar or task Manager)
3. Did you only add Cockpits as sub-folders and nothing else.
4. Are you minimising VC because that will do it.

btw you shouldn't need to drag the cockpit to the Tablet, VC should display it there providing you selected it as the VC monitor.

Roblex
Mar-17-2014, 03:15
Nothing to do with VC. It is not even running. Before running VC, Air Display needs to be making my tablet work as a second screen and that is my problem. Someone told me a long time ago that CLOD does not like Aero so I have not had it running but as soon as I changed to an Aero wallpaper theme Air Display started working as it should and the screen on the Tab changed from black to the windows wallpaper and moving the mouse pointer off the right of my PC screen made it appear on my Tab. Once I had that then VC worked fine. Unfortunately it only worked once and now I cannot get back to that state. Mirroring my PC desktop onto my tab screen still works, it is just the extended screen mode that does not work.

stemar
Mar-20-2014, 03:29
You can keep the VirtualCockpit folders anywhere you like, there is no 'install' process. Just Unzip it to somewhere then right-click VirtualCockpit.exe and 'Send' it to Desktop (makes a shortcut).

With Air Display running and your Tablet showing as a second monitor and displaying your desktop (or at least a part of it) do the following:

Run VirtualCockpit.exe from the Desktop icon. A VC 'control panel' will open on your PC monitor and you can select which cockpit profile to use from the list on the left hand side (there is only Spitfire IIa with the basic download but there are other 'large screen' profiles in this thread like the Bf109 and I think Blenheim and He111 which you can add as folders under the Cockpits folder. Also there is my SpitfiresI-II for a smaller screen version (1280x800). They will both show on a larger screen anyway. Actually they are not very different in pixels-size but mine has had resolution changed to match my Tablet and fonts/colours altered for readability on my physically smaller 8" Tablet (6.25" x 4.25").

Next, in the VC 'control panel', you select which monitor to display the cockpit pit on (presumably #2) and Note that you can also tick 'Scale to Monitor' but I haven't tried that. Finally click the Start button. The cockpit will appear on your Monitor #2 but to start with you will only get a red background and 'No Connection' until you are in-game and in a cockpit.

If you get the process wrong and the cockpit appears on your PC screen it will have replaced the control panel and you will not be able to select screen #2 so just close the PC VC application and start again.

The second screen will 'hold onto' the last cockpit used when you exit the plane but will change when you select a different profile and go into that cockpit.

Simples.

Dear All,

I apologize if an answer of my question already exist, but I can't find it!

I follow the instruction above (Thanks to 56RAF_klem) but so far can't manage to get the things working!
What is my problem:

After starting the VC I got my second screen to black with sign "No connection" which is ok according to the instructions! Then I start the game (chose desired plane according to the cockpit profile), but when I start the mission my second screen turn to black and without any gauges! If I minimize (alt-tab) the game window - immediately on the second screen gauges appeared. If I maximize the game window - the second screen turn to black again!
What I have done wrong?

This is the first time I am trying VC! And I am using the last TF patch - 4.3!

Thank you in advance!

BR
Stemar

arvigna
Mar-20-2014, 08:18
hi ,

i 'm noob on VC , i try it yesterday , but a similar thing happen to me.
so,
be sure that your VC windows is maximize on the n°1 screen and you are on the plane ....

stemar
Mar-20-2014, 09:20
hi ,

i 'm noob on VC , i try it yesterday , but a similar thing happen to me.
so,
be sure that your VC windows is maximize on the n°1 screen and you are on the plane ....

Hi thanks for the reply!

Yes my VC window is active (maximized) on the main screen (1) and I try to be on screen 2 were i should have gauges and am in the cockpit but still can't get to get the gauges on!
I have suspicion:

can some one check in to the cockpit (text file in any of the cockpit folders) what is says in the beginning i have this:
ID = BF109E4N;
Caption = BF 109 E4N;
DeviceLinkClass = IL2_CloD_TF30; - i have suspicion that this should look like DeviceLinkClass = IL2_CloD_TF43;

Thank you in advance!

arvigna
Mar-20-2014, 14:08
no, it's work like this , i have the same.

i am not the best to help you ....:(

be sure all fonctions are selec

8406

56RAF_klem
Mar-20-2014, 14:31
Hi thanks for the reply!

Yes my VC window is active (maximized) on the main screen (1) and I try to be on screen 2 were i should have gauges and am in the cockpit but still can't get to get the gauges on!
I have suspicion:

can some one check in to the cockpit (text file in any of the cockpit folders) what is says in the beginning i have this:
ID = BF109E4N;
Caption = BF 109 E4N;
DeviceLinkClass = IL2_CloD_TF30; - i have suspicion that this should look like DeviceLinkClass = IL2_CloD_TF43;

Thank you in advance!

TF30 is OK
Not at my PC just now but ........
I sometimes get that to begin with. I think it is ok after I Alt+Tab a couple of times or when I click on the VC window before reselecting CoD from the task bar.

matweich
Mar-20-2014, 15:05
Hi thanks for the reply!

Yes my VC window is active (maximized) on the main screen (1) and I try to be on screen 2 were i should have gauges and am in the cockpit but still can't get to get the gauges on!
I have suspicion:

can some one check in to the cockpit (text file in any of the cockpit folders) what is says in the beginning i have this:
ID = BF109E4N;
Caption = BF 109 E4N;
DeviceLinkClass = IL2_CloD_TF30; - i have suspicion that this should look like DeviceLinkClass = IL2_CloD_TF43;

Thank you in advance!

Hi! Try to run CoD in pseudo fullscreen mode.

arvigna
Mar-20-2014, 19:01
i test all config : full screen , pseudo etc !!!
all works fine ....



another question : how to set a "transparent background please ?

stemar
Mar-21-2014, 01:54
Hi! Try to run CoD in pseudo fullscreen mode.

Hi,

I tried in pseudo and it works!!! But in pseudo I got another problem - huge stuttering in the game! So for the moment is better to have a smooth game than fancy gauges! I will keep trying to find some option!

arvigna
Mar-22-2014, 07:49
hello,

please , any answers ?

for how to set a transparent background please ,just see the gauges.?

it is possible or not ?

56RAF_klem
Mar-22-2014, 08:39
hello,

please , any answers ?

for how to set a transparent background please ,just see the gauges.?

it is possible or not ?

If you are using the 'bare' cockpit.ini without a background or foreground image (like a screen shot of the cockpit with holes for the instruments to show through) then you will get a black backgound. I don't know how to make it transpsrent. What are you trying to achieve with it?

arvigna
Mar-22-2014, 09:45
have the black background to be transparent , in my second screen to see other things in.


i am trying in lot of way but with echec.


:ind:

101ECV_GADGET
Mar-22-2014, 19:26
Maybe it is a silly question for some of you, programers, but as I can't program in Free Pascal I find this really disturbing

I am trying to simplify the altimeter in one of my panels, using a modern ONE-NEEDLE altimeter.
I got it working so far, but I would like several things:

1) The most important, to get the INTEGER rounded version of I_Altitude. A this time the Thousend feet unit changes when passing by the intermediate value, it means that 14400 ft is shown in the digits window as 14+(needle lecture), but 14600 ft is shown as 15+(needle lecture). Meanwhile I solved this partially by showing in the digits window also the hundreds of feet.

2) I would like to do separate lectures in the window for thousans andten of thousands, and/or if possible hundreds, so I can choose a different font size for each, smaller for the hundreds and keeping thousend units in teh same position all the time.

Thank you for your help. This is the code so far



Items{
ALT{
Class = Label;
Left = 50;
Top = 100;
Width = 100;
Height = 30;
Font{Size = 15}
}
AltitudeText{
Class = Text;
Caption = Altitude value;
BackgroundColor = $FF000000;
Left = 60;
Top = 55;
Width = 40;
Height = 30;
Format = 0;
Font{Size = 21; Color = $FFFFFFFF}
Input{
ParamType = I_Altitude;
Multiplier = 0,01;
}
}
00{
Class = Label;
BackgroundColor = $FF000000;
Left = 100;
Top = 60;
Width = 30;
Height = 20;
Font{Size = 16}
}
QNHText{
Class = Text;
Caption = Altitude value;
BackgroundColor = $FF000000;
Left = 85;
Top = 165;
Width = 30;
Height = 12;
Format = 0;
Font{Size = 10; Color = $FFFFFFFF}
Input{
ParamType = C_AltimeterPinion;
}
}

101ECV_GADGET
Mar-29-2014, 05:26
I already got it. Thank you



Class = Radial gauge;
Caption = Altimeter;

Width = 300;
Height = 300;

RingWidth = 1;

ForegroundShape{
{Class = Ellipse; Color = $FF000000; Center = 150/150; Radius = 3; LineWidth = 1; LineColor = $FF606060}
}

BackgroundShape{
{Class = Ellipse; Color = $FF000000; Center = 150/150; Radius = 150; LineWidth = 0; LineColor = $FF606060}
}

Inputs{
Alt100Ft{
ParamType = I_Altitude;
MinValue = -1000;
MaxValue = 1000;
Remainder = 1000;
StartAngle = -360;
EndAngle = 360;
Needle{
SpearWidth = 2;
Width = 10;
CenterY = 130;
Length = 50;
Color = $FFFFFFFF;
OutlineColor = $FF606060;
}
Scales{
Outer{
MinValue = -1000;
MaxValue = 1000;
Radius = 150;
RingWidth = 0;
Font{
Size = 24;
Style = ;
Color = $FFFFFFFF;
}
Markers{
Big{MinValue = 0; Count = 11; Width = 3; Height = 20; TextMultiplier = 0,01;}
}
CustomMarkers{
500{Value = 500; Text = ; Height = 20; Width = 3}
}
}
Inner{
MinValue = -1000;
MaxValue = 1000;
Radius = 130;
RingWidth = 0;
Font{
Size = 24;
Style = ;
Color = $FFFFFFFF;
}
Markers{
Small{MinValue = 0; Count = 51; Width = 2; Height = -15; TextFormat = ; Color = $FFFFFFFF;}
}
}
}
}
}

Items{
ALT{
Class = Label;
Left = 100;
Top = 150;
Width = 100;
Height = 50;
Font{Size = 20}
}

AltitudeText{
Class = Text;
Caption = Altitude value;
BackgroundColor = $FF000000;
Left = 100;
Top = 80;
Width = 70;
Height = 40;
Format = 0;
Font{Size = 30; Color = $FFFFFFFF; Align = Right;}
Input{
ParamType = I_Altitude;
Multiplier = 0,01;
Precision = 1;
}
}

00{
Class = Label;
BackgroundColor = $FF000000;
Left = 170;
Top = 85;
Width = 30;
Height = 25;
Font{Size = 20}
}

mb{
Class = Label;
Left = 100;
Top = 190;
Width = 100;
Height = 50;
Font{Size = 15; Color = $FF606060}
}

QNHText{
Class = Text;
Caption = Altitude value;
MinValue = 745;
MaxValue = 1100;
BackgroundColor = $FF000000;
Left = 125;
Top = 250;
Width = 50;
Height = 20;
Format = 0;
Font{Size = 15; Color = $FFFFFFFF}
Input{
ParamType = C_AltimeterPinion;
}
}
}

101ECV_GADGET
Apr-02-2014, 17:50
New question

How can I convert to BMPX other format images?
My CS7 do not even show 32 bit BMP on screen.

I have been searching the net with no solutions. Thank you

arvigna
Apr-02-2014, 18:58
just rename to bmp.

or / and download or /and use "pixelformer"

56RAF_klem
Apr-06-2014, 12:18
New question

How can I convert to BMPX other format images?
My CS7 do not even show 32 bit BMP on screen.

I have been searching the net with no solutions. Thank you

You can get the free PAINT.net and use the attached add-on

ATAG_Septic
Apr-07-2014, 21:04
Hi Chaps,

I can't believe how easy this was to set up! It works brilliantly!

Thanks very much to all the clever types for sharing their work on this.

Septic.:salute:

ATAG_Colander
Apr-07-2014, 22:22
New question

How can I convert to BMPX other format images?
My CS7 do not even show 32 bit BMP on screen.

I have been searching the net with no solutions. Thank you

GIMP is your friend.

101ECV_GADGET
Apr-09-2014, 17:56
thank you

hnbdgr
Apr-11-2014, 05:11
just a heads up: I was looking for a cheap lcd monitor for some time to use with clod instead of my second big monitor or an ipad ... I think i found it! cost is $31.99 USD

http://www.goverlay.com/content/lcdsysinfo/

you can get it from here: http://www.ebay.com/itm/LCDsysinfo-for-GOverlay-USB-2-8-TFT-LCD-Module-gamer-gadget-FPS-Hype-Smartie-/121106592717?ssPageName=ADME:X:AAQ:US:1123

now if I could just figure out how to use it with clod.... :)

hope this helps people out there looking for the same solution as I do!

EDIT: Ezequiel -the developer behind these will do a free plugin for it for Il2 Clod, but he needs a copy of the game! :) Mentioning it here in case some of you have a steam gift copy..? It would be great to have one to give to him.

TWC_SLAG
Apr-11-2014, 23:41
EDIT!

Dooohhhhh!

I didn't see the 'Select Monitor' drop down and Start buttons. I never looked beyond selecting a cockpit from the list. All the 'instructions' I found said start each App, start the game and voila!
:smash:

Working ok now, just got to resize a few instruments to suit.

Klem,

I, too, want to resize some instruments. I want to put just the compass and the DG on myiPad, and have them fill the screen. Do you know how to do this?

Thanks,

badfinger?

56RAF_klem
Apr-12-2014, 02:44
Klem,

I, too, want to resize some instruments. I want to put just the compass and the DG on myiPad, and have them fill the screen. Do you know how to do this?

Thanks,

badfinger?

Unzip the attached into your VC Cockpits folder. "RAF Compasses" should then appear in VC for selection.
Resolution: 1280w x 800h

Depending on your personal preferences:-
Layout is one above the other like in the cockpit. You can change this by editing Left and Top (positions the top left corner of the instrument) of each instrument listed in Cockpit.ini to place each instrument where you want it.
Resize (Scale) the whole thing to fit your iPad by adjusting the value of the bold italic part below
Then....
Resize (Scale) each instrument by adjusting the value of the the plain bold part below.

================================
Cockpit.ini:-
ID = RAF Compasses;
Caption = RAF Compasses;
Foreground = Panel.png;
DeviceLinkClass = IL2_CloD_TF30;

ControlPanels{

Default{

Width = 1280;
Height = 800;

Scale = 1;

BackgroundShape{

{Class = Text; Text = RAF Compasses; Pos = 0/0; Font{Size = 12; Color = $FFFFFFFF}}
}

Font{
Name = #Const(DefFontName)#;
Size = 14;
Color = $FFFFFFFF;
}

Items{
MagneticCompass{
Left = 355;
Top = 460;
Scale = 1.1;
#Include(_MagneticCompass.ini)#
}
DirectionalGyro{
Left = 425;
Top = 260;
Scale = 0.95;
#Include(_DirGyro.ini)#
}
}
}
================================

Hope it works ok

TWC_SLAG
Apr-12-2014, 14:29
Klem,

Changing the Scale makes the diameter of the dial larger, but doesn't change the size of the anything inside it. I'll play around with other settings, to see what affect they have. Part of the problem is eliminating the other instruments still leaves me with the same size panel. The other instruments just don't show up. I need to somehow separate the compass and DG, and put them in their own smaller panel. Then, I can change the resolution to make them the right size....I think.

Anyone out there know how to accomplish this?

Thanks for the .zip file, I now know where to make changes.

badfinger

No.401_Alpine
Apr-12-2014, 15:00
I'm afraid that I can't help you out on the resizing thing buddy.What I am in the process of doing is simply integrating a second 17'' monitor into my simpit to run the program and then cutting out the holes for the guages on a 1\16'' overlay.

56RAF_klem
Apr-12-2014, 15:20
Klem,

Changing the Scale makes the diameter of the dial larger, but doesn't change the size of the anything inside it. I'll play around with other settings, to see what affect they have. Part of the problem is eliminating the other instruments still leaves me with the same size panel. The other instruments just don't show up. I need to somehow separate the compass and DG, and put them in their own smaller panel. Then, I can change the resolution to make them the right size....I think.

Anyone out there know how to accomplish this?

Thanks for the .zip file, I now know where to make changes.

badfinger

Be clear. The first Scale you find in Cockpit.ini is for the overall size of the instrument panel although in VC you can select "Scale to fit monitor" instead and is probably the best idea.

When you use the Scale for each instrument ALL displayed items (needle, fonts etc) will be rescaled so they should all hang together for each instrument.

56RAF_klem
Apr-12-2014, 15:24
I'm afraid that I can't help you out on the resizing thing buddy.What I am in the process of doing is simply integrating a second 17'' monitor into my simpit to run the program and then cutting out the holes for the guages on a 1\16'' overlay.

Try this. Its for a Spitfire IIa but is perfect ok for any Spitfire and even the Hurricane if you can accept the Flaps indicator as a Spit type (shows down even if you only partially lower the Hurricane Flaps).

hnbdgr
Apr-26-2014, 17:28
Hi, I hope someone can help me out here... I'm having some trouble with RD_IL2CloDTF30.exe the executable that was packaged with VC. I can no longer see the window with data when I run it. I can see it in the task manager but there is no window... It worked fine until recently.

with TF 4.3 it worked fine, not sure about whether I've tried it with the hotfix

things that might have affected it - new net framework was installed & sound fix in registry was performed.

VC still works fine by itself but I really want to get RD_IL2CloDTF30.exe working...

memory dump file in case: https://dl.dropboxusercontent.com/u/14123055/RD_IL2CloDTF30.zip (https://dl.dropboxusercontent.com/u/14123055/RD_IL2CloDTF30.zip?dl=1)

fingers crossed somebody knows the answer...!:salute:

1lokos
Apr-26-2014, 17:33
Some pilot "anecdotes" (http://www.telegraph.co.uk/history/Britain_at_War_Readers__Memorie/4401793/Britain-at-War-Taken-prisoner-by-the-Germans-after-crashing-my-plane.html) say that P-8 compass needle have a portion (?) above the cross painted in red (1), hence the expression "red on red" (http://www.bharat-rakshak.com/IAF/History/1940s/TacHurriNotes.html) when this match with red "N".


Align compass grid lines with needle ensuring 'red on red' so as not to fly in the opposite direction to that desired and then uncage (unlock) the D. I. (directional gyro) and set it to agree with the compass and recage it.

If want use this, change in MagneticCompass.ini



Shape{
{Class = Ellipse; Color = 0; RingWidth = 0.5; Radius = 20; LineColor = $FFA0A040}
{Class = Line; Points = 0/-55, 0/-20; Color = $FFA0A040}
{Class = Line; Points = 0/-90, 0/-55; Color = $FFFF4040; Width = 3}
{Class = Line; Points = -10/-50, 10/-50; Color = $FFFFFFFF; Width = 3}
{Class = Line; Points = 0/55, 0/20; Color = $FFA0A040}
{Class = Line; Points = 0/90, 0/55; Color = $FFFFFFFF; Width = 3}
{Class = Line; Points = 55/0, 20/0; Color = $FFA0A040}
{Class = Line; Points = 90/0, 55/0; Color = $FFFFFFFF; Width = 3}
{Class = Line; Points = -55/0, -20/0; Color = $FFA0A040}
{Class = Line; Points = -90/0, -55/0; Color = $FFFFFFFF; Width = 3}
{Class = Line; Points = -65/-65, -14/-14; Color = $FFA0A040}
{Class = Line; Points = 65/-65, 14/-14; Color = $FFA0A040}
{Class = Line; Points = -65/65, -14/14; Color = $FFA0A040}
{Class = Line; Points = 65/65, 14/14; Color = $FFA0A040}
}


http://i59.tinypic.com/24d2bk1.jpg

The "N" and needle pointer change to red. In any case the actual "N" is blue...

(1) No evidence of this on P-8 pictures on Web... probable only a expression... Maybe "Needle on Red"...

Sokol1

Falco
Apr-26-2014, 18:14
Anybody working on a VC for the G50? :recon:

avidflyer
Apr-27-2014, 06:03
Hello,

Can someone help me how to setup vc on a client pc? I download the beta version in this thread but i didnt manage to get it working or is there a final version?

I need this for my Simpit and it would very good to get vc running ob a second pc! Thank you for helping me.


Kind regrads Christian

1lokos
Apr-27-2014, 12:53
Anybody working on a VC for the G50?

I try adapt instruments from Bf 109, but dont understand how get some instruments work

Altitude indicator work only the thousand digit.
Prop pitch dont work
ATA dont work
Magnets work inverted...

Ammo count dont work - I adapt some radial instrument, work on Demo but not in game. EDIT - Work for right MG. :)

9342

Sokol1

101ECV_GADGET
Apr-27-2014, 13:13
Sokol1

Maybe this he first time in many many years I can actually help you intead of the opposite.

If the name of the variables for the exported data is ok, then try to find if the TYPE OF PARAMETER is corect. To find out you should run RD_IL2CloDTF30.exe and look for the specific variable for the aircraft you are flying at that moment.

I include the code for a WARNING PANEL for British aircraft, and notice how this TIPE PARAMETER are used




Class = Panel;
Caption = Caution panel;

Height = 160;
Width = 400;

Align = TopLeft;

Items{
A1 Prop OverRev{
Class = Indicator;
Caption = Prop OverRev;
Left = 0;
Top = 0;
Width = 100;
Height = 40;
ParamType = I_EngineRPM;
ParamSubtype = 1;
MinValue = 1600;
MaxValue = 4000;
Ranges{
Grey{
MaxValue = 3049.9999;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF100505; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = PROP
OVREV; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF300000}}
}
}
Red{
MinValue = 3050;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF401010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = PROP
OVREV; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FFFF0000}}
}
}
}
}

A2 Coolant Temperature{
Class = Indicator;
Caption = Coolant Temperature;
Left = 100;
Top = 0;
Width = 100;
Height = 40;
ParamType = I_EngineWatTemp;
ParamSubtype = 1;
MinValue = 40;
MaxValue = 140;
Ranges{
Grey{
MaxValue = 114.9999;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF100505; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = COOLANT
TEMP; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF300000}}
}
}
Red{
MinValue = 115;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF401010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = COOLANT
TEMP; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FFFF0000}}
}
}
}
}

A3 Oil Temperature{
Class = Indicator;
Caption = Oil Temperature;
Left = 200;
Top = 0;
Width = 100;
Height = 40;
ParamType = I_EngineOilTemp;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 100;
Ranges{
Grey{
MaxValue = 94.9999;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF100505; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = OIL
TEMP; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF300000}}
}
}
Red{
MinValue = 95;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF401010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = OIL
TEMP; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FFFF0000}}
}
}
}
}

A4 Fuel Low{
Class = Indicator;
Caption = Fuel Low;
Left = 300;
Top = 0;
Width = 100;
Height = 40;
ParamType = I_FuelReserve;
ParamSubtype = 0;
MinValue = 0;
MaxValue = 37;
Ranges{
Grey{
MinValue = 7;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF100505; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = FUEL
LOW; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF300000}}
}
}
Red{
MaxValue = 6.9999;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF401010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = FUEL
LOW; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FFFF0000}}
}
}
}
}

B1 --{
Class = Indicator;
Caption = Fuel Reserve;
Left = 0;
Top = 40;
Width = 100;
Height = 40;
ParamType = I_EngineOilPress;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 150;
Ranges{
Grey{
MinValue = 10;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF100505; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = --; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF300000}}
}
}
Red{
MaxValue = 9.9999;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF401010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = --; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FFFF0000}}
}
}
}
}

B2 Pneumatic Pressure{
Class = Indicator;
Caption = Pneumatic Pressure;
Left = 100;
Top = 40;
Width = 100;
Height = 40;
ParamType = S_PneumoContainerPressure;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 480;
Ranges{
Grey{
MinValue = 250;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF100505; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = PNEU
PRESS; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF300000}}
}
}
Red{
MaxValue = 249.9999;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF401010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = PNEU
PRESS; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FFFF0000}}
}
}
}
}

B3 Oil Pressure{
Class = Indicator;
Caption = Oil Pressure;
Left = 200;
Top = 40;
Width = 100;
Height = 40;
ParamType = I_EngineOilPress;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 150;
Ranges{
Grey{
MinValue = 45;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF100505; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = OIL
PRESS; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF300000}}
}
}
Red{
MaxValue = 44.9999;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF401010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = OIL
PRESS; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FFFF0000}}
}
}
}
}

B4 Fuel Pressure{
Class = Indicator;
Caption = Fuel Reserve;
Left = 300;
Top = 40;
Width = 100;
Height = 40;
ParamType = I_EngineFuelPress;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 5;
Ranges{
Grey{
MinValue = 3;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF051005; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = FUEL
PRESS; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF002000}}
}
}
Red{
MaxValue = 2.9999;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF401010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = FUEL
PRESS; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FFFF0000}}
}
}
}
}

C1 Magneto 1{
Class = Indicator;
Caption = Magneto 1;
Left = 0;
Top = 80;
Width = 100;
Height = 40;
ParamType = C_Magneto;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 3;
Mask = 1;
Ranges{
Grey{
Value = 1;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF101005; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = MAGNETO
1; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF202000}}
}
}
Red{
Value = 0;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF404010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = MAGNETO
1; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FFFFFF00}}
}
}
}
}

C2 Magneto 2{
Class = Indicator;
Caption = Magneto 2;
Left = 100;
Top = 80;
Width = 100;
Height = 40;
ParamType = C_Magneto;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 3;
Mask = 2;
BitShift = 1;
Ranges{
Grey{
Value = 1;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF101005; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = MAGNETO
2; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF202000}}
}
}
Red{
Value = 0;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF404010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = MAGNETO
2; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FFFFFF00}}
}
}
}
}

C3 Fuel Select Off{
Class = Indicator;
Caption = Fuel Select Off;
Left = 200;
Top = 80;
Width = 100;
Height = 40;
ParamType = C_FuelTankSelector;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 1;
Ranges{
Grey{
MinValue = 0;
MaxValue = 0.5;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF101005; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = FUEL SEL
OFF; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF202000}}
}
}
Yellow{
MinValue = 0.5;
MaxValue = 1;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF404010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = FUEL SEL
OFF; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FFFFFF00}}
}
}
}
}

C4 Over Speed{
Class = Indicator;
Caption = Over Speed;
Left = 300;
Top = 80;
Width = 100;
Height = 40;
ParamType = I_VelocityIAS;
ParamSubtype = 0;
MinValue = 0;
MaxValue = 500;
Ranges{
Grey{
MaxValue = 419.9999;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF101005; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = OVER
SPEED; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF202000}}
}
}
Yellow{
MinValue = 420;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF404010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = OVER
SPEED; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FFFFFF00}}
}
}
}
}

D1 Boost Ready{
Class = Indicator;
Caption = Boost Ready;
Left = 0;
Top = 120;
Width = 100;
Height = 40;
Param = C_BoostEnabler.1;
Ranges{
Grey{
Value = 0;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF051005; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = BOOST
RDY; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF002000}}
}
}
Green{
Value = 1;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF104010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = BOOST
RDY; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF00FF00}}
}
}
}
}

D2 --{
Class = Indicator;
Caption = Fuel Reserve;
Left = 100;
Top = 120;
Width = 100;
Height = 40;
ParamType = I_EngineOilPress;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 150;
Ranges{
Grey{
MinValue = 10;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF051005; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = --; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF002000}}
}
}
Red{
MaxValue = 9.9999;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF104010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = --; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF00FF00}}
}
}
}
}

D3 --{
Class = Indicator;
Caption = Fuel Reserve;
Left = 200;
Top = 120;
Width = 100;
Height = 40;
ParamType = I_EngineOilPress;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 150;
Ranges{
Grey{
MinValue = 10;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF051005; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = --; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF002000}}
}
}
Red{
MaxValue = 9.9999;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF104010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = --; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF00FF00}}
}
}
}
}

D4 Fuel Reserve Feeding{
Class = Indicator;
Caption = Fuel Reserve Feeding;
Left = 300;
Top = 120;
Width = 100;
Height = 40;
ParamType = I_FuelReserve;
MinValue = 0;
MaxValue = 37;
Ranges{
Grey{
MinValue = 36.9999;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF051005; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = RSRV
FEEDING; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF002000}}
}
}
Green{
MaxValue = 36.9998;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF104010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = RSRV
FEEDING; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF00FF00}}
}
}
}
}
}

matweich
Apr-27-2014, 14:50
Hi, I hope someone can help me out here... I'm having some trouble with RD_IL2CloDTF30.exe the executable that was packaged with VC. I can no longer see the window with data when I run it. I can see it in the task manager but there is no window... It worked fine until recently.

with TF 4.3 it worked fine, not sure about whether I've tried it with the hotfix

things that might have affected it - new net framework was installed & sound fix in registry was performed.

VC still works fine by itself but I really want to get RD_IL2CloDTF30.exe working...

memory dump file in case: https://dl.dropboxusercontent.com/u/14123055/RD_IL2CloDTF30.zip (https://dl.dropboxusercontent.com/u/14123055/RD_IL2CloDTF30.zip?dl=1)

fingers crossed somebody knows the answer...!:salute:

Hi Badger!

You can use this registry file (https://www.dropbox.com/s/5clgcet3xg9a4c7/Fix.reg) or delete registry key "HKEY_LOCAL_MACHINE\SOFTWARE\matweiSoft\Virtual Cockpit\Raw Data\IL2_CLOD_TF30\Forms\frmMain" manualy. To avoid this problem try not to close RD_IL2CloDTF30.exe application when its window is minimized until I fix this issue.

hnbdgr
Apr-27-2014, 15:30
Hi Badger!

You can use this registry file (https://www.dropbox.com/s/5clgcet3xg9a4c7/Fix.reg) or delete registry key "HKEY_LOCAL_MACHINE\SOFTWARE\matweiSoft\Virtual Cockpit\Raw Data\IL2_CLOD_TF30\Forms\frmMain" manualy. To avoid this problem try not to close RD_IL2CloDTF30.exe application when its window is minimized until I fix this issue.

Thank you matweich! as per pm it turned out to be

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\matweiSoft \Virtual Cockpit\Raw Data\IL2_CLOD_TF30\Forms\frmMain

on my machine. Everything back to normal now!:thumbsup:

matweich
Apr-27-2014, 15:53
Hello,

Can someone help me how to setup vc on a client pc? I download the beta version in this thread but i didnt manage to get it working or is there a final version?

I need this for my Simpit and it would very good to get vc running ob a second pc! Thank you for helping me.


Kind regrads Christian

Hi!

There is no final version yet, but here (https://www.dropbox.com/s/rv2b1ok2ti92yj0/VC%202014-04-27.ZIP) is update.
1. Start VCServer.exe on a PC where you running CoD.
2. Start VirtualCockpit.exe on a second PC.
3. Select remote mode.
4. Type your first PC's (where VCServer.exe running) IPv4 address (no name resolving in this version) in "Server IP". You can use ipconfig (press Win+r, type "cmd", press enter, type "ipconfig", press enter) to see it.
Also you need to check your firewall is not blocking communication on selected TCP port (8270 by default).
5. Start cockpit. If something goes wrong, you'll see error message with WinSock error code (can take some time if you use invalid IP or port is blocked by firewall).
6. Start CoD. As soon you as get in a plane, you'll see instruments.

Hope it helps.

PS. Sorry for my English.

avidflyer
Apr-27-2014, 16:56
Thank you very much i will try it next weekend.

Regards Christian

No1_Jacko
Apr-28-2014, 16:06
I can get the VC to start but its not reponding to the ac, I think I need to set the ip and port but not sure where that info is.
Can anyone kindly confirm for me
Cheers
Jacko

1lokos
Apr-29-2014, 23:49
Anybody working on a VC for the G50? :recon:

G-50 "Beta" version done.

Edit (05/26) - Beta 4.0 :)

9776

As most as possible I try maintain the G-50 instrument panel layout (just dont use 2 IAS indicators, probable dont work - as ammo counter (fixed).

The warning lights inside temperature instruments are calibrated with TF Wiki parameters.

Issues - most fix on 2.0:

- At start is show message saying "no data available" for undercarriage indicator, but the indicator work OK.

>>>Still, but dont bother in game.

- Altimeter still dont work, despite use the "I_Altitude" parameter informed by Devicelink.
The adjust for altitude - small scale inside instrument - work...

>>>Altimeter fixed, for others planes the game inform altitude thousands (meters, feet), e.g. 4.558,35 for G50 is only 4.58 - so the "sensibility" of instrument were too low.
I include a digit for hundred meters, the double scale on this altimeters difficult read (but not like one in Spit/Hurri and his 3 needles).

- MG ammo count work for only one MG - or left or right, not for both (used subtype 1 and 2 respectively), in true work for some moments and after stop.
Anyway the info in these are redundant.

I try the panel with just this two instruments, and dot get both work as it should.

>>> Finally fixed, both work now!
I suspect the problem were due use cut and past on Notepad, after change for Notepad++ end in solve this (I hope). :)

- The air pressure related instruments seems hooked wrong in game. Dont causes problems.
In game the animation for "FAST FRENO" instrument, behind control column, dont match with pop-up window and Devicelink values.

>>>This is game error, not Devicelink/VC, dont bother at all.

- The gunsight light ON monitor - the "instrument" on center of panel, just for dont leave the blank space - blink when the gunsight light is turned ON...

>>> Seems this monitor light is done to blink, so reduce his diameter to don't bother when ON.

Donwload Beta 3.0: 9775

Include a picture with Devicelink parameters for G-50.

This "Telepirometro Elettrico" took several hours to understand and get work. :D

>>> Are other crazy instrument on G-50, the "Anemometer Adjust" that turn the IAS dial 540 degrees, include a simplified scale for this... Dont me ask how use and for what. :)

Sokol1

ATAG_Septic
Apr-30-2014, 06:42
Thanks for sharing this Sokol1. You are a very helpful chap on the forums, it's much appreciated.

Septic.:salute:

Falco
Apr-30-2014, 08:20
Awesome, thanks for your time on this, very much appreciated:salute:

1lokos
May-01-2014, 02:30
G-50 updated: http://theairtacticalassaultgroup.com/forum/showthread.php?t=3887&p=116371&viewfull=1#post116371

Sokol1

56RAF_klem
May-01-2014, 19:39
Forgot to add screenshots.

Just out of interest is anyone using this?

1lokos
May-02-2014, 09:20
You say the Spitfire with real panel background picture?

I try but have problems in properly re-scale for 1024x768 (CRT) monitor).

Sokol1

56RAF_klem
May-02-2014, 15:17
You say the Spitfire with real panel background picture?

I try but have problems in properly re-scale for 1024x768 (CRT) monitor).

Sokol1

Yes, I made it for 1680x1050 (1.6 : 1) . At 1024 that would be 1024 x 640 so 1024 x 768(1.3333 : 1) would be a little stretched vertically. You could try going into the Cockpit.ini and changing:
Width = 1680;
Height = 1050;

to
Width = 1680;
Height = 1260;

and resize the canvas (background) of the "SpitIIa_panel_1680.bmpx" bitmap to the same 1680 x 1260, adding some black area at the bottom. Don't just 'resize' the image, add height to the canvas. The instruments should still sit behind the correct holes in the panel as they are referenced from the top left hand corner and you haven't changed the width. Then all you do is select "Scale to fit monitor" and it should display ok.

Use Paint.net with the .bpmx add-on or photo shop, anything that will allow you to edit and save a .bpmx file.

101ECV_GADGET
May-03-2014, 08:50
Why BMPX images such as bezels appear upside down when renderig the panel?

This is an exanple, but it happens in every instrument:



Class = Radial gauge;
Caption = Clock;

Width = 224;
Height = 224;

RingWidth = .5;

ForegroundShape{
{Class = Ellipse; Color = $FFFFFFFF; Center = 112/112; Radius = 7; LineWidth = 0.5; LineColor = $FF101010}
}

Foreground = CLOCK.bmpx;
ForegroundFitMode = Scale; // NoFit, Center (default), Stretch, Scale, Fill

BackgroundShape{
{Class = Ellipse; Color = $FF101010; Center = 112/112; Radius = 100; LineWidth = 1; LineColor = $FF606060}
// {Class = Ellipse; Color = $FF050505; Center = 112/112; Radius = 92; LineWidth = 4; LineColor = $FF404040}
{Class = Ellipse; Color = $FFFFFFFF; Center = 112/112; Radius = 10; LineWidth = 0.5; LineColor = $FF101010}
}

Inputs{
Hours{
ParamType = I_Timer;
MinValue = 0;
MaxValue = 24;
StartAngle = 0;
EndAngle = 720;
Radius = 75;
Needle{
Shape {
{Class = Polygon; Color = $FFFFFFFF; Points = 1/0, 4/40, 0/55, -4/40, -1/0; LineWidth = 0,5; LineColor = $FF202020}
}
}
}

Minutes{
ParamType = I_Timer;
MinValue = 0;
MaxValue = 60;
Remainder = 1;
Multiplier = 60;
StartAngle = 0;
EndAngle = 360;
Radius = 75;
Needle{
Shape {
{Class = Polygon; Color = $FFFFFFFF; Points = 1/0, 3/55, 0/70, -3/55, -1/0; LineWidth = 0,5; LineColor = $FF202020}
}
}
Scale{
Font{Size = 25; Color = $FF809980}
RingWidth = 0;
Markers{
HoursText{MinValue = 0; Count = 5; Height = 15; Width = 5; TextMultiplier = 0,2; Color = $FF809980}
Hours{Count = 13; Height = 20; Width = 5; Color = $FF809980; TextFormat = }
Minutes{Count = 61; Height = 8; Width = 3; Color = $FF959595; TextFormat = }
}
CustomMarkers{
12{Value = 0; Width = 5; Height = 15; Text = 12; Color = $FF709970}
}
}
}

Seconds{
ParamType = I_Timer;
MinValue = 0;
MaxValue = 60;
Remainder = 0,01666666667;
Multiplier = 3600;
StartAngle = 0;
EndAngle = 360;
Radius = 75;
Needle{
Shape {
{Class = Polygon; Color = $FF202020; Points = 1/-27, 1/0, -1/0, -1/-27; LineWidth = 0,5; LineColor = $FF202020}
{Class = Polygon; Color = $FFFFFFFF; Points = 1/0, 1/50, 3/53, 2/59, 0.5/75, -0.5/75, -2/59, -3/53, -1/50, -1/0; LineWidth = 0,5; LineColor = $FF202020}
}
}
}
}

101ECV_GADGET
May-03-2014, 17:02
Also needles when designed with SHAPE command need to be constructed with negative values to indicate correctly.
I had to rectifiy all my new instruments

Please notice the previous code I inserted as needles indicate in the opposite direction

Is this a bug????

matweich
May-04-2014, 05:52
Why BMPX images such as bezels appear upside down when renderig the panel?
I can't find documentation on BMPX file format. Looks like ordinary BMP but can't say for sure. May be something wrong with bitmap header. Try to use GIMP (http://www.gimp.org/).


Also needles when designed with SHAPE command need to be constructed with negative values to indicate correctly.
I had to rectifiy all my new instruments

Please notice the previous code I inserted as needles indicate in the opposite direction

Is this a bug????
No, it's not.
Here is coordinate system: 9436
Needle shape must be defined for angle 0 ("up" on screen, "down" in coordinate system) and it's rotating around point 0,0 so Y-coordinates is negative most commonly.

101ECV_GADGET
May-04-2014, 06:08
thank you

I am converting formats with paint.NET and everything looks normal.

Only the rendering of the instruments bezels is upside down, but apparently not so when presenting background textures for the main panels.

tom.doniphon
May-04-2014, 10:03
Junghans BO-UK-1 clock with functional chrono for Luftwaffe aircrafts from the upcoming BF109 E3 cockpit by Doniphon :D

9438


Class = Radial gauge;
Caption = Junghans BO-UK-1 Clock;

Width = 150;
Height = 150;

BackgroundShape{
{Class = Arc; Center = 75/75; Width = 10; Radius = 66; FromAngle = 0; ToAngle = 360; Color = $FF663300}
}

ForegroundShape{
{Class = Ellipse; Center = 75/75; Radius = 3; LineWidth = 2; LineColor = $FFFFFFFF; Color = $FF333333}
}

RingWidth = 0;
RingColor = $FFFFFFFF;

Inputs{
Hours{
ParamType = I_Timer;
ParamSubtype = 0;
MinValue = 0;
MaxValue = 24;
StartAngle = 0;
EndAngle = 720;
Needle{
Shape{
{Class = Polygon; Points = -0.5/2, -0.5/-7, -3/-12, -3/-35, 0/-40, 3/-35, 3/-12, 0.5/-7, 0.5/2; Color = $FFFFFFFF; LineColor = $FFFFFFFF; LineWidth = 2}
}
}
}
Minutes{
ParamType = I_Timer;
ParamSubtype = 0;
MinValue = 0;
StartAngle = 0;
MaxValue = 60;
EndAngle = 360;
Needle{
Shape{
{Class = Polygon; Points = -0.5/2, -0.5/-7, -1.5/-12, -1.5/-50, 0/-55, 1.5/-50, 1.5/-12, 0.5/-7, 0.5/2; Color = $FFFFFFFF; LineColor = $FFFFFFFF; LineWidth = 2}
}
}
Remainder = 1;
Multiplier = 60;
Scale{
Radius = 58;
RingWidth = 1;
RingColor = $FFFFFFFF;
Font{Name = Alte DIN 1451 Mittelschrift; Size = 18; Style = B; Color = $FFFFFFFF}
Markers{
Hours{MinValue = 5; Count = 12; Height = 7; Width = 3; TextFormat = ; TextMultiplier = 0.2}
Minutes{Count = 61; Height = 4; Width = 2; Color = $FFFFFFFF; TextFormat = }
}
CustomMarkers{
3{Value = 15; Height = 7; Width = 3; Text = 3}
//6{Value = 30; Height = 7; Width = 3; Text = 6}
9{Value = 45; Height = 7; Width = 3; Text = 9}
12{Value = 60; Height = 7; Width = 3; Text = 12}
}
}
}
Chrono{
ParamType = I_Timer;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 15;
StartAngle = 0;
EndAngle = 360;
CenterY = 100;
Needle{
Shape{
{Class = Ellipse; Center = 0/0; Radius = 3; Color = $FFFFFFFF; LineColor = $FFFFFFFF}
{Class = Polygon; Points = -1/2, -1/-15, -0/-18, 1/-15, 1/2; Color = $FFFFFFFF; LineColor = $FFFFFFFF; LineWidth = 2}
}
}
Remainder = 900;
Multiplier = 0.0166666666667;
Scale{
Radius = 20;
RingWidth = 1;
RingColor = $FFFFFFFF;
Font{Name = Alte DIN 1451 Mittelschrift; Size = 18; Color = $FFFFFFFF}
Markers{
Minutes{Count = 16; Height = -3; Width = 2; Color = $FFFFFFFF; TextFormat = }
}
CustomMarkers{
5{Value = 5; Height = -5; Width = 3; Text = }
10{Value = 10; Height = -5; Width = 3; Text = }
0{Value = 0; Height = -5; Width = 3; Text = }
}
}
}
Seconds{
ParamType = I_Timer;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 60;
Remainder = 60;
Multiplier = 1;
StartAngle = 0;
EndAngle = 360;
Needle{
Shape{
{Class = Polygon; Points = -0.5/2, -0.5/-7, -0.5/-49, -3/-52, 0/-58, 3/-52, 0.5/-49, 0.5/-7, 0.5/2; Color = $FFFFFF40; LineColor = $FFFFFF40; LineWidth = 1}
}
}
Scale{
Radius = 62;
RingWidth = 0;
RingColor = $FFFFFFFF;
Font{Name = Alte DIN 1451 Mittelschrift; Size = 7; Color = $FFFFFFFF}
MarkerTextOrientation = Aligned;
Markers{
Hours{MinValue = 0; MaxValue = 55; Count = 12; Height = -0.01; Width = 1; Color = $FFFFFFFF; TextMultiplier = 1}
Minutes{Count = 61; Height = -4; Width = 1; Color = $FFFFFFFF; TextFormat = }
}
}
}
}

101ECV_GADGET
May-04-2014, 12:16
Junghans BO-UK-1 clock with functional chrono for Luftwaffe aircrafts from the upcoming BF109 E3 cockpit by Doniphon :D

9438


Class = Radial gauge;
Caption = Junghans BO-UK-1 Clock;

Width = 150;
Height = 150;

BackgroundShape{
{Class = Arc; Center = 75/75; Width = 10; Radius = 66; FromAngle = 0; ToAngle = 360; Color = $FF663300}
}

ForegroundShape{
{Class = Ellipse; Center = 75/75; Radius = 3; LineWidth = 2; LineColor = $FFFFFFFF; Color = $FF333333}
}

RingWidth = 0;
RingColor = $FFFFFFFF;

Inputs{
Hours{
ParamType = I_Timer;
ParamSubtype = 0;
MinValue = 0;
MaxValue = 24;
StartAngle = 0;
EndAngle = 720;
Needle{
Shape{
{Class = Polygon; Points = -0.5/2, -0.5/-7, -3/-12, -3/-35, 0/-40, 3/-35, 3/-12, 0.5/-7, 0.5/2; Color = $FFFFFFFF; LineColor = $FFFFFFFF; LineWidth = 2}
}
}
}
Minutes{
ParamType = I_Timer;
ParamSubtype = 0;
MinValue = 0;
StartAngle = 0;
MaxValue = 60;
EndAngle = 360;
Needle{
Shape{
{Class = Polygon; Points = -0.5/2, -0.5/-7, -1.5/-12, -1.5/-50, 0/-55, 1.5/-50, 1.5/-12, 0.5/-7, 0.5/2; Color = $FFFFFFFF; LineColor = $FFFFFFFF; LineWidth = 2}
}
}
Remainder = 1;
Multiplier = 60;
Scale{
Radius = 58;
RingWidth = 1;
RingColor = $FFFFFFFF;
Font{Name = Alte DIN 1451 Mittelschrift; Size = 18; Style = B; Color = $FFFFFFFF}
Markers{
Hours{MinValue = 5; Count = 12; Height = 7; Width = 3; TextFormat = ; TextMultiplier = 0.2}
Minutes{Count = 61; Height = 4; Width = 2; Color = $FFFFFFFF; TextFormat = }
}
CustomMarkers{
3{Value = 15; Height = 7; Width = 3; Text = 3}
//6{Value = 30; Height = 7; Width = 3; Text = 6}
9{Value = 45; Height = 7; Width = 3; Text = 9}
12{Value = 60; Height = 7; Width = 3; Text = 12}
}
}
}
Chrono{
ParamType = I_Timer;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 15;
StartAngle = 0;
EndAngle = 360;
CenterY = 100;
Needle{
Shape{
{Class = Ellipse; Center = 0/0; Radius = 3; Color = $FFFFFFFF; LineColor = $FFFFFFFF}
{Class = Polygon; Points = -1/2, -1/-15, -0/-18, 1/-15, 1/2; Color = $FFFFFFFF; LineColor = $FFFFFFFF; LineWidth = 2}
}
}
Remainder = 900;
Multiplier = 0.0166666666667;
Scale{
Radius = 20;
RingWidth = 1;
RingColor = $FFFFFFFF;
Font{Name = Alte DIN 1451 Mittelschrift; Size = 18; Color = $FFFFFFFF}
Markers{
Minutes{Count = 16; Height = -3; Width = 2; Color = $FFFFFFFF; TextFormat = }
}
CustomMarkers{
5{Value = 5; Height = -5; Width = 3; Text = }
10{Value = 10; Height = -5; Width = 3; Text = }
0{Value = 0; Height = -5; Width = 3; Text = }
}
}
}
Seconds{
ParamType = I_Timer;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 60;
Remainder = 60;
Multiplier = 1;
StartAngle = 0;
EndAngle = 360;
Needle{
Shape{
{Class = Polygon; Points = -0.5/2, -0.5/-7, -0.5/-49, -3/-52, 0/-58, 3/-52, 0.5/-49, 0.5/-7, 0.5/2; Color = $FFFFFF40; LineColor = $FFFFFF40; LineWidth = 1}
}
}
Scale{
Radius = 62;
RingWidth = 0;
RingColor = $FFFFFFFF;
Font{Name = Alte DIN 1451 Mittelschrift; Size = 7; Color = $FFFFFFFF}
MarkerTextOrientation = Aligned;
Markers{
Hours{MinValue = 0; MaxValue = 55; Count = 12; Height = -0.01; Width = 1; Color = $FFFFFFFF; TextMultiplier = 1}
Minutes{Count = 61; Height = -4; Width = 1; Color = $FFFFFFFF; TextFormat = }
}
}
}
}




Very nice. Thank you

I like the individual instruments as fragments of code. It is easier to copy/paste than to download and install.

Let me post for your ejoyment a SINGLE NEEDLE MODERN AIRBUS-STYLE ALTIMETER also. It has been designed for a 23" touch monitor, that mesures:

Width = 1920; 510 mm
Height = 1080; 290 mm

so the instrumetnt shows in its actual size of 83 mm bezel and 80 mm chart.
I am designing a generic rational panel with a BASIC-T arrangement of instrumetns, so my personal transition to flying several type of aircraf is minimal. This is only part of this panel.




Class = Radial gauge;
Caption = Altimeter;

// BISEL DE 83 mm (SE INCLUYEN LOS PIXELES DEL BORDE)
Width = 312;
Height = 312;

RingWidth = ;

ForegroundShape{
{Class = Ellipse; Color = $FF000000; Center = 156/156; Radius = 7; LineWidth = 0,5 ; LineColor = $FF606060}
{Class = Ellipse; Color = $FF202020; Center = 156/156; Radius = 3; LineWidth = 1,5 ; LineColor = $FF606060}
}

Foreground = ALTIMETRO.bmpx;
ForegroundFitMode = Scale; // NoFit, Center (default), Stretch, Scale, Fill

BackgroundShape{
{Class = Ellipse; Color = $FF000000; Center = 156/156; Radius = 125; LineWidth = 0; LineColor = $FF606060}
{Class = Polygon; Points = 110/106, 135/106, 135/100, 160/100, 160/112, 208/112, 208/138, 160/138, 160/148, 135/148, 135/144, 110/144; Color = ; LineWidth = 3; LineColor = $FFFFFFFF}
}

Inputs{
Alt100Ft{
ParamType = I_Altitude;
MinValue = -1000;
MaxValue = 1000;
Remainder = 1000;
StartAngle = -360;
EndAngle = 360;
Needle{
Shape {
{Class = Polygon; Color = $FFFFFFFF; Points = 2/-65, 5/-70, 5/-90, 0.5/-103, -0.5/-103, -5/-90, -5/-70, -2/-65; LineWidth = 0,5; LineColor = $FF202020}
{Class = Polygon; Color = $FF202020; Points = 2/70, 2/50, 1/50, 1/30, 2/20, 2/-65, -2/-65, -2/20, -1/30, -1/50, -2/50, -2/70; LineWidth = 0,5; LineColor = $FF202020}
}
}
Scales{
Outer{
MinValue = -1000;
MaxValue = 1000;
Radius = 120;
RingWidth = 0;
Font{
Size = 20;
Style = ;
Color = $FFFFFFFF;
}
Markers{
Big{MinValue = 0; Count = 11; Width = 3; Height = 20; TextMultiplier = 0,01;}
}
CustomMarkers{
500{Value = 500; Text = ; Height = 20; Width = 3}
}
}
Inner{
MinValue = -1000;
MaxValue = 1000;
Radius = 100;
RingWidth = 0;
Font{
Size = 20;
Style = ;
Color = $FFFFFFFF;
}
Markers{
Small{MinValue = 0; Count = 51; Width = 2; Height = -15; TextFormat = ; Color = $FFFFFFFF;}
}
}
}
}
}

Items{
TenThousandAltitudeText{
Class = Text;
Caption = Altitude value;
BackgroundColor = $FF101010;
Left = 115;
Top = 110;
Width = 20;
Height = 30;
Format = 0;
Font{Size = 27; Color = $FFFFFFFF; Align = Right;}
Input{
ParamType = I_Altitude;
Multiplier = 0,0001;
Precision = 1;
}
}

OneThousandAltitudeText{
Class = Text;
Caption = Altitude value;
BackgroundColor = $FF101010;
Left = 138;
Top = 110;
Width = 20;
Height = 30;
Format = 0;
Font{Size = 27; Color = $FFFFFFFF; Align = Right;}
Input{
ParamType = I_Altitude;
Multiplier = 0,001;
Precision = 1;
Remainder = 10000;
}
}

000{
Class = Label;
BackgroundColor = $FF101010;
Left = 159;
Top = 113;
Width = 45;
Height = 20;
Font{Size = 18}
}

ALT{
Class = Label;
Left = 104;
Top = 135;
Width = 104;
Height = 50;
Font{Size = 16}
}

hPa{
Class = Label;
Left = 104;
Top = 175;
Width = 104;
Height = 50;
Font{Size = 12; Color = $FF606060}
}

QNHText{
Class = Text;
Caption = Altitude value;
MinValue = 745;
MaxValue = 1100;
BackgroundColor = $FF101010;
Left = 131;
Top = 230;
Width = 50;
Height = 20;
Format = 0;
Font{Size = 12; Color = $FFFFFFFF}
Input{
ParamType = C_AltimeterPinion;
}
}
}

1lokos
May-04-2014, 12:41
Junghans BO-UK-1 clock with functional chrono for Luftwaffe aircrafts from the upcoming BF109 E3 cockpit by Doniphon :D


Thank you!

I am fiddle with this last night, but my chronometer get crazy or turn too fast or too slow. :D

Work perfectly. :thumbsup:

Sokol1

56RAF_klem
May-04-2014, 17:55
I can't find documentation on BMPX file format. Looks like ordinary BMP but can't say for sure. May be something wrong with bitmap header. Try to use GIMP (http://www.gimp.org/)..............................................

Or Paint.net, also free, which you can get a BMPX plug-in for. Then it includes .bpmx in the Save As... filetype options

tom.doniphon
May-05-2014, 13:06
Why BMPX images such as bezels appear upside down when renderig the panel?


Try with this: ForegroundFitMode = Stretch;




Let me post for your ejoyment a SINGLE NEEDLE MODERN AIRBUS-STYLE ALTIMETER also.

Very good! I've tested this with Gill Sans MT font and looks fantastic.

Doniphon

101ECV_GADGET
May-05-2014, 14:19
Thank you for your words and advice

I will try when I arrive home in a couple of days.

I am in the process to resizing all my instruments to add bezel images, but you can try some of them "naked" if you wish.

clock:



Class = Radial gauge;
Caption = Clock;

Width = 224;
Height = 224;

RingWidth = .5;

ForegroundShape{
{Class = Ellipse; Color = $FFFFFFFF; Center = 112/112; Radius = 7; LineWidth = 0.5; LineColor = $FF101010}
}

// Background = BLIND_PANEL.bmpx;
// BackgroundFitMode = Stretch;
Foreground = CLOCK.bmpx;
ForegroundFitMode = Scale; // NoFit, Center (default), Stretch, Scale, Fill

BackgroundShape{
{Class = Ellipse; Color = $FF101010; Center = 112/112; Radius = 112; LineWidth = 1; LineColor = $FF606060}
{Class = Ellipse; Color = $FF050505; Center = 112/112; Radius = 92; LineWidth = 4; LineColor = $FF404040}
{Class = Ellipse; Color = $FFFFFFFF; Center = 112/112; Radius = 10; LineWidth = 0.5; LineColor = $FF101010}
}

Inputs{
Hours{
ParamType = I_Timer;
MinValue = 0;
MaxValue = 24;
StartAngle = 0;
EndAngle = 720;
Radius = 87;
Needle{
Shape {
{Class = Polygon; Color = $FFFFFFFF; Points = 1/0, 4/55, 0/67, -4/55, -1/0; LineWidth = 0,5; LineColor = $FF202020}
}
}
}

Minutes{
ParamType = I_Timer;
MinValue = 0;
MaxValue = 60;
Remainder = 1;
Multiplier = 60;
StartAngle = 0;
EndAngle = 360;
Radius = 87;
Needle{
Shape {
{Class = Polygon; Color = $FFFFFFFF; Points = 1/0, 3/70, 0/82, -3/70, -1/0; LineWidth = 0,5; LineColor = $FF202020}
}
}
Scale{
Font{Size = 25; Color = $FF809980}
RingWidth = 0;
Markers{
HoursText{MinValue = 0; Count = 5; Height = 15; Width = 5; TextMultiplier = 0,2; Color = $FF809980}
Hours{Count = 13; Height = 20; Width = 5; Color = $FF809980; TextFormat = }
Minutes{Count = 61; Height = 8; Width = 3; Color = $FF959595; TextFormat = }
}
CustomMarkers{
12{Value = 0; Width = 5; Height = 15; Text = 12; Color = $FF709970}
}
}
}

Seconds{
ParamType = I_Timer;
MinValue = 0;
MaxValue = 60;
Remainder = 0,01666666667;
Multiplier = 3600;
StartAngle = 0;
EndAngle = 360;
Radius = 93;
Needle{
Shape {
{Class = Polygon; Color = $FF101010; Points = 1/-30, 1/0, -1/0, -1/-30; LineWidth = 0,5; LineColor = $FF202020}
{Class = Polygon; Color = $FFFFFFFF; Points = 1/0, 1/65, 3/68, 2/72, 0.5/87, -0.5/87, -2/72, -3/68, -1/65, -1/0; LineWidth = 0,5; LineColor = $FF202020}
}
}
Scale{
Font{Size = 9; Style = ; Color = $FFFFFFFF}
RingWidth = 0;
Markers{
SecondsText{MinValue = 0; Count = 13; Height = -3; Width = 8}
Seconds{MinValue = 0; Count = 61; Height = -5; Width = 2; Color = $FF959595; TextFormat = }
}
CustomMarkers{
0{Value = 0; Height = -15; Width = 8; Text = ; Color = $FF709970}
}
}
}
}




caution panel



Class = Panel;
Caption = Caution panel;

Height = 80;
Width = 800;

Align = TopLeft;

Items{
A1 Prop OverRev{
Class = Indicator;
Caption = Prop OverRev;
Left = 0;
Top = 0;
Width = 100;
Height = 40;
ParamType = I_EngineRPM;
ParamSubtype = 1;
MinValue = 1600;
MaxValue = 4000;
Ranges{
Grey{
MaxValue = 3049.9999;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF100505; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = PROP
OVREV; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF300000}}
}
}
Red{
MinValue = 3050;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF401010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = PROP
OVREV; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FFFF0000}}
}
}
}
}

A2 Coolant Temperature{
Class = Indicator;
Caption = Coolant Temperature;
Left = 100;
Top = 0;
Width = 100;
Height = 40;
ParamType = I_EngineWatTemp;
ParamSubtype = 1;
MinValue = 40;
MaxValue = 140;
Ranges{
Grey{
MaxValue = 114.9999;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF100505; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = COOLANT
TEMP; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF300000}}
}
}
Red{
MinValue = 115;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF401010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = COOLANT
TEMP; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FFFF0000}}
}
}
}
}

A3 Oil Temperature{
Class = Indicator;
Caption = Oil Temperature;
Left = 200;
Top = 0;
Width = 100;
Height = 40;
ParamType = I_EngineOilTemp;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 100;
Ranges{
Grey{
MaxValue = 94.9999;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF100505; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = OIL
TEMP; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF300000}}
}
}
Red{
MinValue = 95;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF401010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = OIL
TEMP; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FFFF0000}}
}
}
}
}

A4 Fuel Low{
Class = Indicator;
Caption = Fuel Low;
Left = 300;
Top = 0;
Width = 100;
Height = 40;
ParamType = I_FuelReserve;
ParamSubtype = 0;
MinValue = 0;
MaxValue = 37;
Ranges{
Grey{
MinValue = 7;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF100505; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = FUEL
LOW; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF300000}}
}
}
Red{
MaxValue = 6.9999;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF401010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = FUEL
LOW; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FFFF0000}}
}
}
}
}

A5 --{
Class = Indicator;
Caption = Fuel Reserve;
Left = 400;
Top = 0;
Width = 100;
Height = 40;
ParamType = I_EngineOilPress;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 150;
Ranges{
Grey{
MinValue = 10;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF100505; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = --; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF300000}}
}
}
Red{
MaxValue = 9.9999;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF401010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = --; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FFFF0000}}
}
}
}
}

A6 Pneumatic Pressure{
Class = Indicator;
Caption = Pneumatic Pressure;
Left = 500;
Top = 0;
Width = 100;
Height = 40;
ParamType = S_PneumoContainerPressure;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 480;
Ranges{
Grey{
MinValue = 250;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF100505; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = PNEU
PRESS; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF300000}}
}
}
Red{
MaxValue = 249.9999;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF401010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = PNEU
PRESS; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FFFF0000}}
}
}
}
}

A7 Oil Pressure{
Class = Indicator;
Caption = Oil Pressure;
Left = 600;
Top = 0;
Width = 100;
Height = 40;
ParamType = I_EngineOilPress;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 150;
Ranges{
Grey{
MinValue = 45;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF100505; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = OIL
PRESS; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF300000}}
}
}
Red{
MaxValue = 44.9999;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF401010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = OIL
PRESS; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FFFF0000}}
}
}
}
}

A8 Fuel Pressure{
Class = Indicator;
Caption = Fuel Reserve;
Left = 700;
Top = 0;
Width = 100;
Height = 40;
ParamType = I_EngineFuelPress;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 5;
Ranges{
Grey{
MinValue = 3;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF051005; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = FUEL
PRESS; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF300000}}
}
}
Red{
MaxValue = 2.9999;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF401010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = FUEL
PRESS; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FFFF0000}}
}
}
}
}

B1 Magneto 1{
Class = Indicator;
Caption = Magneto 1;
Left = 0;
Top = 40;
Width = 100;
Height = 40;
ParamType = C_Magneto;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 3;
Mask = 1;
Ranges{
Grey{
Value = 1;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF101005; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = MAGNETO
1; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF202000}}
}
}
Red{
Value = 0;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF404010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = MAGNETO
1; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FFFFFF00}}
}
}
}
}

B2 Magneto 2{
Class = Indicator;
Caption = Magneto 2;
Left = 100;
Top = 40;
Width = 100;
Height = 40;
ParamType = C_Magneto;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 3;
Mask = 2;
BitShift = 1;
Ranges{
Grey{
Value = 1;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF101005; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = MAGNETO
2; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF202000}}
}
}
Red{
Value = 0;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF404010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = MAGNETO
2; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FFFFFF00}}
}
}
}
}

B3 Fuel Select Off{
Class = Indicator;
Caption = Fuel Select Off;
Left = 200;
Top = 40;
Width = 100;
Height = 40;
ParamType = C_FuelTankSelector;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 1;
Ranges{
Grey{
MinValue = 0;
MaxValue = 0.5;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF101005; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = FUEL SEL
OFF; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF202000}}
}
}
Yellow{
MinValue = 0.5;
MaxValue = 1;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF404010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = FUEL SEL
OFF; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FFFFFF00}}
}
}
}
}

B4 Over Speed{
Class = Indicator;
Caption = Over Speed;
Left = 300;
Top = 40;
Width = 100;
Height = 40;
ParamType = I_VelocityIAS;
ParamSubtype = 0;
MinValue = 0;
MaxValue = 500;
Ranges{
Grey{
MaxValue = 419.9999;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF101005; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = OVER
SPEED; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF202000}}
}
}
Yellow{
MinValue = 420;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF404010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = OVER
SPEED; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FFFFFF00}}
}
}
}
}

B5 Boost Ready{
Class = Indicator;
Caption = Boost Ready;
Left = 400;
Top = 40;
Width = 100;
Height = 40;
Param = C_BoostEnabler.1;
Ranges{
Grey{
Value = 0;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF051005; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = BOOST
RDY; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF002000}}
}
}
Green{
Value = 1;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF104010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = BOOST
RDY; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF00FF00}}
}
}
}
}

B6 --{
Class = Indicator;
Caption = Fuel Reserve;
Left = 500;
Top = 40;
Width = 100;
Height = 40;
ParamType = I_EngineOilPress;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 150;
Ranges{
Grey{
MinValue = 10;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF051005; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = --; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF002000}}
}
}
Red{
MaxValue = 9.9999;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF104010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = --; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF00FF00}}
}
}
}
}

B7 --{
Class = Indicator;
Caption = Fuel Reserve;
Left = 600;
Top = 40;
Width = 100;
Height = 40;
ParamType = I_EngineOilPress;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 150;
Ranges{
Grey{
MinValue = 10;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF051005; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = --; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF002000}}
}
}
Red{
MaxValue = 9.9999;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF104010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = --; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF00FF00}}
}
}
}
}

B8 Fuel Reserve Feeding{
Class = Indicator;
Caption = Fuel Reserve Feeding;
Left = 700;
Top = 40;
Width = 100;
Height = 40;
ParamType = I_FuelReserve;
MinValue = 0;
MaxValue = 37;
Ranges{
Grey{
MinValue = 36.9999;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF051005; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = RSRV
FEEDING; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF002000}}
}
}
Green{
MaxValue = 36.9998;
Shape{
{Class = Polygon; Points = 0/0, 100/0, 100/40, 0/40; Color = $FF104010; LineWidth = 3; LineColor = $FF808080}
{Class = Text; Text = RSRV
FEEDING; HAlignment = Center; VAlignment = Center; Pos = 50/20; Font{Size = 14; Style = B; Color = $FF00FF00}}
}
}
}
}
}


Anemometer



Class = Radial gauge;
Caption = IAS;

Width = 300;
Height = 300;

RingWidth = .5;

ForegroundShape{
{Class = Ellipse; Color = $FF000000; Center = 150/150; Radius = 12; LineWidth = 0,5; LineColor = $FF303030}
}

BackgroundShape{
{Class = Ellipse; Color = $FF000000; Center = 150/150; Radius = 150; LineWidth = 0; LineColor = $FF606060}
}

Inputs{
IAS{
ParamType = I_VelocityIAS;
MinValue = 0;
MaxValue = 450;
StartAngle = 0;
EndAngle = 340;
ValueAngles{60 = 5; 140 = 90; 230 = 180; 350 = 270; 450 = 340}
Needle{
Shape {
{Class = Polygon; Color = $FF101010; Points = 6/40, 6/-120, 0/-135, -6/-120, -6/40; LineWidth = 0,5; LineColor = $FF202020}
{Class = Polygon; Color = $FFFFFFFF; Points = 6/-40, 6/-120, 0/-135, -6/-120, -6/-40; LineWidth = 0,5; LineColor = $FF202020}
{Class = Ellipse; Color = $FF101010; Center = 0/50; Radius = 12; LineWidth = 0,5; LineColor = $FF202020}
}
// SpearWidth = 2;
// Width = 10;
// CenterY = 130;
// Length = 50;
// Color = $FFFFFFFF;
// OutlineColor = $FF606060;
}
Scales{
Outer{
MinValue = 0;
MaxValue = 500;
Radius = 150;
RingWidth = 0;
Font{Size = 20; Color = $FFFFFFFF}
Markers{
Big1{MinValue = 60; MaxValue = 200; Count = 8; Width = 3; Height = 20}
Big2{MinValue = 250; MaxValue = 450; Count = 5; Width = 3; Height = 20}
Med{MinValue = 60; MaxValue = 450; Count = 40; Width = 2; Height = 20; TextFormat = }
}
CustomMarkers{
0{Value = 0; Width = 3; Height = 3; Text = ; Color = $FFFFFFFF}
// Vs0{Value = 79; Width = 2; Height = 20; Text = ; Color = $FFFFFF00}
// Vx{Value = 165; Width = 2; Height = 20; Text = ; Color = $FFFFFF00}
Vne{Value = 420; Width = 3; Height = 50; Text = ; Color = $FFFF0000}
}

}
Inner{
MinValue = 0;
MaxValue = 50;
Radius = 130;
RingWidth = 0;
Font{Size = 12; Color = $FFFFFFFF}
Markers{
Small{MinValue = 60; MaxValue = 250; Count = 39; Width = 2; Height = -15; TextFormat = }
}
}
}
}
}

Items{
IAS{
Class = Label;
Left = 100;
Top = 70;
Width = 100;
Height = 50;
Font{Size = 20}
}

MPH{
Class = Label;
Caption = M.P.H.;
Left = 105;
Top = 170;
Width = 100;
Height = 30;
Font{Size = 15; Color = $FF606060;}
}
}



compass



Caption = MAGNETIC COMPASS;

Class = Radial gauge;

Width = 300;
Height = 300;

RingWidth = 1;

ForegroundShape{
{Class = Polygon;
Points = 150/75, 140/120, 80/150, 80/165, 140/150, 145/190, 120/205, 120/215, 148/210, 150/225, 152/210, 180/215, 180/205, 155/190, 160/150, 220/165, 220/150, 160/120;
Color = ;
LineWidth = 3;
}
{Class = Polygon;
Points = 145/0, 155/0, 150/15;
Color = $FFFFFF00;
OutlineColor = $FF606060;
}
{Class = Polygon;
Points = 145/300, 155/300, 150/285;
Color = $FFFFFF00;
OutlineColor = $FF606060;
}
{Class = Polygon;
Points = 0/145, 0/155, 15/150;
Color = $FFFFFF00;
OutlineColor = $FF606060;
}
{Class = Polygon;
Points = 300/145, 300/155, 285/150;
Color = $FFFFFF00;
OutlineColor = $FF606060;
}
{Class = Polygon;
Points = 47/40, 55/55, 40/47;
Color = $FFFFFF00;
OutlineColor = $FF606060 ;
}
{Class = Polygon;
Points = 253/40, 245/55, 260/47;
Color = $FFFFFF00;
OutlineColor = $FF606060 ;
}
{Class = Polygon;
Points = 253/260, 245/245, 260/253;
Color = $FFFFFF00;
OutlineColor = $FF606060 ;
}
{Class = Polygon;
Points = 47/260, 55/245, 40/253;
Color = $FFFFFF00;
OutlineColor = $FF606060 ;
}
}

BackgroundShape{
{Class = Ellipse; Color = $FF000000; Center = 150/150; Radius = 150; LineWidth = 0; LineColor = $FF606060}
}

Inputs{
MagneticCompas{
ParamType = I_MagneticCompass;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 360;
StartAngle = 0;
EndAngle = 360;
RotateScale = true;
Scales{
Digits{
Radius = 150;
RingWidth = 0;
Font{Size = 20; Color = $FFFFFFFF}
Markers{
Big{MinValue = 0; MaxValue = 360; Count = 13; Width = 3; Height = 20; TextColor = $FFFFFFFF; _TextFormat = ; TextMultiplier = 0,1}
Med{Count = 37; Width = 3; Height = 20; TextFormat = }
Small{Count = 73; Width = 2; Height = 15; TextFormat = }
}
CustomMarkers{
N{Value = 0; Width = 0; Text =; Height = 20}
S{Value = 180; Width = 0; Text =; Height = 20}
W{Value = 270; Width = 0; Text =; Height = 20}
E{Value = 90; Width = 0; Text =; Height = 20}
}
}
Labels{
Radius = 150;
RingWidth = 0;
Font{Size = 20; Color = $FFFFFFFF}
CustomMarkers{
N{Value = 0; Width = 3; Height = 20; Text = N; TextColor = $FFFFFFFF}
S{Value = 180; Width = 3; Height = 20; Text = S; TextColor = $FFFFFFFF}
W{Value = 270; Width = 3; Height = 20; Text = W; TextColor = $FFFFFFFF}
E{Value = 90; Width = 3; Height = 20; Text = E; TextColor = $FFFFFFFF}
}
}
}
}

Peilzeiger{
ParamType = I_Peilzeiger;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 360;
StartAngle = 0;
EndAngle = 360;
RotateScale = true;
Needle{
Shape {
{Class = Polygon; Points = -10/-140, -5/-140, 0/-150, 5/-140, 10/-140, 10/-150, -10/-150; Color = $FFFF0000; LineWidth = }
}
}
}
}

Items{
MagneticCompassDigital{
Class = Text;
BackgroundColor = $00200020;
Caption = Magnetic Compass value;
Left = 250;
Top = 0;
Width = 50;
Height = 20;
Format = 0;
Font{Size = 18; Color = $FF00FF00}
HAlignment = Center;
VAlignment = Center;
Input{
ParamType = I_MagneticCompass;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 360;
}
}

HDG{
Class = Label;
Left = 250;
Top = 22;
Width = 50;
Height = 20;
Font{Size = 15; Color = $FF606060}
}

PeilzeigerDigital{
Class = Text;
BackgroundColor = $00200020;
Caption = Magnetic Compass value;
Left = 0;
Top = 0;
Width = 50;
Height = 20;
Format = 0;
Font{Size = 18; Color = $FF00FF00}
HAlignment = Center;
VAlignment = Center;
Input{
ParamType = I_Peilzeiger;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 360;
}
}

RAD{
Class = Label;
Left = 0;
Top = 22;
Width = 50;
Height = 20;
Font{Size = 15; Color = $FF606060}
}
}


RPM



Class = Radial gauge;
Caption = RPM;

Width = 300;
Height = 300;

RingWidth = .5;

ForegroundShape{
{Class = Ellipse; Color = $FF000000; Center = 150/150; Radius = 3; LineWidth = 1; LineColor = $FF606060}
}

BackgroundShape{
{Class = Ellipse; Color = $FF000000; Center = 150/150; Radius = 150; LineWidth = 0; LineColor = $FF606060}
}

Input{
ParamType = I_EngineRPM;
ParamSubtype = 1;
MinValue = 1600;
MaxValue = 4000;
StartAngle = -160;
EndAngle = 160;
ValueAngles{2000 = -90; 2600 = 0; 3200 = 90};
Needle{
SpearWidth = 3;
Width = 10;
CenterY = 130;
Length = 110;
Color = $FFFFFFFF;
OutlineColor = $FF606060;
}

Scales{
Green{
MinValue = 2600;
MaxValue = 2700;
Radius = 145;
RingWidth = 10;
RingColor = $FF10F010;
}
Red{
MinValue = 3005;
MaxValue = 3600;
Radius = 145;
RingWidth = 10;
RingColor = $FFFF0000;
}
Black{
MaxValue = 4000;
RingWidth = ;
RingColor = $FFFFFFFF;
Font{Size = 20; Color = $FFFFFFFF}
Markers{
Big{MaxValue = 4000; Count = 13; Height = 20; Width = 5; TextMultiplier = 0,01}
Med{MaxValue = 4000; Count = 25; Height = 20; Width = 5; TextFormat = }
Small{MaxValue = 3050; Count = 30; Height = 10; Width = 3; TextFormat = }
}
CustomMarkers{
2850{Value = 2850; Width = 5; Height = 20; Text = ; Color = $FFFFFF00}
// 3600{Value = 3600; Width = 5; Height = 30; Text = ; Color = $FFFF0000}
180{Value = 1800; Width = 5; Height = 20; Color = $FF95FF95; Text = 18; TextColor = $FF95FF95}
200{Value = 2000; Width = 5; Height = 20; Color = $FF95FF95; Text = 20; TextColor = $FF95FF95}
240{Value = 2400; Width = 5; Height = 20; Color = $FF95FF95; Text = 24; TextColor = $FF95FF95}
260{Value = 2600; Width = 5; Height = 20; Color = $FF95FF95; Text = 26; TextColor = $FF95FF95}
300{Value = 3000; Width = 5; Height = 20; Color = $FF95FF95; Text = 30; TextColor = $FF95FF95}
320{Value = 3200; Width = 5; Height = 20; Color = $FF95FF95; Text = 32; TextColor = $FF95FF95}
360{Value = 3600; Width = 5; Height = 20; Color = $FF95FF95; Text = 36; TextColor = $FF95FF95}
380{Value = 3800; Width = 5; Height = 20; Color = $FF95FF95; Text = 38; TextColor = $FF95FF95}
}
}
}
}

Items{
HUNDREDS{
Class = Label;
Left = 90;
Top = 80;
Width = 100;
Height = 20;
Font{Size = 14; Color = $FF606060}
}

R.P.M.{
Class = Label;
Left = 100;
Top = 100;
Width = 100;
Height = 25;
Font{Size = 22; Color = $FF606060}
}
}



turn coordinator



Class = Radial gauge;
Caption = Turn Coordinator;

Width = 300;
Height = 300;

RingWidth = 1;

BackgroundShape{
{Class = Ellipse; Color = $FF000000; Center = 150/150; Radius = 150; LineWidth = 0; LineColor = $FF606060}
{Class = Ellipse; Color = $FF000000; Center = 150/150; Radius = 105; LineWidth = 1; LineColor = $50606060}
{Class = Arc; Center = 150/-75; Width = 33; Radius = 285; FromAngle = 165; ToAngle = 195; Color = $FF808080}
}

ForegroundShape{
{Class = Line; Points = 135/195, 135/225; Color = $FF303030}
{Class = Line; Points = 165/195, 165/225; Color = $FF303030}
}

Inputs{
Slip{
ParamType = I_Slip;
MinValue = -20;
MaxValue = 20;
StartAngle = 167.5;
EndAngle = 192.5;
CenterY = -60;
Needle{
Shape {
{Center = 0/-270; Class = Ellipse; Color = $FF150010; RingWidth = 0.5; Radius = 15; LineColor = $FF303030}
}
}
Scales{
Main{
Radius = 210;
RingWidth = 0;
}
}
}

TurnL{
ParamType = I_Turn;
MinValue = -1.2;
MaxValue = 1.2;
StartAngle = -110;
EndAngle = -70;
Needle{
Shape {
{Class = Polygon; Color = $FFFFFFFF; Points = 1/-100, 1/100, -2/100, -10/0, -2/-100; LineWidth = ; LineColor = }
{Class = Ellipse; Color = $FFFFFFFF; Radius = 15; LineWidth = ; LineColor = }
{Class = Line; ; Color = $FFFFFFFF; Points = 30/0, 15/0; Width = 3}
{Class = Line; ; Color = $FFFFFFFF; Points = 15/30, 15/-30; Width = 3}
}
}
Scales{
Main{
Font{Size = 18; Color = $FFFFFFFF}
Radius = 105;
RingWidth = 0;
CustomMarkers{
C{Value = 0; Width = 10; Height = -25; Text =}
1.2{Value = -1.2; Width = 10; Height = -25; Text =}
// L{Value = -1.2; Width = 0; Height = -0.1; Text =L}
}
}
}
}

TurnR{
ParamType = I_Turn;
MinValue = -1.2;
MaxValue = 1.2;
StartAngle = 70;
EndAngle = 110;
Scales{
Main{
Font{Size = 18; Color = $FFFFFFFF}
Radius = 105;
RingWidth = 0;
CustomMarkers{
C{Value = 0; Width = 10; Height = -25; Text =}
1.2{Value = 1.2; Width = 10; Height = -25; Text =}
// R{Value = 1.2; Width = 0; Height = -0.1; Text =R}
}
}
}
}
}

Items{
TURN COORDINATOR{
Class = Label;
Caption = TURN COORDINATOR;
Left = 50;
Top = 165;
Width = 200;
Height = 12;
Font{Size = 8; Style = B; Color = $FFFFFFFF}
}
2 MIN.{
Class = Label;
Caption = 2 MIN.;
Left = 50;
Top = 225;
Width = 200;
Height = 16;
Font{Size = 15; Color = $FFFFFFFF}
}
NO PITCH{
Class = Label;
Caption = NO PITCH;
Left = 100;
Top = 253;
Width = 100;
Height = 12;
Font{Size = 8; Color = $FF808080}
}
INFORMATION{
Class = Label;
Caption = INFORMATION;
Left = 100;
Top = 268;
Width = 100;
Height = 12;
Font{Size = 8; Color = $FF808080}
}
L{
Class = Label;
Caption = L;
Left = 35;
Top = 190;
Width = 50;
Height = 50;
Font{Size = 22; Style = B; Color = $FFFFFFFF}
}
R{
Class = Label;
Caption = R;
Left = 215;
Top = 190;
Width = 50;
Height = 50;
Font{Size = 22; Style = B; Color = $FFFFFFFF}
}
}



variometer




Class = Radial gauge;
Caption = Variometer;

Width = 300;
Height = 300;

RingWidth = 1;

ForegroundShape{
{Class = Ellipse; Color = $FF000000; Center = 150/150; Radius = 3; LineWidth = 1; LineColor = $FF606060}
}

BackgroundShape{
{Class = Ellipse; Color = $FF000000; Center = 150/150; Radius = 150; LineWidth = 0; LineColor = $FF606060}
{Class = Line; Points = 290/130, 290/170; Width = 3; Color = $FFFFFFFF}
}

Input{
ParamType = I_Variometer;
MinValue = -4000;
MaxValue = 4000;
StartAngle = 98;
EndAngle = 442;
Needle{
SpearWidth = 2;
Width = 10;
CenterY = 130;
Length = 100;
Color = $FFFFFFFF;
OutlineColor = $FF606060;
}

Scales{
.5{
RingWidth = 0;
Font{Size = 12; Color = $FFFFFFFF}
CustomMarkers{
+0.5{Value = 500; Text = .5 ; Height = 25; Width = 3; TextColor = $FFFFFFFF}
-0.5{Value = -500; Text = .5 ; Height = 25; Width = 3; TextColor = $FFFFFFFF}
}
}

Main{
RingWidth = 0;
Font{Size = 25; Color = $FFFFFFFF}
Markers{
Climb{MinValue = 0; Count = 5; Height = 30; Width = 3; TextMultiplier = 0,001}
Descent{MaxValue = -1000; Count = 4; Height = 30; Width = 3; TextMultiplier = -0,001}
Medium{MinValue = -4000; MaxValue = 4000; Count = 17; Height = 30; Width = 3; Color = $FFFFFFFF; TextFormat = }
+Medium10{MinValue = 0; MaxValue = 2000; Count = 21; Height = 15; Width = 2; Color = $FFFFFFFF; TextFormat = }
+Medium250{MinValue = 2000; MaxValue = 4000; Count = 9; Height = 15; Width = 2; Color = $FFFFFFFF; TextFormat = }
-Medium10{MinValue = 0; MaxValue = -2000; Count = 21; Height = 15; Width = 2; Color = $FFFFFFFF; TextFormat = }
-Medium250{MinValue = -2000; MaxValue = -4000; Count = 9; Height = 15; Width = 2; Color = $FFFFFFFF; TextFormat = }
}
CustomMarkers{
0{Value = 0; Text = 0; Height = 30; Width = 3; TextColor = $FFFFFFFF}
// +0.5{Value = 500; Text = .5 ; Height = 30; Width = 3; TextColor = $FFFFFFFF; TextSize = 10}
// -0.5{Value = -500; Text = .5 ; Height = 30; Width = 3; TextColor = $FFFFFFFF; TextSize = 10}
+4{Value = 4000; Text = ; Height = 30; Width = 3; TextColor = $FFFFFFFF}
-4{Value = -4000; Text = ; Height = 30; Width = 3; TextColor = $FFFFFFFF}
}
}
}
}

Items{
UP{
Class = Label;
Left = 55;
Top = 90;
Width = 50;
Height = 14;
Font{Size = 12}
}

DOWN{
Class = Label;
Left = 55;
Top = 189;
Width = 50;
Height = 14;
Font{Size = 12}
}

VERTICAL SPEED{
Class = Label;
Left = 75;
Top = 95;
Width = 150;
Height = 15;
VAlignment = Center;
Font{Size = 10; Color = $FF606060}
}

THOUSAND FT PER MIN{
Class = Label;
Left = 75;
Top = 115;
Width = 150;
Height = 15;
VAlignment = Center;
Font{Size = 10; Color = $FF606060}
}

4{
Class = Label;
Left = 250;
Top = 130;
Width = 15;
Height = 30;
Font{Size = 25}
}
}



this is enough for the moment... still a lot of WIP and not much time

1lokos
May-06-2014, 00:58
Blenheim panel repositioned, include "Bombenabwurfgerat" (selector Single/Salvo on Blenheim) and "Bombs Reserve" panel.
The bombs keys on bombardier cockpit is "bugged", on Salvo mode, they dont go down when bombs are dropped,
only after select Single mode again - after drop the bombs - they move down, the VC replicate this behavior...
On Single mode the keys monitor correctly the bombs status, but the keys on panel move down 1, 3, 2, 4.
VC is 1, 2, 3, 4 what is correctly, bombs are drop:
1st left bomb of Left bay
2nd right bomb of Left bay
3rd left bomb of Right bay, etc...

Curiously when bomb are drop the needle of engine temperature instrument swing. :S

9743
9742


EDIT (05.22)- Add a light for help engage Autopilot and some "gadjets".

Sokol1

tom.doniphon
May-06-2014, 04:21
I am in the process to resizing all my instruments to add bezel images, but you can try some of them "naked" if you wish.



Wow Gadget, great work! They look as real instruments. Can't wait to see your virtual cockpit completed.

Doniphon

Steam
May-06-2014, 08:49
Hi. Thanks for DeviceLink
This is my version.
And I'm looking for Ju-87, Ju-88 and He-111 DeviceLink panels

tom.doniphon
May-06-2014, 09:45
Hi!

This is my virtual cockpit for BF109 E3. I'm using a Nexus 7 tablet, great resolution but little real room, so it looks a bit "crowded". I recommend you to resize and relocate according your own resolution.

9470

If you want coloured markings for recommended engine settings, open _ManifoldPressure.ini, look for Scales section and delete the two initial slashes (//) in the lines starting with d, 30 and 5. The same with _RPM.ini file.

For proper use you need install the Alte DIN 1451 Mittelschrift font, included in the file. If not, it will use Arial and maybe don't fit well.

DeviceLink don't send data for Afterburner for the 109 so I've included a false "Notleistung" warning light like a workaround. It lights when the ata is bigger than 1.3. Consider this when you fly the B versions or the E4N, or simply delete the entry WEP in cockpit.ini. It can be used without problems with the rest of E1 and E4 variants.

Well...

101ECV_GADGET
May-08-2014, 10:38
Blenheim panel repositioned, include "Bombenabwurfgerat" (selector Single/Salvo on Blenheim) and "Bombs Reserve" panel.
The bombs keys on bombardier cockpit is "bugged", on Salvo mode, they dont go down when bombs are dropped,
only after select Single mode again - after drop the bombs - they mode the move down, the VC replicate this behavior...
On Single mode the keys monitor correctly the bombs status, but the keys on panel move down 1, 3, 2, 4.
VC is 1, 2, 3, 4 what is correctly, bombs are drop:
1st left bomb of Left bay
2nd right bomb of Left bay
3rd left bomb of Right bay, etc...

Curiously when bomb are drop the needle of engine temperature instrument swing. :S

9461

9462

Sokol1




Moito obrigado, Sokol1

101ECV_GADGET
May-08-2014, 10:39
Hi!

This is my virtual cockpit for BF109 E3. I'm using a Nexus 7 tablet, great resolution but little real room, so it looks a bit "crowded". I recommend you to resize and relocate according your own resolution.

9470

If you want coloured markings for recommended engine settings, open _ManifoldPressure.ini, look for Scales section and delete the two initial slashes (//) in the lines starting with d, 30 and 5. The same with _RPM.ini file.

For proper use you need install the Alte DIN 1451 Mittelschrift font, included in the file. If not, it will use Arial and maybe don't fit well.

DeviceLink don't send data for Afterburner for the 109 so I've included a false "Notleistung" warning light like a workaround. It lights when the ata is bigger than 1.3. Consider this when you fly the B versions or the E4N, or simply delete the entry WEP in cockpit.ini. It can be used without problems with the rest of E1 and E4 variants.

Well...



Big Thankyou

Steerpots
May-09-2014, 03:37
S! All
Thought I'd share my effort at a VC for the Spitfire.
The monitor I use is an old 10" touchscreen I had lying around.
It obviously has limited screen space, however it sits rather nicely under my main monitor.

I removed some of the gauges because of space restrictions.
I also added some features to other gauges:
Indicator light to water temperature
Altimiter now reads down to nearest foot and changed the needle colours so I could see it.
Increased then size of the font in the directional gyro so I could read it easier (better than it looks in this screenshot)
Engine controls gauge was made bigger and colours changed to enhance viewability.
Altered colours on numerous gauges for viewability and aesthetics.

56RAF Steerpots (US-T)

X-Raptor
May-09-2014, 05:29
S! All
Thought I'd share my effort at a VC for the Spitfire.
The monitor I use is an old 10" touchscreen I had lying around.
It obviously has limited screen space, however it sits rather nicely under my main monitor.

I removed some of the gauges because of space restrictions.
I also added some features to other gauges:
Indicator light to water temperature
Altimiter now reads down to nearest foot and changed the needle colours so I could see it.
Increased then size of the font in the directional gyro so I could read it easier (better than it looks in this screenshot)
Engine controls gauge was made bigger and colours changed to enhance viewability.
Altered colours on numerous gauges for viewability and aesthetics.

56RAF Steerpots (US-T)

Great work Steerpots, it is possble for you or you want to share your work with us here? I would be interested to try your panel, I have a 8" TABLET res. is 1024x768 I use VC , do you think it can fit?

56RAF_klem
May-09-2014, 16:16
Great work Steerpots, it is possble for you or you want to share your work with us here? I would be interested to try your panel, I have a 8" TABLET res. is 1024x768 I use VC , do you think it can fit?

Not to steal Steerpot's thunder but it will depend on his screen resolution. If it is the same aspect ratio as yours (1024 / 768 = 1.3333 : 1) then all you have to do is select 'Scale to fit Monitor' and it will be OK. I made one for my Samsung Galaxy Note 8" (back on page 4 I think) but it is 1200 x 800 = 1.5:1, so it would look squashed vertically on your Tablet.

tom.doniphon
May-09-2014, 17:07
Not to steal Steerpot's thunder but it will depend on his screen resolution. If it is the same aspect ratio as yours (1024 / 768 = 1.3333 : 1) then all you have to do is select 'Scale to fit Monitor' and it will be OK. I made one for my Samsung Galaxy Note 8" (back on page 4 I think) but it is 1200 x 800 = 1.5:1, so it would look squashed vertically on your Tablet.

I think VC maintains aspect ratio but resize to fits the selected screen. For example, If I put your Spitfire Mk IIa Lo Panel (1680x1050) in my 1024x768 display, VC draws it at 1008x630 and centered.

Doniphon

1lokos
May-09-2014, 18:50
I am trying make a "Repeater Compass" for He 111, Bf 110... but with no success. :ind:

This instrument have a rotary outside scale, similar to Course setter in P-8 Magnetic Compass in British planes. And respond to keys assigned to adjust Course Setter.

And have a needle (the small plane), that point for true North.

The problem is the instrument (in game) rotate the needle position when you turn the outside scale.

I dont figure how do this in VC...

The actual "workaround" - a Repeater Compass that work like P-8 Compass. :D

http://i59.tinypic.com/aac8ef.jpg

The outside scale is fixed (1) - is DeviceLink "I_RDF" (that dont have use), just to make a independent scale, although is possible use a unused subtype (2, 3, 4...) of one used parameters.

The white rectangle is the "Course Setter", rotate with keys assigned for this command in game, allowing set the course. Use "I_Peilzeiger" data.

The "plane" is the Repeater Compass needle, point for (true) North, what in this case dont point for course at 12:00 o'clock like in game because the scale rotate, but the needle no... use "I_Repeater Compass" data.

(1) This is why is used a fix scale, because if use a rotary one, the needle point to wrong direction. The "Course Setter" commands dont turn the Repeater Compass needle.

Work... But anyone figure how do this in the "right way"?

Code:


Caption = Repeater compass;

Class = Radial gauge;

Width = 250;
Height = 250;

RingWidth = 2;

Inputs{
Scale{
ParamType = I_ADF;
ParamSubtype = 0;
MinValue = 0;
MaxValue = 360;
StartAngle = -360;
EndAngle = 0;
RotateScale = true;
Needle{
Shape{}
}
Scales{
Digits{
Radius = 95;
RingWidth = 0;
Font{Size = 12; Color = $FFA0A040}
Markers{
BigW{MinValue = 30; MaxValue = 60; Count = 2; Width = 1; Height = -3; TextMultiplier = 0.1;}
BigX{MinValue = 120; MaxValue = 150; Count = 2; Width = 1; Height = -3; TextMultiplier = 0.1;}
BigY{MinValue = 210; MaxValue = 240; Count = 2; Width = 1; Height = -3; TextMultiplier = 0.1;}
BigZ{MinValue = 300; MaxValue = 330; Count = 2; Width = 1; Height = -3; TextMultiplier = 0.1;}
Med{Count = 25; Width = 1; Height = -10; TextFormat = }
Small{Count = 73; Width = 1; Height = -3; TextFormat = }
}
CustomMarkers{
N{Value = 0; Width = 0; Text =; Height = -7}
S{Value = 180; Width = 0; Text =; Height = -7}
W{Value = 270; Width = 0; Text =; Height = -7}
E{Value = 90; Width = 0; Text =; Height = -7}
}
}
Labels{
Radius = 100;
RingWidth = 0;
Font{Size = 12; Color = $FFA0A040}
CustomMarkers{
N{Value = 0; Width = 2; Height = -7; Text = N; TextColor = $FFA0A040}
S{Value = 180; Width = 2; Height = -7; Text = S; TextColor = $FFA0A040}
W{Value = 270; Width = 2; Height = -7; Text = W; TextColor = $FFA0A040}
E{Value = 90; Width = 2; Height = -7; Text = 0; TextColor = $FFA0A040}
}
}
}
}

RepeaterCompass{
ParamType = I_RepeaterCompass;
ParamSubtype = 0;
MinValue = 0;
MaxValue = 360;
StartAngle = -360;
EndAngle = 0;
Needle{
Shape{
{Class = Ellipse; Color = 0; RingWidth = 0.5; Radius = 18; }
{Class = Ellipse; Color = 0; RingWidth = 0.5; Radius = 10; }
{Class = Line; Points = 0/-82, 0/-60; Color = $FFA0A040; Width = 10}
{Class = Line; Points = 0/-50, 0/30; Color = $FFA0A040; Width = 3}
{Class = Line; Points = -40/-25, 40/-25; Color = $FFA0A040; Width = 3}
{Class = Line; Points = -10/25, 10/25; Color = $FFA0A040; Width = 3}
}
}
Scale{
Radius = 82;
RingWidth = 0,5;
RingColor = $FFA0A0A0;
Font{Size = 10; Color = $FFA0A0A0}
MarkerTextOrientation = Aligned;
_Markers{
Big{Count = 13; Height = 5; Width = 1}
Med{Count = 37; Height = 3; Width = 1; TextFormat = }
}
}
}
Peilzeiger{
ParamType = I_Peilzeiger;
ParamSubtype = 0;
MinValue = 0;
MaxValue = 360;
StartAngle = 0;
EndAngle = -360;
RotateScale = true;
Needle{
Length = 0;
CenterY = 100;
Width = 0;
SpearWidth = 0;
Color = $FFA0A040;
OutlineColor = $FF006000;
OutlineWidth = 2;
}
Scales{
Digits{
Radius = 95;
RingWidth = 0;
Shape{
{Class = Line; Width = 10; Points = 125/33, 125/43}
}
}
}


Sokol1

56RAF_klem
May-09-2014, 18:54
I think VC maintains aspect ratio but resize to fits the selected screen. For example, If I put your Spitfire Mk IIa Lo Panel (1680x1050) in my 1024x768 display, VC draws it at 1008x630 and centered.

Doniphon

Ah, OK. I didn't realise that. Maybe my 8" one for the Spitfire will suit you.

tom.doniphon
May-10-2014, 06:10
X-Raptor, maybe you want try these: Hurricane and Spitfire VC for Nexus 7 tablet.

Hurricane I

9532

Spitfire Ia

9533

And the files:

9534

Doniphon

tom.doniphon
May-10-2014, 06:28
I am trying make a "Repeater Compass" for He 111, Bf 110... but with no success. :ind:

Sokol1

No luck here with this, anyway I'll send you a PM. If anyone could help I'll be very grateful.




The outside scale is fixed (1) - is DeviceLink "I_RDF" (that dont have use), just to make a independent scale, although is possible use a unused subtype (2, 3, 4...) of one used parameters.
Sokol1

AFAIK, you don't need to use another parameter for make a "dummy" second scale, only name it differently.

Doniphon

1lokos
May-10-2014, 20:55
Tom

Thanks for files, saves a lot of work. :thumbsup:

Well, I think for Repeater Compass work as should only if DeviceLink
has a parameter "C_RepeaterCompassPinion " to turn the needle...

Sokol1

tom.doniphon
May-11-2014, 06:27
Tom

Thanks for files, saves a lot of work. :thumbsup:

Sokol1

:salute:

1lokos
May-13-2014, 19:34
Tiger Moth with fake (but functional) Artificial Horizon - the parameters I_AH, I_Variometer for this planes is frozen - so use Z_Orientation.2.

9624
9625

EDIT - Add Slats and Trim. DeviceLink dont export fuel indicator data...

Sokol1

tom.doniphon
May-14-2014, 03:50
Thank you!
:thumbsup:

101ECV_GADGET
May-14-2014, 09:57
obrigado Sokol1

101ECV_GADGET
May-14-2014, 21:23
I have got several questions for the experts about instrument rendering:

1) How can I draw an Elypse (defining major and minor radii). So far I can only draw circles.

2) How can I draw a circle sector, from DDD degrees, to GGG degrees. I can only draw archs, but I need to fill them witha solid color.

3) How can I add alphanumeric characters to an artificial horizon. I have tried everything and the characters always rotate with the movement of the horizont to stay paralel to the bottom of the instrument. I want the characters to stay in teh same position so they can move with the artificial horizont.

4) How can I orientate the alphanumeric characters of a scale, for instance to run vertical, horizontal, etc. indepentdenly of the orietation of the scale (perpendicular to the movement for instance).

5) I am interested in rendering bezels for the instruments (pics of bezels cause a big drop in FPS), but I would need to set transparent some sectors of a complex polyline. Can it be done?

6) Can I add rendered textures to surfaces?

Thank you in advance

1lokos
May-14-2014, 23:22
1) How can I draw an Elypse (defining major and minor radii). So far I can only draw circles.


I try an work:

{Class = Ellipse; Center = 50/50; RadiusY = 10; RadiusX = 20; LineWidth = 2; LineColor = $FFFFFFFF; Color = $FF808080}

Sokol1

101ECV_GADGET
May-15-2014, 03:53
it works !!!!!!!!

Gracias !!!!!

Now. to draw only a sector of that elypse?

X-Raptor
May-15-2014, 10:14
X-Raptor, maybe you want try these: Hurricane and Spitfire VC for Nexus 7 tablet.

Hurricane I

9532

Spitfire Ia

9533

And the files:

9534

Doniphon

:thumbsup: Hallo Doniphon !:) Thank you very much for you help about Hurry and Spit VC files! I'll go to try this night and report back!Thank you again. Best regards and have a good day.!. cheers from Italy.:)

tom.doniphon
May-15-2014, 18:26
:thumbsup: Hallo Doniphon !:) Thank you very much for you help about Hurry and Spit VC files! I'll go to try this night and report back!Thank you again. Best regards and have a good day.!. cheers from Italy.:)

:salute:

Steerpots
May-16-2014, 04:54
S! All
The latest incarnation of my spitfire VC.
Have re-used other peoples gauges (when I liked them)

56RAF_Steerpots(US-T)

9627

1lokos
May-16-2014, 11:09
I need help with G-50 Altimeter.

This have two scales, the Outer 0 - 5 in 360 degrees, and Inner 5 to 8 in 180 degrees.

If I set a 540 (360+180) degrees a "gap" appear between 5 and 0. :S

http://i60.tinypic.com/etfwhc.jpg

I try use a Multiplier, this fix the Outer scale, but broken the Inner...
Try "Remainder", AngleFrom/To... used in other Altimeter but none solve this... :stunned:

Sokol1

tom.doniphon
May-16-2014, 12:29
Hi Sokol1

Try this:

MinValue = 0;
MaxValue = 8000;
StartAngle = 0;
EndAngle = 540;
ValueAngles{5000 = 360}

Hope this help

1lokos
May-16-2014, 14:57
Perfectly! :thumbsup:

http://i58.tinypic.com/16lfzvd.jpg

Need only change the value for 5=360. Some G-50 data output is different from other planes.

Thank you.

Sokol1

tom.doniphon
May-16-2014, 16:00
Like I've read somewhere: Dr Wholeg world... :):)
:thumbsup:

Steam
May-17-2014, 04:25
S! All
The latest incarnation of my spitfire VC.
Have re-used other peoples gauges (when I liked them)

56RAF_Steerpots(US-T)

9627

Very nice.:thumbsup:
May I download your version?

Steerpots
May-17-2014, 11:44
Very nice.:thumbsup:
May I download your version?

S! Steam
I'm more than happy to share my VC with you, or indeed anyone who wants it.

Be aware that I use the version of the VC software that allows both "." and "," to repesent the decimal point.
My ini files therefore contain both punctuation marks for the decimal point.
If your VC software doesn't accept both then my VC will not work for you and will throw an error when you try to run it.

I have updated it a little since the last post, I added a low fuel warning indicator.

tom.doniphon
May-19-2014, 11:02
Hi!

BF110 C4 Virtual Cockpit:

9683

Thanks to 1sokol for his help with the Repeater Compass (and the nice plane drawing). It works slightly different to the real instrument. The scale is fixed. The yellow triangle is the Peilzeiger, with it you select the course you want to follow (Course setter +/-). The plane and the white triangle mark your real course (Repeater Compass). When both triangles are coincidents you are heading desired course.

This VC uses the same font as the Luftwaffe did, Alte DIN 1451 Mittelschrift. It is included in the zip file.



Hope you like it.

Doniphon

ATAG_Bliss
May-19-2014, 12:05
Hi!

BF110 C4 Virtual Cockpit:

9683

Thanks to 1sokol for his help with the Repeater Compass (and the nice plane drawing). It works slightly different to the real instrument. The scale is fixed. The yellow triangle is the Peilzeiger, with it you select the course you want to follow (Course setter +/-). The plane and the white triangle mark your real course (Repeater Compass). When both triangles are coincidents you are heading desired course.

This VC uses the same font as the Luftwaffe did, Alte DIN 1451 Mittelschrift. It is included in the zip file.



Hope you like it.

Doniphon

Hi Tom - That is awesome! Thank you very much! :salute:

LBR=H.Ostermann
May-19-2014, 19:11
Hi!

BF110 C4 Virtual Cockpit:

9683

Thanks to 1sokol for his help with the Repeater Compass (and the nice plane drawing). It works slightly different to the real instrument. The scale is fixed. The yellow triangle is the Peilzeiger, with it you select the course you want to follow (Course setter +/-). The plane and the white triangle mark your real course (Repeater Compass). When both triangles are coincidents you are heading desired course.

This VC uses the same font as the Luftwaffe did, Alte DIN 1451 Mittelschrift. It is included in the zip file.



Hope you like it.

Doniphon


Thank you!

1lokos
May-20-2014, 12:35
Hi!

BF110 C4 Virtual Cockpit:



Thank you. Very nice design. :thumbsup:

I use your Kurssteurung disengage button to add a Autopilot help in Blenheim VC.

Since Devicelink dont export Kurssteurung data for Blenheim (after all he use a "captured" one :D ) I use DI values to indicate when engage Autopilot:
The pilot need remember that in Blenheim is "forbidden" touch Kurssteuerung right/left adjust keys before engage, or the Autopilot get "crazy".

If DI read 0 - 1.5 the light turn ON. Autopilot can be engaged without oscillation.
If DI read 2 - 359.5 the light turn OFF. Condition not adequate to engage Autopilot.

The lamp does not indicate that autopilot is active (no data for this), just the ideal condition for engaging.

http://i58.tinypic.com/sfxq47.jpg

http://theairtacticalassaultgroup.com/forum/showthread.php?t=3887&p=117337&viewfull=1#post117337

Sokol1

Steerpots
May-25-2014, 10:52
S! All
I have a question;
I want to have a flashing indicator light, that continues to flash on/off while the input parameter is between two values.
In simple programming terms I want to implement a loop that repeats while the input parameter is <= MaxValue and >= MinValue.

Is this possible ?... and while I'm at it is there any documentation for the VC software ? specifically something listing all the possible commands/operators available.

56RAF_Steerpots

101ECV_GADGET
May-26-2014, 06:53
Yes
I am still working on my caution panel and also thought about an intermitent flashing warning, creating a counting loop, but no successs.

I would also appreciate some help here

hnbdgr
May-28-2014, 04:25
Hi All

I'm currently talking with a developer who is doing plugins for this little panel: http://coldtearselectronics.wikispac...CD+System+info

the software used for it is called goverlay http://www.goverlay.com/content/lcdsysinfo/

It is basically a very cheap LCD, capable of displaying various info, among others telemetry information.

The developer has agreed to do a plugin for it for free(!) bought and installed a copy of cliffs of dover on his machine. But he contacted me saying he's got trouble using the code provided in the TF Device Link thread as that's not exactly how Goverlay works. In that regard he asked me to get in touch with someone who knows more about telemetry in CloD so I'm posting here to ask for help.

His latest message was:

I’ve been taking a look at the way the info is gathered.

Im able to convert the code that was shown in the thread to grab the sensors but its not the way GOverlay can read it, the problem is that the info shown in that thread is not much, I need a structure of how the shared telemetry shows.

Do you have any more info about it or a way to speak to whoever did it to see whats the structure of the telemetry?



Can anybody help with this?

many thanks

badger

Steerpots
May-30-2014, 05:01
S! All
Another iteration/example of a spitfire VC.
This one was for a friend using a 2nd monitor running at 1900x1200
I have re-used other peoples gauges/needles when I liked the work...all due respect to originators

There are a few notable features to mention:
1. VC is not overcrowded with gauges/switches...easier on the eye
2. IAS has numeric display to nearest 1 MPH and has a warning lamp
3. RPM has numeric display to nearest 1 RPM and has a warning lamp
4. Boost has negative numbers and has been made easier to read
5. Oil temp has scale showing when it's cold and a warning lamp
6. Water temp has scale showing when it's cold and a warning lamp
7. Altimeter has a numeric display to nearest 1 foot
8. Magnetic Compass displays your current heading to nearest 1/100th of a degree and the entire bezel rotates rather than just the needle.
9. There is NO directional gyro
10. Fuel gauge has numeric display to nearest 1/100th of a gallon and a fuel level warning light
11. Oil pressure has a warning light
12. Fuel pressure warning light moved to sit with the fuel pressure gauge

Happy to discuss and share should anyone want to.

56RAF_Steerpots

tom.doniphon
May-30-2014, 11:28
Hi Steerpots,

The Brakes Pressure Gauge you're using is for Blenheim. You can use this from my Spitfire VC that has the correct scales:

9852

Some things that I'd add:

IAS Gauge with two needles:

9853

Some COD's Spitfire cockpit animations are unfinished (Like Trims, Slow Running Cut-Out...). If you look carefully the IAS gauge, it has two needles but working together so I made like Hurricane's: one for the outer and one for the inner.

Proper needles for Elevator Trim and Slip/Turn:

9854 9855

And the correct scale for the Fuel Gauge:

9856

I made this later so here it is the code:


Class = Radial gauge;
Caption = Fuel Reserve;

Width = 150;
Height = 150;

ForegroundShape{
{Class = Arc; Center = 75/75; Width = 6; Radius = 72; FromAngle = 0; ToAngle = 360; Color = $FF333333}
}

Inputs{
TailOnGround{
ParamType = I_FuelReserve;
MinValue = 0;
MaxValue = 37;
StartAngle = 210;
EndAngle = 150;
CenterY = 0;
ValueAngles{5 = 198; 20 = 180}
Needle{
Shape{
{Class = Polygon; Points = -1.5/-2, -1/-90, 0/-95, 1/-90, 1.5/-2; Color = $FFFFFFFF; LineColor = $FFFFFFFF; LineWidth = 1}
}
}
Scale{
Radius = 100;
RingWidth = 2;
Font{Size = 8; Style = B; Color = $FFFFFFFF}
MarkerTextOrientation = Inverted;
Markers{MaxValue = 30; Count = 7; Width = 2; Height = 5}
CustomMarkers{
37{Value = 37; Width = 2; Height = 5}
20{Value = 20; Width = 2; Height = 5; Text =}
}
}
}
NormalFlignt{
ParamType = I_FuelReserve;
MinValue = 0;
MaxValue = 37;
StartAngle = 210;
EndAngle = 150;
CenterY = 0;
ValueAngles{5 = 199; 20 = 181; 25 = 174; 30 = 165}
Needle{Visible = false}
Scale{
Radius = 100;
RingWidth = 0;
Font{Size = 9; Style = B; Color = $FFFFFFFF}
MarkerTextOrientation = Inverted;
Markers{MaxValue = 35; Count = 8; Width = 2; Height = -5}
CustomMarkers{
37{Value = 37; Width = 2; Height = -5}
15{Value = 15; Width = 2; Height = -5; Text =}
25{Value = 25; Width = 2; Height = -5; Text =}
35{Value = 35; Width = 2; Height = -5; Text =}
}
}
}
}

Items{
GALLONS FUEL{
Class = Label;
Left = 0;
Top = 45;
Width = 150;
Height = 14;
HAlignment = Center;
VAlignment = Center;
Font{Size = 11; Style = B; Color = $FFDE9D7F}
}
NORMAL FLIGHT{
Class = Label;
Left = 0;
Top = 118;
Width = 150;
Height = 10;
HAlignment = Center;
VAlignment = Center;
Font{Size = 7; Style = B; Color = $FFDE9D7F}
}
TAIL ON GROUND{
Class = Label;
Left = 0;
Top = 60;
Width = 150;
Height = 10;
HAlignment = Center;
VAlignment = Center;
Font{Size = 7; Style = B; Color = $FFDE9D7F}
}
CAPACITY TANK{
Class = Label;
Left = 0;
Top = 22;
Width = 150;
Height = 10;
HAlignment = Center;
VAlignment = Center;
Font{Size = 7; Style = B; Color = $FFF01010}
}
37 GALLONS{
Class = Label;
Left = 0;
Top = 32;
Width = 150;
Height = 8;
HAlignment = Center;
VAlignment = Center;
Font{Size = 7; Style = B; Color = $FFF01010}
}
}

Feel free to use anything of this if you like it.

S!

Steerpots
May-30-2014, 12:06
S! tom
Thanks for the fuel gauge scale stuff.
I like your spitfire brakes gauge, can you supply the code please.

56RAF_Steerpots

tom.doniphon
May-30-2014, 15:24
Sure!


Class = Radial gauge;
Caption = Pneumo Container Pressure;

Width = 200;
Height = 200;

RingWidth = 6;
RingColor = $FF333333;

BackgroundShape{
{Class = Text; Pos = 100/100; Text = SUPPLY; Radius = 75; PosAngle = -45; HAlignment = Center; VAlignment = Center; Font{Size = 9; Style = B; Color = $FFDE9D7F}}
{Class = Text; Pos = 100/100; Text = MAX; Radius = 89; PosAngle = 104; HAlignment = Center; VAlignment = Center; Font{Size = 8; Style = B; Color = $FFDE9D7F}}
}

Inputs{
PCP{
ParamType = S_PneumoContainerPressure;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 480;
StartAngle = -90;
EndAngle = 90;
Needle{
Shape{
{Class = Polygon; Points = -1/-66, 0/-86, 1/-66; Color = $FFFFFFFF; LineColor = $FFFFFFFF; LineWidth = 1}
{Class = Ellipse; Center = 0/-60; Radius = 6; Color= 0; LineColor = $FFFFFFFF; LineWidth = 2}
{Class = Polygon; Points = -2/0, -1/-54, 1/-54, 2/0; Color = $FFFFFFFF; LineColor = $FFFFFFFF; LineWidth = 1}
{Class = Ellipse; Center = 0/0; Radius = 5; Color = $FF404040; LineColor = $FFFFFFFF; LineWidth = 4}
}
}
Scale{
Radius = 90;
RingWidth = 2;
Font{Size = 12; Color = $FFFFFFFF}
Markers{
BigNumber{MinValue = 240; MaxValue = 400; Count = 2; Height = 7; Width = 3; TextMultiplier = 0.125}
Big{Count = 7; Height = 7; Width = 3; TextFormat = }
Med{Count = 31; Height = 5; Width = 1; TextFormat = }
}
}
}

PortBrake{
ParamType = A_Brake;
ParamSubtype = 1;
MinValue = 0;
MaxValue = 1;
StartAngle = -170;
EndAngle = -10;
CenterX = 89;
CenterY = 119;
Radius = 68;
Needle{
Shape{
{Class = Polygon; Points = -2/0, -0.5/-61, 0/-62, 0.5/-61, 2/0; Color = $FFFFFFFF; LineColor = $FFFFFFFF; LineWidth = 1}
{Class = Ellipse; Center = 0/0; Radius = 5; Color = $FF404040; LineColor = $FFFFFFFF; LineWidth = 4}
}
}
Scale{
RingWidth = 2;
Font{Size = 12; Color = $FFFFFFFF}
Markers{
Big{MinValue = 0.5; MaxValue = 1; Count = 2; Height = 7; Width = 3; TextMultiplier = 20}
Med{Count = 5; Height = 7; Width = 3; TextFormat = }
Small{Count = 17; Height = 5; Width = 1; TextFormat = }
}
}
}

StartbdBrake{
ParamType = A_Brake;
ParamSubtype = 2;
MinValue = 0;
MaxValue = 1;
StartAngle = 170;
EndAngle = 10;
CenterX = 111;
CenterY = 119;
Radius = 68;
Needle{
Shape{
{Class = Polygon; Points = -2/0, -0.5/-61, 0/-62, 0.5/-61, 2/0; Color = $FFFFFFFF; LineColor = $FFFFFFFF; LineWidth = 1}
{Class = Ellipse; Center = 0/0; Radius = 5; Color = $FF404040; LineColor = $FFFFFFFF; LineWidth = 4}
}
}
Scale{
RingWidth = 2;
Font{Size = 12; Color = $FFFFFFFF}
Markers{
Big{MinValue = 0.5; MaxValue = 1; Count = 2; Height = 7; Width = 3; TextMultiplier = 20}
Med{Count = 5; Height = 7; Width = 3; TextFormat = }
Small{Count = 17; Height = 5; Width = 1; TextFormat = }
}
}
}
}

Items{
BRAKES{
Class = Label;
Left = 50;
Top = 37;
Width = 100;
Height = 15;
HAlignment = Center;
VAlignment = Center;
Font{Size = 11; Style = B; Color = $FFDE9D7F}
}
PORT{
Class = Label;
Left = 45;
Top = 90;
Width = 50;
Height = 16;
HAlignment = Center;
VAlignment = Center;
Font{Size = 9; Style = B; Color = $FFDE9D7F}
}
STARB{
Class = Label;
Left = 105;
Top = 90;
Width = 50;
Height = 16;
HAlignment = Center;
VAlignment = Center;
Font{Size = 9; Style = B; Color = $FFDE9D7F}
}
MR1D{
Class = Label;
Caption = MR 1D;
Left = 75;
Top = 125;
Width = 50;
Height = 16;
HAlignment = Center;
VAlignment = Center;
Font{Size = 9; Style = B; Color = $FFDE9D7F}
}
}

S!

101ECV_GADGET
Jun-03-2014, 14:33
Any idea about how to make touch screen buttons?

Steerpots
Jun-03-2014, 18:49
Any idea about how to make touch screen buttons?

Hi Gadget, I used the following a few years ago http://www.touch-buddy.com/forums/

56RAF_Steerpots

Bait
Jun-04-2014, 03:17
Any idea about how to make touch screen buttons?


Hi Gadget, I used the following a few years ago http://www.touch-buddy.com/forums/

56RAF_Steerpots


If you have an iPad, you might want to take a look at this.

http://touchpilot.com/touch-pilot-one/

I have a old iPad 1 that I am thinking of using for this. Sets up as a Virtual Joystick in Windows.