jonsky7

You can export a second view, but I don't think you can exclude it from TrackIR etc This is the actual viewports section, just need to get the syntax right. The whole "viewports" section has opening and closing brackets {} Each viewport has opening and closing brackets inside the viewports section You'll notice the closing bracket after the "center" section now has a comma, and the last one doesn't I'm pretty sure Dx values adjust the view left and right and 1 = 90deg, although you can use many decimal points ie 0.999999998

I don't know of any other way than changing the monitors' resolution in Windows display settings BEFORE running DCS. Either that or setup the config file for full resolution, then use DLSS to increase the frame rate. (I dont know much about it) Seems like running exports messes up the "fullscreen" rescaling.

As far as I'm aware, the list on page 1 is up to date. Under the section "advanced editing by aircraft type"

GU MAIN VIEWPORT should be GU_MAIN_VIEWPORT Is there a specific aircraft you are looking that is not listed on page 1, in the part with the title Advanced editing by aircraft type. ?

I don't think it is exportable by default. You could probably do the display export mod, it will break IC on pure scripts required servers though. https://forum.dcs.world/topic/258735-how-to-export-displays-like-rwr-and-cmsp-set-up-guide-jan-2021/

Is this when you start the game? Or after the monitors have gone to sleep (switch off). My screens go all weird if I let them "sleep" when the game is running, only a restart will fix it. If it is when you start the game, you could try adding a "Displays Table" to your monitor config file. How to do that is explained on the first page of this thread.

Seems strange. Is the tablet always plugged in and acting as a display, or do you plug it in to play DCS? If you plug it in to play DCS, does it ever take over "Main screen" in windows display settings?

Adjusting the original file will break all of the Integrity checks I believe, meaning you won't be able to join any multiplayer server. Doing it with the modified files at least let's you play on servers that DO NOT require pure scripts. It's been a while since I tried doing it the way you suggested so that might have changed. There is an alternative solution. You could place your ddi displays to the left of your main display in windows display settings. You would have to alter your monitor config file for the new positions. There's also the possibility of needing to add a "Displays table" to the config file. Info on that can be found on page 1 of this thread.

The free version of voice attack allows 20 commands (IIRC) to be programmed. It is however only $10 and in my opinion extremely worth it. For the most part, voice attack is an automated key-pressing program, where each command is voice activated. So you would say something like "Set up Viper MFD", and then voice attack would simulate pressing keys in the order you set them. You can add pauses between keys, do modifiers and keys {eg Ctrl+A, Ctrl+Shift+A etc), make the mouse click, hold the mouse button, move the mouse around, and many other things. In order to fully utilise this feature, it is necessary to set keybinds for the things you want VoiceAttack to use. eg A user by the name of @Bailey worked with the developer to create a code that uses DCS BIOS - a script that directly communicates with DCS. That is a little bit more difficult to set up the commands, but the keys are sent directly to DCS, which means while it is running a command, you can do other things, even minimise DCS, and all the button presses still work, and you don't have to set up a keybind for every button in the cockpit, or any at all for that matter, Thanks Bailey! (the odd thing doesn't work, DCS BIOS doesn't usually work for axis commands unfortunately) As Razbam didn't use the normal macro-sequencies.lua file for their start ups, I found this really useful for making my own F-15E start-up sequence. This section looks really long, but it does in fact press every key almost simultaneously. null As MAXsenna mentioned, you can also use it to operate the mouse, to move the kneeboard for example. null It really is a remarkable tool.

I'm not 100% sure on how the graphics card maximum resolution works, but most of them these days are listed as 7680x4320. I have come across several people who have tried to do multiple monitors with larger than the 7680 horizontal resolutions who have had the partial filling of a screen problem. But that might also be a DCS maximum. You could always try putting the right monitor under the centre monitor in Windows display settings, and put your MFDs under the left then reconfigure the monitors. See if that works?

That was an amazing show, very well done to all! Lest we forget.

