shagrat

River Seine sure got way more polluted and dirty in the last 80 years. And more ship traffic on top... Do you have any photo from 1944?

I've found something interesting: tldr: Voice chat PTT cuts the transmission and "closes" the channel/noise gate/squelch Weekend MP session, was flying an OH-58D Kiowa. Radio noise was present as before, but I have mapped the Voice chat PTT to a rudder pedal brake as a "foot button". So when I accidentally pressed the pedal in flight, the static stopped. I could verify the PTT button a) cuts of any script triggered transmission over the current selected radio and b) closes the channel/noise gate/squelch so the static stops. Before someone asks: We were using Discord for comms between pilots as it's convenient for instructions, testing the mission and talking about what goes wrong. So we don't used DCS Voice chat often at the moment. I'll crosscheck if this is the same in the AH-64D and map VoIP PTT.

Die Christen Eagle II gäbe es auch noch. Klassisches Kunstflug Propeller Flugzeug.

We should wait for the finished product to judge "how it looks" and make assumptions on the "new DCS". Especially if judging of a heavily WIP early access product.

Agreed on most, minus the church and mosque part. A) high towers/minarets double as visible landmarks for orientation, especially close to the ground (Helicopter, Combined Arms). B) in modern conflicts they pose a tactical challenge, as typically ROEs will have them as "no fire zones"/protected areas, that can integrate nicely into mission design and planning etc. But I agree we would benefit from more power plants, dams, military installations.

Unfortunately it's neither a beacon, nor an airfield frequency (at least on the Afghanistan map). It's also not exclusive to VHF, it is also happening with FM radios/transmissions. Again, I suspect this to be related to a script/trigger radio transmission, as it seems to occur only after the first transmission from a unit/trigger... I can't pin it to a specific trigger/frequency, we changed both frequency and transmitting unit, but it makes no difference.

Gefunden: https://forum.dcs.world/topic/336367-29-object-camera-with-position-inheritance-rshftrctrlf2/

LSTRG+F11 - Freie Kamera. Am besten erst Pause drücken, dann positionieren für Screenshot. Im Flug gibt es neuerdings eine Erweiterung der F2-Kamera (probier mal mit den üblichen ALT, L/RSTRG, L/RSHFT...) wo man die Kamera Position speichern kann.

IRL the gunner guiding the AT4 would have a very challenging job to keep the crosshair dead on the small silhouette moving helicopter, even with zoom optics, at 5 km plus... but the AI is way better than any human being with the joystick.

...and an announcement of a new Instant Action Generator that I am not aware, has been talked about, before, from ED. I am stoked to see more on that topic. It's a "News"letter. What do you expect? Made up stories about "exciting news" that never happened?

Actually, we got development pictures, of a third party product and info of a mission editor update. I wasn't even aware they are working on a new Instant Action Generator! It's a newsletter that is scheduled weekly, like the daily roll call... if there's new things in the pipeline (like the new IAG) they tell us, if not there are updates and reminders of things in progress. I personally prefer the weekly status updates, to being left in the dark.

Yeah, needed to do a sanity check on the varUnit, as a continous trigger will check the condition every second and if the unit crashes it won't find said unit... local varUnit = Unit.getByName("00_Player") if varUnit ~= nil then if varUnit:getDrawArgumentValue(86) >0.5 then trigger.action.setUserFlag("DOOR_00",1) else trigger.action.setUserFlag("DOOR_00",0) end end I also did adjust for the fact, you have more than one player. So The script can be executed for individual units Flag ("DOOR_00" and "DOOR_01"). Additonally I eliminated the need to use a second Flag so I added a FLAG "DOOR_00" EQUAL 1 to the conditions using the same flag that is set in the script, and I added a message from a virtual "crew chief" to let the pilot know if the ramp is lowered or raised. Have a look at all the orange triggers in the Script Editor to see what has changed: Here is the MIZ file with the changes: Chinook training mission - RAMP fixed.miz

