mkiii

It is, if it's military - and there is an alert state (or war on). This is a combat sim y'know ;)

The Bucc has a lot of things going for it - Navy or Air Force. Martel, Sea Eagle, Paveway / Pavespike, sidewinder, bombs galore - internal or external, including nukes. Lots of fuel, and ability to refuel others with a refuelling pod... 2 seat Nav/Pilot. In fact the only downside is the one shot chaff dispenser (cardboard chaff packets taped to the inside of the airbrake) & no flares. Why they bothered with the chaff is beyond me, since when I was on 208, I doubt they flew high enough for it to be of use. Whover did it would have to faithfully simulate the little details, like the Polystyrene cone needed to be able to view the scope, and the Hydraulics failing to fold more than one wing at a time without having to get a groundcrew to jump up & down on the offending wingtip to make it move... followed bu a swiftish exit from said wingtip before it did so. Alas, I don't see much sign that it is likely to happen...

But then the argument will go - "That's a General Electric T-58 built under licence blah blah blah"... The Wessex and the RR Gnome engines were different beasts to the original designs. Suck it up, sometimes American (or should that be Russian - at least in Sikorskys' case?) designs can be improved upon ;)

I look forward to seeing the manual pointing out what the "Relief tube" between the crew seats is for. ;)

I was originally running a 3 screen 1920x1080 and don't recall things being too difficult to spot and now mostly just use a single 2560x1440 for the 3d stuff. I get the feeling that things are harder to spot now. That could be due to a number of things. My eyesight is not getting better, and DCS World has gone through a lot of changes since 1.5x Some of it is because of our need to see the whole cockpit - so we artificially have a wider FOV than necessary to try and fit more of the world view into our main monitor - which is why I preferred 3 monitor setups because they provide more realistic peripheral vision, but like Random - can't justify the expense of upgrading on a whim. Another consideration to bear in mind when choosing, is that having a non standard screen can mean a LOT of fiddling with FOVs in LUAs to get snapviews & default FOVs working in the new screen setup. That is one reason I stopped using 3 screens.

https://www.flight-mechanic.com/brake-anti-skid-systems-part-one/ https://www.flight-mechanic.com/brake-anti-skid-systems-part-two/ https://forums.eagle.ru/showthread.php?t=224862

Sorry to burst any bubbles re vertical arrangements, but my setup is side by side and my MFDs are stuck onto a 1280x1024 monitor to the side of the main (2560x1440) display, with 414x414 MFD windows - blurry as hell on F-18 and crisp as lettuce on all other aircraft. I have 3 main monitors but currently only use the centre one for 3d display since the side ones are lower res. 1 either side is used for Kneeboard and control displays, (and sometimes 3d if I can be bothered), with the MFD monitor off to the right of those 3. total max dims of all 4 is 7680x1440 This is more readable for me - but it doesnt seem related to scale. stroke_thickness = 0.6 -- 0.8 stroke_fuzziness = 0.2 -- 0.5 -- Currently is used for DMC generated fonts black outline DMC_outline_thickness = stroke_thickness * 3 -- 1 DMC_outline_fuzziness = stroke_fuzziness * 1.1 -- 1.1 DMC_stroke_thickness = 0.5 -- 0.65 DMC_stroke_fuzziness = 0.2 -- 0.42

Strikerdg - if all else fails, look for Chucks F18 guide. He details his Hotas setup. It isn't what I use, but it looks functional enough. I don't have the F-5, but the A-10 is what this beast was made for - so it's unsurprising that it just work - I'd have hated to have to set it all up manually. I wouldn't worry too much about the more complex setups - most of the time you don't need them, and don't forget that using one of your spare buttons as a shift helps a lot when you want to get 2 commands on a 1 way switch. If you are feeling really brave - you could try Target for DCS, but I don't think many people bother (I certainly don't), because you need a different script for each aircraft - and that's a PITA.

Yes - it is a wonderful thing to go through all buttons for both keypads - only to find that someone in dev has decided that the everyone else is wrong starting at button 1, and 16 is much more coder friendly number ;) BTW: set up one pad + shift button to use as the 3rd MFD buttons if you only have 2 cougars - just remember to press the shift button.

