VpR81

Lad Dir mal Cinebench R20 (das ist ein CPU Benchmark) runter, lass das mal drüber laufen und schreib dir die Punktzahl auf. Dann nochmal nach dem Übertakten, dann siehst Du sofort ob es was gebracht hat. Vielleicht noch CoreTemp runterladen um die Temperatur präzise auszulesen, aber bei cinebench brauch man das nicht unbedingt. Bei Prime95 dann schon. Bei mir hat es in DCS definitiv was gebracht, wieviel genau kann ich dir allerdings nicht mehr sagen. Erstens ists lange her und zweitens war ich da noch in 2D unterwegs. Und den Leistungszuwachs in 2D kann man mit dem in VR nur schwer vergleichen. Deine Kühlung ist auf jeden Fall OC-geeignet. Vermutlich. Die PD (und die frisst wohl ganz ordentlich) ist mir gestern sofort ins Auge gestochen, habe aber gerade in DCS gesehen, dass ich Heat Blur und Bloom Effect abgeschaltet habe was bei dir beides aktiviert ist. VR ist halt sehr subjektiv und wie du bereits gesagt hast, manche können mit Kompromissen leben die für andere wiederum ein no-go sind. Meine Einstellungen, ich hoffe man kann die DCS Screenshots einigermaßen lesen. Ich wollte noch einen Screenshot auf nem belebten Supercarrier machen, aber leider nimmt er das fpsVR Overlay nicht mit auf. Interessant ist allerdings, das DCS bei mir 17GB VRAM belegt. Cinebench gibt immer den Standard-Takt an, meine CPU ist auf 4.2 GHz übertaktet mit 1,169v Kernspannung. Luftgekühlt, Temperaturen in Prime95 liegen be etwa 80°C. Da ist noch Raum nach oben, aber vorher will ich mir endlich mal ne WaKü zulegen. Mein System zum Vergleich: I7 6800K @4.2 GHz MSI Gaming 7 X99 LGA 2011-3 64GB RAM Quad-Channel ( 8 x 8GB ) @3000 MHz MSI Suprim RTX 3090 DCS auf 2TB M.2 SSD installiert (keine Ahnung ob das wirklich was bringt)

Hmm... also ich vermute einfach mal, dass dein System (vielleicht bis auf die Grafikkarte) im Gro leistungsstärker ist als meines (Ist halt schon ein paar Jahre alt). Ich habe allerdings höhere Grafikeinstellungen (z.B. Sichtweite hoch, alle Texturen hoch) in DCS, von der PD mal abgesehen, und so wie es sich liest was du schreibst, sind meine FPS aber besser. Finde ich komisch, da ich mir nicht vorstellen kann, dass die GraKa bei DCS VR so viel ausmacht. Trotzdem sollte ich vielleicht doch mal ne höhere PD und niedrigere SteamVR Auflösung ausprobieren. Einen Test ist das auf jeden Fall wert. Wenn DCS in VR für dich flüssig läuft brauchst Du deine CPU nicht unbedingt übertakten, aber wenn dann würde ich immer manuell übertakten und die Finger von diesen dubiosen, voreingestellten Übertaktungsprofilen der Mainboard-Hersteller lassen. Was dabei raus kommen kann, hast Du ja jetzt selbst erlebt. Vor allem die automatische Anpassung der Kernspannung ist mir dabei nicht so ganz geheuer, darüber will ich beim Übertakten selbst die Kontrolle haben. Vielleicht gehts aber auch nur mir so...

Was mir an deinen Einstellungen aufgefallen ist, dass du die Pixeldichte in DCS (1.3) und die Auflösung in SteamVR verändert hast. Ich habe mich tagelang durch unzählige Threads zur VR optimierung gelesen und es scheint allgmeiner Konsens zu sein, dass man genau das eben nicht machen soll (frag mich nicht warum, als ich es gelesen habe klang es logisch) und nur einen der beiden Werte verändern sollte. Setz doch mal PD in DCS auf 1.0 und gleiche das dann mit einer etwas höheren Auflösung in SteamVR aus, vielleicht sind deine FPS dann etwas besser.

Sir, you got it spot on! Renaming the files / loading a dummy file and save the mission did the trick. Thank you very much for your help and the fast response! Cheers

