Hey RAZBAM, I had an idea for the Kneeboard

[Shadow_1stVFW]

Dear Devs,

 

I came up with an idea that I'd figure I'd throw out there.

 

I remember Cpt Smiley sending out the .Lua file that corrected the Kneeboard page after an update a little while back and it had me thinking. How cool would it be to have another (fourth) kneeboard page with an editable lua so we could place information into the in game cockpit that is both editable and yet persistent across multiple games.

 

Here is an example:

 

 

The utility cannot be overstated. Here are just a few uses

 

1) As shown, pertinent information for a flight. Mission designers could provide this file to players so they share it

2) In MP servers like Blue flag, players could plug in well known points (cities/farps etc) or common points of interest (CAP points, Rendezvous points etc)

3) Hotkey commands which are easily viewable (with the press of one button)

4) Listing important frequencies

 

The page would be a very useful notepad customizable for each player. I'm aware that one could do nearly the same thing currently by making a photo and adding it to the kneeboard as well. I got this idea after using this tool to edit the aircraft's ECM programs https://www.digitalcombatsimulator.com/en/files/2262585/

 

Just my 2 cents, cheers

[CrashO]

Tested the theory

 

You already can do this (apparently).

 

I liked the idea so decided to do a quick (and really dirty..) proof of concept try to see if it works with what is already there. And you can do it with the current implementation.

 

 

 

All I did was go into:

DCS World\Mods\aircraft\M-2000C\Cockpit\KNEEBOARD\pages

 

and created a new file (in addition to the 3 existing ones), called 4.lua .

And stuck this in there:

 

dofile(LockOn_Options.common_script_path.."KNEEBOARD/indicator/definitions.lua")
SetScale(FOV)

add_picture("Mods/aircraft/M-2000C/Cockpit/Resources/IndicationTextures/notepad.dds")

-- GENERAL SCALE
local general_font_scale = 1.0

FontSizeX1	= 0.0075 * general_font_scale
FontSizeY1	= FontSizeX1 

predefined_font_20 = {general_font_scale* FontSizeY1*2.0, general_font_scale* FontSizeX1*2.0, 0.0, 0.0}
predefined_font_10 = {general_font_scale* FontSizeY1, 	  general_font_scale* FontSizeX1	, 0.0, 0.0}
predefined_font_09 = {general_font_scale* FontSizeY1*0.9, general_font_scale* FontSizeX1*0.9, 0.0, 0.0}
predefined_font_08 = {general_font_scale* FontSizeY1*0.8, general_font_scale* FontSizeX1*0.8, 0.0, 0.0}
predefined_font_07 = {general_font_scale* FontSizeY1*0.7, general_font_scale* FontSizeX1*0.7, 0.0, 0.0}
predefined_font_06 = {general_font_scale* FontSizeY1*0.6, general_font_scale* FontSizeX1*0.6, 0.0, 0.0}
predefined_font_05 = {general_font_scale* FontSizeY1*0.5, general_font_scale* FontSizeX1*0.5, 0.0, 0.0}

function AddElement(object)
   object.use_mipfilter = true
   Add(object)
end


local LineSizeY   = FontSizeY1 * 9
local ColumnSizeX = FontSizeX1 * 48 / 72 * 8 

firstLineY = - LineSizeY

local hints_scale		= MakeMaterial("arcade.tga", {255, 128, 64, 255})

local base_size_x   = ColumnSizeX * 45.0
local base_size_y   = LineSizeY   * 17.0
local base_size_x05 = base_size_x * 0.5
local base_size_y05 = base_size_y * 0.5

HintsBase					= CreateElement "ceSimple"
HintsBase.name				= "HintsBase"
HintsBase.init_pos			= {0, GetAspect() - 3.5 * FontSizeY1}
AddElement(HintsBase)

-- Alignment Vars
local delta_pos_y = LineSizeY * 1.35

-- Page Title --

