skypickle

actually i got the answer to the second ques here: and forgot it

I have a specific lua to define two mfcds on a second screen below my main monitor: _ = function(p) return p; end; name = _('Camera + 2 MFCDsBelow'); Description = '2 MFCDs on the right and camera on the top' Viewports = { Center = { x = 0; y = 0; width = 3840; height = 2160; viewDx = 0; viewDy = 0; aspect = 3840 / 2160; } } function reconfigure_for_unit(unit_type) --unit type is string with unit name if unit_type == "AH-64D_BLK_II" then LEFT_MFCD = { x = 0; y = 2160+120; width = 768; height = 768; } RIGHT_MFCD = { x = 768; y = 2160+120; width = 768; height = 768; } else LEFT_MFCD = { x = 10; y = 2160+140; width = 663; height = 663; } RIGHT_MFCD = { x = 768+10; y = 2160+140; width = 663; height = 663; } end end GUI = { x = 0; y = 0; width = 3840; height = 2160; } UIMainView = GUI GU_MAIN_VIEWPORT = Viewports.Center My screen res is set to 3840x (1600+1024) since my main screen is 3840x2160 and I have a 1920 x 1024 monitor below it. It works well for the Apache and all aircraft that have MFDs. But when am in the Huey, I cannot see the ROE of my gunners and copilot - whether they are wep free, safe etc. Is there a way to specify the screen res in the lua? Alternatively, can I specify the location of the ROE display?

I did a repair and the problem went away. as for cycling the trigger, i dont know what you mean

There is also a button on the TADS to change ‘first’ to ‘last’ in the event of backscatter

well if core count is your thing look at the Intel® Xeon® w9- 3495X 56 cores 105 mb L3 cache 4.8 ghz turbo

why intel and not 7800x3d?

I have a specific monitor config for the Apache because I amusing the Total Controls frames. However, I also use them for all the other aircraft that use smaller displays with only 5 buttons. So I want the monitor config to be different depending on which airframe is chosen. My monitor config file is below: --3840 x 3184 3840x2160 LG B2 OLED screen with 768x1024 screens below _ = function(p) return p; end; name = _('Camera + 2 MFCDsBelow'); Description = '2 MFCDs on the right and camera on the top' Viewports = { Center = { x = 0; y = 0; width = 3840; height = 2160; viewDx = 0; viewDy = 0; aspect = 3840 / 2160; } } if unit_type == "AH-64D_BLK_II" then --Viewports = ... define new Viewports table -- also you can define cockpit displays viewports here LEFT_MFCD = { x = 0; y = 2160+120; width = 768; height = 768; } RIGHT_MFCD = { x = 768; y = 2160+120; width = 768; height = 768; } else LEFT_MFCD = { x = 10; y = 2160+140; width = 663; height = 663; } RIGHT_MFCD = { x = 768+10; y = 2160+140; width = 663; height = 663; } end GUI = { x = 0; y = 0; width = 3840; height = 2160; } UIMainView = GUI GU_MAIN_VIEWPORT = Viewports.Center The problem is that the montior config is ALWAYS what comes after the 'else' I figured that I am referencing the Apache wrongly and also tried "AH-64D BLK.II" as well as "AH-64D" but no, DCS is not cooperating. Has anyone successfully specified an Apache multimonitor config? SOLUTION: The if then statement has to enclosed by a function. Like so: function reconfigure_for_unit(unit_type) --unit type is string with unit name if ... else ... end end

Also, editing the server.lua in the Saved Games folder for the Apache does not work. Edits have to be made in the View.lua file in the game folder.

@Rudel_chwThank you for this helpful post. I was perusing your server.lua file which you posted some years ago and am curious about the entry for the Huey. After you defined the local cockpit views, there was this code: local function player(x,y) return { CockpitLocalPoint = {x,y,0.0}, CameraViewAngleLimits = {20.000000,140.000000}, CameraAngleRestriction = {false,90.000000,0.500000}, CameraAngleLimits = {200,-90.000000,90.000000}, EyePoint = {0.00000,0.000000,0.000000}, ShoulderSize = 0.25, Allow360rotation = false, limits_6DOF = {x = {-0.050000,0.25000},y ={-0.300000,0.100000},z = {-0.30000,0.30000},roll = 90.000000}, } end but nowhere in the server.lua file is the function, player(x,y) called. Is it doing something ? Also, I added an entry of the AH64D. In the originalViews.lua file for the Apache there is something similar. There is the expected viewSettings but also a bunch of functions not referenced. For example, local function head_pos_default_PLT(tab) if not tab then tab = {} end tab.viewAngle = tab.viewAngle or 76.0 tab.hAngle = tab.hAngle or 0.0 tab.vAngle = tab.vAngle or -10.0 tab.x_trans = tab.x_trans or 0.0 tab.y_trans = tab.y_trans or 0.0 tab.z_trans = tab.z_trans or 0.0 tab.rollAngle = tab.rollAngle or 0.0 return tab end Again, the function, head_pos_default_PLT(), is not used in the original Views.lua file What do you imagine it is for?

Maybe someone can educate me about the difference between a search radar and a track radar. When an f18 is in rws mode is that search? And when it locks you then it becomes a track radar? What is tws then? What scenarios would benefit from either rwr mode? Should i press the ‘s’ button when i get an awacs call of bogeys headed my way? i just dont know how to use that button either with or without the mod.

It happens even on a fresh install

No it did not. I simply put the correct values in the third option of the streamdeck button and unchecked’display default values’

