dcs76

Also if I would do 2 second bursts per target as instructed by the FE, I would be Winchester long before all targets were killed.

After killing everything at TARGET1 to TARGET3, I seemed to have missed a few targets at TARGET4. I killed the first vehicle in the column and the column stopped. Then I reengaged all other targets, yet the FE still told me to reengage. According to the flight log, I killed 9 targets in total at TARGET4 WP. The mission file lists 16 targets in the convoy (no idea where they went, I searched the whole area). In any case, as I killed more than 50% of the group I should have received a Q- rating - not an Unqualified rating according to the briefing.

Could it be that ED tweaked all quality related parameters beyond the boundaries which would result in really bad performance and then captured the video frame by frame to make it look more appealing? I was never able to achieve this high video quality output as shown in the Persian Gulf final trailer.

I was talking about the FE going up and down like crazy. Impossible to follow him in formation while still staying at 1000 ft AGL. I did not save the trk file from my first attempt. When I ignored FE in the second attempt, I recorded a video: Already at MTR entry point, FE was behind. I slowed down too much through MTR and barely made it in time to the WP 10 and WP 15. FE was way back and did not make it in the given time.

Issues still there. Nothing changed. I have to reattempt and will totally ignore the FE after the trigger for the VO about hitting entry point. This Fe is crazy!

BTW, that white noise frame happens in ALL VR apps - even in the VR home app. This is not a DCS / shader issue. I hope Oculus will address this with a firmware update.

Yes I noticed another post about the removal of that rubber piece. At least this is not an issue then.

I sincerely doubt that the IPD has anything to do with this chromatic aberration. I have those distortions on each lense/eye separately. I tested this with closing each eye and trying to find the optimal position and angle for each eye and it was still horrible.

My Rift S came yesterday and I am fairly disappointed. It seems the FOV is slightly smaller compared to the CV1 and most importantly the chromatic aberration and distortions towards the edges is absolutely horrible. There is only a very small sweet spot in the dead center of the lense which is sharp enough, but a virtual inch (about 2 cm) to the left, right, up or down of that spot the image gets distorted. So I basically cannot read text without staring just at this sweet spot and turning my head all the time. Neither can I read all the HUD symbology in the A-!0C without moving the head nor can I read the left engine RPM gauge when directly pointing my head at the right engine RPM gauge. At the edge of the FOV there is just a blurry mess. Mostly blue. Someone else having also a Rift S does not seem to have this issue. A pretty common issue, which I experienced with the Rift S as well, is the occasional white noise frame. This is quite annoying as well and I never had this with the CV1. I'm not sure if my Rift S is faulty or if this is normal. I will give it back and try another one. If that one has the same problem, I stick with the CV1. Edit: More issues I had: The foam isolation seems to be thinner than with the CV1. There is a rubber at the edge towards the nose gap. This shields better against light from outside, but it prevents peeking through to use keyboard when wearing the Rift S. Also this rubber seems to get heated up by the Rift displays quite quickly. The rubber pinches against my nose (might be that my nose is too big for the Rift S) - it is annoying and more so when the rubber is heated up. Also the lack of a good headset forces me to put on an additional headset and I am unable store away the cable of this headset so that it does not annoy me. Putting the headset on and of with additional headset is tedious as well. Yes, the display (in the sweet spot) is sharper compared to the CV1 and I can read better there. However, I had to change MSAA from 2x to NONE and reduce PD from 1.5 to 1.2 in order to run the 40 Hz with the Rift S compared to the 45 Hz with the CV1. I have an i7 at 4GHz and a GTX 1080TI.

My Rift S came yesterday and I am fairly disappointed. It seems the FOV is slightly smaller compared to the CV1 and most importantly the chromatic aberration and distortions towards the edges is absolutely horrible. There is only a very small sweet spot in the dead center of the lense which is sharp enough, but a virtual inch (about 2 cm) to the left, right, up or down of that spot the image gets distorted. So I basically cannot read text without staring just at this sweet spot and turning my head all the time. Neither can I read all the HUD symbology in the A-!0C without moving the head nor can I read the left engine RPM gauge when directly pointing my head at the right engine RPM gauge. At the edge of the FOV there is just a blurry mess. Mostly blue. Im not sure if my Rift S is faulty or if this is normal. I will give it back and try another one. If that one has the same problem, I stick with the CV1. Edit: I noticed there is a Rift S thread .... posting my comment there .... now. Don't reply to this post here pls :)

I was following the instruction very precisely. I always stayed within the instructed heading (+- 5 degree), altitude (+- 100 ft) and speed (+- 10 knots). However the FE was barely finished explaining the spiral maneuver before he called TERMINATE for leaving the MOA. I am unable to stay in the MOA while flying the instructed heading. When I deviate from the heading, I get a Q- or worse.

