pdmarsh

@ESAc_matador -- You could very well be correct, but I must say that the script written by Chump as posted did indeed resolve the issue, so I'm doubtful that it is strictly a DCS issue. Yes, lots of the AI troops do get killed, but it makes for a heck of a battle to watch. You just keep dropping fresh troops until the job is done. I will try the firesupression script again, but the last time I tried it I was getting game crashes. In any case, thanks for your response and suggestions. Paul

I am having a similar issue with CTLD that I first experienced with CTTS. After dropping AI troops, they will not engage the enemy. In the case of CTLD, the troops will begin to move toward the enemy troops, but not only are they in single file, they stop as soon as the first shot is fired and will not engage or move any further. In my mission, the AI troops have to move up a slight incline to see and engage the enemy. As soon as the first AI troop reaches the crest, shots are fired and the AI troops stop moving as I noted, so the rest don't even see the enemy as yet. In the case of CTTS, this problem was resolved by script written by Chump and posted below. I tried to replace the findnearestenemy script in CTLD with this code, but it didn't work (which I was afraid would be the case). If anyone has any suggestions on how to improve the behavior of the AI troops, I would greatly appreciate it. I am trying get one of my missions updated from DCSW 1.0 to DCSW 1.5. Thanks, Paul -- Find nearest enemy to coalition according to a reference position function FindNearestEnemy(refpos, radius, groupside) local minDist = maxDistEnemy if radius == 0 then minDist = 50 end local EnemyPos = nil local destination = nil local xdest = nil local ydest = nil local selected = nil local group = nil local groupName = nil local units = nil local leader = nil local leaderpos = nil local dist = nil local RedList = coalition.getGroups(1, Group.Category.GROUND) local BlueList = coalition.getGroups(2, Group.Category.GROUND) local tbl = nil if groupside == 2 then tbl = RedList elseif groupside == 1 then tbl = BlueList end for i = 1, #tbl do if tbl[i] ~= nil then groupName = tbl[i]:getName() group = Group.getByName(groupName) if group ~= nil then units = group:getUnits() if units ~= nil then for x = 1, #units do if units[x]:getLife() > 0 then leader = units[x] break end end if leader ~= nil then leaderpos = leader:getPoint() dist = GetDistance(refpos.x, refpos.z, leaderpos.x, leaderpos.z) if dist < minDist then minDist = dist EnemyPos = leaderpos end end end end end end if EnemyPos ~= nil then xdest = EnemyPos.x + math.random(100, 200) - math.random(100, 200) ydest = EnemyPos.z + math.random(100, 200) - math.random(100, 200) else xdest = refpos.x + math.random(0, radius) - math.random(0, radius) ydest = refpos.z + math.random(0, radius) - math.random(0, radius) end local destination = { x = xdest, y = ydest, } return destination end

Thanks for the response. I guess we'll have to wait and see how things go, but I understand that things do change. Paul

I have essentially the same question as Blooze, but, put another way, when 1.5 or 2.0 are out of beta and released, will some (many?) existing missions remain broken until the scripts they use are themselves updated, or can we expect these scripting issues to be resolved within DCS World 2.0 itself? Thanks, Paul

Good to hear. Thanks for posting. Looking forward to trying the new beta. Paul

MFDs on 4th Monitor Show Last Image on Power Down This is a minor issue, but I will report it nonetheless. I noticed in both the A-10C and Ka-50 that when you power down the MFDs or the Shkval in-cockpit, the remote displays of these devices on a 4th monitor (in my case) do not go blank. They continue to show whatever was on them just before the power down. However, the in-cockpit displays do go blank. Thanks, Paul

I was about to post the Ka-50 HMS issue as well, but found this thread. I agree that setting up a single screen across three monitors is not ideal. I was experimenting with that to resolve another issue -- the F10 in-game map getting compressed into the middle monitor. By going to a single screen set up across three monitors you do lose the multi-monitor correction ability. However, it did resolve the map issue in that it spread across all three monitors and was not distorted. Thanks, Paul

@Mole--Thanks for the information. If I recall, I believe Saitek said that they could not reproduce the issue. In meantime I have switched to using Flightpanels to program my TPM and other Saitek panels. Paul