local PDA_Adjust_x = -0.9
local PDA_Adjust_y = -LineSizeY * 1.35

txt_PageTitle					= CreateElement "ceStringPoly"
txt_PageTitle.name				= "txt_PageTitle"
txt_PageTitle.material			= "font_hints_kneeboard"
txt_PageTitle.init_pos			= {PDA_Adjust_x,  PDA_Adjust_y, 0}
txt_PageTitle.value				= "PILOT NOTES:"
txt_PageTitle.parent_element	= HintsBase.name
txt_PageTitle.stringdefs		= predefined_font_08
AddElement(txt_PageTitle)

local PAD_pos_x0 = 0
local PAD_pos_x1 = -0.95
local PAD_pos_x2 = -0.20
local PAD_pos_x3 = -0.30
local PAD_pos_y = -delta_pos_y * 2.2


local Ground_Adjust_x = -0.9
local Ground_Adjust_y = - LineSizeY * 1.35
local weapon_delta_pos_y	= LineSizeY * 1.35
local weapon_names_pos_y	= Ground_Adjust_y - LineSizeY * 1.35
local ConfigWarning_pos_y	= weapon_names_pos_y - weapon_delta_pos_y * 1





-- Repeating line-blocks below here

notes_element_01				= CreateElement "ceStringPoly"
notes_element_01.name			= "notes_element_01"
notes_element_01.material		= "font_hints_kneeboard"
notes_element_01.init_pos		= {Ground_Adjust_x,  weapon_names_pos_y - weapon_delta_pos_y * 1, 0}
notes_element_01.value			= "WAYPOINTS:"
notes_element_01.parent_element	= HintsBase.name
notes_element_01.stringdefs		= predefined_font_05
AddElement(notes_element_01)


notes_element_02				= CreateElement "ceStringPoly"
notes_element_02.name			= "notes_element_02"
notes_element_02.material		= "font_hints_kneeboard"
notes_element_02.init_pos		= {Ground_Adjust_x,  weapon_names_pos_y - weapon_delta_pos_y * 2, 0}
notes_element_02.value			= "N POINT N12.45.45 E124.58.2"
notes_element_02.parent_element	= HintsBase.name
notes_element_02.stringdefs		= predefined_font_05
AddElement(notes_element_02)


notes_element_03				= CreateElement "ceStringPoly"
notes_element_03.name			= "notes_element_03"
notes_element_03.material		= "font_hints_kneeboard"
notes_element_03.init_pos		= {Ground_Adjust_x,  weapon_names_pos_y - weapon_delta_pos_y * 3, 0}
notes_element_03.value			= "TGT N12.34.56 E123.45.67"
notes_element_03.parent_element	= HintsBase.name
notes_element_03.stringdefs		= predefined_font_05
AddElement(notes_element_03)

 

(basically it is just the code from the existing pages stripped and some test lines added). If you scroll down to the bottom you can see some nice repeating segments that are just asking to be parsed and generated by a helper tool (like the one I wrote for the countermeasures :D). After cleaning up the rest of the file.

 

However, I still have to find out how to use special characters (like ( ) ) or even lower-case letters. Because anything else then Captital letters will break things at the moment.

 

But perhapt Razbam might me able to shine a light on the format nessescary (already tried escaping entries with backslashes) :D

 

*edit*

Or do you mean editable from within the plane itself? (That is gonna give the poor developers nightmares and delay my beloved Harrier :megalol:)

Edited February 24, 2017 by CrashO

[Shadow_1stVFW]

That's very cool. I'll have to play around with it this weekend. I can tweak some stuff but this looks like it's above my abilities. So I posed it to the community and devs, figured someone smarter than me could do something with it.

 

BTW, ECM tool is great, especially since you can move the program from 2.0 to 1.5 and such. That's awsome.

 

Sent from my SAMSUNG-SM-G900A using Tapatalk

[VTJS17_Fire]

We use our own missioncards created in MS Excel, save this as PDF and load it via the Kneeboard Builder tool into the DCS kneeboard.

 