Hello everyone, I hope somene can help me with this. I recently discovered a nice text to speech website with relative natural voices and started to implement voice overs into my missions (via "sound to group"). I recorded a view voice overs and implemented the .wav files into a few missions. I quickly realised .wav files to be much too large (some missions increased to 20MB+) so i converted the soundfiles into .ogg format. My issue is, that everything worked perfectly with .wav files but with the .ogg files some voice overs aren't played, already in the very first mission i converted the soundfiles to .ogg format. They work fine when test-played in the mission editor, but somehow aren't activated in-game (the related text message gets activated though). I've tried a couple of things, like splitting triggers to have only one sound file played per trigger, or switching from "sound to group" to "sound to country/coalition" and nothing helped. I'm pretty sure i'm doing something wrong and became blind for my own mistakes, but i cannot figure out what exactly it is. I just hope the .miz file is not corrupted. The specific mission is attached. The radio voice overs wich aren't activated are easy to ID, as there is a text message displayed in tandem. One of the sounds not beeing activated is a short (about 90 seconds) music theme that should be played as soon as you get the order to abort the mission and intercept the iranian fighters. The trigger is named " Activate Interceptors 1C". Hope this makes it easier to find in the trigger list. The mission is a very early one wich is just in the process of overhauling (new briefing and kneeboard images, voice overs etc.) and i had to remove some images in order to attach it as the .miz file was larger than 5MB, so pls don't judge me on it's overall state Hornet/PG is needed for testing. Thank you guys in advance, Cheers Meet and Greet.miz

Die Artillerie fängt nicht sofort an zu feuern, sondern fängt um 6:01:00 damit an Feuerbereitschaft herzustellen und feuert dann los. Das ganze dauert aber etwas, sie wird nicht um Punkt 6:01 Uhr anfangen zu feuern. Außerdem hast du den Befehl "fire at point" bei WP1 gesetzt. D.h. die Einheit muss sich erstmal zu Wegpunkt 1 bewegen, halten, Feuerbereitschaft herstellen und dann feuern. Funktioniert einwandfrei, so wie Du es gesetzt hast. Nur eben nicht so wie Du es Dir wahrscheinlich gedacht hast Die DCS Artillerie feuert m.W.n. auch nicht aus der Bewegung, sondern muss dazu anhalten. Wenn Du möchtest, dass sie bei Wegpunkt 0 feuert, musst Du den Befehl "fire at point" bei WP 0 setzen. "Tasks" haben vorrang vor Wegpunkten , d.h. sie wird dann erst feuern und danach zu WP 1 verlegen.

Got all three, Warthog, WarBRD and T50CM2 base. The Warthog base served me absolutely great for several years, but is catching dust since i switched to Virpil a year ago. Still using the Warthog grip on the WarBRD base though. T50CM2 and WarBRD base do have different cam/spring designs. The T50 has single cams (one per axis) while the WarBRD has mirrored cams (two per axis) wich imo is, from the mechanical point of view, the better design. However, i find the cams and the springs on the T50 easier to exchange but this maybe just me. Both are definately worth the higher price. If your wallet allows it, get a WarBRD base. I'd also recommend getting a TM Warthog/Hornet grip over the Virpil grips, but that's just personal preference.

Don't think this is going to happen anytime soon. I don't want to push you in any direction. People experience VR very different. I.e. i do have zero issues playing with my G2 set to 60Hz to get smoother gameplay, i don't see any flickering nor do i get sick. Very different with one of my friends, he is more sensitive to that and can't play with 60Hz as he starts to feel sick after a couple of minutes due to he recognises the displays flickering. I think your system can handle VR, it's just that you would propably need to sacrifice some eye-candy (i.e. lower the resolution of the VR headset, lower visual range, textures etc.) to get decent fps. People for instance, have very different sweet spots regarding the resolution and fps so it is very hard to tell, if you would like the VR experience you'd get with it. And again, overclocking your CPU will definately help with VR wich you should realy consider since you do have a decent cooling. It's not that difficult and you can hardly break something nowadays. Cheers