OK, I believe I have found the source of the issue along with a temporary workaround. In the code below you can see how I have my three main monitors set up in the lua file. In addition, the "UIMainView" has been defined as the "Center" viewport. This worked fine in DCSW 1.0, but the code is being interpreted differently in DCSW 1.5. The in-game F10 map view is being forced to fit into the center screen only, but at the higher resolution of 5282x1050 in my case. The view is not oblique as it appears, but is actually distorted as was noted in a post above (the clue I needed). Viewports = { Left = { x = 0; y = 0; width = 1760; height = 1050; viewDx = -1; viewDy = 0; aspect = 1760 / 1050; }, Center = { x = 1760; y = 0; width = 1761; height = 1050; viewDx = 0; viewDy = 0; aspect = 1761 / 1050; }, Right = { x = 1760 + 1761; y = 0; width = 1761; height = 1050; viewDx = 1; viewDy = 0; aspect = 1761 / 1050; } } UIMainView = Viewports.Center If I change my monitor set up as shown below, both the sim view and F10 map view span all three monitors and the image is not distorted. The problem with this is that you lose the "viewDx/Dy" triple monitor compensation or correction. It really isn't a good final fix. Viewports = { Center = { x = 0; y = 0; width = 5282; height = 1050; viewDx = 0; viewDy = 0; aspect = 5282 / 1050; } } UIMainView = Viewports.Center I have tried to use the original code and define the "UIMainView" as follows, but it doesn't work. If I can figure out how to properly define the "UIMainView," I think I might have this problem licked. UIMainView = { x = 0; y = 0; width = 5282; height = 1050; viewDx = 0; viewDy = 0; aspect = 5282 / 1050; } I am very open to any suggestions on how to set up the UIMainView. Thanks, Paul

Thanks Bourrinopathe. I just assumed this was intentional. Here is more info: System specs: Intel Core i7-4770K Haswell 3.5GHz LGA 1150 84W CPU GIGABYTE GA-Z87X-D3H LGA 1150 Intel Z87 HDMI SATA 6Gb/s USB 3.0 ATX Intel Motherboard GIGABYTE GV-N760OC-4GD GeForce GTX 760 4GB 256-Bit GDDR5 PCI Express 3.0 HDCP Ready WindForce 3X 450W Video Card CORSAIR Vengeance Pro 16GB (2 x 8GB) 240-Pin DDR3 SDRAM DDR3 1866 Desktop Memory Model CMY16GX3M2A1866C9R Seagate Hybrid Drive ST2000DX001 2TB MLC/8GB 64MB Cache SATA 6.0Gb/s NCQ 3.5" Desktop SSHD Microsoft Windows 7 Home Premium SP1 64-bit The mission was just a simple one generated by the DCS utility. However, this oblique view occurs in every mission I have tried so far. I run four monitors. Three are for the main view and the fourth is used for MFDs. When I use the in-game F10 map, it appears on the center monitor only (of the three that make up the main view). In DCS 1.0 it stretched across all four monitors. If I had a preference, I'd like the map to display across the three monitors that make up the main display. Same for the map view in mission editor. If I can or should post any other information, please let me know what that is. Thanks, Paul

I use a 4th monitor to display MFDs. In DCS World 1.5 a distorted background image appears. Is there a way to force this to just be blank or black as it is in 1.0? Thanks, Paul

Is there, or will there be, a way to get an overhead satellite view of the in-game F10 map in lieu of the current oblique view? Thanks, Paul

I recently made an interesting observation regarding saving mission tracks for later replay and DCS-BIOS generated commands. When using Flightpanels, I have some switches programmed as key stroke emulators and others using DCS-BIOS commands. It appears that only emulated key strokes get saved in the track file. Any DCS-BIOS inputs do not get saved. As a result, it becomes impossible to replay a mission. For example, I use DCS-BIOS for canopy open and canopy close commands in the A-10C. During replay, the canopy never closed, nor could I close it manually (as expected during replay, I suppose). I rarely use replay, but still it's a shame to not have this feature available when using Flightpanels. I'm so spoiled with FP that I can't see myself going back to keyboard control just on the off chance I want to replay a mission. If I were making videos from replays, though, I would have to avoid DCS-BIOS altogether. If anyone has any comments on this, we'd like to hear them. Maybe this can be "fixed." Thanks, Paul

Good point re. keeping the HDG button lit. I'll look forward to hearing how your testing goes. Thanks, Paul

@bouncerj21 -- I don't believe this is possible. You can set a keystroke to be held for up to sixty seconds, but not indefinitely--at least not that I have found. If I hear differently, I'll post that info. Paul

