Highwayman-Ed

Exactly the same here as toutenglisse describes for me with a Pimax 5K XR too.

The scripted kneeboard in the Mi-8 is missing items, has layout issues and shortcuts for bindings that aren't available. For example, Page 1 details the items from the before APU start with a Key shortcut of LSHIFT+NUM1 which isn't mapped to anything. Page 2 then details the items from After starting the APU with a Key shortcut of LSHIFT+NUM2, which again, isn't mapped to anything. But nowhere on either of the two pages does it actually cover starting of the APU? Maybe I'm missing something, they seem like a great idea, but are incomplete or have lost something in translation?

Haven't used this mod in ages, but decided to give it another try today. I don't know which tweak does it, but it's fixed the screen flickering issue that was introduced in the open beta a few builds ago, and my wing vapours and LEX vertices are working again! I also don't notice the clouds in the far distance popping in and out of one eye quite as much as with the stock Open Beta either. I do however need to disable the Simple Shadows as they're way too dark, like the interior of the cockpit that isn't in direct sunlight is black... (Edit: I found this happened because I'd let the shaders compile in Desktop mode first. Deleted them all, and re-compiled in VR, and they were normal again)

Bump, same problem. But until the official update, I've done a quick hatchet job and changed the cockpit arguments in the mission triggers to highlight and check the new radio. You can get my modified version here: M-2000C Batumi Cold Startup Training Mission

As you said, the slider makes no difference, the same issue occurs at 30%, 50%, 100%, it doesn't matter, it only affects the distance at which you observe the anomalies. I just included the options so that the devs had a clear view of all of the other settings I use that may be a contributing factor, such as a specific shadow setting that could be causing it. In your later videos, 2nd one to be precise, you nail the visual anomaly completely as I see it too. But, I tend to agree with BIGNEWY's statement that it could just be a simple LOD issue for the shadow banding where the 4th layer trees have been accidentally switched with the 5th layer trees, for example, as a starting point, and that would also back up the fact that it occurs with any tree slider setting.

No mods, repair run, shaders folders deleted. This is the second run after the shaders re-compiled, I forgot to save the track file on the first one! In the screenshot, the trees don't look quite as bad from this angle, but you can see something is not quite right with the trees on the other side of the river off the wingtip. When you're flying along it's sooo noticeable as they really pop when they switch from 3d trees to 2d flat textures, and it's happening at about a 1km radius from the player with my settings. It's the same kind of phenomena as in my previous screenshot that causes you to really notice it, where the lighting on the 3d trees comes from the direction of the sun, but the 2d trees seem to be from the opposite direction. Track file: trees.trk Log File: dcs.zip Options.lua: options.zip

It's definitely a LOD based thing, but also a shading issue. I fly on Medium distance due to being in VR, but the lower Rez trees are truly horrible, and primarily because of the shading, it's like the textures have been pre-shaded and simply don't match their surroundings. For example, this capture is taken on a freshly repaired install with no mods from the Quickstart F/A-18C River Run mission, right at the start. See how the high poly trees in the foreground are lit from the right side, as per the position of the sun? Now look at the low poly trees on the other side of the water behind them. They look like the light is coming from the opposite direction on the left side. When you're flying, seeing not only the shift in low to high poly models or vice versa, but you're also seeing what looks like a complete change in the lighting of them, it really sticks out. If you've never seen this before, and now can't "unsee it", I apologize!

Hey guys, just thought I'd share some feedback on the campaign so far. The campaign flows well with a good overriding story, and the voice-overs and scripts are great. Everything works as it should, even though I'll admit that the first time I was asked to do a ground power start and manual INS alignment I freaked out a little (even after seeing that it was coming in the brief)! I'm up to mission 4 now after completing 1-3 and have found the campaign interesting, if a little information-heavy. Briefings are very detailed, and there are certainly lots and lots of kneeboard pages to tell you everything that you'd ever need to know, but I've actually found these to be more of a distraction when trying to flick through them to find something specific, and there's a lot of info that doesn't necessarily need to be there at your fingertips when you're in the air, but could still be called upon from the briefing images. The biggest thing for me though is that I expected a bit more training information rather than just a series of tests. Maybe that will come, probably I just didn't read the description properly on the purchase page on the store. There are of course the threat profiles, but the counter-tactics provided for ALL of the adversaries state "Jam the radar, pre-emptive chaff and flares then within visual, 2D or 3D manoeuvre, but nothing about the actual aircraft or its weaknesses that could be exploited. I personally was hoping for a briefing about how to fight an adversary, what weaknesses to look for, and what to avoid doing, rather than just being thrust into 3, 1 on 1 guns flights on my first outing. For example, something along the lines of "Your first adversary is the F-5E Tiger II. The Tiger II is a high-performance multipurpose tactical fighter with a primary mission of air superiority. It has two afterburning General Electric J85-GE-21 engines providing supersonic flight capability but is lightweight, very reliable, and designed to be cheap to maintain. Whilst the F-5E can be highly maneuverable and can achieve supersonic flight, its engines don't produce enough power to sustain airspeed with high G loading, it's relatively slow to accelerate in comparison to your Hornet, and at lower airspeeds, its maneuvering performance rapidly degrades below 300 knots" Hey, maybe that's a scope for a new campaign ;) Just my 2 cents, off for mission 4 now