Very comfortable and you get a lot of information in one page.

[CrashO]

Did a quick cleanup of the code and wrote in some code that removes and replaces some stuff that messes things up. So you can just insert brackets and mix capital and lowercase letters without having to wory about breaking the kneeboard.

And I got it to use a single multi-line variable.

 

So all the way at the top of the lua file you will get something like this:

local pilotNotes = [[
WAYPOINTS:
N Point (N12:45.45 E124:58.2)
TGT (N12:34.56 E123:45.67)
TNKR (N12:34.56 E123:45.67)

Code Word:
Miller Time - Mission Complete
Burt Renolds - AAA Down
Sterling - SAMs Down
Lana - GND TGTs engaged

Times (UTC)
Start - 16:31
Taxi - 16:50
T/O - 17:00
IN TNK - 17:20
Rendez - 17:58
CAP - 18:15 - 18:50

FR Units:
Boar 1: A-10C x4
UZI 5: SA432 x2
Dark Star : AWACS
ARCO: TNKR
Enfield: F-14D x2
]]

 

And that generates this ingame:

 

So it is a lot easier to edit for people who get confused by large walls of code :D

Still haven't figured out how to get lowercase letters in there though.

 

Will try and work out something later tonight and post the entire code (and instructions) once it is working correctly.

Edited February 24, 2017 by CrashO

[Oceandar]

Hmm, I just use my pen and paper and place it near my Hotas. Simple :D

[Sarge55]

Pencil would be better. You know, just in case...

[Shadow_1stVFW]

Did a quick cleanup of the code and wrote in some code that removes and replaces some stuff that messes things up. So you can just insert brackets and mix capital and lowercase letters without having to wory about breaking the kneeboard.

And I got it to use a single multi-line variable.

 

So all the way at the top of the lua file you will get something like this:

local pilotNotes = [[
WAYPOINTS:
N Point (N12:45.45 E124:58.2)
TGT (N12:34.56 E123:45.67)
TNKR (N12:34.56 E123:45.67)

Code Word:
Miller Time - Mission Complete
Burt Renolds - AAA Down
Sterling - SAMs Down
Lana - GND TGTs engaged

Times (UTC)
Start - 16:31
Taxi - 16:50
T/O - 17:00
IN TNK - 17:20
Rendez - 17:58
CAP - 18:15 - 18:50

FR Units:
Boar 1: A-10C x4
UZI 5: SA432 x2
Dark Star : AWACS
ARCO: TNKR
Enfield: F-14D x2
]]

 

And that generates this ingame:

 

So it is a lot easier to edit for people who get confused by large walls of code :D

Still haven't figured out how to get lowercase letters in there though.

 

Will try and work out something later tonight and post the entire code (and instructions) once it is working correctly.

 

Looking really good, actually worked out better than I originally thought.

 

And for everyone else, here is the stream of consciousness that lead me to making this post

 

One day I was filming a video, starting from the cold start. The mission didn't have waypoints pre loaded. While I was looking down at my real kneeboard as I was typing in my waypoints and while doing that the video was jumping all over the place and was really disorienting. And I thought to myself, man, it'd be nice if my waypoints were loaded into the kneeboard like the initial position was. That way I could just keep looking in game to plug it all in.

 

As I thought more about it, I figured having some standard reference points in there would be nice. As well as my waypoints, but it couldn't just be the waypoints from the flight plan because in Blue flag or something it wouldn't be helpful. So a standard set of data that I had on there would be great. So, after I made a different mission I thought it'd be nice to send a quick file that my friends could place in a folder (or JSGME), they don't all use kneeboard maker or what not.

 

Sure, paper works fine, but that's not what I'm looking for, nor is it the point of the post.

[Zeus67]

You already can do this (apparently).

 

I liked the idea so decided to do a quick (and really dirty..) proof of concept try to see if it works with what is already there. And you can do it with the current implementation.

 

 

 