@Baldawg -- I have been testing this and here is what I found. First, I mapped the EGI Steer Point Button to the number "1" keyboard key (just happens to be available). I then mapped the Multi Panel HDG button ON position to the number "1" as well. In game this does act as a momentary press of the Steer Point Button. However, now the HDG button on the panel is lit and I don't want it to be. I did not map the HDG button OFF position to anything, so another press of that button on the panel simply turns off the LED. The in-game state of the Steer Point Button stays where it was. From reading your post, it sounds like this action no longer works for you. Is that correct? Now, if I try to use DCS-BIOS for Steer Point Button control, I cannot find any setting that will act as a momentary press. I'm guessing this is a limitation we would have to live with. So, it seems that you can use Multi Panel buttons as momentary inputs when mapped to keystrokes even though you have to deal with the LED state on the panel, i.e. you have to press the button a second time to turn off the LED. I do this in a number of profiles, so I'm used to it now. The trick is to leave the OFF state un-mapped. I'm not sure if this helps at all. Let us know if you are still having trouble. Thanks, Paul

Enjoyed the live stream and looking forward to more. For some of us there was confusion as to the start time. I was 45 minutes late as a result. I wonder if others missed it as well for this reason. I believe the start time was given as PST, but we are in daylight time now. Even a post with GMT given appears now to have been incorrect. What I did catch was great, though. Thanks.

@mightyseaking -- Wow, that's great information. Thanks for posting this--I'm sure it will help others. Paul

I'm glad the profile is working out for you. I like the BIP as well--it's a great addition to the sim-pit. Thanks for the label tip. I'll be making new tiles again soon. Paul

Our small group of players tried this mission recently and the artillery battery never fired any shells. We moved all 10 nuclear warheads to the artillery battery, placed FOs and called in the Tornado as well. While we certainly could have done something wrong, or did not complete a necessary step, we're wondering if updates to DCS World might have made the artillery script inoperable, i.e. broke it. :) If anyone has flown this recently, what was your experience? Speaking for myself, I do not have the ability to troubleshoot scripts as yet or I would be happy to have a look. Thanks, Paul

@JaBoG32_Prinzartus -- I have attached my Huey configuration file to this post. Included in the zip file is my template for the Switch Panel. This will show you how the switches are configured. The knob on the left is set up to turn on a number of radios (four, I think). Please let me know if you have any questions on any of this. Thanks, Paul UH-1H.zip

I will post my configuration file this evening. I make heavy use of the Switch Panel. I have the Radio Panel configured as well as some of the LEDs on the BIP. I have to share BIP LEDs with the A-10C, so there's a bit of a compromise there. At the moment, I am only using the flap lever on the Multi Panel to shut off the alarm. I have not configured any Multi Panel buttons or knobs for the Huey as yet, I'm afraid. I do have altitude and heading configured on the display, though. Paul

@Hammer -- I don't have time for much more at the moment, but I have attached my A-10C profile. You should be able to see how I have the push buttons mapped. You also should be able to cut and paste the lines if you want. Hope this helps for now. Paul A-10C.zip

@Hammer -- I might change things around a bit, but at the moment I'm using the push buttons for the start-up tests: signal lights, fire warning, fuel gauge and oxygen tests. I use another push button to set take-off trim. I use the knob to set heading and the trim wheel to set bearing on the HSI (or vice versa, not sure). I don't use the flap lever in the A-10, but I do use it in the MiG-21. Hope this helps. Paul

