Hobbes83

Wow, thanks for your quick response. Well I am a noob when it comes to scripts and so I will have to set triggers for all of them. I bet I will get confused at some point and miss one or more units

Hey everyone! I try to explain my problem I am unable to solve. I am building a mission with different targets. And when a target gets destroyed, a sound shall be played to everyone. That by itself isn't my problem. But I have multiple targets and everytime one of those gets destroyed, the same sound has to be played. I could create a trigger like this: Trigger (Once) => Condition (Unit 1 dead) => play sound This works, but this would mean I would have to create that trigger for every target. And I am sure, there is a solution that goes somewhat like this: Trigger (Once?/Continiusly?) => Condition (Unit 1 dead) or (Unit 2 dead) or (Unit 3 dead).... => play sound Well, with this kind of trigger in type ONCE it will only happens once, whenenever one of the targets under the condition is destroyed. With the trigger type CONTINOUSLY it will play forever again, because one of the units under the condition tab is allways dead. But I need something that triggers again the same action (play sound) when another target gets killed. I tried with flags, but my idea was when one units gets killed, it sets flag und that triggers the sound and resets another flag which will be in the condition list of the first (unit killed) trigger. But than again the condition will also be met as well forever because: one of the units in the list is dead and the trigger is reset. So I am only able to get the event happening once or in an infinite loop. And I cannot come up with an solution other than building dozen of triggers for each unit. I hope someone can help me out with this. THANKS!

Hello everybody! I've been working on a new livery for the A-10CII we want to use in our squadron (don't worry about the color, it's a livery for <profanity>s an giggles ). I've been working on the templates with GIMP, exporteted them and viewed the results in the ModelViewer. After a lot of changes and flawless exports I suddenly had these yellowish rectangles on all templates I had worked on previously. What have I done, what are they and how do I get rid of them? Any help would be appreciated!

Thank you very much! That does work indeed. I allready made a copy of that .lua but just renamed it F-14A but not the full name. But with that, it works! Thanks a lot!!!

Hello everyone! I am using the Streamdeck together with the DCS Interface and the exportscripts. Works fine so far. But I will have to fly the F-14A in a few weeks. So I wanted to create a Profile for the F-14A on my streamdeck as well. But that does not work. It seems, the export scripts only cover th F-14B but not the A!? Is there a solution to this? I don't want to assing keyboard buttons to all the radar stuff and put them onto the streamdeck. Is it possible to use the exportscript for the F-14B also for the F-14A somehow? Thanks for your help!

Update: Ich hab jetzt Nägel mit Köpfen gemacht! Ich habe meinen Rechner formatiert, anschließend die Platten kontrolliert, keine Fehler. Diagnose mit dxdiag war ebenfalls ohne Fehler. Dann Treiber etc. installiert und schließlich DCS wieder installiert. Siehe da, alles läuft wieder! Was auch immer den Fehler verursacht hat, die Lösung war jedenfalls gelinde gesagt: aufwendig. Aber so hab ich mal wieder einen von Grund auf aufgeräumten Rechner, ist ja auch nicht schlecht. Ich danke euch allen für die Hilfe und Ratschläge! Allzeit guten Flug! Danke!

Hallo QuiGon, den DCS Ordner unter gespeicherte Spiele hatte ich auch schon gelöscht und durch DCS einen neuen Anlegen lassen, keine Veränderung. Ich habe festgestellt, dass auch die F-14 Probleme macht und die Instrumente schon nicht richtig dargestellt werden. Auch wenn ich da eine Rakete abfeuer, stürzt DCS ab. Ich wollte daher schon den Titel des Threads hier ändern, aber irgendwie funktioniert das nicht. Der ist ja nun leider ein bisschen irreführend. Jedenfalls lasse ich gerade die Neuinstallation laufen, dauert ja doch ne Weile. Aber heute Abend werde ich weiter testen können... Danke jedenfalls!

Kurzes Update: dxdiag wirft keine Probleme aus hab mit CrystalDiskInfo die betreffende SSD geprüft, keine Fehler Ich versuche es einfach noch mal mit ner Neuinstallation, danach hab ich dann auch keine Idee mehr.

