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.

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:)

If immersion is the point, it's the FC3 arcade stuff that should be removed, Not the only fully simulated plane. :D

Tactics differ on the specifics. But my main go to tactics generally are: - Gain momentum by gaining altitude that you can exchange for speed when you need it , - Notch (90 degrees aspect on your bandit)while popping chaff (on a launch) and doing S turns while closing the distance - Stay low and use the terrain. Fly with your radar standby (not emitting) (or only on for short bursts) and use your RWR to get track your target until you (think you) are close enough. Only then engage it.

A lot of people are. Which is why SimpleRadio is so handy. You can report stuff that happens to either a GCI or other players. And just have private tactics/banter on a private freq or on your own teamspeak. SRS just allows for way more global awareness. And the lack of red using it is a large reason why many people join blue. (I hear people saying they went red x restarts ago, and because no-one used comms they came back to blue, all the time). Just look at this: See something different between the two teams?

Well, time so balance then.. (just kidding, red can keep their We-are-too-cool-for-simpleRadio because we don't have GCI players) :D

It's going to be a massive pain for the helicopters without INS to locate the farps and CommArrays without the map though. (like the Huey). I Wouldn't be against it, but only if all the bases get Radio beacons (or are anywhere close to existing beacons).

I have seen similar behavior, this was last week: u6ujZCErNCo I level off by hand (at 7sec) and engage AP + Altitude hold. Causing the nose to drop and AP spending half a minute to recover to a level flight (and losing 4000ft in the process). I then disengage it again, again level off and engage it. And it works just fine.

Red has 3 aircraft without RWR. Blue has 3. (L-39, MI-8, K-50) vs (Hawk, MI-8, Huey). So it is just a pissing match of pro's and cons either way. And no reason red never has a GCI. And to counter, RED has Migs/Su's with optical systems, so they can be effective without using radar, rendering blue's RWR useless. (if I had to count the amount of times I got a surprise Fox 2 up the six from a Mig29 while cruising the mirage ..)

No it's not. Those "mobile" EWR's don't do much. And are removed after each 3 hour reset anyway. And friendlies are always visible, regardless of EWR. You don't just need a GCI to send you to a blip on the map.. you need one to coordinate the right player to the right area (and alternate backups). 90% of the time when I am doing GCI I am blind. But if 2 people (such as strikers) report RWR nails to me, I can triangulate the position from there and dispatch the closest fighter over. Even when I don't actually see hostiles. When one player has radar track, he just has to report the position (Magic, Reaper 11, tally bandit 12 o-clock for 25 @ 11000 tracking West. And magic draws a nice line and knows exactly where the bandit is and where he is going, without seeing something. You don't need to see hostiles, to be a effective GCI.

How about, No GCI? Take one for the team and be one yourself at times.. On blue there are very few people who actually like to be GCI, but a lot of people (including myself) do the task when necessary, because it just doesn't make sense to have a ton of uncoordinated people doing random circles. And if their not on comms, bark at them in chat to come online. A few months ago 20% of blue was on SR during most times, nowadays it's > %75. But if no one at red takes the task on them and moans about it whilse they keep being part of the problem.. nothing while change :doh:

Getting Michael Bay to do your effects can be pretty expensive. I suggest investing in a GCI :D

Wouldn't it be easier to just change the scale labels? (and adjust default to a lot lower). I get the feeling that a lot of people don't expect to ever need to go below 0% for a good volume. Until they tune in at the server en get a lot of angry pilots telling them to turn it to -25% or lower :D Instead of -95 to 700. Make it (for the front-end) 0 - 795 (not sure if the 700 is fixed or hardware dependable?). And just make the default something like 100. I just feel that the negative - positive scale is confusing a lot of less tech savyi pilots who feel it needs to be in the positives to work, while on most pc's it need to be (way) below 0..

Then so does the MIG-29. I see them take-off with pretty close to their starting fuel (20%) loads of times to defend their airbase. How I know this? Because they spawn and roll onto the runway in less then a minute. With Mirages you have to wait at least 3 minutes after startup, until the radar is warmed up and ready before you can be any sort of effective. MIG-29's can just smack on some weapons and launch on takeoff with the default (minimal) fuel and start firing as soon as their gear is up.

Red has Mirages, same as blue has. Blue does not have russian stuff that can launch ER or ET's.. (red already has, from carriers on SU-33's). You need even more advantage? Not that hard to outmaneuver if your know its limitations. The 530 has some very powerfull trust, but it only last seconds. So just change your direction a few times after it has run out of fuel and you will be fine. Example: (watch from 1:10)

And to add to the problems, since ~30min. The server is not allowing any new clients. People on there, can still play. But it doesn't show up in the server list and directly connecting by IP results in a time-out. (I have seen this bug before, happens about once every couple of days). The chatlog clearly shows only people leaving since half a hour and no one connecting. I have seen this problem on other servers before, not sure what is causing it.

It crashed again (2min ago) after about 1 hour since the last reset.

Same with the A-10. It can use all of the weapons now, no restrictions.

It seems to be running 1.5.6 as of an hour ago. However, the update did brake weapons on the mirage (can only select magic's, no eclair, no 530, no external tank). Mission probably needs to be re-saved with the new version.

You posted in the Russian section of the forums :)

Yes, and no. The flares/chaff you select are for the internal dispensers. The eclair adds 18 chaff and 16 flares. You cannot change the amount it holds. So if you select the eclair, you just get +18 Chaff & +16 flare to whatever you have selected for the internal dispensers already :) You will see it after rearming, just look at the flare en chaff counters inside the cockpit.

FWD = Switch Forward AFT = Aft = Stern = Rear = Switch Backward

Viggen is getting released to 1.5.6. So yes, if you want it today.. you need open beta

I've posted the same reaction pretty much every single time you updated your thread. But there is not a whole lot to add. Awesome looking!!

With nav panel, you mean the data panel? Or the actual panel with the navigation instruments?