I've gotta back that up and say that the Harrier training missions are, without doubt, THE BEST training missions I've ever experienced in DCS. Yes they're incredibly detailed, yes they're complex, but they also teach you all about the aircraft, it's limitations and how to operate it. I wish all of the aircraft training missions were this detailed!

Still an issue here, plus I've noticed that unlike other aircraft, the Audio warnings are ONLY played over the "In-cockpit" audio channel and not "Helmet". Turning up the "In-Cockpit" audio channel to 100% helps a little, but I still think it's a bug.

Ran the mission again this evening to mixed results. I started up quickly this time, but just turning around on the apron seemed to stop the lead aircraft from moving. After waiting and waiting, I taxied to the runway, but he started moving after I'd gotten halfway there. I moved over and let him take the runway first and get airborne. The first thing that I noticed is that the altimeter setting from ATC was 28.03, and lead had indicated that we maintain 10,000ft. It seems the AI doesn't seem to care about this as flew at 8,100ft according to my altimeter, however, in the F10 view, he was bang on 10,000ft 7:39:30.358 ATC (NellisControl): Hawg 2-1, NellisControl, you are cleared for takeoff when ready, climb 300 at QFE 28.03 Lead was also flying along as fast as he could possibly go and was pulling away from me. In the screenshot above, you can see he's holding 350kts True at 10,000ft, whilst I'm barely managing to keep 320kts True... Edit: I flew the mission again tonight, this time asking the crew chief to remove my stores and take 2000lbs of fuel out of the bird whilst I was aligning my INS, and I just managed to keep up at a steady 290kts IAS

Just started the campaign tonight and was impressed, but then as the 3 flights all started jockeying for position to land it went to hell. All the flights conflicted and one of the A-10’s from the lead flight came around and near missed me only to collide with another one of the A-10’s from the 3rd flight. Then on the landing run my 2nd and 3rd wingmen collided as well! Maybe breaking the flights into holding to wait turns would help?

Same here, just flew it for the first time tonight and did a proper start by the checklist (it’s been a while since I’ve spent much time in the A-10C too). Lead was passing Waypoint 1 by the time I was ready to taxi and seemed to be running at 99% throttle the whole way, I had real issues catching up.

Lots of potential causes for this it seems. As of the latest Open Beta (2.5.5.41371), I'm getting not just the odd black flicker when I'm in a shadow, but also the odd white flicker now, usually when I can see wing vapours. I don't use any SSA.

I own and have used the Oculus CV1 and HTC Vive in DCS, but now have the Pimax 5K XR and it's fantastic. The field of view (I use Normal, 150° Horizontal) is breathtaking and adds a LOT to the immersion and getting sensory input that helps with flying, and I couldn't live without it any more, but it does need quite a bit of horsepower to drive it. The sweet spot of the headset is huge, there is plenty of adjustment for IPD settings, and digital offsets, as well as the physical lens spacing, should you need it. The clarity (inside the normal 120° Field of view) is crystal clear with a good head strap, I use the Vive Deluxe Audio Strap. I have had to revert back to my Rift or Vive a couple of times, and the loss of the field of view was debilitating. This was due to issues with the manufacturing quality of the Pimax, and I've had to RMA 2 headsets due to cracking and the second with a couple of dead pixels, BUT Pimax has replaced them without any arguments. I will be upgrading to an 8K X when they're available, as the only thing that bugs me with the 5K XR is that the screen door effect of the OLED screens pentile (diamond-shaped) matrix is only slightly better than the Rift or the Vive due to the Pixel density not being much better than the older headsets because to the wider Field of View.

