rrutko

"HUD Power. Enables/disables power to AN/AVS-7 Heads-Up Display. (N/I)" Currently not implemented but I'm anxiously awaiting.

I have created this overlay to be able to create custom label overalys for the Orion 1 throttle. This will not work with the Orion 2 throttle (coming soon.) Hope it helps for the people that have been looking. https://www.thingiverse.com/thing:6882707

I made one for myself. https://www.thingiverse.com/thing:6882707

Ok that fixed the blank controls pages, But now the custom inputs are not listed at all (no "custom" in the drop down menu OR custom input controls listed). I installed the "InputCommands" into saved games/dcsopenbeta EDIT: I got it to work via hand replacing the files instead of OvGME. I just need to dig deeper into that on my end I think. Thank you for the correct file.

I am have the same freeze/stutter issue. I turned off HAGS (was ON) and un parked all cores. Attached is my log. There where 2 big spikes and 1 small one. Game updated today 12/14/24. EDIT: Watching the CPU usage in resource monitor and I am using around 80% cpu. When the Stutter/freeze happens CPU usage drops to 20% for about a second or so. Only happens when in the modules not within main menus. I9 12900k, 4090, 128g DD4, 2G NVME. dcs.log.old old log file was before parked core disabled. Same stutters/freeze x 3. dcs.log

dcs.logSorry for the delay. My A10C2 controls are blank. I have not checked any others yet.

In the last few game updates, when I reenable this mod other modules controls will just disapear completly. Example I have AH64 binds I use but when i go to check on A10C2 controls they are non existant (all controls, blank screen). The only way to fix that is to repair DCS and then it resets the command injector mod. any thoughts? Injector mod has the latest update.

bumb, I have same question

perfect now for the MI-24

Since I have no clue on how to enable/code for this request maybe others could help. I would like one of the options for display for as many helicopters that can extract the VVI date to be able to display it. I know UH-1 does as do a few others. Looking for KA-50, MI-24, MI-8 (been awile since I checked that one.) Again stellar work to all that have contributed/created this.\

