Search the Community
Showing results for tags 'menu'.
-
I would really like to see DCS's standard setting for the radio similar to what Heatblur did for the Viggen. Short press activates the menu, long press activates the PTT.
-
Since 2.9 the custom liveries in the saved game folder seems not to work anymore. In my Saved Game folder I have multiple liveries that were visible from the loadout menu before 2.9. Now these liveries are still there but not available from the loadout menu. Did something changed in 2.9 ? I checked the folder names and folder structure and I everything looks fine. Anyone else has the same problem ? ...any solution ?
-
Cinematic Camera's Menu & Automatic Xbox Controller Input Tool I was able to make a cinematic cameras menu using steam input, but the steam version of DCS is not required for the tool. When using my tool you can tap once then press down on the d pad of your xbox controller for the camera menu to appear. If you select an option from the camera menu, the tool will switch to that camera and automatically switch the control scheme of the Xbox controller to best manipulate that specific camera type. You should theoretically be able to create a DCS cinematic video without having to the touch keyboard with my tool. In Depth Video Tutorial Here: A Quick Text Based Guide This is assuming you own the stand alone version of DCS but if you own the steam version skip to step 3. Within Steam, enable steam input for xbox controllers. Add DCS to steam as a non steam game. Enable steam overlay while in game: Steam Settings, In Game, Tick Enable steam overlay while in-game. Enable steam input for DCS (for stand alone users its' the one you just added) With DCS selected in your games library, click on the controller icon on the far right side. Refer to step 3 if you don't see it. With the steam controller input window open, click on browse community layouts. Then under community search "DCS FILMIING" Apply the highest version number of DCS FILMING created by the user Crow(Me) If you don't see my layout in the community tab click on show all layouts towards the bottom hopefully you will see it now. To test it, load an instant action of any DCS officially created aircraft. Once in game press escape and make sure to clear out any commands that DCS may have applied to your xbox controller. Clear any commands it applied under the general controls tab and the current aircraft your using or plan to use for film making. Tap and hold down on the D pad of the xbox controller for the menu to appear. Move your thumb around the menu then let go on the camera you want to select. You don't need to hold down for the menu to appear to select another camera menu option on the d pad. But the menu helps if want to enter any options that exist in the diagonal selections. Refer to my most up to date controller input guide image on my DCS user file page in screen shots to understand how manipulate the camera, but its pretty intuitive. I initially created this tool for members of the flying community I'm apart of but I thought I might as well improve upon it and share it publicly. This is the sort of thing I wished existed for me when I first trying make videos in DCS. So I hope others find it helpful. Refer to my DCS user file page below for updates to the steam controller input guide image and denotation of further updates to my tool. https://www.digitalcombatsimulator.com/en/files/3334129/ I have not had much experience with creating tutorials so hopefully it all make's sense.
-
Hi all! After updating to the latest version, the default " \ " key for the communications menu doesn't work. When I tried reseting it back to the default, still doesn't work and only when I change it to any other button, seems to work. I also uninstalled the entire module and installed it again and still isn't working! The same bug also applies for the communications menu on the F-5 E (trial mode) dcs.log
-
Hi guys! Do you want to dynamically spawn, respawn and despawn groups in your DCS mission? Do you want to have sub folders in the F10 menu? Did they tell you you'll need to learn LUA coding and the DCS scripting environment to do it? Well, I learned LUA so you don't have to. This script will create submenu's in the F10 menu based on the names of groups. It will create a sub menu for every group that has within a spawn and despawn button, these do exactly that. For now it's possible to go 1 submenu deep and also to add multiple groups to 1 spawn/despawn button. An example: If I have the following groups: !! Red 1 !?Wave 1?! Red 2 !?Wave 1?! Red 3 !?Wave 2?*BULK 1*! Red 4 !?Wave 2?*BULK 1*! Red 5 The following F10 menu will be created (not accounting for the random order it will be in): Red 1 Spawn Despawn Wave 1 Red 2 Spawn Despawn Red 3 Spawn Despawn Wave 2 BULK 1 Spawn Despawn As you can see Red 4 and 5 are not shown as they are a part of BULK 1 and both will be spawned or despawned by the buttons. To learn more check it out on GitHub: https://github.com/Markoudstaal/DCS-Simple-Spawn-Menu Need help? Join this Discord: https://discord.gg/8VbKnKvN5r
-
Like the title says to have the ability to turn the rudder trim off in the special menu like the ka-50 and huey. Helps for people that don't have rudder pedals to easier control the rudder.
-
Hi everyone, With the Mirage F1 introducing 23 variants of the aircraft (which FWIW I absolutely love - no other module is that comprehensive, even with only AI variants) would it be possible to have collapsible menus within the unit listing? Primarily for instances where we have multiple variants, so for the Mirage F1 we'd have something like [+] Mirage F1, which when clicked on would expand into all the variants: [-] Mirage F1: Mirage F1B Mirage F1BD Mirage F1BE Mirage F1BQ Mirage F1C Mirage F1C-200 ... Something like this though would be perfect for things like battery components of SAMs. It would also have the added benefit of allowing us to use names that are simultaneously shorter and less ambiguous while keeping them very easy for users to figure out what goes with what. So for example, instead of having: SAM SA-10 S-300 “Grumble” Big Bird SR SAM SA-10 S-300 “Grumble” C2 SAM SA-10 S-300 “Grumble” Clam Shell SR SAM SA-10 S-300 “Grumble” Flap Lid TR SAM SA-10 S-300 “Grumble” TEL C SAM SA-10 S-300 “Grumble” TEL D We'd have [+] S-300PS [SA-10b Grumble], which when clicked on would expand to show: [-] S-300PS [SA-10b Grumble] 54K6 'Baikal' BCP 5I57A generator 5N59S [Tin Shield B] SR 5N63S [Flap Lid B] FCR 5N64S [Big Bird B] SR 5N66M [Clam Shell] SR 5P85S TEL(M) 5P85D TEL(S) Here the Big Bird and Tin Shield should also be listed separately, with the name given (omitting the SAM SA-10 S-300) as these are also used as general purpose EWRs (though perhaps EWR should replace SR in that case). Where components are present in 2 different groups, they should be present in each menu (essentially duplicating it), an example being Rapier, where we have the components to make the initial Rapier and Rapier FSA: This sort of thing could also be used for ships, both for ships where we have individual members of classes/subclasses as separate units and where individual units are contained within the liveries. Obvioulsy in any case, there should be buttons to expand/collapse all.
-
It would be nice to be able to have the cursor cross used in the cockpit and have it align with the radio menu and other context menus that pop up. I fly in VR and it is a really big faff to move the cross cursor in an area other than the menu in order for the white dot to show up so I can finally click on options. multi crew name selection window……what a pain that is!
-
For the last month or two I've had an annoying bug playing DCS in VR (doesn't occur in pancake). Whenever I launch the game, the view is offset vertically by about a screen height, maybe a little more. All I can see is the top of the plane's wing in the hangar, not the intakes or (more importantly) the menu. There is a simple workaround which is to recentre the VR view using Num5 or in my case a HOTAS bind. No further problems when playing after this, and startup views in all aircraft are fine, it's just the launch menu. I'm playing in SteamVR over Quest 2 and Virtual Desktop for the link. System specs probably not relevant but are 5800X3D, 64GB RAM, 7900XTX on latest drivers. A minor bug, but feels like this should be a simple fix in a config file somewhere. Can anyone help?
-
When you go into the Special Options tab, and select an aircraft, there is most often a dropdown option on any particular module to set its cockpit livery. However, on the Apache (and P-51 too while mentioning this), creating a new livery in DCS World OpenBeta\Mods\aircraft\AH-64D\Liveries\Cockpit_AH-64D doesn't function correctly. While I can see the new livery I created as an option in the drop-down menu in Special Options, DCS will not render that cockpit ingame, and will only render the 'default' cockpit...despite an otherwise cockpit livery being selected. Oddly, in other modules that have cockpit language options, those will work correctly in DCS. However DCS seems to have an aversion for applying any cockpit livery other than what is installed default with the module. What the result is, while the cockpit livery function is broken, I must hijack the 'default' livery manually, and overwrite it with my own livery. However this requires destroying the default cockpit livery in the process to inject my own. Please fix this for the Apache (and other modules plagued with similar problems).