The DCS loading screen for VR users has always been a little uncomfortable with smearing, lag, very low frame rates and the like, but it seems to have gotten worse over the last few months with updates to DCS and to the Steam VR client. I'd like to request that the loading screen for VR users is disabled entirely so that it drops us to the Steam VR or Oculus loading areas until the mission has loaded? Right now, it's incredibly uncomfortable with a rapid flickering of different images in each eye. One time during loading I even had an F-16 image in one eye and an F-18 image in the other eye, both flickering between two slightly different positions where I'd moved my viewpoint very slightly. The result is I end up having to just closing my eyes as soon as I press fly until I can no longer sense the flickering!

We could really do with some Axis bombers to shoot down...

I have a request that an option be added to repeat a keystroke a selectable number of times for use with the rotary switches. In my scenario, I (and a few of my friends) have a Derek Spears Design button box with 5 momentary rotaries that I use for radios, lights and other functions, but when turning the dial Clockwise for example to rotate the Console lights CW button in DCS, I have to physically rotate the DSD rotary 360 degrees to get about 30 degrees of movement of the corresponding rotary in DCS. This means that I sit there winding the switch like crazy to get small movements. An option to add a "repeat" of the button press, 1, 2, 3, 4 or 5 times per press would be awesome in these situations. Thanks!

Similar issue here, same scenarios where heading toward the city results in a 50% performance drop, turn away, the FPS comes back.

Excellent stuff. Been thinking that DCS should have a COD for ages, but adding an Orion to the pack is just the icing on the cake!

Hey, just checking in to see if this is still on your to do list in terms of increasing the shut down time. I've recently jumped back into the A-10C whilst waiting for the F-16C to get its legs under it, and I've stuffed up the shutdown twice now because of a rushed 2 minute procedure and missed the power switch on ILS the first time and the VHF-FM radio the second time, both times doing VR Gymnastics in the cockpit to get to those difficult to reach switches and, well, missing them with the mouse when it's at the boundaries... Repeating the whole thing because of a missed radio switch gets frustrating :(

I get something similar in the latest update (2.5.5.39384) after firing a missile or rocket (something with a smoke trail), as soon as I do, the clouds flicker whilst the smoke trail is present, and then stop when the smoke trail expires.

For the CCIP training mission, the procedure for dropping the ripple of MK83's does not select a fuzing method, thus the bombs dropped would not be fuzed to explode (DUD shown in hud, fuzing for Mechanical and Electronic fuzes show None). DCS World Open Beta 2.5.5.39384 Track File Ignore the fact that I did set the fuzing to drop them myself ;)

You Sir, are spot on. As QuiGon mentioned, I do not ever recall this being a thing that the bombs would drop out of alignment once they had it, but I flew the training mission again this morning and flew very sedately whilst listening to the instructions. As you described the GBU-38's showed RDY in the DSMS page whilst flying toward the target. Rather than drop GBU-12's on the first pass, I selected the profile for GBU-38's and whilst on Autopilot, flying straight and level, the GBU-38's dropped to ALN RDY. I turned toward the target, now just past my 10 O'Clock and as I came out of the turn they switched to RDY again. As I approached the target, having flown straight and level for a few minutes again, and just as I was approaching the release point, they dropped to ALN RDY once more. I depressed the pickle button when inside the DLZ, and no bomb dropped. I 'waggled the wings' and they switched to RDY immediately and a press of the pickle button dropped the bomb. Intended and or accurate behaviour? I'll leave that to ED to answer, but here is the Track File

Nope, perfectly aware what SOI and SPI are and how they relate to the various sensors and weapons. I'll admit that it has been several years since I've flown the A-10C, but I logged a lot of hours in it as an original beta backer of the aircraft. A friend of mine recently showed an interest in flying the aircraft and I directed him to the training missions. He had issues with that mission, so I coached him through what should be done, and after not coming up with anything that he did or didn't do, I decided to fly the mission myself and experienced exactly the same issue, hence the post. Not sure if like I said it was sloppy flying on my part with relation to the JDAM's, but I could not get the bombs off the rails on the 3 passes I made over the target in the original track. The mention of "POINT" in the resolution post is it to my knowledge is the ONLY thing that was different about the SOI, the SPI and the aircraft configuration, and that time the weapon came off the rail.