ams999

It works for me, thank you Esac_mirmidon! Also, a single file, 85kb, is all that is needed and it hasn't been fixed in months? Unbelievable...

I also prefer 1.18 to 1.19, especially the 'erosion lines' seem more numerous yet more subtle in 1.18 and rather coarse in 1.19

Ja, hat er.

Thank you, finally I can read the gauges at a glance without switching the lights on... :)

It works, it's just not changed on the bracket anymore... https://forums.eagle.ru/showthread.php?t=224084 which doesn't make it much better as you can't see the altitude where the antenna points...

As a work-around, yes. However, I would prefer an offset setting like for the Ka-50 HMD in the special settings. I have the default view a few degrees down, too, to see the DDIs a bit.

Have the same, hot from parking at Gudauta, so it's not the cold start-up. Going to test air start.

A one-for-all NATO tanker with several refueling spots would be great!

I really like the Gaz Minigun and enjoy flying around in it but I do wish for two things: 1. Make aiming similar to the door guns in the Huey, where the gun shoots in the middle of the screen so you can zoom in and still hit stuff (especially when pressing right_shift-t). In the Gaz, it shoots anywhere but where I look so I always have to walk in targets. Unlike the Huey it actually has a sight installed but I can't use it. 2. AI for the minigun like in the Huey but I doubt that will come, unfortunately...

I would like to suggest a blue faction with Russian modules (com language English) as an equivalent to the red side AUSAF to make it easier to place same module dogfights in the ME (Su-33 at the moment only either Russian or AUSAF).

I simply assume that this is a bug since there still is the 'Hellenic Air Force Ghost' skin for the Su-33. Sometimes, it's nice to place Russian modules on blue side, however, now the Su-33 is only available for Russia and AUSAF which usually are red side. So far, I could place Greek Su-33 and -27s but that option is gone. Is that on purpose? I know I could mod some files to allow those for other countries but so far it worked without.

Although I appreciate the intend of providing presets for certain input devices - why are those forced on the customers? Why not make it optional, e.g. by putting them on the website and say: 'we are providing presets for these devices, if you wish to use them please download for the appropriate devices and import the profiles into DCS the following way...' Why ruin the experience for people who do not wish to use presets as they have assigned the bindings as they saw fit for themselves? Why force them to rebind, possibly again in the future as changes may be made? The only profile I would be interested in is the Warthog profile for the A-10C as it translates pretty much one-to-one. All other preset profiles can stay very well off my PC as I will do that myself. Preferably *once*.

I watched the track now. When recording and watching tracks I always disable any mods I have as I found that mods (for whatever reasons) can muck up track recording and playback... Anyway, my observations: - unfortunately, you don't show the autopilot switch at all times, so it's hard to guess when you switch it to altitude hold - however, I see it disengaged when you switch on the UV lights, then you show the VSI with the climb rate (circling you mouse pointer) and shortly afterwards I see the switch on altitude hold - during that time, the VSI consistently shows a climb rate of at least 1 hm/min, mostly a bit over 2 hm/min - from my experience, the autopilot won't engage altitude hold at this rate even if you throw the switch to engaged, the climb rate is too high, it won't bring you down to 0 hm/min - it has to be within +/- 0.5 hm/min when engaging, then it will level you to 0 hm/min - also, if you are on altitude hold and it is on 0 hm/min and you pull or push and force it beyond a certain climb or descend rate, often it won't return to 0 hm/min but disengage - in that case you have to flip the switch back to neutral, go between +/- 0.5 hm/min and reengage I think this is the desired behavior and in your track you are not within desired limits to successfully engage altitude hold. This should not only go for the Mistral but all Gazelle versions. Additionally, Chuck's guide mentions that the autopilot will disengage when below 120 km/h. At my test now I could go down to 90 km/h before it warned and then disengaged.

Just tried the Gazelle Mistral, autopilot works as intended for me.

Hi Devrim, thank you very much for your phantastic work! I really appreciate the English cockpits, not only for the Gazelle but also for the other modules you provide! If you don't mind, I have two points I'd like to make: 1: Maybe it is known already: the Gazelle cockpits also work from the saved games folder as you provide the description.lua for the cockpits - just did that so I don't have to disable them for updates, so Thanks again! 2: regarding the size of this mod: a) I have copied all files to the Cockpit_SA342M/English folder and deleted all *.dds files in the L, Minigun, and Mistral folders. b) in those folders (for L, Minigun, and Mistral) I modified the description.lua to look for the *.dds files in the M folder by adding to each appropriate line '../../Cockpit_SA342M/English/' I have attached the description.lua for the L-Version as an example. This way, you only need one set of *.dds files in the M folder, this makes the mod smaller. However, should the M folder get deleted, all four English cockpits won't work. Maybe this helps to keep the mod smaller - Thanks again!

When entering the 'airspace' (think an imaginary cube with the top edges being the tops of the minarets) of the Sheikh Zayed Grand Mosque, e.g. when trying to land there, I get a large drop in FPS. Hovering just slightly above this airspace, everything is normal.

And yes, I realize that means that people would put arresting cables on the top of Mt. Elbrus to land their F/A-18C - so what :) The novelty will wear off eventually and I would find arresting gear helpful in general...

I'm still in favor of arresting systems on runways ;) Maybe even better, make them placeable in the Mission Editor - that way, ED doesn't have to equip all the appropriate airfields, have all the discussions about which airfields should and should not have them and we have the chance to have expeditionary systems for landing aircraft on short or temporary runways ;) http://www.boeing.com/commercial/aeromagazine/aero_13/runway_story.html https://en.wikipedia.org/wiki/Arresting_gear#Land-based_systems

I think we are just talking past each other - never mind.

No it doesn't for the Spitfire but it works for other modules given the correct description.lua in a cockpit_module folder (e.g. SavedGames/DCSworld/Liveries/Cockpit_P-51D/) I hope somebody finds/exports a newer description.lua so we can make it work (the extractor always crashes for me).

Has anyone found the right syntax for the description.lua yet so one could use the files from the saved games folder? SpitfireIX_CPT_GLASS_DIFF.dds SpitfireIX_CPT_GLASS_DIFF_FILTR.dds SpitfireIX_CPT_GLASS_DIFF_RoughMet.dds

Yeah, not really sure what the difference is supposed to be, either. One difference I *did* notice is that the flat/military skins are shinier now and the shiny skins less than before. Don't know if that is a consequence of the change in glass transparency - otherwise, I really don't see the relevance why this was changed - of all things that need fixing this was unnecessary...

Still there for me.

Thank you! That was exactly what I was looking for! Was always wondering why I couldn't use my throttle for this...

From what I've seen so far it happens when you are in/get into a rainy area.