All I did was go into:

DCS World\Mods\aircraft\M-2000C\Cockpit\KNEEBOARD\pages

 

and created a new file (in addition to the 3 existing ones), called 4.lua .

And stuck this in there:

 

dofile(LockOn_Options.common_script_path.."KNEEBOARD/indicator/definitions.lua")
SetScale(FOV)

add_picture("Mods/aircraft/M-2000C/Cockpit/Resources/IndicationTextures/notepad.dds")

-- GENERAL SCALE
local general_font_scale = 1.0

FontSizeX1    = 0.0075 * general_font_scale
FontSizeY1    = FontSizeX1 

predefined_font_20 = {general_font_scale* FontSizeY1*2.0, general_font_scale* FontSizeX1*2.0, 0.0, 0.0}
predefined_font_10 = {general_font_scale* FontSizeY1,       general_font_scale* FontSizeX1    , 0.0, 0.0}
predefined_font_09 = {general_font_scale* FontSizeY1*0.9, general_font_scale* FontSizeX1*0.9, 0.0, 0.0}
predefined_font_08 = {general_font_scale* FontSizeY1*0.8, general_font_scale* FontSizeX1*0.8, 0.0, 0.0}
predefined_font_07 = {general_font_scale* FontSizeY1*0.7, general_font_scale* FontSizeX1*0.7, 0.0, 0.0}
predefined_font_06 = {general_font_scale* FontSizeY1*0.6, general_font_scale* FontSizeX1*0.6, 0.0, 0.0}
predefined_font_05 = {general_font_scale* FontSizeY1*0.5, general_font_scale* FontSizeX1*0.5, 0.0, 0.0}

function AddElement(object)
   object.use_mipfilter = true
   Add(object)
end


local LineSizeY   = FontSizeY1 * 9
local ColumnSizeX = FontSizeX1 * 48 / 72 * 8 

firstLineY = - LineSizeY

local hints_scale        = MakeMaterial("arcade.tga", {255, 128, 64, 255})

local base_size_x   = ColumnSizeX * 45.0
local base_size_y   = LineSizeY   * 17.0
local base_size_x05 = base_size_x * 0.5
local base_size_y05 = base_size_y * 0.5

HintsBase                    = CreateElement "ceSimple"
HintsBase.name                = "HintsBase"
HintsBase.init_pos            = {0, GetAspect() - 3.5 * FontSizeY1}
AddElement(HintsBase)

-- Alignment Vars
local delta_pos_y = LineSizeY * 1.35

-- Page Title --

local PDA_Adjust_x = -0.9
local PDA_Adjust_y = -LineSizeY * 1.35

txt_PageTitle                    = CreateElement "ceStringPoly"
txt_PageTitle.name                = "txt_PageTitle"
txt_PageTitle.material            = "font_hints_kneeboard"
txt_PageTitle.init_pos            = {PDA_Adjust_x,  PDA_Adjust_y, 0}
txt_PageTitle.value                = "PILOT NOTES:"
txt_PageTitle.parent_element    = HintsBase.name
txt_PageTitle.stringdefs        = predefined_font_08
AddElement(txt_PageTitle)

local PAD_pos_x0 = 0
local PAD_pos_x1 = -0.95
local PAD_pos_x2 = -0.20
local PAD_pos_x3 = -0.30
local PAD_pos_y = -delta_pos_y * 2.2


local Ground_Adjust_x = -0.9
local Ground_Adjust_y = - LineSizeY * 1.35
local weapon_delta_pos_y    = LineSizeY * 1.35
local weapon_names_pos_y    = Ground_Adjust_y - LineSizeY * 1.35
local ConfigWarning_pos_y    = weapon_names_pos_y - weapon_delta_pos_y * 1





-- Repeating line-blocks below here