also cant get the uhf channels to change even tho the correct button IDs are used for tumblers. How would I get a clue to resolving that? the F-5E-3.lua has this for the radio knobs: in the function function ExportScript.ProcessIkarusDCSConfigLowImportance(mainPanelDevice) there is this line: ExportScript.UhfRadioKnobs(mainPanelDevice) -- AN/ARC-164 UHF and that function is defined thusly: function ExportScript.UhfRadioKnobs(mainPanelDevice) --AN/ARC-164 UHF local lTmp327 = tonumber(string.format("%0.1f", mainPanelDevice:get_argument_value(327))) local lTmp327_2 = lTmp327 if lTmp327 == 0.0 then lTmp327_2 = 0.0 elseif lTmp327 == 0.1 then lTmp327_2 = 0.3 elseif lTmp327 == 0.2 then lTmp327_2 = 0.2 elseif lTmp327 == 0.3 then lTmp327_2 = 0.1 else lTmp327_2 = lTmp327 end local lTmp328_2 = 1 - mainPanelDevice:get_argument_value(328) local lTmp329_2 = 1 - mainPanelDevice:get_argument_value(329) local lTmp330_2 = 1 - mainPanelDevice:get_argument_value(330) local lTmp331 = mainPanelDevice:get_argument_value(331) local lTmp331_2 = 0 if lTmp331 == 0.0 then lTmp331_2 = 0.0 elseif lTmp331 == 0.25 then lTmp331_2 = 0.75 elseif lTmp331 == 0.5 then lTmp331_2 = 0.5 elseif lTmp331 == 0.75 then lTmp331_2 = 0.25 else lTmp331_2 = lTmp331 end ExportScript.Tools.SendData(327, lTmp327_2) ExportScript.Tools.SendData(328, lTmp328_2) ExportScript.Tools.SendData(329, lTmp329_2) ExportScript.Tools.SendData(330, lTmp330_2) ExportScript.Tools.SendData(331, lTmp331_2) end but the DCS_IDs (327,328,329,330, and 331) do bizarre things when assigned to tumbler buttons. Streamdeck crashes. The button IDs as assigned from the plugin are (3002,3003,3004,3005,3006). Where do these come from?

I wish some of this stuff was uploaded to the user files where it wouldnt disappear. All the pics from the beginning are missing.

@bones1014thank you. I guess instead of declaring a function I could just put these two lines in the F-5E-3.lua file: local indicator_value = ExportScript.Tools.round(mainPanelDevice:get_argurment_value(52) * 10 ) ExportScript.Tools.SendData(5000, indicator_value) Why did you choose to use a function definition in the main ExportScript.lua? Just asking so I can learn. Also, why put it in this function: function ExportScript.ProcessIkarusDCSConfigLowImportance(mainPanelDevice) and not this function: function ExportScript.ProcessDACConfigLowImportance(mainPanelDevice)

I know i can change my default head position (F1 view)with alt-num 0. I would like to change other default views as well. Does anyone know where DCS keeps these parameters? SOLUTION: I followed Rudel's helpful post here: Once you create the proper entry for each aircraft as he describes, then the chase view can be modified. Too get a chase view that looks back (so you can quickly check 6 (without needing to dislocate your neck) it can be edited thusly: Chase = { LocalPoint = {-5.0,1.0,3.0}, AnglesDefault = {180.000000,0.000000}, }, The angle of 180 degrees is mie. Most aircraft have it set to 0 so the unhelpful default chase view has you looking forward.

I am still suspicious. Why would a module that is not new and unchanged (supposedly) start tripping alarms? Dlls are easy to hide trojans in

I guess some evil person put a virus in the code. This is not a new module and the changelog says nothing about CA. So why is antivirus flagging it? I am not whitelisting it until ED says its safe

well I guess the malcontents who put the virus in the combined arms dll figured out a way to fool windows defender

Thank you but i was hoping that @DD_Friarwould tell us why he isn’t getting that prob. i agree, it is perplexing that combined arms is throwing up this error as it is not a new module. it makes me worry that someone has slipped a trojan into the code

Although im late to the party, i think there is a fundamental difference that makes spotting difficult w trackir. Our eyes move in saccades. And part of that movement is predictive based on what our vestibular system is telling our brain. In trackir, you have to move the eyes Opposite to what we do all the time IRL just so we can see the flat screen. This totally messes up how the brain stitches the images together. And also the eyeball muscles instead of keeping the bogey fixed on the same spot on the retina, now have to keep the eyeball fixed on the screen. As a result you have to constantly engage a new and different part of your retina . In addition this cockeyed motion often puts the blind spot (the part of the eyebal where the optic nerve enters) right into the trajectory of the bogey. We literally do not see it. Vr avoids this but until recently had its own burdens (poor peripheral focus due to the lenses, screen door,limited resolution) To help tracking we should be able to lock the camera onto the target once we designate it. This lock would eliminate the unnatural eye movement necessary but also would not be unrealistic because we are not changing the rendering

Which antivirus do you use? Specifically which version of eset and have you changed any of its scanning options or added any exclusions?

Secondary screens as MFDs are much darker than their rendered brightness on the main screen. I fixed this by going into the NVIDIA control panel and adjusting the gamma, brightness and contrast of those screens as shon below: now they are similar:

@DD_Friar are you using the open beta? There are several threads here documenting that ESET sees the combined arms dll as a threat and deletes itt immediately on download

The F5E pitch trim indicator is hard to see under the sun shade. I found the DCS ID to be 52 and got it to display on the stream deck. However, this is a decimal value with 4 places. For example, a pitch trim of 5 degrees is shown by the value 0.05000. How can I get the display to read 10x the actual value?