Flagrum

Maybe ED wants to consider making a changelog mandatory for 1...2...3rd party devs. I.e. when they upload their changes to ED's servers, always an (updated) "changelog.txt" must be present as part of the distribution files of a module. That would also help to collect the changes for the compiled changelog posting and keeps it consistent with the content of a patch. (yes, if someone does not keeps their changelog.txt up to date, this will not help either. But that is then a different problem.)

*bump* ... maybe this can be fixed together with the oter, general rearming issues? Please? :-)

The question should be, "since when are they being removed" :-D According to wikipedia, the Celts began to build them 2000 years ago, as a way to fence in their property. Since 19th/20th century, more and more are removed - probably as they make modern farming difficult. I also read somewhere (can't remember where) that they shall help to keep the soil in place. Otherwise the costal winds would erode the flat land into the atlantic eventually. Not sure, if this function was intentional (by the celts?) or just a positive coincidence.

My understanding is, a NAV fix overwrites what the aircraft thinks where it is at. The TERNAV only adjusts the nav polygon, but is unable to overwrite the pilot decision. Lets say, you perform a nav fix on a land mark. The nav polygon adjusts accordingly. But you were off by a few dozent or so meters - this will be detected (after some time) by the TERNAV and further adjusts the nav polygon. TERNAV will recognize the height profile around the aircraft, if the nav fix was only a bit off. But if your nav fix was completely off, the TERNAV data will be completely different from the real situation. TERNAV then goes into one of those reduced-precission modes. TERNAV is like a microscope. If you look at dirt with a microscope, would you be able to tell where on the crop field you are standing? :-)

Wait ... did I understand you right, you bought a license for the F5 module, but refunded it. And now you wonder that you can not use the F5 anymore?

The sound quality is unbearable. It took me a while to realise that you are speaking german (I am german as well) - I can barely understand anything, maybe only 20% of what you are saying. Seriously, get a better microphone ...

That was interesting - thanks! Quite interesting to see how the markers are often aligned with the shadow of a forrest: the sun is in front of the a/c and the area before (flat ground) and after (the forrest itself, the treetops) the shadow are probably heated by the sun but the shadow is cooler. Also interesting - although this could just be an effect of using the camera to capture the HUD? - is that the V markers seem to be drawn a bit over the actual hot spot. Which would make some sense at least - probably to not obscure/cover the actual point.

Iirc, black or grey text in the radio menu means "Radio Assists = on". So DCS is telling you if the receiver is able to receive a transmission, i.e. if the choosen radio is set up for the correct frequency. So it seems that the wingman is theoretically able to hear you, but you are using the wrong freq. If you modified a mission yourself to fly it with the Viggen, you should double check the radio presets in the mission editor.

It might be a far fetched guess, but maybe this is the intent of the procedure ... The thing is, StarForce is not just "a DRM". It is a tool box that allows a software vendor to implement several kinds of DRM checks. StarForce can be configured in different ways and the program code has to be adopted accordingly as well. For example, one developer can decide to configure SF that way that the software simply cease to work. Or he decides to only disable certain features. Or that it should run for a limited time. Etc. In the end, there are many aspects that require developer decisions that can affect how intrusive or unintrusive a DRM like SF will behave. Maybe LNS made some unlucky decisions - which M3 now tries to remedy.

Afaik the different fuze settings or other details of the fuzes are only for "the looks". differences of specific fuze types are not modelled in DCS right now. Everything is either an impact fuze with no delay or, in some cases, a few(!) seconds(!!) delay.

Could a fix for this get some priority, pretty please? That would tremendously help with training, etc. due to the Viggens "you have ONE attempt"-nature of it's weapon deployment philosophy ... :-D

How does that hotspot detector work in reality? It compares the temperature with the surroundings and if the difference is greater x, then it is assumed a hot spot? How big is x? And can it be changed by the pilot? What I am thinking about is, how does this feature behave in different ambient temperatures? I.e. summer in Nevada vs. winter in Caucasus? Oh, and +1 for the idea to throw in some random hot spots!

Well, curves and FFB don't go well together in DCS. This is not Huey specific, afaik. It seems, the curves are only applied on the way into DCS, but not the other way, out to the FFB motors. Like, you deflect the joystick to 50%, DCS applies the curves, and makes for example 25% of it. In game, the cyclic now defects to 25%. Now you trim. DCS sees that you trimmed at 25% and tells that to the FFB motors. Your joystick now deflects (from 50%) to 25%. And now it all starts over: DCS applies the curves to your 25%, makes something else of it, etc. ... BUT ... this thread was originally about central trimmer mode, i.e. non-FFB sticks ...?

https://forums.eagle.ru/showthread.php?t=159288

Do you have any curves configured?

No.

I am not sure what your question exactly is ... Guard frequency is just a VHF or UHF frequency that is internationally agreed upon to be used only in case of emergencies. But technically they are no different from any other frequency. The guard channel feature of radios is just an aid to enable the pilot to listen to the guard frequency and any other freq. that is tuned in at the same time. So, for DCE, there is (voice) communication on the guard frequency ... if there is a pilot in distress - be that a human pilot in case of MP, or programmed by the mission designer in case of AI.

+1 edit: but I'd rather call it a bug report than a feature request... ^^

Afaik: UH-1 ... U H ... englisch Ju Eitsch ... JuEi ... Huey :smartass:

That is as easy to answer as it is subjective .... hands down Huey and Mi-8!

Great efford! Sadly, I have to find the time to dive into MOOSE, yet, but it is looking really sophisticated. So this leaves me with a more general question: how customizable are all the communication messages - i.e. from the command center or the task dispatchers? Two points I have in mind here in particular: 1. does the comms utilize the aircraft's radios or is it all done by MESSAGE TO xxx? I'd love to see missions with "realistic" comms reqirements - like, if you have dialled in the wrong frequency, you won't hear the task dispatcher and thus you will be of no help to the war ... ;-) The other point is, aside from the debugging output, the tasking messages look somewhat "technical". Efficient, but maybe not too realistic in terms of how the real communication would go. Can the wording of those messages be customized in some way?

How it Works: Mi-8 Fuel System :drink: How it Works: Mi-8 Electrical System :idea: How it Works: Mi-8 Flight Controls :joystick: How it Works: Mi-8 Hydraulic System :Flush: How it Works: Mi-8 Ice Protection System :cold: How it Works: Mi-8 Fire Protection System :furious: (Maybe a Mod might want to move those threads here to this forum section?)

One summer, back in the 80ies, I was riding my bicycle to get to somewhere. By bike was the only way to get anywhere - as a kid, living somewhat out in the country side of germany (not too far away from Gütersloh RAF base). Back then, not one day passed without you seeing and hearing the jets practicing low(ish) level flights. After the cold war, these now seem to have disappeared completely ... But anyhow, low level flight was permitted, iirc, down to 300 meters AGL. Maybe not everywhere, but certainly not lower. Germany is densely populated area. So I was riding along, minding my own business and suddenly vVVROOOOOOOOAAAAAAAMRRRsshhhhhhh O.M.*.G. I almost fell off my bike, heart pounding like a sledge hammer. I didn't see it coming, I didn't hear it coming. I only noticed the jet - I think it was a F-4 as they were common these days - as it was already right above me. 300 meters? I don't know but I could smell the burnt kerosene (somewhat similar to shoe polish?) and it felt more like 100 meters. :D

Ragnar, you might want to talk to BigNewy. It is suspected that this might be a general DCS World problem as several other aircraft seem to suffer from similar problems. BigNewy is collecting infos and trying to reproduce the problem to work with ED on this issue.

Why not?