jonsky7

@Deadseed You Sir are a hero of mother Russia , and me. Seriously though, never thought that a fix would come so quick ! Thank You very much !

Well this is the first few lines of 9K113_CAM_base_page.lua As the LALT-A Keybind is listed as "9k113 aiming profile on/off" I thought it was a good bet on being the file responsible for the sight view. And from looking at it, it seems to me that it should be getting the center viewport information, but it isn't. I've played around with the entries from ULX,ULY,SZX,SZY,GUI_scale = get_UIMainView() to aspect = SZX/SZY but nothing seemed to make any difference. I don't really know what I'm doing, was just hoping to hit the jackpot by guessing, but sadly no. dofile(LockOn_Options.common_script_path.."elements_defs.lua") dofile(LockOn_Options.script_path.."ASP17V/Indicator/ASP_17V_definitions.lua") HUD_DEFAULT_LEVEL = 2 HUD_NOCLIP_LEVEL = HUD_DEFAULT_LEVEL - 1 ULX,ULY,SZX,SZY,GUI_scale = get_UIMainView() local v = find_viewport ("GU_MAIN_VIEWPORT", "CENTER") if v ~= nil then ULX = v.x ULY = v.y SZX = v.width SZY = v.height else ULX = ULX ULY = ULY SZX = SZX SZY = SZY end aspect = SZX/SZY SetScale(FOV) HUD_OnlyX = LockOn_Options.screen.width / 100.0 -- 6.0 HUD_OnlyY = LockOn_Options.screen.height / 100.0 --6.0

Same, it was reported earlier but it got moved to multi-monitor bugs.

In a word, no, sorry

Same here Autopilot indicator in top right, on 3rd monitor Petrovich flight helper, not over to the left (not sure if correct or not) Petrovich weapon helper not in centre viewport Weapon sight not in centre viewport, LWin+H helper box on third monitor Thanks

you're welcome

bump

Track and log file dcs.log cursor.trk

Sounds awesome.

Track and log attached cursor.trk dcs.log

Still the same in open beta 2.7.1.6430

Still the same in open beta 2.7.1.6430

Visual recon mode needs to be enabled on the server you are playing, and generally needs some sort of "Fog of War" enabled too. Which means that the enemies don't show at the start of the map but will show up when spotted by an Ai for example. 1. Turn off mouse clickable cockpit, either LALT+C or double click middle mouse button (wheel) 2. Right click your mouse button, you should see a red crosshair appear on your screen (may need to keybind the right mouse button under "enter visual recon mode") 3. Look at an enemy target, or group of targets, and Left click your mouse. Enemy targets should now appear on the map, you may or may not get a message detailing the units you have spotted, or if no units were detected. Answers 1. Yes, if visual recon mode is enabled in the server 2. Marks targets on the map (on the servers I've used it on anyway) 3. Don't know 4. Don't know 5. Don't know 6. Don't know

I see this is now reversed and the displays in F18 don't freeze anymore in external view, that's awesome, thankyou Now if we can just get the same for F16 and A10C

F18 exported displays don't freeze anymore One down, two to go

Came searching for this, BUT on further investigation it seems there's been a fairly significant change to the default.lua binding files. So if you are using any mods to add toggle switches etc, you will need to update your mod files.

The F-15C Radar display is exported as "LEFT_MFCD" So if you have a multi-monitor setup you can follow any guide that gives instructions on how to export the MFCDs to a second monitor I made this one

Are you using a multi-monitor setup? If so the autopilot indicator might not be on your main display, and possibly in an area of the resolution where you don't have a screen to show it. in the file DCS World\Mods\aircraft\Mi-8MTV2\Cockpit\Scripts\ControlsIndicator\Controlsindicator_page.lua line 276 autopilot_base.init_pos = {0,(1 - autopilot_height)} You can play with numbers to move the box around. mine is autopilot_base.init_pos = {-5.35,-(1 - 0.3*size)} --{0,(1 - autopilot_height)}

My Intercom entries look like this

If you're on the newest Beta, the time acceleration has been moved into the "UI Layer" controls section Are you on the latest Beta? I don't see these controls in my list. In your Saved Games\DCS\Config\Input\SA342\joystick Saved Games\DCS\Config\Input\SA342\keyboard folders are all the files in there xxxxxx.diff.lua? Or do you have some that are called default.lua? I know quite a while back they added all these pre-sets for commonly used joysticks, totally messed up my configs.

Yours is not too bad to work-around. You have one line that should be bindable to the keyboard, and another line that should be bindable to joystick buttons. It's orange because there are duplicate entries for the same thing. I think it happens when the entries in the keyboard default.lua and joystick default.lua don't perfectly match. E.g. the P-51D canopy closing entry for the keyboard is {combos = {{key = 'C', reformers = {'LCtrl'}}}, pressed = device_commands.Button_2, cockpit_device_id = devices.CPT_MECH, value_pressed = -1.0, name = _('Canopy Closing'), category = _('Systems')}, but the joystick is {pressed = device_commands.Button_4, cockpit_device_id = devices.CPT_MECH, value_pressed = -1.0, name = _('Canopy Closing'), category = _('Systems')},

SOLVED: Deleted the Settings.lua file from %%%/Saved Games/DCS/MissionEditor Never touched it, don't know what's gone wrong there, but nevermind, it works now. Thanks @G.J.S, sometimes I just need to know if it's just my game or everyone.

Just in the editor, and the mission planner before mission start seems to have the same issue

Am I the only one who does't have ANY airfield textures on any map any more since last update? Ran a repair, turned all mods off, still the same

Not sure if this is solely a multi-monitor bug. I fly in a server where we use Visual Recon quite a bit. Some players say they have this problem, some don't. VR users seem not to have the problem, some 2D players do, and some don't. Leading me to expect that this is multi-monitor setup related. I made sure to remove all mods, and ran a repair, before confirming that the cursor was still showing here for me. As per the title, The visual recon cursor no longer in the middle of the screen, it is now in the upper left quarter, and is very small. Thanks Edited Thursday at 12:54 AM by jonsky7