mkiii

It's worth noting that braking too soon can end up making the brakes less effective over the landing run if they overheat before you are travelling slow enough for them to work correctly. A clean F-18 should be easily able to land on a 7500ft runway in DCS with Full Flaps, air brakes, Aerodynamic braking (Stick back) and braking only once speed reduces to <100 Knots. I just tried it (I have no experience landing the F-18), and used up about 3500 ft of runway - stopping just past the half way mark on Kobuleti. I think the standard landing is for something like 5000ft+ in dry conditions 3500lbs weight at sea level. The manual is somewhat lacking in info on such things.

Where is his cigarette?

Yup. an hour to start her up followed by cruising around the ocean for 8 hours, hoping to spot a ship or a sub would be a blast! Do we have an ocean big enough? Perhaps the Bucc might be a bit easier on the sim/life balance ;)

The Nav Lights illuminate the whole fwd face of the ailerons on both sides, viewed from the cockpit, which should not be possible. Additionally, the position of the lights seem to be too far rearward compared to photos of surviving examples of Doras They should be visible from the front:- https://abpic.co.uk/pictures/model/Focke-Wulf%20Fw.190D-13xSxR11 http://www.skandalshirt.com/Flugwerk/html/_media/GAL_DIR/FW_Langnase/_1.jpg

BMW969: I think you will find your setup a lot easier if you place your small screen to the right of the Main screen in your monitor settings in Windows - that is to say physically it still sits below, but is positioned to the right, and level with the top of the main screen as far as Windows is concerned. This is how I use it because I have a monitor physically below, and triple screens (although only using one at present). Other than the fact that I have different sizes, and more instruments exported - this is how I do it. This can have the benefit of using fewer pixels (in some setups). However, Arrange as you see fit - it just means changing the numbers to suit how you want it - to the side or below. I suggest a quick tool such as Cursor Position From Mattlav software to get a rough idea of your positions. The important thing to remember is that the 3d view size, and GUI position is what goes in the lua, while the total screen size in the GUI set-up screen is the overall size of all your screens - so 5760x2160 in this case, or 3840x3240 if you have a top & bottom set-up. Aspect ratio should be calculated too - if you don't then it will assume that you want the total aspect ratio for both screens - and that will be stretched. Then you can use a modified 1 screen MonitorSetup lua like this:- _ = function(p) return p; end; name = _('MD_TestScreen'); Description = '1 screen as 1 viewport plus small Monitor physically below, but to rh/top in windows screen config' Viewports = { Center = { x = 0; y = 0; width = 3840; -- Width of 3d viewscreen (main monitor) height = 2160; -- 3d world will only display in this area initial splashscreen however doesn't know about this setting. viewDx = 0; -- NOTE Options.lua via the gui option settings uses 5760 as the TOTAL screen width. viewDy = 0; aspect = 1.7777777778 } } LEFT_MFCD = -- Built-in { x = 3841 y = 360; width = 512; height = 512; } RIGHT_MFCD = --Built-in { x = 5247; y = 360; width = 512; height = 512; } -- F-18C (or other) centre MFD Built in (ish) CENTER_MFCD = { x =4544; y = 360; width = 512; height = 512; } GUI = { x = 0; y = 0; width = 3840; height = 2160; } UIMainView = GUI

It is like the M2000. Search for the Commands "Left MPCD Export View ON/OFF" and assign a keystroke or button to use it. Same goes for the Right MPCD of course.

I think you missed the smiley ;) <-

I'm not sure starting the engine with empty tanks is going to help :) Interestingly, the RL Pilots Notes make no mention of engine restart. They just let you decide whether to do a dead-stick, ditch or abandon (see page 33) :- http://www.wwiiaircraftperformance.org/mustang/P-51D-manual-5april44.pdf

Just give me a clickable Su-25... Then include some older British Jets (Buccaneer, Hunter, E.E. Lightning Jet Provost Strikemaster) ;)