It depends on what the threshold of the IR sensors in WHOT (or BHOT) mode is. The IR sensor and TGP show everything white which has a temperature above a specific threshold that the pilot is able to locate and identify vehicles with running engines. An explosion of a bomb/rocket has definitely a higher temperature as this vehicle. So it is totally normal that also this cloud is shown in white (WHOT) and even blinds the rest of the screen. Same Might also be said for smoke generated by WP. Phosphorus is burning at quite a high temperature and part of this heat energy is being carried by the smoke itself. I cannot say how hot this smoke will actually be though. Not sure if this would blind an IR sensor. The example and reasoning given that IR cameras are used to look through smoke is just a matter of where the threshold for showing things white/bright is. For a burning building they would usually have this threshold very high to only see the fire through the clouds. As you watch the video, you can see that the firefighters are actually black (pretty much as black as the background). In the FLIR of the TGP those firefighters would be visible as white as the threshold there is different.

Actually .... you would not be required to wait 5 minutes before shutting down the engines. Waiting 5 minutes is only required after a flight and as long as the engines have not been run above 80% RPM during the taxiing an immediate engine shutdown is ok.

The official documentation as well as the amplified checklist provided with this DLC states that the ejection seat is armed before takeoff - not during the engine startup phase before taxiing. Arming the ejection seat before taxiing is simply wrong and inherently unsafe. However, the IP checks for arming the ejection seat before taxiing.

When flying this mission in VR at least, I get strange display artefacts belonging to the F2 view (which I have disabled in the game settings along with all other external views), but they are persistent in the F1 view. Have a look into the attached screenshot.

Ich werde zum Event streamen: Twitch: Youtube: https://gaming.youtube.com/channel/UC-l8jXiAXcmoNdNWo5wHy4Q/live Freue mich!

I started recording the missions: Already after the first two missions it becomes obvious that the new campaign is several level higher in production value than the former version and that it is actually a completely new campaign which only has a similar setup and overall story line but is something totally new. Same same. But different :-)

Habe mal begonnen, die Missionen aufzuzeichnen: Schon bei den ersten zwei Missionen wird klar, dass die kaum noch was mit dem Vorgänger zu tun haben.

Zur Aussage von @Yurgon kann ich noch ergänzen, dass es auch viele gänzlich neue Missionen gibt und selbst, die noch vom Thema ungefähr denen aus Version 2.0 ähneln sind so stark überarbeitet, dass auch diese sich wie gänzlich neue Missionen anfühlen. Das Setting und die allgemeine Story ist analog zu TEW 2.0, aber sonst ist das für mich eine gänzlich neue Kampagne, die sogar den vollen Preis verdient hätte.

@Ghost: Da ich noch nicht so viel Erfahrung mit F-18 habe, lieber WM. Wenn sich für mich ein Lead finden würde, wäre das super. Zur Not mach ich aber auch Lead - muss ich halt noch etwas mehr die Kommunikationsprotokolle büffeln ...

Ich würde gerne als STRIKE mitmachen wollen - CS: "Fuzz"

Hm KND ... klingt interessant. Harrier und F-18 stehen bei mir auch als nächstes an ... Werde ja wieder Beta-Testing für BDs kommende Harrier Kampagne machen (hey tintifaxl, dich kenn ich doch schon vom TEW 3.0 Betatesten - toxygen hier).

(huch Doppelpost). vjabog32 wollen übrigens einen recht hohen Mietgliederbeitrag und vjabog66 wollen niemanden aktuell aufnehmen :-(

Wie erwähnt wäre Spaß zusammen das wichtigste und Fokus PVE. Das heißt, ich nehme es nicht zu ernst. Ich denke aber, dass ich den Vogel soweit ganz gut beherrsche (AAR klappt nie und Formationsflug weiß ich gar nicht, ob ich das kann, da das im SP egtl. nie vorkommt). Die vjabogs hatte ich mir schon angeschaut. Die waren mir tatsächlich zu ernst. Zwar ist es schön, sein Wissen/Können auszubauen, aber da wird ja NUR trainiert. Und Kommandostab und Dienstgrade schrecken mich ab ;-) Mir wäre es am liebsten, gemeinsam Missionen/Kampagnen zu spielen. Die Gamestar-Staffel kucke ich mir mal an. Das klingt tatsächlich mehr nach meinem Geschmack. Danke!

Hi ho, ich spiele seit Mai 2018 DCS fast ausschließlich A-10C. Habe mir aber auch alle möglichen anderen Module (moderne Flieger, Helicopter, Maps, Kampagnen) schon bei Angeboten zugelegt. Nachdem ich nun schon durch die ganzen A-10C-Kampagnen durch bin, würde ich jetzt mal gerne die Multiplayer-Welt kennen lernen. Mir geht's vor allem ums Spaß haben. Mein Fokus wäre PVE (mit der A-10C nicht verwunderlich). Nachdem ich mich durch die Multiplayerthreads durchgewühlt (sowohl englische als auch deutsche) und mir die verlinkten Homepages so angeschaut habe, ist aufgefallen, dass die meisten Geschwader eher dünn besetzt (ca. 8 bis 12) und auch nicht (mehr) wirklich sehr aktiv sind. Auch bei den Multiplayer-Servern in DCS findet man nicht viele Server und vielleicht eine Handvoll hat mehr als 5 Spieler gleichzeitig online, die dann aber auch in den USA sind und man durch den hohen Ping ausgeschlossen ist. Gibt es noch so richtig aktive europäische/deutsche Geschwader?