shagrat

Du hast vermutlich den falschen Installationspfad ausgewählt. Du musst den zweiten Punkt (DCS World) anwählen, dann den Pfad zur Standalone Installation eintragen. Vermutlich C:\Programme\Eagle Dynamics\DCS World oder entsprechend da, wo du die Standalone installiert hast.

Mega 80er-Vibes! ..."Das Allerschönste was Füsse tun können ist, Tanzen!"

Kleine Ergänzung zum Config/Input/Joystick: die .diff.lua Dateien lassen sich im Device configuration Menü je Gerät importieren. Im Ordner C:/Program Files/Eagle Dynamics/DCS World/Docs/ (...oder wo sonst du DCS World installiert hast), gibt es eine extra Anleitung zum Device Configuration Menu (allerdings nur auf Englisch). Oben beim Gerätenamen das Kontextmenü öffnen und Import wählen, dann unbedingt darauf achten in Backup Config Verzeichnis den richtigen Ordner für das ausgewählte Modul zu gehen, und die entsprechende Datei bspw. "TM HOTAS Warthog Throttle <wilde Device ID>.diff.lua" für den Warthog Throttle auswählen. Solange die Namen der Buttons passen, sollte alles passen. Virpil Devices können individuelle Button Zuordnungen haben, weswegen du evtl. nicht einfach eine .diff.lua eines anderen Virpil Nutzers importieren kannst.

Interestingly, I am glad to finally have the fixes rolled out, accidentally, or not. As long as it doesn't break a lot of important features, I am happy to enjoy the glimpse at the work done and just patiently wait for your finalization. Please consider to not roll back, unless there are really critical bugs introduced through the update now. I can only speak for myself, but I can certainly live with a month or two in an intermediate state, like in any early access phase, we are quite used to.

The thing is, then you unnecessarily removed all files of the map that were not changed by the update and had to download the whole(!) map, again. With map sizes growing, this means you have to juggle a lot of deinstalling and reinstalling unnecessary. It does make sense to deactivate and remove a map you don't play for a longer time, but to just remove it, to reduce the update size, it's way more efficient to have multiple (smaller) parts, with just the changed files, that you can individually download and unpack/install.

Automation requires thorough testing under every conceivable scenario, so only the scenario nobody thought of, breaks the automation and causes issues. I would rather use a manual selection process, that you can troubleshoot/adapt, if you encounter issues. You may select all parts and it works fine, but if you encounter an issue, with hardlinks, or redirected folder, or cosmic radiation, you can try again part by part...

@joker62 Yeah, I think installing only one part of the update (core) without updating the map etc. may not be possible. The idea is to be able to download, say a 20-30GB Core update, decompress and install, download a map update of 50 GB for a map you own, decompress and install, and so on. This way we could reduce the space required for download and installation, as after each part the installer can clean up and delete the temporary files and download.

Actually the Installer checks the checksum of files installed, already, so it downloads only what's needed. Also, it is about splitting the 150 GB plus downloads into smaller chunks, especially, as there's a need for temporary decompression of the files, before they can be copied/installed. For the install location manager, I suggest to open another wishlist post, as it is a separate thing, but a good idea, as well. Both concepts can work in parallel and both have their benefits.

Done. https://forum.dcs.world/topic/361350-split-update-into-multiple-downloads-for-core-maps-aircraft-and-campaign/

Split larger Updates into parts, as in: Part I - Core Game Updates, Part II - Kola Map Update, Part III - Syria Map Update, Part IV - Aircraft Updates, Part V - Campaign Updates. So you can individually select, one or more, and then download, decompress and install, one at a time, or all at once. This can help to manage disk space during for download, decompression and installation, if you don't have enough disk space.

He meant to split the Update into parts, as in: Part I - Core Game Updates, Part II - Kola Map Update, Part III - Syria Map Update, Part IV - Aircraft Updates, Part V - Campaign Updates. That you can individually select, one or more, and then download, decompress and install, one at a time, or all at once, if you have enough disk space. Actually, I think this is a good idea!

What is depicted on page 376 and 377 in the A-10C II Manual, then? To me post designate symbology looks pretty much exactly how the CCRP symbology looks, with the exact same cues? Where did I go wrong? I assumed CR modes are to allow attacking a target below your nose, after acquisition in CCIP. And the 5 mil vs 3/9 mode is about the accuracy of the drop? Didn't think about anything F-16, especially not "dive toss" with an A-10C It has more similarities with the AV-8B's CCIP to AUTO conversion... which is not a dive toss mode, as well. EDIT I read a little bit. From the A-10C II Manual (P. 375): (...)"3/9 Release and 5 Mil Consent to Release (CR) Bombing Modes Both the 3/9 and 5 Mil options use what is termed Consent to Release (CR). The only difference between the two is how accurately you must have the pipper pass through the solution cue to release the bomb. The advantage of using CR is that you may designate a target point and then pull-up and release the bomb in a non-diving attack. This gives you the option of wings-level bombing and toss bombing depending on the attitude of the aircraft at weapon release."(...)

It may help to understand, what CCIP CR is useful for. If the pilot needs to acquire the target visually (does not know the exact location), but doesn't want to dive too low (risk of AAA or restricting terrain) CCIP CR allows to dive into, a valley surrounded by high mountains, for example and acquire the target in CCIP, put the pipper on top and then press and hold the pickle button. This gives CR symbology (Steering Line) and now the pilot can pull out of the dive (no longer seeing the target) and fly the TVV on the Steering Line as he would in CCRP and avoid the mountains or pulling up too hard (slowing down). So as Yurgon explained above, CCIP CR is a separate mode from CCIP and CCRP. CCRP only works with Consent to Release, whereas CCIP CR is a "specific submode" combining CCIP's visual target acquisition with switching to what is basically CCRP, on the fly.

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