Draken35

The first time I did the uninstall/reinstall (last Friday) I got also v43. This morning, I decided to give it another try... Nothing to lose... These are the steps I did: 1) uninstall your oculus software 2) factory reset your headset 3) once done, pair it again with your phone and check the version... 4) install oculus software again, have the file that is in the first post of the above thread handy and follow the readme instructions (I also renamed the tmp folder to tmp.bak) 5) restart the pc and check versions. Don't really know if I got lucky of if the order of the steps really matter... I hope that Meta get their read end in gear and fix this crap soon.

did you do a factory reset if the headset?

instructions are in the readme, inside the file attached to the first post. I was able to fly with my usual settings and FPS without any issue! You will have to click through an Oculus "error" telling you that it is unable to update... Funny thing is, they consider that a "critical" error

null 30% of the CPU... With the Headset OFF!!! v43 really sucks and the fact that they control when to update , is really making thinking about switching to a different headset Update: I managed to revert back to v42 by uninstalling the oculus software and doing a factory reset of the quest 2. Upon reinstalling the Oculus software I applied the no updates trick from the OP. The v42 software looks like this in the task manager: null

I'm having issues with v43 and, no, I'm not on PTC. My issue is worse than stutters, link crashes between 2 and 5 mins of starting a mission and the Oculus Home Software start saying that the port is not USB 3... Unplug and replug the cable and it is USB 3 again... Unfortunately the reinstall of the Oculus software brought back v43... I have a support ticket open with Oculus... So, I'm going thru the usual script of verifying for them that everything is up to date , try different ports, etc etc... Meanwhile, I'm grounded

At the end, I went the dampener route: Took a bit of trial and error to find the sweet spot for the brackets but no issues since.

AH! I counted full squares but did not pay attention to the actual grid. Thanks

Fantastic script! A small request/suggestion for 2.0 if it is not too late: Allow the use of optional airplane templates per mission type ( a template is no more that a group set to delay start with a specific loadout) and have the script pick one randomly. If there is no template defined for the type of mission, use the current methodology . This will help mission creators to adapt to the time frame and specific conditions for the mission. Thanks a lot for your work.

The closest thing to external documentation is the couple of videos posted above... Bearing in mind that the format of the target file changed a bit. Sorry... Doing the script is fun...documenting not so much... It will happen, eventually

When trying to input UTM coordinates, the top ODU does not populates. Track and mission attached null null Harrier-UTM.miz HarrierODU.trk

Not so far... Get used to lean forward and then check six

The most recent version of the scripts are in this mission... It uses the A4 & 776th targets mods. Target definition and features have changed a bit since 2.0 but they follow the same general principles CA BSA 3 Auto - Unlimited.miz

If for some reason, you don't see anything else mapped in the axis, like firefox121 suggested, just do a clear category of all of your axis and remap one at a time and test. Make sure you check your hand controller axis is you are in VR.... My nephew went thru the same issue and we spent quite some time trying to figure out. The axis mapping screen for his VR hand controllers showed nothing mapped, but once he did a "clear" of that category, everything started working.

Ah! Sorry, yes... Only that element of the F1 cockpit. Last nigh, I looking for a way to avoid the issue (other than disabling the hand controllers), and I found that If I lean towards the HUD and then turn to look (i.e. the head set does not go through the face blind handles) the issue doesn't happen. I really appreciate your help and time on this issue!

By themselves? Nope, they do not click anything anywhere unless I have a full grip on them and touch the appropriated button

Well, it is definitely related to hand controllers... I cleared the oculus touch category of the binding and the problem persisted. So, I disabled the hand controllers in VR option and was unable to reproduce the issue, then I reenabled them and boom...I was floating under my canopy. I haven't seen this with any other module.

I was careful not to touch anything other that my sick ... But, I will do a reset of the oculus touch. There is nothing mapped but I have a suspicion of a "phantom" mapping there... Saw one (while helping a fellow pilot) figuring out an axis mapping issue with the Vive and the F1... I'll report back

Actually, spoke too soon... Watched my track again and figured out how to reproduce it on demand: pulling hard to the left while looking left and up through the face blinds handle . Track 1 is with my hardware ejection handle mapped and the second one is without 1.trk 2.trk seems that we cross posted... I'm not experiencing that issue that I've noticed.. I'll keep an eye on it

That is an ejection handle that I've been using for 2 years and 10+ different modules... This spontaneous ejection happens only in the F1 and, so far when looking up and left, although I have not been able to reproduce it on demand yet. Yes, even that I've been using it for long time, my first thought was that somehow I was accidentally activating it with the F1 only... So, believe, I've been trying to "accidentally" pulling it enough to eject... Unsuccessfully.

I've had 3 instances of the jet ejecting me out on its own. The 3 times had been in dogfights (1 in MP , 2 in SP) while looking up and left near the Face Blind handle. My settings: and the track for the 3rd time (SA map) is attached F1CE spontaneous ejection.trk

Or what is the deal with the HUD Horizon Line moving around in Nav mode... Is it a bug or a feature? If it is a feature, well is very unique, so how do we use it and for what?

When in approach mode it seems to reference the horizon, but when in normal mode, it seems related to AOA? I couldn't find any references in the manual and since I don't seen any bug report for it, I assume is WAD but can somebody shed some light on to what it references? Thanks!

Thank you! Will try that!

I have it mapped to button in my throttle and when I'm in TEL mode, master arms on, cannon sight is uncaged but I see no changes in position of the sight when pressing the 300-600 button like Redkit's video shows... I tried with and without targets locked. Can anybody confirm if it is working?... I'll post a track later and if needed....Done flying for the day.

+1