@Bailey, First I love this app. I am trying to figure out how to add the ARC 201 FM frequency display on the UH-60 to a streamdeck tile. I have found this in DCS-bios but when I try to implement it into the exsisting export module lua I get no return. local ARC201FM_1 = ExportScript.Tools.split(list_indication(9), "%c")[7]:sub(1,5) --(added ARC201FM_1 as a label) It returned 30000. (in DCS Bios lua enviroment. I commented out the original FM1 frequencies as they show incorrect frequencies anyways. Here is the code I have tried. function ExportScript.ProcessIkarusDCSConfigLowImportance(mainPanelDevice) ExportScript.Radios(mainPanelDevice) ExportScript.FlightInstruments(mainPanelDevice) ExportScript.NavInstruments(mainPanelDevice) ExportScript.NavModes(mainPanelDevice) ExportScript.VrsCalculator(mainPanelDevice) ExportScript.PlayWithFire2(mainPanelDevice) ExportScript.UhfSuperFromListIndication(mainPanelDevice) --ExportScript.HiLowCalculator(mainPanelDevice)--Not implemented --ARC 201 FM freq display local ARC201FM_1 = ExportScript.Tools.split(list_indication(9), "%c")[7]:sub(1,5) ExportScript.Tools.SendData(6000, string.format("%-5s", ARC201FM_1)) end function ExportScript.ProcessDACConfigLowImportance(mainPanelDevice) end -- -- -- -- -- -- -- -- -- -- -- -- Custom Functions -- -- -- -- -- -- -- -- -- -- -- -- function ExportScript.Radios(mainPanelDevice) -- ADF Radio local ADF_digit1 = round(mainPanelDevice:get_argument_value(625)*2,0) local ADF_digit2 = round(mainPanelDevice:get_argument_value(626)*10,0) local ADF_digit3 = round(mainPanelDevice:get_argument_value(627)*10,0) local ADF_digit4 = round(mainPanelDevice:get_argument_value(628)*10,0) local ADF_digit5 = round(mainPanelDevice:get_argument_value(629)*10,0) local ADF_freq = string.format("%4.1f", ADF_digit1 .. ADF_digit2 .. ADF_digit3 .. ADF_digit4 .. "." .. ADF_digit5) ADF_freq = trim(ADF_freq) if #ADF_freq == 3 then --1.0 to 0001.0 ADF_freq = "000" .. ADF_freq elseif #ADF_freq == 4 then --10.0 to 0010.0 ADF_freq = "00" .. ADF_freq elseif #ADF_freq == 5 then --100.0 to 0100.0 ADF_freq = "0" .. ADF_freq end ExportScript.Tools.SendData(4000, "ADF KHz\n" .. ADF_freq) -- Uhf new method local UHF_freq = string.format("%3.3f", GetDevice(5):get_frequency()/1000000) ExportScript.Tools.SendData(4001,"UHF MHz\n" .. UHF_freq) -- FM1 --local FM1_freq = string.format("%3.2f", GetDevice(6):get_frequency()/100000) --ExportScript.Tools.SendData(4002, "FM1 MHz\n" .. FM1_freq) -- FM2 local FM2_freq = string.format("%3.2f", GetDevice(10):get_frequency()/100000) ExportScript.Tools.SendData(4003, "FM2 MHz\n" .. FM2_freq) Any Ideas?

Go with the highest card you can afford. There is quite a significant performance jump between the 30 series and 40 series cards (4090 is 60-80% increase over 3080.) That being said if you can only afford a 30 series then stick to 3080ti or 3090. Especially if you are an exclusive VR player. Also consider 64gb ram as the bare minimum. Most people forget to factor in all the other programs and devices installed and running while playing the game. I have 128 and routinly hit 48-52 percent ram usage.

For the many of use that have to alter these scripts for them to show up correctly on larger screens, it removes many servers from availabilty due to failing IC checks. Is there a way to move these to saved game side or remove these from IC checks?

and now the stock version is working. Sorry for me lack of knowledge to know where to put the string you provided.

So I replaced the option 4 line with this one in the UH-1 file. It did not work and has since killed the function for that module. Even after reverting to the previous non edited version and reinstalling a fresh WWT folder it still does not display anything for the Huey. All the other modules behave as expected. Not sure what I did to kill it for the huey.

Is there a way to show VSI on all heli profiles? Is there a generic output for that parameter and then the existing profiles can be made to display that? It is nice for the AH-64, but would be even better for the UH-1, MI-8, and MI-24.

I assume this is in SP only? In MP there is a Desync with moving targets and always miss (usually behind) target.

Fix works correctly, Thank you

@ANDR0ID I would think that you would want to display items that are not available on the HUD. Heading and Radar alt are availble on the HUD. I like the fuel and weapons, chaff, flare, radio etc. Cant wait to try it.

thats what I was hoping for. Radar Altitude for window 1 (to match scratchpad) then IAS to window 2, VSI window 3, And then maybe BARO alt window 4, Also chaff flare counts to comms windows like Androids (if possible). I tried to look at the Aircraft mainwindow lua to see about adding IAS and VSI, but idk if they can display without a digit (like the radar Alt.) However IDK much about the coding.

This is fantastic. Anxiuosly awaiting Androids Blackhawk additions. Would like to see VSI, ALT, Airspeed. etc for Mi-24, MI-8, and Huey (basically any helo without a hud.) I have already submitted one issue I found in the Huey (not a big one though)

Fixed my own issue, SCALLING. I had my gui set to 1.25, reverted back to 1 and everything functions normally.

So I have an Ultrawide and 3 MFDs. I have my monitorsetup working fine other then the F10 map only has partial functionality. I can move and zoom (with a smaller resolution GUI) but selecting objects I cant do, (airbases,other players, etc.) I can't use the CA functions of the map. When I put markers down they are doubled (distance between depends on zoom). If I run a single monitor setup with stock screen resolution (5120x1440) everything functions as it should, including CA arms options. The only difference in the 2 monitor setup files is the mfd exports. Any thoughts, let me know if a track file will show you what im referring to.

I purchased a ps/2 (old keyboard/mouse connectors) splitter of amazon and then cut off one end and shaved the rubberized coating enough to fit inside my 3d printed extension. Its about 12" long. Just make sure it has the same amount of pins. It has worked pretty well.

So far that fix removed the FPS drop upon CMWS power up. I did notice before the fix that the simulation score in FPS counter would increase 3-5x as soon as the bit test was completed. It would go back to normal if the CMWS was powered off.