jonsky7

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

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

Why would you want that removed If you don't want one in the water, simply don't put one there.

Nice!

In free camera view, when pressing "Numpad Del" for the padlock view to an aircraft, there's some kind of boundary that moves the camera out of the way if the aircraft gets too close. Anybody know how to remove it, perhaps like the terrain boundary trick?

I made a recreation of Breitling Fighters flying LOW down a canal, no music, just the sound of raw powerrrrrrrrrrrr. All sounds recorded in game. The original

In this screen shot the M2A2 is moving along the pathway to it's left. I think one of the problems might be that the end of the pathway is very far ahead of the unit itself. So it ends up trying to hit the end of the path, which makes it go off road. The units also stop before reaching the destination point because the path line has already made it there.

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

I'll give that a try, thanks

From your video at 1:25 mark The problem is that when you set Saturation X to 80%, the virtual axis Y doesn't go to 120%, it just hits the limit of 100% before you hit 100% on your physical axis. That is the reason for my suggestion. Saturation X set to 50, virtual joystick has a Y limit of 100. What I propose is being able to set Saturation Y to 150, and maybe something like this red box appears to show you where the 100% virtual axis limit is. So when you are using force trim, you can still achieve more or full virtual axis deflection. Well that is what we do now yes, I was just looking to see if there something that may be better.

With the Huey in default trimmer mode, there's a half a second delay before they joystick input becomes active again, but it doesn't need to be returned to centre. In the Mi8, in default trimmer mode, on depressing the trimmer button the joystick input is immediately added to the new centre. It's not a major problem, I'd just like to have them all behave the same. I'm actually trying to come up with ideas on how to improve the system as a whole. What I find incorrect is that you do not have full control deflection authority when there is some force trim applied.

Yeah that's a good idea, I do use my joystick for flying fixed wing too though, thanks for the suggestion though.

Thanks for you input, however as you say, that doesn't actually increase the range of saturation, there's a limit at 100%. It's the Saturation_Y I would like to be able to extend.