notes_element_01                = CreateElement "ceStringPoly"
notes_element_01.name            = "notes_element_01"
notes_element_01.material        = "font_hints_kneeboard"
notes_element_01.init_pos        = {Ground_Adjust_x,  weapon_names_pos_y - weapon_delta_pos_y * 1, 0}
notes_element_01.value            = "WAYPOINTS:"
notes_element_01.parent_element    = HintsBase.name
notes_element_01.stringdefs        = predefined_font_05
AddElement(notes_element_01)


notes_element_02                = CreateElement "ceStringPoly"
notes_element_02.name            = "notes_element_02"
notes_element_02.material        = "font_hints_kneeboard"
notes_element_02.init_pos        = {Ground_Adjust_x,  weapon_names_pos_y - weapon_delta_pos_y * 2, 0}
notes_element_02.value            = "N POINT N12.45.45 E124.58.2"
notes_element_02.parent_element    = HintsBase.name
notes_element_02.stringdefs        = predefined_font_05
AddElement(notes_element_02)


notes_element_03                = CreateElement "ceStringPoly"
notes_element_03.name            = "notes_element_03"
notes_element_03.material        = "font_hints_kneeboard"
notes_element_03.init_pos        = {Ground_Adjust_x,  weapon_names_pos_y - weapon_delta_pos_y * 3, 0}
notes_element_03.value            = "TGT N12.34.56 E123.45.67"
notes_element_03.parent_element    = HintsBase.name
notes_element_03.stringdefs        = predefined_font_05
AddElement(notes_element_03)

(basically it is just the code from the existing pages stripped and some test lines added). If you scroll down to the bottom you can see some nice repeating segments that are just asking to be parsed and generated by a helper tool (like the one I wrote for the countermeasures :D). After cleaning up the rest of the file.

 

However, I still have to find out how to use special characters (like ( ) ) or even lower-case letters. Because anything else then Captital letters will break things at the moment.

 

But perhapt Razbam might me able to shine a light on the format nessescary (already tried escaping entries with backslashes) :D

 

*edit*

Or do you mean editable from within the plane itself? (That is gonna give the poor developers nightmares and delay my beloved Harrier :megalol:)

 

The Kneeboard page uses a special font set that only has Uppercase letters and no special characters. I also wanted to use lowercase and special characters as well, but since I am dealing with somebody else's code I decided to play it safe and use what was made available.

 

I'll try to create my own font for the Harrier's kneeboard page and if successful I will updgrade the M-2000C's kneeboard as well.

[CrashO]

While I was looking down at my real kneeboard as I was typing in my waypoints and while doing that the video was jumping all over the place and was really disorienting. And I thought to myself, man, it'd be nice if my waypoints were loaded into the kneeboard like the initial position was. That way I could just keep looking in game to plug it all in.

Well, if it is about immersion, I wouldn't use the screenoverlay "K" kneepad, but rather the one modeled on the pilots leg (rShift+P to toggle pilot). :music_whistling:

 

Unfortunately, that one doesnt use code, but is a static image.. So, some coffee later, I bring you this: Worlds most limited image generator, ever :D

 

 

 

Write the text (and any funky characters you might want). Push the save button for the version you want (same principle as my ECM tool). And start up your game :pilotfly:

 

 

 

As of now, typing and saving stuff works great for all versions (and saving a empty textbox restores the orginal-kneeboard).

But I still have to implement the "load" buttons, so you can change existing boards, before I release the tool.

Edited February 26, 2017 by CrashO

[Nash]

Hey RAZBAM, I had an idea for the Kneeboard

 

Oh this is sick...

 

Love this... When are you releasing it mate...

Edited February 26, 2017 by Nash

[Shadow_1stVFW]

Well, if it is about immersion, I wouldn't use the screenoverlay "K" kneepad, but rather the one modeled on the pilots leg (rShift+P to toggle pilot). :music_whistling:

 

Unfortunately, that one doesnt use code, but is a static image.. So, some coffee later, I bring you this: Worlds most limited image generator, ever :D

 

 

 

