jonsky7

Not exactly sure about one of the buttons as it's a icommand type keybind, but I've collected all the stuff needed for the M2000C and written the keypress flow in the attached .lua Hope it helps M2000C WAYPOINT ENTRY FLOW.lua

Engine also not repaired after taking enemy fire.

@Comrade Doge That makes sense yeah Good luck! Where do these codes come from, I thought I could try help by writing the input files for the M2000C, Ka-50, or Gazelle button list, all are device 17 DCS rtn 3032 -1 DCS dn 3035 -1 DCS up 3034 1 rokr up 3031 rokr dn 3030 1 3003 2/N 3004 3 3005 4 3006 5 3007 6/E 3008 7 3009 8 3010 9 3011 0 3002 ENTR 3016 */

@Comrade Doge Firstly, fantastic, the A10 entered the coordinates so fast I didn't think anything had happened Precise coordinates in the hornet also working great. Bug Reports/feedback ..................................................................................................................................................................................................................................................................................................... Like I mentioned, having your program automatically press PRECISE button, causes precise mode to be off in some circumstances. So if you collect some waypoints, enter them into the 18, then add some more waypoints, precise mode is turned off the second time inputs are made. Say you plan some targets, go and hit them, land and re-arm, plan some more targets, precise mode is then turned off. or Plan targets and enter coordinates, on the way to targets, new tasking is given, enter different targets, precise mode is turned off. We could turn precise coords off before using the tool every time, Or just turn it on once when starting in a new airframe (I'm thinking multiplayer) I would prefer just turning it on during start-up procedure. (this I could myself for me if you could point me in the direction of turning the source code into an exe file please) ...................................................................................................................................................................................................................................................................................................... Non F18 related In version 113 I noticed that the waypoints weren't cleared after "begin transfer to DCS" was pressed In v120 the waypoints aren't cleared and the "cursor" dot remains on screen, until Discard button is pressed, not sure if that's intentional or not. ..................................................................................................................................................................................................................................................................................................... The tool doesn't work in Nevada map, as Longitude is West eg W115'21.36 Doesn't work on Marianas Map, Longitude is more than 100deg East, eg E114'54.767 both the 18 and the 16 can accept a first zero eg E054'25.658 Those two maps aren't the popular, just though I'd point it out The Channel map has both East and West coordinates on the map. (mainly ww2 map) Possible to acquire whether East or West during coordinate capture? ..................................................................................................................................................................................................................................................................................................... Trying really hard not to come across as ungrateful, you did ask for feedback Thanks again

This is still happening

@Comrade Doge That is seriously cool! Thanks

+1 I'm getting CTD quite often when removing the pylons in multiplayer (saving weight for logistics). The game CTD's immediately after the ground crew call "rearming complete". Nothing in the log though.

It's AMPCD PB 19. But I really wouldn't bother with it. As it's a toggle. So each press of the button while the HSI is in data mode, turns precise mode on/off. I think it will get out sync. Unless of course you can extract from the sim whether precise mode is activated or not, and turn it on if it isn't. That seems a lot of work though. I would just put in the instructions that precise mode needs to be on before the transfer of waypoints. Another request, in the 16, I see you have this code at the end of the inputting. Until you add elevation, if you're going to of course, could you remove that so it stays on the Steerpoint page? As at the moment we have to go back into steerpoint page to manually enter the elevation. I would have done it myself but I don't know how you turn all of the files into an .exe //return to main page commandArray.put(new JSONObject().put("device", "17").put("code", "3032").put("delay", "10").put("activate", "-1")); I can sort of understand the .lua files that do the inputting, but I looked at the code for getting the coordinates and was completely lost lol. I wouldn't know how to make it enter only the first 4/5 digits from the coordinates, press enter, then do the other three either. Also, would there be any chance of making a dark mode window, to be less intrusive on a black background? I know I'm being a pest, sorry about that, but coding is a bit beyond me. thanks!!!

Good from an aesthetics point of view, but it doesn't remove the weight of the suppressors

As I'm one of those who would really like Hornet precise coords and elevation, if I can help with what buttons need to be pressed etc, I'm very willing to help. and with @TrichomeCharlie I'd chip in. For precise coord entry in the hornet, if we take an example, assuming Precise mode is pre-activated. Precise is a toggle, so I don't think you could press it for each waypoint, the user would have to set Precise before using the tool. N25'54.675 E054'23.430 @ 573ft Then: increment steerpoint press UFC press position 1 Press North (this is where it will get tricky) start entering latitude (first 4 digits) 2 5 5 4 press UFC enter press 6 7 5 press UFC enter Press East Start entering longitude (first 5 digits) 0 5 4 2 3 press UFC enter press 4 3 0 press UFC enter Press position 3 (elevation) press position 1 (feet) or position 2 (meters) press 573ft or 175m Press enter end of waypoint

