Search the Community
Showing results for tags 'f10'.
Found 9 results
-
As in the title, flipping between F10 and F1 seems to have a % chance of starting long-lasting stutters and screen-tearing in VR. Usually happens after the 5th or 6th time looking at the map while on a mission. This is actually so bad that it immediately stops my gameplay, I cannot continue with it. See attached video. This bug never appeared before multithreading was introduced. https://cdn.discordapp.com/attachments/865742930064965662/1100018920297070692/20230424_200758.mp4 Oculus Quest 2 3070ti M.2 SSD for DCS 32GB memory X570 Gaming+ Ryzen 7 5800X3D -
It would be most effective if further peripheral controllers were permitted to be bound to the F10 Coordinate Picker tool. Currently, it is only permitted to be bound to keyboard. Further controllers like throttle and sticks would be great. Mainly however, mouse controls would be most effective and a natural place to bind such a tool. Myself, I have an extra 5 buttons on my mouse I could bind to this otherwise very excellent tool
-
- 1
-
-
- f10
- coordinate
- (and 9 more)
-
I know it's likely been asked for before, I would like to reiterate and try to breath life however temporary into the topic once more. ED: To who it may concern, please implement a universal scratch pad that may be viewed and edited in the F10 Map, that can be recalled in the cockpit so Coords may be stored and entered manually by a pilot for navigation and preplanned entries. And or allow info on scratch pads to be imported into onboard nav computers. This ability would be greatly appreciated surely not just by this pilot but by many if not all pilots in DCS world. Thank you. -
Hi everyone, In the future, would it be possible to expand the icons displayed in the mission editor and F10 map? Currently we have 2 icon styles available, NATO and Russian. Personally, I'd like to request another symbol set be included, and that's NTDS symbology (for air and naval units) and NATO APP-6A (or later) for ground units. One limitation of the current NATO symbology, is that it doesn't have direction information present, so when the game is paused, you can only find direction by clicking on a unit and reading the heading from the information table. See the spoiler below for a full legend: Where NTDS falls over on though is classifying ground units, so if NTDS would be considered, it should be used for naval and airborne units exclusively, with ground units classified under NATO APP-6A symbology (or later). Regarding the NATO symbology though, DCS typically gets symbols correct (but not always, I'll go through them all and report them), however, introduced in APP-6A, is an affiliation indication, which is done by symbol shape, and colour (currently DCS does colour, but not shape). For ground units: A blue rectangle is used to denote units that are friendly A red square at a 45° is used to denote units that are hostile A green square is used to denote units that are neutral A yellow quatrefoil is used to denote units that are unknown Another thing DCS does, is that it uses hostile symbology for REDFOR and friendly symbology for BLUFOR. Personally, I think it would be better (and more accurate) if it uses friendly symbology for units that belong to a certain side, and hostile symbology for units belonging to the side that's hostile to said side. Even better would be coalition specific symbology, even if it was NATO for BLUFOR and Russian for REDFOR (though personally, we need a drastically different coalition system that's more flexible, which I might make a separate wishlist thread about, though a similar thing has been requested before). One thing that I did mention here, is the usage of icons per unit, and icons per group. When sufficiently zoomed out, units belonging to a group should use an icon appropriate for the group (even if user defined), positioned over the average position of all the units in the group, instead of having an icon for each individual unit, which when zoomed out, end up cluttered and stacked on top of each other. When zoomed in however, such that icons are sufficiently spaced apart, they should switch to individual icons (like we have now). When clicked on the group icon, it should show a small list of units to be selected, organised the same way as the group. The only other thing I'll mention is airfield icons, would it be possible to change these to the kind of icons seen on aeronautical charts? Filled circle with runway layout for an airfield with hard-surfaced runways 1500 - 8069 ft Unfilled circle with a coloured border for airfields without any hard-surfaced runways Runway layout with a thick coloured border for airfields with at least one runway that is longer than 8069 ft Blue used to denote airfields that have a control tower Magenta used to denote airflields that don't have a control tower
-
Add 1 or more decimals to F10 measurement tool. QOL improvements: More accurate use of offset waypoints with all (capable) modules. Better use of the Viggen with roadbases etc. Maybe also change the accuracy depending on what coordinate system is in use? So: When using DDMMSS -> XXX degrees When using DDMMSS.SS -> XXX.YY degrees
-
.thumb.jpg.994bf4b3db407ea363f18d306306588b.jpg)
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 -
Greetings All, I was making a script that will allow specific groups access to given options for the F10 Menu in multiplayer. In this example there are 4 groups, (e.g. XX-DRAGON-1-1-XX, ...) as seen in the code below. When the mission starts, I 'DO SCRIPT FILE' and run the following code to no avail. ------------------------------------------------------------------ -- CustomLUA F10 Menu for Specific Groups -- ------------------------------------------------------------------ ------------------------------------------------------------------ -- https://wiki.hoggitworld.com/view/DCS_func_addCommandForGroup -- https://wiki.hoggitworld.com/view/DCS_func_addSubMenu -- https://wiki.hoggitworld.com/view/DCS_func_addSubMenuForGroup ------------------------------------------------------------------ local function successSound() -- Run when called trigger.action.outSound("1-success.wav") -- Play sound end local function failureSound() trigger.action.outSound("2-failure.wav") end local tbl = {"XX-DRAGON-1-1-XX", "XX-DRAGON-1-2-XX", "XX-DRAGON-1-3-XX", "XX-DRAGON-1-4-XX"} -- List of group names to get menu access for i = 1, #tbl do if Group.getByName(tbl[i]) then local groupId = Group.getByName(tbl[i]):getID local adminM = missionCommands.addSubMenuForGroup(groupId, 'ADMIN MENU') local soundM = missionCommands.addSubMenuForGroup(groupId, 'Play Sounds', adminM) missionCommands.addCommandForGroup(groupId, 'Success', soundM , successSound, tbl[i]) missionCommands.addCommandForGroup(groupId, 'Failure', soundM , failureSound, tbl[i]) end end This code is based off of several links and I'm not quite sure why it does not work. When run in game, after joining the unit of said group, the menu never even shows up... Any ideas?
-
Nothing I can't hold my breath for, but it irks me ever so slightly that every single unit on the DCS F10 map view has its proper designation... except SAM sites. Every single Soviet/Russian SAM has its respective NATO designation. I think it would make sense to toggle between NATO and proper designations depending on whether the Editor Icon Style setting is set to "NATO" or "Russia". Being more familiar with names like '9K330 Tor' or '2K22 Tunguska' or 'S-300' means it requires an extra mental step to translate what I'm seeing on the Map. Not that it would take particularly long to memorise, but it's just preference.
-
fixed F10 Map wont show airport info when left clicked...
BigBlackDelta posted a topic in General Bugs
Running latest stable and MT. both have this problem so it must be me. I have AWACs option on. See everything under map options. nothing happens when i click on airport for info. no other programs running except reshade.