look at DCS World\Scripts\Aircrafts\_Common\Cockpit\ViewportHandling.lua put something like this at the very top of the file:- local kneeY = 800 -- size local kneeX = 550 -- size local kneePosY = 270 -- offset from top of leftmost monitor local kneePosX = 1330 -- RH side of Leftmost monitor. Then look for the following line:- dedicated_viewport = {default_x,default_y,default_width,default_height} And change to this:- dedicated_viewport = {kneePosX,kneePosY,kneeX,kneeY} Bear in mind that this is best done via some sort of mod manager such as Generic Mod Enabler, otherwise it will be overwritten the next time you update.

Perfectly? Your labels work OK then?

Yep it works the same, but labels are broken again if you use a setup that involves a setting wider than the gui/3d world screen to export MFDs for example.

Maybe it's just the Quickstart mission that's broken then. Because it sure as eggs is eggs, ain't working without a kerfuffle here. NOTE: As mentioned above, they are OK when no other weapons (apart from gunpods) are loaded. Which is what you get if you load up the Q.S. Caucuses Mission "Rockets & Guns", but try the "AV-8B Weapons Practice" Q.S. Mission & It does what I describe & only fiddling with the Manual selection allows firing.

The FMOptions lua has not altered at all since early on. I just compared 1.5 and 2.5 versions to see if anything new is there - they are the same. You can get rid of some bounce by changing the following line in that file:- tailGearSpringForceFactor = 9000000 -- Original 17000000 I can't say I ever worked on spitfires, but I have worked on other tail draggers (DH Chipmunk), and if they bounced as much as this, I would have been worried.

Just did a very heavy wheels up pancake into the ground, followed by a nose-over, and general tumble across the ground to find... no damage, prop still spinning & revs OK. Only caused damage when I tried Lowering the landing gear, seemingly only causing a bit of coolant leakage - note that even the wingtips are unscathed. EDIT: Aww... probably should forget that. I just noticed that "Immortal" was set to ON in the System settings. I'm not sure why that should relate to the aircraft though. I just assumed it was the Pilot that was immortal.

Rocket selection seems to be broken in 2.5. At least in the Quickstart mission "Weapons Practice" in Caucuses. I cannot get rockets to fire using normal selection & fuzing methods. Once selected, any change of fuzing from Safe gives "SMC Error Cannot find selected weapon release progmam". It is possible to fiddle with the Manual dial and make them work, but you have to do things in a particular order:- 1: select weapon 2: Select Mode CIP 3: Set Quantity > 0 4: Set Mult > 0 5: Flick Manual Fuzing dial to N/T (It might be necessary to do this more than once). Please tell me that it's not just me. ;)

My previous setup for 1.5 (I used the mic switch), no longer seems to function in 2.5. So it is working for some OK but not others. Can you say what your setup is (DCS Version, and button) if you do have it working so we know whether it is a bug or just a settings issue.

Yes, same setup. You do have to turn them on in-game via a command for each though. There's a thread describing this.

Just try installing 2.5 from scratch (via main DCS page download) & copy your existing control, monitor and log files across if you are impatient to get it and don't have the beta.

My BBC Micro Model B won't run 2.5. I am disappointed ;) Seriously though, If you set absolutely everything to the lowest possible settings on any sim, all you should reasonably expect is green for land and blue for sky.

I think that might just cut it to shreds ;)

It does seem better in 2.5. However, I did notice that there was a tendency for the sensor to lock onto the poles of streetlamps (not the lights themselves), instead of vehicles moving down the road behind them. I'm not sure that the steel poles would provide a better target than the vehicle behind. Perhaps this should be corrected, it seems that those poles are a little too hot.

I get flashing on 2 monitors to the side of the main monitor (when black & unused in 3d) that seems to correspond to tracer fire if for example, I attack a tank. With the labels bug currently affecting multiscreen setups, I also see labels flash by when they are turned on. My 4th monitor designated as a viewport for MFDs etc doesn't get the flashing.

Multiscreen or Single? Kadins fix changes the appearance of the labels, but (I assume) not where they appear if affected by the ongoing and recurring multiscreen label offset bug, which makes them appear offset to the right by a monitors width.

Yep. This is the same as we had in 2 then 1.5, and now 2.5 Which is odd, because I'm pretty sure it was fixed a while ago. The old fixes where you either set the GUI to the leftmost monitor or allow it to spread across all screens doesn't seem to work now, not that they were satisfactory anyway.