Draken35

You almost gave a hard...attack... Until I realized that you meant the F-5E I will test the Tiger and report back

I have the list posted above... But I'm coming out blank about which has a click and hold functionality... I'll be happy to test it if I can think of one or you tell me If its new, (didn't know about it)... Most recent modules are the Apache, Mosquito and F1 (P-47 maybe?) I have all of those....

But then, why doesn't it happen with any other module (official or mods)? In the past 2 years I've flown with Oculus. I own these: Harrier, Hornet, Huey, C-101, F-5E, Mirage 2000, Warthog, Gazelle, Tomcat, HA-50, Apache, Mosquito, P-47, F-86, Yak-52 and a few mods (A-4E, T-45)... Also, evaluated (2 week trial) the Viggen and JF-17 and never seem or hear about anything similar to this issue. Also, remember that it only seems to happen to the ejection handles over the seat on the F1... If it was a Oculus thing while interaction only with the cockpit of the F1, then I would expect to also activate other controls. The only possibility I see, for this issue to be on the Oculus side, is some sort of a bug related to tracking position (looking up and back) ... Are there any other reports of similar issue in any other modules @Flappie? I can't recall (no coffee yet) which ones on my list have top ejection handles...

Yes, that definitely will work for me since I have the ejection mapped to a device.

Dunno what to say, it works for me... Do you own the Mosquito? I'm not sure if that has a bearing or not in the issue

Yes :

Scripts updated: https://www.digitalcombatsimulator.com/en/files/3325875/

Sept/12/2022 Update - Upgraded the missions to the latest version of the scripts and fixed the bug with the Automatic Range Clearance reported in the comments Also, change summary to indicate that the mission is compatible with MP

Funny, I was just flying it and doing some strafing and it works... Which target are you strafing and what message are you getting? What plane are you using (shouldn't matter...but...) EDIT to add: I was flying the limited version of the mission. Same mission, same scripts versions, same targets, only difference is the "unlimited weapons" unchecked and it does work (just retested) but with the unlimited weapons checked in the missions options, the script indeed, does not report the hits for strafing... My guess is that something changed in how the data is reported by the API in the past few updates... I'll take a look when I have a chance, but for now, uncheck the unlimited weapons.

I'm sure it will help if you post a track, perhaps using the mouse to retract the landing gear

Quest 2 or something else?

Still happening as of last patch to OB

this is the way

I have the cheapest thrustmaster pedals with no curves... I also have 0 issues taxing with the A-4 in a carrier or airfield... What I have issues with, is the entitlement of some people... This mod is free, done by people using their free time to pursue their own goals and they graciously share their work with us, even if they have no obligation to. It is fine and understandable that somebody might not agree or like those goals but calling them "stupid" is crossing the line. This entitlement might end up killing the desire of sharing one's work. I'm personally in this situation, even that what I've shared with this community is not remotely close to what the A-4 team has shared. I'm sure the dev team, any mod dev team, can take constructive feedback and apply it if it fits their goals. Let's respect those, be grateful and if we do not like a mod for whatever reason, just let's move on. We are here to have fun after all... In whatever way each one of us define "fun".

They had released several builds of v43 ... I have a FB account only but 43.0.0.161.173 43.0.0.175.173 had the issue ( 30 to 60% cpu utilization in idle making PCVR a slide show - not only DCS)... My system was about 45% (using the FB account with those builds) I got today: 43.0.0.192.173 And, just it case, I logged out re-started and logged back in with my FB accounts. In the Oculus thread posted above, there are reported cases for users logged in with Meta accounts in supposedly fixed v43 builds reporting high CPU utilization and the recommendation from Oculus, was to log out, restart services and login back with FB account.

Yeah... This whole thing with v43 convinced me to look for a replacement ... I just updated and can confirm that the CPU usage for oculus stays at 0% in idle...

Apparently the CPU issues with v43 are solved by login out of the pc app, restart the oculus services and log back in with the Facebook account .. https://forums.oculusvr.com/t5/Announcements-and-Releases/PTC-v43-Release-Megathread/m-p/980388/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufEw3N0g1NjI5V1k2TDgwfDk4MDM4OHxTVUJTQ1JJUFRJT05TfGhL#M2895

null

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