Hallo Urbi, vielen Dank für deinen Hinweis, das werde ich heute Abend gleich mit ausprobieren. Der TEMP und TMP Ordner wird regelmäßig geleert, sollte also nur ein wenig gefüllt sein. Ich habe eine SSD mit 250 GB, auf der ausschließlich DCS installiert ist, daneben liegt noch SRS auf der Platte. Ich weiß jetzt nicht ganz genau, wie voll die ist. Aber mit einigen Fliegerchen und Maps sollte dennoch ausreichend Platz übrig sein. Das Betriebssystem liegt auf einer eigenen 120 GB SSD, der ganze Rest auf einer (3.) SSD bzw. HDD. Danke!

Hallo! Ich habe (mittlerweile mehrere) Reparaturen laufen lassen (über dieses DCS updater tool und auch über Skatezillas GUI), brachte kein Erfolg. Ich habe es neu installiert, auch kein Erfolg. Auch das Löschen der Ordner fxo, metashader und metashader2 habe ich schon probiert, kein Erfolg. Ich habe eine private Nachricht von einem User erhalten, der meinte, ich solle mal meine SSD über s.m.a.r.t. checken, denn seiner Ansicht nach deuten die Fehler in der Log darauf hin, dass dort Dateien nicht gelesen werden könne. Das werde ich heute Abend mal ausprobieren und ggf. auf eine andere SSD installieren...vielleicht liegt's ja daran. Jedenfalls schon mal vielen Dank für eure Tipps, wenn euch noch was einfällt, immer her damit.

Hi, did everything as you suggested, no changes. That's some weird stuff...and I have no idea where it came from. Just did a driver cleaning via Windows Safe Mode and installed the GPU drivers again...nothing. I am running no third party shaders or tweaks. Just a vanilla DCS openbeta install...

Something went terribly wrong. Find attached a screenshot of my F-14. That doesn't look normal...:cry: Everything, that lies in shadows, is pitch black.