Write the text (and any funky characters you might want). Push the save button for the version you want (same principle as my ECM tool). And start up your game :pilotfly:

 

 

 

As of now, typing and saving stuff works great for all versions (and saving a empty textbox restores the orginal-kneeboard).

But I still have to implement the "load" buttons, so you can change existing boards, before I release the tool.

CrashO, I hate that you are so productive. I had thought about this, but figured it wasn't open for editing. This is great. Even better than I originally hoped for. Great, just great.

 

Is it limited to a single page?

I know some aircraft that texture is linked to the kneeboard overlay.

 

Sent from my SAMSUNG-SM-G900A using Tapatalk

[CrashO]

I finished the tool (for the texture board, not the lua "K" one).

 

 

And a list of data to insert if you want to give it a testrun (for those flying BlueFlag)

Farps:
#1 DK58: N45:00.25 E038:32.37 @ 00040 ft
#1 EJ08: N44:08.45 E039:01.98 @ 00133 ft
#2 FK93: N44:31.75 E041:27.00 @ 00000 ft
#2 EJ98: N44:05.20 E040:08.88 @ 01989 ft
#3 LN71: N42:36.58 E043:27.82 @ 02755 ft
#4 GJ35: N43:47.27 E041:54.95 @ 02887 ft
#4 GH22: N42:36.23 E041:44.68 @ 00231 ft
#6 MM59: N42:26.53 E044:29.28 @ 05488 ft
#6 MM05: N42:01.57 E043:49.28 @ 02112 ft

CommArrays
#1 DK61: N44:23.90 E038:31.97 @ 00180 ft
#2 GK40: N44:16.40 E042:06.26 @ 01939 ft
#3 KP90: N43:21.30 E042:26.25 @ 18435 ft
#4 FJ57: N43:59.98 E040:57.75 @ 02625 ft
#5 LM55: N42:01.62 E043:11.62 @ 00919 ft
#6 MM39: N42:22.12 E044:13.38 @ 07812 ft

Cities:
#1 Anap: N44:54.33 E037:19.17 @ 00000 ft
#1 Novo: N44:43.15 E037:44.92 @ 00287 ft
#1 Abin: N44:53.70 E038:10.22 @ 00087 ft
#2 Kras: N45:02.12 E039:01.09 @ 00091 ft
#3 Pyat: N44:02.52 E043:05.18 @ 01942 ft
#3 Vlad: N43:03.28 E044:41.75 @ 02148 ft
#4 Bzyb: N43:13.63 E040:21.53 @ 00131 ft
#4 Sukh: N43:01.57 E040:59.68 @ 00307 ft
#5 Zugd: N42:30.65 E041:51.95 @ 00347 ft
#5 Kuta: N42:14.95 E042:37.50 @ 00361 ft
#5 Poti: N42:08.32 E041:40.30 @ 00000 ft
#6 Tbil: N41:43.23 E044:44.13 @ 01658 ft
#6 Rust: N41:33.05 E045:02.88 @ 01168 ft

 

You can download it here. Don't think there is a need for a manual. It works exactly the same as the ECM tool. Insert your text (and/or change the header text). And press the save button for the version of DCS you want to use it on.

 

After flying find out you want to change the text? Use the load button for that version and it loads up the current text again.

 

I will leave it here for a few days until there is some feedback regarding fonts and sizes (I tried a few, this seemed a nice compromise between readability and the amount of stuff that fits on there, and all characters are the same size, so you can align things using spaces). Or any other issues. And upload it to the file libary on the dcs website once everyone is happy with it :)

Edited March 19, 2017 by CrashO
link got broken, updated to new download

[Shadow_1stVFW]

I finished the tool (for the texture board, not the lua "K" one).

 

 

And a list of data to insert if you want to give it a testrun (for those flying BlueFlag)

