jonsky7

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.

Not sure what you mean, are you using VR? I run the app, TheWay app window opens. If I click on the Green + button, I get a crosshair appears in the middle of my screen, hit the save button to create a waypoint based on the crosshair. If you run VR, I think you can minimize the app and use the keybinds to save and then transfer waypoints. I don't really use VR so I'm not 100% sure on how it works. Hmm yeah, sorry, this hadn't crossed my mind as I don't use VR. I will have a look to see if I can implement keybinds for the options, but it may be beyond what I'm capable of. So far I've managed to create the extra options needed in the list of keybinds, and selected binds seem to save, but I'm stumbling on getting the option to select when the keys are pressed, this may take a while. As for the procedure, at the moment that seems to be the only way to do it. Or transfer the same points twice, once into nav points, and a second time into the weapons. Do you think a "both" option would be beneficial? So TheWay transfers the same points into the Jet and Weapons on the click of the transfer button. That I may be able to do. It would however just transfer the points twice. I won't be able to look at it until after the holidays I'm afraid.

Thanks for this

I would of thought it would be able to do that yes. It did do that when boresighting with the TGP was first introduced.

Has it started accounting for distance again? Currently if you boresight something at 4 miles, then at 7 miles it is not accurate.

@MAXsenna Done, called Helios3, in the "solution" post @MadKreator Whatever Helios is doing, it's obviously working even though it is different to what I'm used to.

I'll be totally honest and say I'm not 100% sure. I'm not really a coder, I can generally muddle my way through. The viewports are always first in the DCS original files, so I followed that order. What I did first was upload Max's file into chatGPT and asked it to check for any errors, it said the false statements are redundant As I don't know lua, I don't know if certain things make a difference or not, sometimes the order doesn't seem to make a difference and with other things I've tried (not monitor related) it has done. Changing it to have elseif statements instead was just following the way the "instructions" that can be found in the original 3cameras.lua file use it. Other thing I wasn't sure of was the use of commas instead of semicolons, and missing semicolons _ = function(p) return p end name = _('Helios') description = 'Generated from compatible Helios Profiles' instead of _ = function(p) return p; end; name = _('Camera + RMFCD(on left side)'); Description = 'Right MFCD on the left and camera on the center' Is it still modifying display names? As I mentioned earlier, not necessary with configure for unit type. Doesn't make a difference to you really, but if someone just wants to use Helios to position default displays, then that is a un-necessary modification that will break IC on pure scripts servers. I don't know if that is an option as I don't use it.

No space, just enter 3840x2960 In the same settings menu, system tab, just uncheck "Fullscreen" at the bottom right, I see very little to no change in performance.

Oops, Justs needs a "then" adding after the Ka-50 at line 128 from elseif unit_type == "Ka-50" or unit_type == "Ka-50_3" to elseif unit_type == "Ka-50" or unit_type == "Ka-50_3" then

Brilliant!

If you launch into the game and go the settings menu, you can manually type a resolution into the box, can't do this in the launcher for some reason. You will need to enter 3840x (2160+small screen height in pixels), you haven't given the resolution of your smaller displays unfortunately. You might also have to turn off "full screen" mode for your windows monitor to not turn black.

I've made a few changes bringing it in line with the description that was found in one of the original config files. Not sure if FC3 was a usable unit type, so added them separately for each aircraft. Removed the duplicate entries for the Mirage F1 exports. On a side note, the whole point of the configure for unit type was so you didn't have to modify the export names for any default exportable display. Most of your aircraft have mods applied for the RWR etc, so it's a bit redundant. Helios2.lua Give a try I suppose, there wasn't anything glaringly obvious, name in settings menu = Helios2 When I asked ChatGPT to compare it said: Helios2.lua is now better written, more efficient, and easier to maintain than the original Helios.lua. With additional comments and modularization, it could be even more user-friendly and robust. edit: error in the above file at line 128, corrected below Helios3.lua

Can we see the config file please?

I believe the RTX3060 only supports 2x8K displays, or a maximum of four displays, but at lower resolution.

Hmmm, I haven't been able to try this yet, but I wonder if putting a displays table in the monitor config file would prevent this. Example The displays table is a list of all your monitors, the reference point is your windows main display. My setup above is a fairly straight forward 3 monitor setup, two 1440p monitors, and a 1080p monitor, laid out from left to right. Let me know if you need assistance writing a displays table.

I do occasionally get this if my displays go to sleep, and when they wake up it is all squished. I have no idea why my monitors go to sleep when running DCS as I have that switched off in power options. Nothing seems to work for me either, other than restarting the game. Sorry to not be able to offer a solution at this time.

I watched a setup video to try and understand what is going on. The following is based on the assumption that your "folds" are vertical and equally spaced on your main screen, which is the view from the pilot seat: There seems to be a setting in the app that chooses between 3 screen setup and single screen, have you perhaps chosen the 3 screen setup? This setting may refer to the Main view (or cockpit view), and not the actual number of screens you have in your setup. DCS has two default settings Single screen, which is one view looking forward out of the cockpit, 3 screen has a left view, forward view, and a right view. I think the app is asking which one of these you want, and then it writes a DCS monitor config file for you. I can see where this may be a bit confusing. You could think of it as asking do you want a single view, or three views. DCS doesn't really care how many actual monitors you have. It treats all of your monitors as one large display area, and the config file tells it where to place various "views" in that display area. So it will squash the "3 Views" onto one monitor if you, or the app, tells it to. If this doesn't help, let us know and we can try something else.

I don't have WinWing displays. Do they show up in Windows Display Settings like normal monitors do?

Found out these are Civ. Traffic related. Don't show when off, from low to high they all follow the same path, with decreasing gap between tugs as you increase the level of civ traffic.

Now there's two lines of tug boats tugs.trk

Well i would have thought you'd get a wider field of view. It's at least worth a try isn't it?

Yeahhhhhh, that's not very good at all. Totally understand your frustration, was just trying to help. How does the 1 camera setup look, but with the resolution adjusted to include all 3 monitors?

Not sure if you are aware or not, but the view is adjustable, but not in the settings menu. You have to do that in the configuration file. This is the default 3 camera config file, DCS > Config > Monitorsetup > 3Cameras.lua If you are going to make adjustments, I suggest you copy the file to Saved Games > DCS > Config > Monitorsetup > *name the file something different* Also change the name inside the file, below it is called 3 Screen To adjust the left/right angle, adjust the values of viewDx, negative values for left, positive for right, -1 = left 90deg, 1 = right 90deg To adjust up/down, adjust the value of viewDy, negative values for down, positive for up, -1 = down 90deg, 1 = up 90deg 1 degree = 0.011112 30 deg = 0.33333 45 deg = 0.5 You can also run 3 screens with the 1 camera file, this should give you a wide forward view To do that, just adjust the resolution in the DCS settings menu to cover all 3 of your monitors i.e. 11520x3184

If you upload the file I can take a look. Just to be sure, you said F-14_TDI but it should be F14_TDI No hyphen (dash) in F14 and is that in the core directory, or your saved games folder? It won't change on updates if you save the config file in the saved games folder Saved Games > DCS > Config > Monitorsetup > your config file.

I've not changed the names and mine is still working Did you use my guide to do your setup, or did you use Helios? Notepad++ Search Find in files Search for try_find_assigned_viewport(" filter *.lua Point it at your game directory.