B.I.P. Configuration Example @GunfighterSIX -- I'll do the Pitot Tube as an example. 1. Right click on the LED you want to configure, then left click on "Configure." 2. Left click on the "New Green" button. 3. In the "...search words:" field type "pitot." 4. Double click on the line with "ENVCP_PITOT_HEAT." 5. In the "Enter trigger value:" field, change the "0" to a "1" 6. Click on "OK" You have just configured that LED to go green when pitot heat is on. Now... 7. Left click on the "New Dark" button. 8. Repeat steps 3 & 4 above. 9. This time, leave the trigger value at "0" 10. Click "OK" This will cause the LED to be dark when pitot heat is off. You might have to go through some trial and error with search terms. Also, I noticed that occasionally the 1s and 0s seem backwards. This probably has to do with how DCS-BIOS was set up in that case, or with DCS itself. In case it might help, I'll post my A-10C B.I.P. configuration code below. You can copy and paste this into your own config file if you wish either to use or just experiment with. Hope this helps. If you are having trouble with something specific, we'll try to help with that as well. Thanks, Paul P.S. -- If you do want to use the code below, you will have to change the panel ID number. Just find yours and do a search and replace. I believe the manual has notes on how to get your panel ID number. #---------------------------------------------BackLitPanel, \\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}--------------------------------------------- PanelBIP{Position_1_1|GREEN|DCSBiosOutput{EPP_BATTERY_PWR|Equals|1}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_1_1|DARK|DCSBiosOutput{EPP_BATTERY_PWR|Equals|0}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_2_1|GREEN|DCSBiosOutput{EPP_INVERTER|Equals|2}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_2_1|DARK|DCSBiosOutput{EPP_INVERTER|Equals|1}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_3_1|GREEN|DCSBiosOutput{OXY_SUPPLY|Equals|1}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_3_1|DARK|DCSBiosOutput{OXY_SUPPLY|Equals|0}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_2_2|GREEN|DCSBiosOutput{NOSEWHEEL_STEERING|Equals|1}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_2_2|DARK|DCSBiosOutput{NOSEWHEEL_STEERING|Equals|0}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_1_3|DARK|DCSBiosOutput{LCP_POSITION|Equals|1}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_1_3|GREEN|DCSBiosOutput{LCP_POSITION|Equals|2}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_2_3|GREEN|DCSBiosOutput{LANDING_LIGHTS|Equals|2}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_2_3|DARK|DCSBiosOutput{LANDING_LIGHTS|Equals|1}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_3_3|GREEN|DCSBiosOutput{LANDING_LIGHTS|Equals|0}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_3_3|DARK|DCSBiosOutput{LANDING_LIGHTS|Equals|1}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_1_4|RED|DCSBiosOutput{MASTER_CAUTION|Equals|1}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_1_4|DARK|DCSBiosOutput{MASTER_CAUTION|Equals|0}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_3_4|RED|DCSBiosOutput{AHCP_MASTER_ARM|Equals|2}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_3_4|YELLOW|DCSBiosOutput{AHCP_MASTER_ARM|Equals|0}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_3_4|DARK|DCSBiosOutput{AHCP_MASTER_ARM|Equals|1}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_1_5|RED|DCSBiosOutput{L_ENG_FIRE|Equals|1}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_1_5|DARK|DCSBiosOutput{L_ENG_FIRE|Equals|0}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_1_6|RED|DCSBiosOutput{R_ENG_FIRE|Equals|1}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_1_6|DARK|DCSBiosOutput{R_ENG_FIRE|Equals|0}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_2_5|YELLOW|DCSBiosOutput{CL_I2|Equals|1}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_2_5|DARK|DCSBiosOutput{CL_I2|Equals|0}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_2_6|YELLOW|DCSBiosOutput{CL_I3|Equals|1}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_2_6|DARK|DCSBiosOutput{CL_I3|Equals|0}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_3_5|YELLOW|DCSBiosOutput{AHCP_TGP|Equals|1}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_3_5|DARK|DCSBiosOutput{AHCP_TGP|Equals|0}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_3_6|YELLOW|DCSBiosOutput{AHCP_LASER_ARM|Equals|2}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_3_6|DARK|DCSBiosOutput{AHCP_LASER_ARM|Equals|1}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_1_7|GREEN|DCSBiosOutput{FLAPS_SWITCH|Equals|0}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_1_7|DARK|DCSBiosOutput{FLAPS_SWITCH|Equals|2}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_1_7|DARK|DCSBiosOutput{FLAPS_SWITCH|Equals|1}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_2_7|YELLOW|DCSBiosOutput{FLAPS_SWITCH|Equals|1}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_2_7|DARK|DCSBiosOutput{FLAPS_SWITCH|Equals|0}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_2_7|DARK|DCSBiosOutput{FLAPS_SWITCH|Equals|2}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_3_7|YELLOW|DCSBiosOutput{FLAPS_SWITCH|Equals|2}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_3_7|DARK|DCSBiosOutput{FLAPS_SWITCH|Equals|1}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_3_7|DARK|DCSBiosOutput{FLAPS_SWITCH|Equals|0}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_2_4|GREEN|DCSBiosOutput{ENVCP_PITOT_HEAT|Equals|1}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_2_4|DARK|DCSBiosOutput{ENVCP_PITOT_HEAT|Equals|0}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_3_2|RED|DCSBiosOutput{SEAT_ARM|Equals|0}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_3_2|DARK|DCSBiosOutput{SEAT_ARM|Equals|1}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_1_2|GREEN|DCSBiosOutput{ANTI_SKID_SWITCH|Equals|1}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} PanelBIP{Position_1_2|DARK|DCSBiosOutput{ANTI_SKID_SWITCH|Equals|0}}\o/\\?\hid#vid_06a3&pid_0b4e#9&1c05bf1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}