For some strange reason the "AWACS Request Bogey Dope" line in the control setup does not allow any buttons to be set, just the keystroke. The other radio shortcut commands are fine, and can be assigned to buttons. NO F-18 mods are loaded.

I'm not sure it is related to your issue, but some missions start with Auto Throttle Enabled - so that sometimes messes me up.

I get the impression that the reflected pilot is moving fore & aft when I move myself irl. I'm still not sure why the mirrors seem to be angled to show just the pilot and nothing much else in the default view. Maybe navy pilots liked to do their lipstick on long flights?

Seems to me that some people must be seeing something completely different to me. Perhaps some GFX setting is making what I see worse, screen resolution, Antialiasing, my fov setting? If you think that looks correct - then good luck with that. I for one feel that it would not be a major effort to look at the way the material settings and bitmaps are being applied. This isn't necessarily just a Heatblur thing, but It's been used on modules since the Mustang was released - and is much subtler on that module for example. - just compare the two.

Blinde/Jowen. NP. Just so I'm clear... I really DO like the F14 and the Viggen modules - they are both very immersive - as I like to put it - the only thing missing is the "fart" smell in the cockpit, but that doesn't mean small things can't be improved upon. I do understand that this scratch/crazing thing seems to be an ED thing... that needs updating imho. Dawson - Is the M2000 good to work on? I always thought the MV was a nice A/C - Did line servicing (Nato XServ) in Germany in the late 80's - on Belgian Mirages, My favourite was always the F16 though - nice & easy - no chute to fit - just the slight issue with the Hydrazine power-pack ;)

Jowen: Mirage200 does not have a flat glass windscreen panel. Just curiou to know is the curved windscreen actually made from glass then? I am specifically talking about the glass - not any form of plastic compound. The Mirage V, did have a flat windscreen, & I don't recall that glass being crazed, scratched or gouged. Crazing is sort of an irrelevant term as far as this sim goes - because it doesn't really represent either. There is only one effect, so it doesn't matter what you call it. In any case - the M2000 canopy/screen looks fine in game. Nothing like this. Blinde: I did it for the Spitfire ages ago - since it's the same file in all modules afaik - just renamed, I'm assuming it can be reused, it's just a bit less scratchy than the original. Try this: https://1drv.ms/u/s!AlvGQxoyD0PcwQjJtHYQSMC1rYcT EDIT: Hold on one: that is a dds - but my F14 uses *.bmp. Here is the correct file type: https://1drv.ms/u/s!AlvGQxoyD0PcwQmZeVGif2tiD8Xs If you want a much more toned down version - but still showing crackles/scratches - use this one (You will have to rename it to remove the (2) from the filename). https://1drv.ms/u/s!AlvGQxoyD0PcwQrNLQRE4VKJeaBA Both files are at the same resolution as the original ED texture.

The windscreen is glass - not "glass" - I do know the difference between glass and acrylic/plexiglass/perspex etc. I think some people are conflating windscreen with canopy. I am being specific here, about the windscreen glass, (although I do think some modules have overdone the effect on both). The tiny normal map that is used by most modules to get this effect is too low res and too heavy - just look at it. :( I use a modified version with about 50% of the scratches removed, and it looks a lot better, but even so - should not be on the glass of the windscreen itself at all IMO, but without access to how the materials are set up - I can only edit the normal map. It is possible to do this subtly - just look at the P-51, the A-10C, the MiG-21, the Mirage and Albatross. 17 years on Military a/c line work / maintenance Schlapperklange, so I have sat in a couple of fighters, and some of them were even facing the sun ;) Some of these were newish (at the time), such as F-16s and Jaguar, Tornado, Alpha-Jet, and some pretty old, Lightning, F-104, F-5, F-4f - FGR-2, Mirage V, Buccaneer, Hunter. The only ones that ever looked this bad were in a scrapyard. Dirty and possibly scratched perhaps, but never like this, and not the glass portions. Anyhoo - take it or leave it - it's just an opinion.

