jonsky7

Ah, brilliant, thanks very much

It's been quite a while @Spger40, but I think I may have a solution for you. The entry UIMainView = Viewports.Center in the monitor config file, declares the position of the User interface. This controls the position of the Main Menu, the mission editor, and also the boundaries of the UI within the cockpit. So if we restrict those boundaries to your centre monitor, the comms messages should stay on your centre monitor too. So we can replace UIMainView = Viewports.Center with UIMainView = { x = 2560; y = 0; width = 2560; height = 1440; } I think these values will be correct for your setup.

You may also specify the size and location of the UIMainview in your monitor config, so instead of UIMainView = Viewports.Center, you can enter UIMainView = { x = 0; y = 0; width = 1920; height = 1080; } So you can put it where ever you like. This will effect the Main menu, the mission editor, and declare the boundaries of any comms menu. If you are unsure what the code means, check out this thread, the principle is the same.

Glad to hear it solved your issue, and you are very welcome

Hi I'm trying to set something up for the Mossie so that the Radio beacon could be selected by the pilot without having to change seats. My idea was to have a vehicle at each airfield/target transmitting on the same frequency, but transmitting a different message. Then via the comms menu or trigger, I wanted to turn on the selected vehicle's transmission, whilst turning all others off, but be able to do this repeatedly. So on the ground, say at Manston, you'd would turn on the nav radio and set it to the right frequency and the Manston vehicle would be transmitting. Then after take-off the pilot could, via the radio menu, select Hawkinge. The Manston transmission would stop, and the Hawkinge transmission would start, thus bypassing the need to jump into the co-pilot seat and retune the radio. I can't seem to get a transmission to stop once it's started however. I've tried with Flag condition from within the unit's advanced waypoint menu. Turning group AI on/off doesn't seem to work either. Anyone have any suggestions please?

Strange, in order to help we need some more information. What resolution are your monitors? Can you post your monitor config file? Can you take a screenshot of your DCS settings page? Or If both your monitors are 1080p then you could try this monitor config file Schmafuzius 1080.lua if both are 1440p then try Schmafuzius 1440.lua In DCS in game settings your resolution should be either 3840x1080 for 1080p, or 5120x1440 for 1440p Enter the aspect ratio as either 3840/1080 or 5120/1440 and choose the monitor config file after placing in saved games\DCS\Config\Monitorsetup\

Seems to working fine for me, The data is entered into the Waypoint slots. You don't need to enter editing mode manually, that is automatic. I Even tried hitting the transfer to DCS switch with the PVI switched off, the waypoints were entered, and when finished it switched to Operating mode. All happens in the blink of an eye, the only thing I saw was the switch going from off to operating. Sorry, I forgot to enable mouse pointer recording

Hi, I was trying to make a mission that had a sort of automated/AI Navigator, my idea was that at some point at the start the Navigator would set up the Direction finding radio. The problem is that when you are occupying the pilot seat, some switches/controls are not available to you, eg the power switches for the Navigation radio, and the navigation radio itself. This also carries over when you try to script these actions in the mission editor, the actions are not completing because I am in the pilot seat. I would like to see at least the scripted actions being able to complete without changing seats, possible? Thanks

It's not too difficult to have this effect if you are creating missions yourself. In the scripts parts of the editor create a new entry, the second box would be "when unit dead", and the last box would be "explosion at unit" or something along those lines. You can also choose how large the explosion is. Then you'd get something like Below

I havent been on for a few weeks but it was definitely working. If I recall correctly the data entry in the Ka-50 is so fast that it's easy to assume nothing has happened. This is also the same in the A10C. Be aware that "TheWay" enters data into the PVI800 navigation system. The PVI800 system and the ABRIS are NOT linked, so you won't see any new info on the ABRIS screen. This is not like when creating missions with waypoints in the mission editor for the Ka-50, as DCS automatically enters that information into both the PVI800 and the ABRIS systems, so you get your route displayed on the ABRIS. But for any new waypoint whilst in the cockpit, you would have to enter the data into both systems individually. However the PVI800 system is the source of the waypoint information that is displayed on the HUD, and also what controls the autopilot for waypoint following etc. So "TheWay" is still really useful in this regard, you just don't get a fancy waypoint line on the ABRIS screen.