For whatever reason DCS does not like "Switched Condition" with "Do Script". I changed the Script trigger to "Contineous" and added an else condition to the script. local varUnit = Unit.getByName("CH47player") if varUnit:getDrawArgumentValue(86) >0.5 then trigger.action.setUserFlag("DOOR",1) else trigger.action.setUserFlag("DOOR",0) end Then two separate "switched condition" for the appropriate Flag "DOOR" is 1 (ramp lowered) and Flag "DOOR" is 0 (ramp raised)... But easier to see for yourself. I attach the MIZ file so you can see what exactly I did there. TEST_CH47_RAMP_TRIGGER.miz

Yes, and especially more of the map buildings! That would allow to add "specific target buildings" that actually blend in with the environment. The currently available "static buildings" for any of the middle eastern/afghan environment are absolutely outdated and stick out like a sore thumb. In addition it would be incredible to have at least a couple of the "AI traffic vehicles" available for mission creators to add deliberate "civilian" traffic or simulate VBIEDs that blend into the traffic, until they behave suspicious, etc. ...and just one(!) insurgent model without a weapon in his hand, that allows mission creators to enforce consequences Rules Of Engagements. ED, pretty please?

The default invite link for discord expires after 7 days. You can edit to "never", if you click on the "Edit invite link".

You can simply put the code into a switched condition "do script" trigger and use the Flag is true "DOOR" to do stuff like Message to coalition/group etc. Just reset the flag with a "set flag false" in the trigger, if you need to track multiple uses of the ramp. You only need to add the UNITNAME to the script in the get.unitByName("unitname") part. The moment the ramp is lowered more than half it should trigger the "DOOR" Flag as true.

You can use the Lua Script function "getDrawArgumentValue" to check a model argument. local varUnit = Unit.getByName("theCH-47s unitname here") if varUnit:getDrawArgumentValue(86) > 0.5 then trigger.action.setUserFlag("DOOR", 1) end Now you can use the Flag "DOOR" to trigger things as usual e.g. send messages etc. Reset the Flag by setting it to 0. Not tested, but should work.

Thanks for investing your time into the community. It's so incredibly helpful to get these infos first hand and "unfiltered" and have someone for questions, that come up.

Perfect stereotypical white caucasian males... John from Oklahoma and Bob from Wisconsin. We could argue the underrepresentation of the multicultural society of all kinds of ethnicities that is representative for the modern US, though.

The noise wasn't there a couple updates, ago. Same Mission. So no. It's not a beacon, or issue with something on the map. It typically happens, after a transmission per script is triggered and finished, as if the sender keeps the microphone open. Though it is not related to the squelch settings, from what I could check, so far.

Since some updates a triggered radio transmission will start to produce a static noise on the radio frequency selected, as if the sender doesn't stop transmitting. It is not related to squelch settings. In the AH-64D the noise can't be stopped by pulling the knob (radio to off). Master Volume affects the static noise, but not individual radio volumes. Only if you switch the frequency the static noise stops (so I suspect it is related to the specific frequency used in the trigger).

Can only say for the VPforce Rhino with TelemFFB, as that's what I have. There is no ForceTrim, yet (Emulation of the Centering Spring). What I get is the dampening effect like you would feel if moving the cyclic against the hydraulic fluid. TelemFFB (export of events from DCS) recognizes it as a helicopter and applies effects, like deceleration when hitting the brakes or rotor rumble and ETL.

There is FFB, though it is only the basic stuff. At least with the VPforce Rhino I have the dampening (hydraulic) stays in place and the generic helicopter effects through TelemFFB.

Up to 1.5 tons internal cargo capacity or up to 2 tons external as slingload seems to make a lot of sense to me...

Evtl. die Throttle-Achse(n) auf den/die Schubhebel-Achse(n) gemapped und in der Idle oder Cutoff position? Ich hab das, wenn ich bspw. nach dem Landen, alles ordentlich abschalte und die Throttle auf "Cutoff" stehen habe. Sobald man dann, beim nächsten DCS-Flug in einen Air- oder Hotstart springt, synchronisiert mein Virpil-Throttle die Achsen und die springen auf IDLE, bzw. Cutoff und die Triebwerke gehen aus. Ist man schnell genug, und schiebt die Schubhebel auf 100% ist nur das GPS unaligned (aligned aber innerhalb von ein paar Minuten) aber die Triebwerke kommen zügig und die Generatoren liefern Strom.