Do you already have a headset? Nonetheless you should consider overclocking your CPU for VR if your cooling allows it. If not, get a AiO liquid cooling and then oc. Same for your RAM. Also VRAM helps a lot with VR so you might lower your graphic settings a bit with that 3070. A helpful tool for VR is fpsVR wich i highly recommend. It is about 10€ on steam iirc. Besides that, i don't think there is anything you would desperately need to enjoy VR. My specs for comparison: I7 6800K @ 4.2 GHz (air cooled) 64 GB Quad-Channel (8 x 8 GB) @ 3.000 MHz MSI Gaming X99 LGA 2011-3 MSI RTX 3090 I followed Speed-of-heats ( and some others) setting advise and adjusted Steam SS a bit and get 45-55fps with the Reverb G2. Depending on map and scenery. Not perfect, but always good playable for me even in MP and/or low level flight and definately enough to be unable to go back to a flat screen. No shader mods installed btw. Cheers

Kann ich mir eigentlich nicht vorstellen. Bei deinem Pedalset ist jedes Pedal eine separate Achse, in DCS gibt es m.W.n. nur eine Ruder-Achse und keine separat belegbaren Achsen für Ruder links und Ruder rechts. Ruder rechts/links geht, soweit ich weiß, nur über Tastaturbefehle oder DX-Buttons aber nicht über analoge Achsen. Einzelne Joysticks für unter hundert Euro bekommt man schon was einigermaßen brauchbares, wie z.B. den bereits genannten T16000. Der Stick einzeln kostet knappe 70€. Da hättest Du eine Z-Achse für die Ruder und eine weitere Achse für den Schub am Stick. Dann kannst Du DCS schon richtig nutzen während Du auf Schubregler und Pedale sparst. Aber ein komplettes HOTAS für unter hundert Euro? Da bekommt man m.M.n. nur Schrott an dem man nicht lange Spaß hat. Wie die anderen bereits geschrieben haben, wirst du wohl etwa 200€ ausgeben müssen wenn du was einigermaßen brauchbares willst. Grundsätzlich würde ich im mittleren Preisbereich noch CH Products empfehlen. Sind zwar noch Potis verbaut und keine Hallsensoren, aber die kann man einzeln nachkaufen und sind leicht auszutauschen. Leider sind da aber die Preise inzwischen so weit gestiegen, dass man auch gleich nen Warthog kaufen kann. Vielleicht mal auf Ebay nach gebrauchten Sachen von CH Ausschau halten. Unbedingt darauf achten, dass es die USB Ausführung ist.

Nice to hear, looking forward to play through your campaign a second time then. Ah you're right, i missed the Mi-8 beeing 2 separate groups wich is indeed difficult to manage by trigger. Glad you already have a promising script on the way.

Keep on practice, AAR is realy satisfying and once you're familiar with it, it's pretty easy as well. Keep your eyes on the tanker instead of the drogue. When close/connected to the basket move your stick only half as much as you think you'd need to. Decrease throttle as soon as you register acceleration and vice versa. Sounds weird, but works. Once you mastered it, stay trained and do it regulary to maintain your skill.

Afaik you cannot have both stable and OB installed via steam. The only thing you can do is to switch via mouse click between stable and OB within steam. The point is, Steam does not change the folder name after switching to OB and since you always have to install stable and then switch to OB, the path will never be openbeta in steam as it does not reinstall DCS when switching to OB, but only exchange specific files.

Bessere Downloadgeschwindigkeit, Rückgaberecht, DCS wird (zumindest im SP) auch weiter funktionieren sollte ED eines Tages insolvent gehen und seine Server abschalten weil die Autorisierung über die Steam Server und nicht über die ED Server läuft.

I've just played Mission 02 and realy like your campaign so far. If the missions maintain that quality throughout the campaign, it can definately compete with some of the paid ones. Still i would like to mention some suggestions. What comes to my mind is the Mission Planner. Imo you should hide much more units there. I appreciate the fact you're not showing enemys on the F10 map, but since i could see everything in the mission planner (even the later activated Iranian fighter reaction) there wasn't realy anything surprising during the mission. I for example only show mission critical stuff in the planner (such as known SAMs in the AO or airborne BARCAP) but never show later activated stuff or fighters that are meant to scramble during the mission. Also i never show allies in the planner, except they're part of the mission (i.e. your own escort or a 2nd Strike Package). Imo this keeps the mission planner clutter free and the mission a bit more thrilling. Not realy an issue, but maybe something to consider... When i shot down the last of the Mi-8 in mission 02, i recieved both messages that the helicopters have left the area and that all helicopters are down at the same time. I'm assuming this is related to the trigger b/c as soon as the last Mi-8 is killed, they technically also have left the trigger zone. I'm always putting a "unit alive" condition in tandem with "out of zone" to avoid exactly this. Hope this was constructive.. Nonetheless realy well done and great ideas in terms of mission content. A very big thanks for your effort and for sharing your work!! Cheers