So I was pondering on what the best solution for this was for a while, a special version that removed a dobber down action, an option select screen (VR people don't like those) etc. When I was testing though, it's not ALL the Steerpoints 21 and above, somewhere in the 100's range, it goes back to being able to auto-sequence again(bug?) Then it occurred to me that if we simply dobber up from the Steerpoint number select instead of down, we can miss out the auto/man selection altogether. Takes a fraction of second longer to enter 1 waypoint, shouldn't be any different at all for 2 or more because we had to go back to the start anyway. So I present my version 2.5.8, which should do the waypoint entry regardless of the Steerpoint numbers used. https://github.com/jonsky752/DCSTheWay/releases/tag/2.5.8 No other changes from 2.5.7

Yes, but you need to read all of it! I mean at step 12 you're only going 35mph, which is when Chuck says "Slowly release the stick to centre" Step 8 is when you're at the end of the runway, lined up, brakes on (9), and you throttle up (10), holding the stick back prevents a nose over.

It does say at the end of video "Colour correction, sound FX, and visual enhancements have been used for cinematic effect" I'd love to know how they make these, not a jaggy edge or artifact in sight. I've got a got a pretty decent rig, but in-game never quite matches the quality of their videos.

It looks like you are on a multiplayer sever so I'm assuming you are on the latest version of DCS? I ask because there was a change to the F16 steerpoint entry. TheWay just follows a set routine for getting the waypoints into the jet, and it looks like the routine for yours is different to mine. Your DED cursor is not moving over to the MAN/AUTO select position. Before the change it was dobber down once to go from the steerpoint number select, down to North coordinate entry. After the change, dobber down once goes from steerpoint number select, to man/auto select, then dobber down again for North coordinate entry. in pics On Sterrpoint number select Dobber down once Dobber down again You can manually try to do the inputs in the same order as "TheWay" by: 1. Data Control Switch Left (Dobber RTN), this makes sure we are at the default screen showing comms freq, current steerpoint, and the time. 2. UFC button 4/STPT, Steerpoint screen select 3. Data Entry Display Increment button (left of dobber up/down buttons - press up), increments to next steerpoint. 4. Dobber down - DED cursor moves to man/auto select 5. Dobber down - DED cursor moves to North coordinate select 6. Verify on North Coordinate selection.

I've just tested it on mine, seems to be working ok The button entry speed seems very fast on your video, this can be an issue if you are running very high framerates. If you click on the settings cog in TheWay window and scroll down you will see a Button Press Delay, try setting this to maximum (100ms) and see if it works then. If that does the trick, you can always try lower delays until the issue arises again, then just increase the delay a bit again. Or Try limiting the frame rate (FPS)

Which version have you downloaded?

HAHAAAAA I win!! The problem was that the displays were not perfectly aligned in Windows Display settings. DCS was leaving a 6 pixel gap at the bottom of my second and third display and this must have prevented the taskbar from "going behind" DCS.

bump, Had to buy a new monitor because one of mine stopped working, everything was working fine before. Plugged in the new monitor and now my 2nd and small 3rd monitor have the taskbar permanently ON TOP, WTF, doesn't make a difference if I'm in fullscreen mode or not. This is probably a windows problem.

Do you have any mods associated with Petrovich? Maybe something that alters the position of the AI controls? The file HelperAI_page_common.lua which is sometimes used to modify the position of the AI controls has undergone a fairly substantial update recently.

If you are not bothered about passing the IC check on multiplayer servers with "Pure Scripts" required, you could modify the macro_sequencies.lua (yes it is spelt wrong) file. DCS > Mods > aircraft > F-16C > Cockpit > Scripts > That file is what is used to run the auto-start procedure, but it will run whatever is in there when Win+Home is pressed. So you could either: 1. If you like to start up the jet yourself, delete everything else and just enter the button commands to set up your MFDs 2. If you use auto-start, modify the file to include the MFD setup. You could also edit the "auto-shutdown" section. That part of the script will run whenever Win+End is pressed. So you could leave the auto-start as is, and then press Win+End to setup your MFDs. You are able to set the delay, if any, between button presses, so you can make it do it's thing very quickly. Here I have included my file, this does a stored heading start-up, and set up my MFDs how I like them, you could modify it as required Macro_sequencies.lua Or, as I've just remembered somebody made an add-on, check out

I've not tested this in VR, but for 2D Mods > aircraft > AH-64D > Cockpit > Scripts > AI > PrestonAI_page_common.lua Lines 24-25 compass_pos = {-0.82, -0.7} weap_control_pos = {0.8, -0.7} The Compass position controls the compass ring (Commands to Pilot when in CPG seat), and the Target List from CPG when in the Pilot seat weap_control_pos controls the round circle thing that displays the gunner info from the pilot seat. I believe the numbers are Left/Bottom Edge: -1 Center: 0 Right/Top Edge: 1 edit: It is possible to enter values above 1, this will move the indicators onto the next monitor for multi-monitor setups. There are also some extra lines for VR, Lines 9-10 local compass_pos = {0, -0.40} local weap_control_pos = {0, 0.32} --seems okay, may be a subject to change Good luck!

Hello, A1, not that I'm aware of, the switching of MFDs per seat needs to be coded into the module. A2, I've had a look at your file and it seems fine, although the Left and Right MFDs for the harrier seem to be exported to the exact same location in the file you posted. I haven't come across that issue before, but my config file has an entry for every module I own, even if the export locations are the same for multiple aircraft I still separate them. Only other thing I noted was a slight difference to the center viewport You have Viewports = { Center = { x = 1024; y = 0; width = 1920; height = 1080; aspect = 1920/1080; dx = 0; dy = 0; } } and I would have it Viewports = { Center = { x = 1024; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 1920/1080; } } I'm not sure if that make a difference or not.

To make the cursor dot dissappear press the "add waypoints" button again after you are done adding waypoints. Just for clarification, that's the circle button with a + in it, it changes to an X. It's not possible to make it work with the F15C, IIRC there's no way to manually enter waypoints into it. The new-ish built in route planning tool may be of use to you for that, but that only works before you spawn.

It wouldn't really, just if you want to enter the same waypoints as both nav points and weapon points i could probably get it to do both on one transfer. What I'm usually doing is programming the weapons to drop on multiple targets in the same area, then I delete all but one of the points and enter that as nav/steerpoint to get me close enough for release. If you're planning at route through a valley or something, and then having completely different weapon points, then I think that will always require two transfers. You can always use the now built in route planner for your steerpoints, and just use theway for you weapon points. Merry Christmas to you. I'm not the original author of this program, and I have very limited coding knowledge. I just found other people had made some modifications that I found useful. I used the supplied source code to build a version with all those modifications built into it and just thought I'd share it. Most of it is far beyond my coding abilities if I'm honest.