mkiii

Why? Surely it is better if every aircraft had the same L/R/C MFD display export name as they do now? If all are unique, then you need to create a separate entry for each. aircraft in your monitorsetup config. Or are you concerned about something other than exporting them to a screen?

And I personally would like to see this one finished before they even think about another version. Personally, I only have experience with Dutch & Belgian F-16As, and would love to see those, but I guess it will need a third party or a modder to do this any time soon.. While they are at it, can they create a Tornado GR1, Jaguar, Buccaneer, Hunter, Wessex, Puma, Chinook, Bulldog and Chipmunk, and other types I have worked on.

All true. Stanley airport is much changed, with the metal strip extensions gone, and runways now shortened again. Most of the bomb craters still exist if you look at recent imagery, and the terminal doesn't looks much different from what I remember. Port Stanley City itself seems to be much expanded now. There are roads all over the place that did not exist in '82. The Harrier strip at Port San Carlos (post landings) is gone, and the "village green" of the sheep farm no longer looks like something out of M.A.S.H. I'm not sure that Goose green had a lot going on in 82 structure-wise that is, there were some slit trenches and gun emplacements, but the strip was just mown grass, same on Pebble Island. The main thing you would notice since '82 is the relative lack of utterly destroyed Argentine equipment littering the place.

Interesting. I do 2d and 3d work on this PC, so I usually leave my Main monitor "un-enhanced" - might be worth a looksee.