Imho the best module to start with is the one you're interested in. If you would like to fly the Hornet, grab it. The Hornet is easy to learn, but hard to master. It is pretty easy to get into it, start-up, take-off, flying, landing and all that stuff is pretty easy with the Hornet, but once you dig deeper into it's avionics and weapon systems you'll learn that this bird is one of the most complex jets in DCS system-wise and comes with tons of stuff to learn. In other terms, it is newbie-friendly and veteran challenging at the same time, provides massive fun and countless hours of entertainment.

Yes it is normal with both of the cam sets that come with the base, the aviasim soft center and the aviasim no-center cams. Both provide a non-linear force to the axis beeing meant for flight sim purpose. If you want a linear force you would need the cosmosim cams (again soft center and no-center variant), wich are sold separately. As Lange_666 said, the base may still flip. The WarBRD baseplate in general is much too light imo. I've my base attached to Virpils compact baseplate (wich is significant heavier than the WarBRD baseplate) and then screwed down on a simrig, so no issues here. The best thing you could propably do, is to get a desk mount for you stick or build your own one. All the materials used i.e. by Monstertech are easy to get online and pretty cheap compared to buying a Monstertech setup. Also find the Virpil deskmounts to be not too expensive, but i don't know if these are any good. I would assume so. Otherwise, i would do as advised and drill 4 new holes into the Warthog baseplate and use that one for the WarBRD base. The thread size on the WarBRD base is M4, so you would need a 4,2mm - 4,5mm drill for the holes on the Warthog baseplate. Just make sure that the spacings between the holes are precise and that you countersink the holes so the screws aren't scratching your desk

Thanks for the clarification.

I have the heavy springs and the no-center cams installed. Both come with the base. Also purchased the extra heavy springs in case i would need them for the heavy Warthog grip, but the heavy springs are ok. In the Virpil Joystick tester the stick is tilted forward by about 1%, but it's not recognised in DCS. You're good with the springs that come with the base, just not with those wich are installed from the factory. Cheers

I had something similar. Each time i entered the control settings, the game stuttered like hell. Over time, it became worse until i couldn't even enter the control settings without my game crashing. I figured out, that it was my WarBRD base. No game crashing nor stuttering once it was not connected. A firmware update of the WarBRD base solved the issue for me. Maybe you wanna give that a try. But be sure to have your stick plugged into your mainboard and not into a USB Hub while doing a firmware update. Cheers

True, that was my fault. I was assuming a 1 vs. 1 situation when i wrote that. Of course 1 vs. 2 respective 2 vs. 2 demand different tactics than 1 vs. 1, but this is also the case when facing an equal aircraft.

Hmm, good point... I put small rubber stickers on some of the buttons (on each middle button of each side) to support it. Works good and muscle memory did the rest for me. I rarely push the wrong buttons now...

It's a not a part of the core game but a new module. You need to search the steam store for dcs: marianas and install it.

Hello gentlemen, I've got a small question about the lighting at night. I'm not sure if this is a bug, a VR issue, related to my settings, or already reportet. I couldn't find anything in the forum, so i'm posting this here. I recently discovered the lighting at night isn't properly displayed on my headset without zoom. I cannot see the runway lights at 5nm or further away without zooming in. And when i'm about to touch down, the light at the beginning on the runway is very dimm, while at the end of the runway it is totally bright. Same for cities and villages. I just flew (online) over Beirut at night and at 30k feet there is no light visible without zoom, the city is completely dark. In general without zoom, the light is only visible in a very small bubble around the aircraft, wich was definately not the case for me prior to the 2.7 OB update and i didn't change any settings. Does anyone else experience that, or is it just me? The fact, that i couldn't find any reports about it realy made me a bit nervous, but one of my buddies has the same issue. Apologies if this has already been reported but the search function didn't came up with anything for me. If this has already been adressed, a mod may feel free to delete this thread. I'm on the latest open beta and my system specs are I7 6800K @ 4.2GHz, RTX 3090, 64GB RAM, Reverb G2 and DCS is installed on a M.2 SSD. I doubt this to be important, but maybe it helps... Cheers