Farps:
#1 DK58: N45:00.25 E038:32.37 @ 00040 ft
#1 EJ08: N44:08.45 E039:01.98 @ 00133 ft
#2 FK93: N44:31.75 E041:27.00 @ 00000 ft
#2 EJ98: N44:05.20 E040:08.88 @ 01989 ft
#3 LN71: N42:36.58 E043:27.82 @ 02755 ft
#4 GJ35: N43:47.27 E041:54.95 @ 02887 ft
#4 GH22: N42:36.23 E041:44.68 @ 00231 ft
#6 MM59: N42:26.53 E044:29.28 @ 05488 ft
#6 MM05: N42:01.57 E043:49.28 @ 02112 ft

CommArrays
#1 DK61: N44:23.90 E038:31.97 @ 00180 ft
#2 GK40: N44:16.40 E042:06.26 @ 01939 ft
#3 KP90: N43:21.30 E042:26.25 @ 18435 ft
#4 FJ57: N43:59.98 E040:57.75 @ 02625 ft
#5 LM55: N42:01.62 E043:11.62 @ 00919 ft
#6 MM39: N42:22.12 E044:13.38 @ 07812 ft

Cities:
#1 Anap: N44:54.33 E037:19.17 @ 00000 ft
#1 Novo: N44:43.15 E037:44.92 @ 00287 ft
#1 Abin: N44:53.70 E038:10.22 @ 00087 ft
#2 Kras: N45:02.12 E039:01.09 @ 00091 ft
#3 Pyat: N44:02.52 E043:05.18 @ 01942 ft
#3 Vlad: N43:03.28 E044:41.75 @ 02148 ft
#4 Bzyb: N43:13.63 E040:21.53 @ 00131 ft
#4 Sukh: N43:01.57 E040:59.68 @ 00307 ft
#5 Zugd: N42:30.65 E041:51.95 @ 00347 ft
#5 Kuta: N42:14.95 E042:37.50 @ 00361 ft
#5 Poti: N42:08.32 E041:40.30 @ 00000 ft
#6 Tbil: N41:43.23 E044:44.13 @ 01658 ft
#6 Rust: N41:33.05 E045:02.88 @ 01168 ft

 

You can download it here. Don't think there is a need for a manual. It works exactly the same as the ECM tool. Insert your text (and/or change the header text). And press the save button for the version of DCS you want to use it on.

 

After flying find out you want to change the text? Use the load button for that version and it loads up the current text again.

 

I will leave it here for a few days until there is some feedback regarding fonts and sizes (I tried a few, this seemed a nice compromise between readability and the amount of stuff that fits on there, and all characters are the same size, so you can align things using spaces). Or any other issues. And upload it to the file libary on the dcs website once everyone is happy with it :)

I'll give it a try tonight and give you some feedback.looks good though.

 

Sent from my SAMSUNG-SM-G900A using Tapatalk

[Shadow_1stVFW]

I will leave it here for a few days until there is some feedback regarding fonts and sizes (I tried a few, this seemed a nice compromise between readability and the amount of stuff that fits on there, and all characters are the same size, so you can align things using spaces). Or any other issues. And upload it to the file libary on the dcs website once everyone is happy with it :)

 

Alright, did a little test flight in it. Overall, I think it's great, it gets the job done, definitely an improvement to the game. It adds to the overall immersion. From the FOV that I use the text was a bit small, but not enough to require a change in my mind, I definitely had to zoom in just a bit to read, but that's no worry. It's on par with how I have to use the Kneeboard in the KA-50 as well. The tool is simple enough to use, I really like the interface that you designed for the kneeboard and ECM tool.

 

I don't know how much work it would be, but the only thing I could even think to add would be an option to format the text a bit. Namely Bold, Italics, Underline, and Font color, I don't think I'd really need or use a different size, but like my headers to be at least underlined. Though, all that may be more trouble than it's worth. This definitely adds what I was originally thinking about when I started the thread.

 

Thank you CrashO, great add. 10/10 should use if they fly the Mirage.

[ESAc_matador]

Is this compatible with kneeboard builder?