I'm only trying it out as part of the free trial, and not learning anything in-depth, but honestly, I think it has some of the clearest set of instruments in DCS. I especially like the effort that has gone into making the luminous paint look... well... luminous. Are you spreading the view across multiple screens, or using a very wide screen? That can affect the default FOV / zoom quite badly if you don't account for it. on a single 2560x1440 monitor at default zoom the windscreen arch fills the screen, and the wing guns are not visible. Any wider than that, and yes, the instruments do start getting hard to read, but the same can be said for other aircraft. Your screenshot is certainly a wider FOV than the others, and not what I am seeing. If you want the advantage of an unnatural FOV, rather than having to move your head around, then you pay the cost of a panel that looks like it is 6 feet away and not 2. EDIT: Bear in mind also that the P-47 cockpit is a fair bit wider (about 36" below the sills, between the sidewalls), compared to the others, especially the 109, which is more like 24".

Well they sort of do, since all your user configs are external to the Install, and a simple copy/paste can deal with that, and most of the rest has to be dealt with using OvGME or similar, but no matter what, you always have to mess around with control settings. Its as if the system was designed to use a single 4 button stick and nothing else. Having every controller be assigned pitch, roll and yaw as well as POV quickviews every time is getting tedious in the extreme.

Enclosed cockpits are dark - especially when everything is painted Black. All the others are ridiculously bright, especially the FW, Me and Spit. As mentioned above, they could do with using the same settings as this one.

PST is Pacific Standard Time, not Eastern European Time . Tha is only 2 to 3 Hours ahead of GMT not 9 hours.

You should be fine with those, they are made for each other, but it is fair to mention that you can get by with only the F-18, since a functional carrier (not as detailed & no deck crew though) is built in to the free version, and you have the large expanse of the Black Sea to place it on. The AV-8 is also a good fit for Naval operations, perhaps not on the Supercarrier itself of course. FC3 is fairly cheap too and will give you a number of aircraft including the Russian/Chinese Carrier borne aircraft to a similar standard as the SU25-T supplied in the free version. The JF-17 is a good buy too, being very complete already, even though it is still Early Access.

It must have just cleared after I last tried it then. I just checked, & it is working. I can now search using Edge too.

I have been checking all afternoon, and so far nothing has show up as a free trial, although I do see the sale items on the E-Shop. Maybe they meant the 23rd?

The notion that trees might be there to be removed is funny. The only ones I saw were in the grounds of buildings. In 1982 I was flown past what is now RAF Mount Pleasant, It was just a farm then, although I didn't see any buildings myself. The aircrew pointed out the semi flat area of heath, surrounded by what looked like bogs and lakes, & said that is where they were planning to build a base. There were no roads, except at Port Stanley, just the odd muddy farm track around settlements. But there you go, they now have roads and a big RAF base in the middle of nowhere, surrounded by nothing but gorse bushes, tussock grass and rocks., but trees? I don't think they will be an issue.

The infrequent updates of some config files can catch you unawares, so it it is a good idea to occasionally compare your modified files with the default versions using the handy compare plugin free with Notepad++. These command binds are sneaky, and you might be adding a mod to a file that was fixed in an update. Additionally, JSGME was no longer supported last time I looked, and although it still seems to work, you may find that the newer OvGME is a more reliable alternative.

If you start with a fresh install on a new machine, and let DCS create new sets of files in the Joystick folder, they will automatically have the current IDs appended once you exit and they are saved. You could just copy and paste these filenames if you really had to. I think it would certainly be a whole lot quicker to just copy all your old files and just reload for each controller, than to laboriously copy / paste / rename all the files, for all your modules.

Well at least that problems is fixed now: It was MS Edge to blame. Posting works fine on Google Chrome.

Ahah! Panic over. The problem seems to have been Microsoft Edge.... I'm posting this from Google Chrome with no bother. Had me worried for a moment there. It's my own stupid fault for trusting that MS P.O.S. in the first place.

Since the recent forum change, I have been unable to get any search results. I set the search options to look for any of the words typed in any post, from any time in the last 10 years. No results for anything. I tried logging in on Chrome & MS Edge. No difference. Any clues? Apologies if this has already been brought up.... I have no search, and I'm not going to ready every post to find out.

This is still an issue. I think the Chiefski needs to put some Nitrogen in the Nose oleo. And while he is at it, perhaps some in the main gear. This thing is wallowing about from side to like it is a bicycle and rattling itself to death. I haven't flown it for a while, but I don't recall ever being in danger of the aircraft falling over on take-off before now. What has changed?

Good catch Bailey. Just on the off chance, that anyone has a similar setup to me: This is what I put in script\aircrafts\_Common\Cockpit\KNEEBOARD\indicator\init.lua I set my side monitors to align with the top of the main monitor, and returned my GUI to the centre monitor.:- allow_manual_viewport_placement = true manual_viewport_dlg = "Scripts/UI/KneeboardCanvas.dlg" manual_viewport_margin_left = 1920 manual_viewport_margin_right = -1920 manual_viewport_margin_up = 0 manual_viewport_margin_bottom = -0 Note If your side monitors do not align with 0, then just use that offset in Up & bottom.

No. It is multi monitor related here. My scale is set to 1, and I don't have a 4k monitor. My monitors layout = [ 1 ]+[ 2 ]+[ 3 ]+[4] (sizes:1920x1080+2560x1440+1920x1080+1280x1024) So 3 main monitors in a line. Although I am currently using just the middle one for my Main Windows Monitor, and 3d [2] - I sometimes use all 3. And 1 small monitor with MFDs stuck to it at the end [4]. Therefore the GUI and 3d screen [2] have a resolution of 2560x1440, while the overall "desktop" size set in my Monitors lua is the width of the 4 screens, 7680x1440, run in windowed mode, and MFD/Instruments displayed on monitor [4] outside of the 3d viewport. The kneepad has always appeared at the extreme right edge of [4] and is unmovable. With screen [4] disabled, and the numbers in the GUI adjusted to 6400x1440 the Kneepad appears at the extreme right edge of screen [3], and is unmovable. Before this update, I manually positioned it with a modified lua. Using the lua with this update causes the frame to be separated from the map by exactly one monitors width to the right (1920 pixels) because that is the offset that determines the position of the GUI in the centre screen, as specified in the GUI= section of the Monitors lua config file. WORKAROUND:-. It's not ideal, because I have a stiff neck already, but it does prove the point that the multi-screen is an issue. IF you want the GUI to be anything other than screen 1 If I specify the left monitor [1] to be the GUI, leaving the centre one [2] as the 3d, then the Kneepad AND Frame appear - Initially, still at the extreme right hand of the 3 monitors, but movable. Like this:- GUI = { x = 0; -- Usually 1920 for me to get it on screen [2] y = 0; -- IRL mine is set a bit lower width = 1920; height = 1080; } UIMainView = GUI Unfortunately, since I have monitor 1 lower than monitor 2 by 78 pixels, it means my frame is offset down by that amount from the MAP. If you use 3 identical monitors, OR make sure the side monitors align with the main monitor, all will work.

Thanks for that. What would REALLY be good, would be the ability to define the position in a setting or a config, as it once used to be (in the MonitorSetup folder), or at least to set a default position, that ONLY relied on screenspace used by the 3d views. At the moment, and since forever, it takes into account the entire desktop width, the bane of all multi monitor users. I had everything set up with a modded viewportHandling.lua, to force local x/y settings to make the Kneepad appear on the LH monitor, and since this update, got the separated window frame and map. Removing the mod defaults to placing the Kneepad on the extreme right, partially off screen on my 4th Non-3d view monitor, used for MFD displays only. Same as the above post, it is unmoveable & un-selectable - just like before the update. Really, the problem is the way multiple monitors beyond the basic 3 are handled, or at least, how we must configure them. The config files are opaque at best. I really like being able to export my instruments to my MFDs, it is no problem for BMS. each 2d and 3d display gets an XY setting entered in a little GUI based setup app. perhaps that would be easier than altering the code of the main app?

Glad top hear that my brain is not completely addled then. The guys with more recent experience are clearly used to a pretty different aircraft to the one I remember, and as depicted in the photo of the older models I posted up top.