I don't have this issue using both "TheWay" and DCS-BIOS in the same export.lua. However I can't comment about using both Santi's editor and theway together.

I personally have never been able to make DCS display anything left of x=0 y=0. With these coordinates being the top left of whatever display is set as "make this my main display" in windows display settings. So my suggestion to try is moving your primary monitor in display settings so it aligns with the left dashed line in your image above. Pressing and holding CTRL while dragging monitors around in display setting will disable "snapping" and give finer control. Your Center viewport would then look something like Center X=0 Y=1080 Width= 3020 Height=1080

Quite a long standing reported issue

I dont use Helios, but the Su25T shkval is exported as RIGHT_MFCD by default.

No problem

I'm sorry I can't answer that as I don't use Viacom Pro. I have programmed it to use 4 modifier keys Win+shift+ctrl+Alt and another key for all the required binds to try and not conflict with anything else but I can't be sure Viacom doesn't use these. However, I have made it so there is one section that has all the keybinds, and all other actions then reference that section, so you can change the keybinds in the keybind section and it will all still work.

Just popping by to say thanks for the "exported MFD freezes in external view - fixed" for F16 and A10

And the other two seem to be fixed now, Thanks very much!

Much better after today's update

It has improved, the flames don't seem be as lazy now, but could still do with a bit of tweaking imho. They could definitely do with a bit of sharpening up, multiple very short flashes instead of the seemingly constant flame, and maybe randomise it a bit between cylinders. They are still a bit too bright though I think, they should be rarely visible during daylight hours, even dawn and dusk to an extent. Heading in the right direction, but not quite there yet for me.

Simply turning off FULLSCREEN mode in the settings menu should fix this. I don't notice any performance difference when using fullscreen or not with multiple monitor setup.

Please check out the lower half of this post edit: I've edited this post with a link to my main post about this topic. The file has been updated on the post below. Cheers If the link below doesn't take you directly to the correct one, it is the lower half of the second post on page 1 of the topic,

My monitor config file may well be a bit overly complicated for most people, it's not 100% necessary to set it up like that. Basically the reason behind it is that the screens in the FC3 planes are always called LEFT_MFCD and RIGHT_MFCD, and they can not be changed. So in order to display the FC3 plane's screens in a different location from the other aircraft, I had to give all of the other aircraft screens unique names. This was so I could have the SU-25 TV Screen large on my second monitor, but my MFDs are usually on my third monitor which has Cougars, if that makes sense. So for you, with one big screen for your cockpit view, and 3 little screens for MFDs you could probably get away with LEFT_MFCD CENTER_MFCD (default name for F18 AMPCD) EHSI (same coordinates as center) RIGHT_MFCD (M2000 screen default) F14_VDI (same coordinates as LEFT_MFCD) F14_TID (same coordinates as CENTER_MFCD) F14_HSD (same coordinates as RIGHT_MFCD) and you wouldn't need to modify any of the aircraft lua files. But if you want to, feel free to modify my monitor config file from the "Display Exports.zip" on page 1, make sure to use the modified aircraft files in there too. I'm not sure if the files have had any updates since I posted them, so here's the latest ones I'm using. They don't change that often during updates. Display Exports.zip I think when you get all of your screens setup, especially if you have TM Cougars, you will need to do a bit of editing of the MFD coordinates. This little program will come in handy for that... http://breakthrusoftware.com/html/onlinedocs/kb/installkb/ScreenCoordTool.html

Yes that seems ok, just bear in mind that the names you have given to some of the MFDs are not the default, and some aircraft lua files need to modified to use those names. For the F16 you could always have the EHSI in the centre screen For the F14 you can actually display a RIO screen without the need to switch your front seat screen. Just a couple of ideas.

You must have seen that post before I deleted it, I noticed tacview was the same, and indeed mine is the same way