Does anyone else experience the SLAM-ER just spazzing out at 300ft ish? I set the waypoint fairly close to the target, with the high flight setting, they cruise great at 35000ft, then dive, the missile tracks perfectly, then just changes course and misses by a few hundred feet. I have no idea if this is a problem with the weapon, netsync, or the server I play on, or I'm doing something wrong but they won't hit anything lately. I thought it was the servers turbulence setting, but apparently it's been turned off recently. edit: I should maybe point out that I'm trying to use them to hit runways. Thanks for any input.

guess not, just the keybind for opening the pop-up window had been deleted

Still the same

Am I right in thinking that the ability to use the NS430 pop-up window has been removed in the last patch?

Nice one

If your desktop is spread across your monitors, then I can't see not being activated would stop DCS doing its thing. As for the black sky, all I can suggest is going to saved games/DCS and delete the folders fxo metashaders2 They will be rebuilt when DCS next starts. In order for me to help you sort out your mfds, I need: 1. Screenshot of your windows display settings showing the arrangement of your monitors. 2. Resolution details of your monitors 3. Where you want the MFDs to be. 4. Screenshot of DCS settings, the page with resolution etc 5. Maybe attach the monitor config file you are using.

Cool

Weird, Elmo seemed quite adamant that this was "Working as intended". yet today.... Added: AFC will disengage when more than 60 knots and more than 15 degree angle of attack Added: AFC will disengage when less than 50 knots and more than +20 degrees pitch or less than -15 degrees pitch Added: AFC will disengage when less than 50 knots and more than 20 degrees roll Added: Implemented AFC WCA logic, if AFC goes fully off, requires momentary RESET to allow it to go back on Added: AFC Advisory will trigger when AFC Alt Hold forced or commanded off, will clear on master caution reset command Added: AFC Advisory will trigger when AFC forced off or commanded off, will clear when AFC reset is commanded Added: AFC Advisory will not trigger when AFC turned off due to weight on wheels Fixed: Corrected AFC Alt Hold to lock in reference altitude when within 500 FPM after being engaged Fixed: Corrected AFC Alt Hold to disengage when leaving reference altitude by more than 250 ft Fixed: AFC will now not operate (but not disengage) when outside of 60 degrees roll and 30 degrees pitch until pilot returns within 60 degrees roll and 30 degrees pitch Improved: Adjustments to Yaw SAS feedback based on SME testing Improved: 30% stick pitch tolerance before disengaged AFC Alt Hold Improved: Adjusted for more representative pitch and roll response during AFC Improved: Adjusted stick behavior while AFC engaged to allow for more representative maneuvering flight during AFC based on SME feedback and testing.

Nice guide

Haha awesome, you know a reaction like that is all it takes to make it worthwhile, glad to have helped mate.

Yeah, I wasn't sure about how to set it up, I've never done a MFD export with more than one screen as the "camera". I've also not played around with when main monitor wasn't the most left in the display settings. Not having your main monitor as the most left used to cause all sorts of problems, but I have been told that is no longer the case, but I'm not sure how it's implemented. The coordinate system for the screen works on x y position. I'm not sure if your main display is classed as x=0 y=0, or it's just the top left corner of the entire resolution is x=0 y=0. Try this one 3 monitors, MFD side v2.lua

If either of those completely mess up your DCS and you can't press "OK" to revert back, if you move or delete Saved Games\DCS\Config\options.lua that will restore the graphics setting to default.

So I have assumed that all of your monitors are 1080p. There's two ways you can do this 1. leave your monitors setup like you have, but that is over 4 million more pixels DCS has to render, and leaves a lot of un-displayable space, shown in red. There are many of the "games indicators" like the Crew status windows for Huey and Mi8, the controls indicator, NS430 pop up window, and the kneeboard etc, that are configured to open in the bottom corners of the total resolution, and since you do not have a display there you won't be able to see them. But here's a config file for you to try. Use 5760x2160 as your DCS resolution Monitor config file---- 3 monitors, MFD under.lua 2. Personally I think the following would be better. Re-arrange your displays like this Use 7680x1080 as your DCS resolution Monitor config file--3 monitors, MFD side.lua As I have no way to test your setup, you'll probably have to do some adjustments. I'm also not sure about not having the main monitor as the far left one. So report back if needed. But do check out the guide to give yourself an understanding. Good luck

try looking here @Mule What graphics card do you have? What resolution are each of your monitors? Which monitor is the main monitor set to in windows, 1? with that info, attach the monitor config file you are using and I'll take a look

Check out the guide I made for setting up MFCDs, I think that doing it the way you want to will cause some issues in DCS, nothing major, things like the controls indicator might not appear where you want them, then you'll have to decide if it's better for you to have your desktop behave as you want it, or DCS. You shouldn't need to change your centre viewport, just the y position of anything you want to display on the 2nd monitor. Viewports = { Center = { x = 0; y = 0; width = 2560; height = 1440; viewDx = 0; viewDy = 0; aspect = 2560/1440; } } DCS will render things within the resolution you give it, whether or not you have any part of a display to actually show it. So similar to the examples in my guide, yours will look like this. Anything DCS renders in the red area, you won't be able to see it as there is not any part of an actual display there.