Draken35

@Dave62ndFF I don't think you missed anything... I don't do too many air starts (I have just one mission setup for it, quick AAR practice), so I haven't seen that before n I use the APKWS a lot! I see that the TPOD was on 1688 and so where the rockets (kneeboard) but they behave like they were in a different code. Definitely smells like a bug to me. Two tests come to mind: 1) trying to fire an LMAV from air start after a failed launch of an APKWS 2) Manually setting the code to 1688 (perhaps, even setting it up to something else first and back to 1688) after a failed launch of an APKWS and retry

Well, I don't have it I only thing I can think about is that, somehow, you modified that payload way back them and since it was modified, it is keep after the updates....

How are you doing it? I just tried from the Mission Editor and from the Mission planner, latest 2.7 OB and I see the same options as the manual payload.

Well... I wouldn't trust the "manual" at this point but it says that the sequence starts at that time, not that it will continue it if you stop pressing the Weapon Release button... Anyway, you have to keep pressing it until all bombs drops. Works the same in several other airplanes . So, not a bug. Also, make sure you box "tone" in the stores page. It will beep to provide feedback on weapon release.

But it was in 3D so it cannot be a track-ir / pancake mode .... Nahhh... The VR Zoom Toggle keybind is mapped to the Hotas

I wish we have that quality of displays in VR.... Also, did you notice that they also have VR zoom???

Ah! I was hoping but since I was very aware that my case could be a coincidence, I asked for third party confirmation....

@hazzer @fagulha Yesterday I found that my flood lights and flashlight was rendering also in one eye. Found this thread: Turned out that I had the parser turned on... ( options.graphics.stereo_mode_use_shared_parser = true ) in this file [Drive:]:\Users\[user]\Saved Games\DCS.openbeta\Config\autoexec.cfg So I changed to: options.graphics.stereo_mode_use_shared_parser = false It fixed the flood light and flashlight issue... And since I made that change, I have not seen the flickering I reported in the first post of this thread...

Other that your fuse being on SAFE, the settings should be correct. Make sure you keep pressing weapon release until all the bombs dropped. Watched the track a couple of time and it is kind kind of weird... The Harrier seems to be rearming itself... Are you flying with unlimited weapons? Anyway, 4 bombs, in 2's with 0 interval will not feel too much different that 4 in 1'1 with 0. Repeat your test with 010 interval and, perhaps, uncheck unlimited weapons...

Good point. I wear progressive lenses and can't see s... nothing with out my glasses. It was really difficult to use the headset with them, so ordered VR Opticians adapters with my distance Rx only.

Just tested them too. They are very close indeed.

That is a cool feature of the Vive Pro! ... I don't think it can be done with the Quest 2. Yes, I suspect the real value is the IPD of ones eyes, despite all the posts to the contrary... But without a real yardstick (like in your case) , I have not not been able to prove it. My method gave me 55 and my pupil distance is 60.. To be honest, I don't perceive a difference between those two values... Most likely, my chair width is different to the Harrier's seat width and that is why I got 55 and not 60 or closer. Hopefully, if Bog9y finds the the real width, I should be able to take a more accurate measurement.

You mentioned that the ground crew ignored you...As in they did not answer your request? If recall correctly, before they answered "unable to comply) to the request to remove the chocks... Was this in a FARP or Airfield?

Fresh for the oven... Pardon the jerkiness of the recording and the lack of helmet audio (VR user here) and pay no attention to the abbreviated startup and the fact that I did not notice that my nozzles where at 82 degrees, but it shows that you can in fact remove and place wheel chocks with the engine on. Recorder in the latest beta build as of the time of this post. 001.trk

I'll test those values when I get a chance... Link for the charts (if rules allow it) please?

Do you know the width of the Harrier's seat? I fly mostly the harrier too... I got to 55 using the Harrier btw. Edit: lol... Just read that "have no reference other than" ,,, Need more coffee

I just did an empirical test for VTO Caucasus: Harrier with 30% fuel, 2xMk83, 2xMk82, 2xMk81 for 20660Lbls. Starting from the runway. VTO (wet), few seconds stable hover at 50'AGL, transition to wingborne fly. Tested from Kobuleti (60'ASL), Tbilisi-Lochini (1574'ASL) and a couple of farps at 3000'ASL and 6000'ASL. Temperatures from 0C to 50C in 10C increments 1) Kobuleti: success across all the the temp range (really struggling at 50C) 2) Tbilisi-Lochini: success at 0C and 10C ... I suspect 15C should work too but did not test 3) FARPs... Total failure at any temperature

I actually like it... Now you have to really be mindful of you weight for vertical take off and landings...

lesson learned!

Do you guys practice with your backup/standby instruments? I normally don't but today, I have a practice forced on me.... I was flying the ground attack sortie of Pirate Voyage - Mission 1 - Blackbeard's Folly (https://www.digitalcombatsimulator.com/en/files/3311380/ ) and without giving too much away, Dash 2 collided with me during a low altitude ingress, about 80nm from the closest friendly airbase... Surprisingly, my Harrier was still flyable ! The caution lights panel lit up like a Christmas tree but I was too low and with enemy air nearby to risk opening my kneeboard and trying to decipher the lights. Suffice to say that the engine was still working and I saw no fires in the mirror. Lost some data elements from the HUD, like my speed, altitude and heading tape and the plane was flying a bit funny... So, why not, I decided to bring the plane home. Dumped my ordnance and turned around about 180 degrees. Nav system was working so I selected WP 1 (closest to the departure airfield. After a few minutes I was close to it... Here my luck ran out... Low ceiling and 0 visibility near the airport, Bandar-E-Jask... So I climbed a bit and used the moving map, had to turn it on and do the gain trick (PLEASE Razbam improve the quality of the MCPDs! We VR users will appreciate it) and flew around until I got into the right approach... I couldn't remember if Bandar-E-Jask has ILS or not but, either way, I did not had the data at hand (I have a self imposed rule of not using the F10 map while flying) ... So, I got out of the soup at about 800' AGL ,250 knots and pretty much lined up with the runway at about 3 miles... So, I tried the landing gear, and it came down and locked up as it should, next where the Flaps... Set them to VTOL and the moment they passed 20 degrees, the aircraft back violently to the left and went nose down... Tried to retract the flaps and recover but didn't work and the Harrier went nose down to the ground....Barely had chance to pull the ejection handle ... Fun mission... From now on, I'll practice flying with my backup instruments... At the very least to know where they are!

@Recluse this might help

Ability to set "Landing" and "Landing & Refueling" waypoints on FARPs, in the Mission Editor, and making sure that the AI can use these waypoints for AI only flights.

It is not in the change log... I discovered it by... hum... accident? Let's hope it stay fixed

Finally figure out how the range script works with strafing! v1.01 uploaded with a working scored strafing range: https://www.digitalcombatsimulator.com/en/files/3316143/

Fixed in 2.7 open beta...