So, work done...time for the fun...or not? :( I renamed the saved games folder and let DCS create a new one. After that I set up a tiny mission with a F-18 and a SAM search radar to have something to shoot the HARM at. Same result as yesterday. Tried to launch an AIM9...same thing. I think it does not depend on weapons or aircraft. Anyways, both log are attached as zip files. dcs.log-20191126-184944.zip dcs.log-20191126-184513.zip

Thanks again, will try this tonight. Just have to get this work day done...:thumbup:

Hey thanks for your advice. I maybe shoud have mentioned, that I did uninstall DCS on Sunday and did a new install yesterday. The CTD happened with the old install and happens with the new one as well.

Hello everyone! Since a few days I have a problem with DCS (latest open beta release) crashing to desktop. I noticed some crashes when switching views between my aircraft and enemy units for example. Yesterday I strarted to test some scenarios and usually DCS crashes when firing missiles (yesterday I tested the F-18 with HARM). DCS created a .log-file and it says the following (excerpt): 2019-11-25 20:54:10.139 ERROR DX11BACKEND: semantic 'TEXCOORD0' is not declared in shader 'particlesystem2/smoketrail.fx' 2019-11-25 20:54:14.443 ERROR DX11BACKEND: Failed assert `shader != render::INVALID_HANDLE && technique != render::INVALID_HANDLE` at Projects\render\dx11backend_win8\Source\DX11Renderer.cpp:1047 2019-11-25 20:54:14.443 ERROR DX11BACKEND: Failed assert `this->wantedShader != render::INVALID_HANDLE && this->wantedTechnique != render::INVALID_HANDLE` at Projects\render\dx11backend_win8\Source\DX11Renderer.cpp:1590 I searched for DX11BACKEND and found some threads stating, that the shadow setting might be an issue. So I tried every setting on that with the same result. I attached the log as a .zip because the .log-file is not allowed and the .txt-file is too big...:huh: So if anyone has an idea that would be great. Thanks! dcs.20191125-205643.zip

Hallo zusammen! Ich habe seit ein paar Tagen ein unerfreuliches Problem. DCS openbeta in der aktuellsten Version produziert immer wieder Programmabstürze. Zuletzt passierte es immer in genau dem Moment, in dem ich eine HARM mit der F-18 abfeuern wollte. Es ist aber auch schon passiert, wenn ich die Sichten durchgeschaltet habe. Ich habe die Grafiktreiber (NVIDIA RTX 2070) runter geschmissen und neu installiert und zuletzt DCS World selbst. DCS ist auf einer SSD installiert, auf der auch nur DCS drauf ist. Der Prozessor ist ein i7-4770k mit 4,0 Ghz (übertaktet) und 32 GB RAM sind eingebaut. Ich habe irgendwo gelesen, dass die Schatten ggf. das Problem verursachen könnten, habe alle Schatteneinstellungen durchprobiert, ohne Änderung. In der LOG-Datei taucht folgender Text auf: 2019-11-25 20:54:10.139 ERROR DX11BACKEND: semantic 'TEXCOORD0' is not declared in shader 'particlesystem2/smoketrail.fx' und 2019-11-25 20:54:14.443 ERROR DX11BACKEND: Failed assert `shader != render::INVALID_HANDLE && technique != render::INVALID_HANDLE` at Projects\render\dx11backend_win8\Source\DX11Renderer.cpp:1047 2019-11-25 20:54:14.443 ERROR DX11BACKEND: Failed assert `this->wantedShader != render::INVALID_HANDLE && this->wantedTechnique != render::INVALID_HANDLE` at Projects\render\dx11backend_win8\Source\DX11Renderer.cpp:1590 Ich habe die Log-Datei mal als .rar Archiv angehangen (.log-Format ist nicht zulässig und als .txt war sie zu groß:huh:) Nun ja, vielleicht hat jemand von euch ein Idee? Ich bin für jeden Hinweis dankbar! dcs.20191125-205643.rar

I posted the queation on reddit as well and got the following answer from Cobra: "This was an issue pre-launch that we worked with ED to fix (it's in the core engine). It was corrected, but obviously there still seem to be issues :( We'll prod this issue a bit more and fix it." So we will have to wait for a fix obviously.

First of all thank you Heatblur! It's been a fantastaic week of flying since the F-14 came out. I've been flying this beauty every evening together with my dad since last week and we highly enjoy learning to fly and use the F-14 properly. So thanks a lot. So while flying we discovered a radio problem. Since my dad is hosting our server, only he is able to use the radios to call tower or tanker. We hoped it would be possible that I as a RIO am able to contact the tanker while my dad concentrates on flying which is highly needed whil trying A2A refueling. ???? But I do not get the tanker to respond. Same thing when I am flying as pilot, I cannot contact tanker or tower but my dad as RIO can. It all switches around when I am hosting a MP-server. Than I can use all the radios but my dad cannot. Is that a known issue? Are we missing something or is it just not implemented yet? Thx for every help!

Radios in Multiplayer/Multicrew? I may be a bit confused right now. But my RIO and I are flying on multiplayer and my RIO tries to contact a tanker. But with now success. Is it a bug or are we doing something wrong? We both tuned in the tanker frequency on each radio. I as a pilot and Host of the server can communicate with the tanker and my RIO can hear the answer from the tanker. But when he tries to contact the tanker (e. g. ready for contact), no answer and I cannot hear him speaking on the radios (not SRS, we are using TeamSpeak while flying, but I mean the DCS generated radio voice). Any ideas? Are we doing something wrong or is it just not working right now? Thx

@WildBillKelsoe The mission is for the Persian Gulf map. But you found the mistake. It appears that they can only attack sea targets. Since this is only for the "effect" at the beginning of the mission I put some enemy ships in there and my ships do start to attack them. So thank you very much, good to know. Have a good one.

Mission is attached, thanks for your help!!! Blau gegen Rot.miz

Hello everyone! I am building a small mission for the Harrier. I want to start from a carrier surrounded by some ships. These ships (I downloaded the Burke mod for that purpose) shall attack some targets on land. But they don't...neither the stock Normandy nor the Burke. I gave them the task to attack the target units. They are all named and so on and the editor shows the line between my ships and the targets. But they just do not attack. Am I missing something? Do I need Combined Arms to let ships attack targets on land? Can someone help please?

Das war der entscheidende Hinweis. Warum auch immer, ich konnte speichern und neue Missionen mit Sounds erstellen wie ich wollte, in der miz-Datei tauchen die Sounds jedenfalls nicht auf. Ich habe sie daher in das Archiv gebastelt und das dann wieder in die miz-Datei umgewandelt und siehe da, es läuft. Vielen Dank euch allen, das hat super und schnell geklappt! :thumbup:

P.S. hab die Mission im Editor noch mal geöffnet und neu gespeichert, dann wieder in ne rar umgewandelt, gleicher Inhalt...