skypickle

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?

Is there a mission where you are guided on a proper carrier landing w a hornet? Including comms and the significance of what is said/heard?

Thats what i had to do. Reinstall dcs (remember when this was the solution to windows?) I didn’t add CA and got my modules back

Well, v2 of enigma's mp server is up. Any idea where the campaign is?

did today's update and got this notice in the log: 00758.500 ERROR: Can't move C:\Eagle Dynamics\DCS World OpenBeta\_downloads\Mods/tech/CombinedArms/bin/CombinedArms.dll to C:\Eagle Dynamics\DCS World OpenBeta\Mods/tech/CombinedArms/bin/CombinedArms.dll: (2) The system cannot find the file specified. 00758.982 STATUS: Can't move C:\Eagle Dynamics\DCS World OpenBeta\_downloads\Mods/tech/CombinedArms/bin/CombinedArms.dll to C:\Eagle Dynamics\DCS World OpenBeta\Mods/tech/CombinedArms/bin/CombinedArms.dll: (2) The system cannot find the file specified.

I have a 3090 connected to 3840x1600 screen with displayport and an LG OLED C2 television connected to the HDMI port of the 3090. The TV is on the right and designated the primary monitor.I deleted the options.lua in Saved Games\DCS.openbeta\Config so that DCS can start fresh. I start DCS and the game loads onto the main monitor as expected. The system options show this resolution: The main monitor is an LG C2 OLED connected by HDMI. In the LG settings, the aspect ratio is set to 'original'. If I try to correct the resolution to 4096 , then the game switches to the monitor on the left. I tried changing to a display port to HDMI cable for the OLED but it makes no difference. As soon as i bump the resolution to 4k, the game jumps over to the monitor. And it spills over onto the television as well as having the bottom cut off. It sems like the game is putting out 4096x2160 on the wrong display.

thank you. got it to work. only issue now is nav drift. since the targets are over water I did not do any fixes. I should have done a target fix. I was off by a couple of hundred meters. next time I will need to fly along the coast where I can have a couple of waypoints set up for nav fixes as well. I know, bk90s are not for ships but I was wondering what kind of damage they could inflict.

fixed

the files are visible but nothing downloadable. nginx 404 error

user files now also down- trying to download anything gives 404 error

dont remember. will try again. I thought the existence of an M2 point was sufficient and I thought it would switch to M2 automatically after B1.

bravo palikari

I made a flight plan in F10 map with a couple of waypoints, B1 and B2. I did the steps in the picture attached. The picture is a mix of three snapshots: 1)the F10 map in the planning phase on the left 2)a pic of the kneeboard page 3)the F10 map after BK 90 release I dont know why the BK 90 turned and headed back to Batumi ..