-
Posts
648 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by bones1014
-
They changed the contents of the folder with the VTB elements in it. Sent from my ASUS_I01WDX using Tapatalk
-
Figured it out. I have the VTB exported to an external monitor and they updated the files so I had to make some changes to my setup. Sent from my ASUS_I01WDX using Tapatalk
-
I was going to try that if there weren't any other suggestions.
-
My VTB screen is blank when in cockpit. Even if I just do an instant action at the take off position with everything already turned on for me or in free flight. What can cause this?
-
Where can you find the name of things to add commands. I'm looking at adding a up/down command for the F14 RIO Weapon Type Wheel. There isn't a Weapon Type Wheel listed in the default.lua in the DCS World OpenBeta\Mods\aircraft\F14\Input\F-14B-RIO\keyboard folder. This is what I've come up with on my own. It appears in the controls selection now and I can map it but it only selects two values, 0 and 0.0232. What should I use instead to make it rotate? return { keyCommands = { {down = device_commands.WEAP_Type_Wheel, cockpit_device_id=devices.WEAPONS, value_down = 0.023255813953488, value_up = 0, name = _('Weapon Type Wheel Up'), category = _('Bones Custom')}, {down = device_commands.WEAP_Type_Wheel, cockpit_device_id=devices.WEAPONS, value_down = -0.023255813953488, value_up = 0, name = _('Weapon Type Wheel Down'), category = _('Bones Custom')}, } }
-
I'm looking for a keyboard command to rotate the RIO weapon type wheel. Is there such a command? I can't find it in the controls.
-
Is there a keyboard command to rotate that wheel? I can't find one.
-
@Chacal_IX I'm not getting any output from that added line. Is there somewhere else it needs to go? I was trying to get my Radar mode buttons to light up like yours but I can't get them to stay on either. Can you give me a hand with those too? None of these below do anything when I add them to the F-14B.lua -- [b4 RIO - Center Panel] ---------------------------------------------------------------- -- HCU [2007] = "%.1f", -- HCU IR/TV [2008] = "%.1f", -- HCU RDR [2009] = "%.1f", -- HCU DDD Cursor [2010] = "%.1f", -- HCU TID Cursor -- [END B4] ------------------------------------------------------------------------------- -- [b5 RIO - Center Console] -------------------------------------------------------------- -- Display [17] = "%.1f", -- IFF [6114] = "%.1f", -- PD STT Lamp [6115] = "%.1f", -- PULSE STT Lamp [6116] = "%.1f", -- PD SRCH Lamp [6117] = "%.1f", -- RWS Lamp [6118] = "%.1f", -- TWS AUTO Lamp [6119] = "%.1f", -- TWS MAN Lamp [6120] = "%.1f", -- PULSE SRCH Lamp -- [END B5] -------------------------------------------------------------------------------
-
The backlighting on the WCS Mode buttons, CAP Buttons, TID display buttons, and HCU mode buttons is extremely dim. I can't tell which mode is selected very easily. I tried to repair DCS and removed and reinstall the F14 module.
-
To get anything at all to display output I used [3009] = "%.1f", --datapanel selector custom And even then it only displayed 0.0 regardless of switch position. Thanks for the tip though.
-
I went through the Viggen folder itself until I found a file called "clickabledata.lua" inside there was a line that said -- Datapanel rotary selector elements["Datarot-PTR"] = multiposition_switch_limited(_("Datapanel Selector"), devices.NAVIGATIONPANEL, 3009, 200, 7, 0.1,false,0) I took the 3009 from that line and added to the script like so: -- Datapanel [3009] = "%ld", --datapanel selector custom [200] = "%1d", -- Datapanel Selector and now the datapanel selector rotates under a single button! I can't get it to display any output like current position yet. Still have the problem with using the master mode as a rotary. It freezes the scripts between streamdeck and DCS.
-
Of course! I'll share the profile with you too. Sent from my ASUS_I01WDX using Tapatalk
-
I've made some progress. I have weapons figured out. Just the master mode and data panel selector to go. Hopefully I'll eventually figure it out. Sent from my ASUS_I01WDX using Tapatalk