Great module - but I really do not like having windscreen glass that looks like it has just been hit by a sledgehammer. Please get rid of it - and tone down the crazing on the canopy perspex if you would be so kind. I can almost live without being able to see out of the heavily crazed perspex, but not windscreen glass. Ta

Cheers chap - I knew it couldn't be that easy :) I shall just have to be patient then. Still have to learn to just fly the thing yet.

ANyhoo - it's early days right now, so nothing is set in stone.

Thanks Alerax. I tried to add HSD HDG & CRS knobs - they work as clickable (if in TACAN Mode), but not if I add these commands in the keytrokes file you provided - I just tried tacking this near the end, and although it appears OK in the GUI, and I can assign buttons or keystrokes to it - it does nothing to the Heading or Course bugs on the HSD. -- Heading knob {pressed = device_commands.HSD_Knob_Heading, cockpit_device_id = devices.HSD, value_pressed = 1.0, value_up = 0, name = _('ALT HSD Heading Correction Inc'), category = _('PDCP')}, {pressed = device_commands.HSD_Knob_Heading, cockpit_device_id = devices.HSD, value_pressed = -1.0, value_up = 0, name = _('ALT HSD Heading Correction Dec'), category = _('PDCP')}, -- Course knob {pressed = device_commands.HSD_Knob_Course, cockpit_device_id = devices.HSD, value_pressed = 1.0, value_up = 0, name = _('ALT HSD Course Correction Inc'), category = _('PDCP')}, {pressed = device_commands.HSD_Knob_Course, cockpit_device_id = devices.HSD, value_pressed = -1.0, value_up = 0, name = _('ALT HSD Course Correction Dec'), category = _('PDCP')}, Any Clues?

Seems to be aligned ok on mine as far as I can tell. Max on the quadrant at the top detent, Full AB at top of range. idle detent position is exact. Cutoff buttons at bottom end. Not 100% sure about Max AB setting - the throttle looks to be at the right place on the quadrant in game, but the nozzles only open to 3.5 not 4. I don't know if that is correct - but they look pretty full open in external view.

I keep an OB on my SSD, and a Release on an HD - both have separate settings in their respective installs of course, and both have their own folders in Saved Games so nothing gets lost. This requires space of course. Some things require the OB. If you want to play with that shiny new release, it will often only be available in OB for the first week or so. EG the MiG-19. Personally, I just use the OB now, and keep the release copy as a backup/reference in case I frig up my configs.

Seems an odd thing to happen, but that doesn't help his situation. Try this thread:- https://forums.eagle.ru/showthread.php?t=211982

I think it's worth pointing out once more that setting your FOV via the zoom axis is only a part of the fix, and ideally, you want the midpoint of your zoom axis if you are using a slider or the warthog "Tension" lever, to be at the midpoint of travel. Before you do that, you need to know what DCS thinks that travel IS. If you just set up your screens and ignore it, then yor range will be so far out that you can only zoom in one direction. Each views.lua has a setting near the start in the Cockpit section :- CameraViewAngleLimits = (20.0000, 140.0000), or similar - which gives a default mid range fov of 80degrees. Change those figures to give a different range. I used settings around 100,165 rather than 20,140 in the example mentioned below. Additionally, your snapviews will probably be zoomed in so far that your nose is up against the dials. Don't use them I hear you say? Maybe not - but DCS does - and that's where the initial FOV comes from afaik. For me, I had to modify the SnapViews ViewAngle setting for every slot Views.lua for each aircraft, most importantly number [13] which is the DefaultView. This defaults to 80 degrees - I had to set it to around 120 to 140 depending on the aircraft (this was on a triple 1920x1080 setup with an extra small monitor for instruments). I also had to tweak the hAngle,vAngle, x,y,z_trans for most of them. Then I fine tuned with the Axis settings in-game. This is such a lot of work if you have lots of modules, that you will really wish that there was a universal setting - or just give up as I have done.

Nope. Still not fixed. Lights/Flares are still flashing on black screen areas. I don't think they really care much about multi monitor issues TBH.