Lange_666

I'm having the same problem, Windows (10) is up to date. Only happened after the 24/8 update. Pancake mode works however it also takes sometimes quite some time before the game is loaded with a black screen in between the splash screen and the actual game screen. In VR it sometimes goes through to the game screen, most of time it hangs in the black screen. No mods installed, worked fine before the update. Guess this is the same problem...

I don't, i just used this link ( https://www.oculus.com/rift/setup/ ) which offered OculusSetup.exe which in turn installed V42 on my system. I blocked the future updates so V42 will stay there until the problems with V43 are solved.

When a new update is available, the software will tell you there is an update is being downloaded but if you then check the notifications it will be marked as queued. It will stay that way just until you remove de blocking folder/files. On the next restart then the download will take place.

For me re-installing brought back v42 but it directly offers v43 when run for the first time (and luckely also the option to postpone so i could block the update). V42 works nice.

PC software, i have a Rift-S

I have not been on PTC since like v16 or v17 and i was not on PTC either with v42 installed when the update to v43 got offered.

Updated to the latest Oculus release today, going from V42 to v43. Big mistake, after v43 was ready i went in for a little multiplayer and got big stutters every few seconds (it was playing nicely on v42 before). First thought it could be the server (quite a few people on), quit and started a simple single player mission, same problem. Oculus doesn't offer a revert option so going back to v42 was out of the question the only option was to delete and re-install. After re-installation i found that the software reverted back to v42 and was ready for an update to v43. I declined (postponed for 4 hours) and tested v42, no stutter. Reloaded, ran de update to v43 again, stutter came back. Uninstalled everything again, ran the setup which installed v42 again with he question to update to v43 or postpone, postponed, stopped the software and used the update blocking trick to block Oculus from updating to v43. All is good again now... A lot of people on the Oculus forum mentioned stutter/flickering problems after updating to the v43 beta. But somehow this wasn't adressed and the bug made into the release version of v43. A bit more of this and these guys are on the same level as Garmin. Prevent Oculus Client Updates.zip

It's not possible to zoom slowly in VR, only toggle zoom and spyglass are available.

Sure, that's the basic to set controllers up.

Thx for the heads-up. Back In Black

Somehow, i miss that "Language - Theme - Privacy Policy - Contact Us" part. This is FireFox, same on Brave or Edge.

See topic tittle...

Can only refer to the Rift-S but starting either the Oculus software of the Tray Tool first doesn't make any difference. But i have the habbit to start the Tray Tool first.

This means that the power is turned off on the USB that the throttle is plugged in into. When the power comes back on, so do the throttle lights. If you keep power to that USB while the PC is turned off (or rebooted), the throttle lights will stay turned off.

I own: Behind it Yes/No if i fly/flown it. If Yes, it doesn't mean i know the module throughly, like for instance i can only cold start the A-10 C. Yes in bold means those are flown the most the past 2-3 years. - FC3: - A-10A: Yes - F-15: No - Mig-29: No - Su-25: No - Su-27: No - Su-33: Trial runs on the Kuznetsof - Combined Arms: No - A-10C (and II): Yes - ASJ37 Viggen: No - AV8BNA: No - C-101CC/EB: No - F-5E-3: Yes - F-14: No - F-16C: Yes - F-18C: Yes - F-86F: Yes - Hawk: Yes (but is no more) - L-39: No - M-2000C: No - MIG-15Bis: No - MIG-21Bis: No - S-25T: No WW2 - FW-190D9: No - Bf-109K-4: No - Spitfire: No - P-47D: No - P-51D: No - TP-51: No Helo's: - UH-1H: Yes - KA-50: Yes (but long time ago) - Apache AH-64-D: Yes (started when it was released, since then on hold). Mods - A4: No Terrains: - Caucasus: Yes - NTTR: Yes - Persian Gulf: Yes - Syria: Yes - Normandy + WWII Assets pack: No (still have to see one of those assets, lol) - Channel Map: No - Marianas: No: nice looking but to heavy for my system - South Atlantic: No Not in my collection: - Mi-24P Hind - Gazelle: Flown in a 14-day trial, didn't buy - Mi-8MTV2 - FW-190A8 - Mosquito - Yak-52 - I-16 - JF17 - Christen Eagle (no idea what this is doing in DCS) - MIG-19P - NS430 - Most campaigns

Never happened to me, updated quite a few times already. Re-setting it up doesn't take that long though.

Steps: - Make a copy of your current install and put it somewhere on your PC (can be on the same drive if it's large enough). - Use Skatezilla's updater (https://forum.dcs.world/topic/134493-the-dcs-updater-gui-utility/ ) utility and update your just copied copy into the version you want. - Either create icons to the new install or use Skatezilla's updater to launch the version you want to use.

I agree with admiki. It would be different if TrackIR would be part of the helicopter system but it's not.

That was my first thought too but then not being able to "click" switches in the cockpit has nothing to do with control assignment.

Works fine here in the F-16 (and also the F-18), slewing the cursor and clicking in both pits. Latest update (today).

On what aircraft?

Yep, DCS differs from that compared to other games/sims. They all have a total general setup, same for every type of plane you fly. (WT, IL-2, MSFS etc...). However, in general, jets developed by ED have almost the same terminology, pre-DCS (Flaming Cliffs jets) differ a bit from these but can be considered as a group, same for all warbirds by ED which use again use a bit different terminology (except for stuff that specifically to a certain aircraft). Aircraft by 3th party developers then again differ here and there. But depending on the software (if any) you use for the controllers, you can single write a lot of general stuff which you can then use across all aircraft. Also, i set up my controllers +/- the same for each airplane regardless of reality. Result are less brainfarts. Nothing wrong with autostart, i can only manually start the A-10C, for all others i use autostart. With this in mind you can spend some more time to get other stuff ironed out. You'll need it...

I would pick one aircraft to start learning, not multiple since you can mess up yourself if you start mixing both. There are lots of Youtube channels who offer a complete step through one step at a time. A few examples: A-10: https://www.youtube.com/playlist?list=PLF779D43F5153AD8E F-18: https://www.youtube.com/playlist?list=PLer9oF4AanvFOfG4sSZSHJQZeMQx7YGr6 and F-18: https://www.youtube.com/playlist?list=PLer9oF4AanvGAo-V9XWyHsyMaGE8r22RH

DCS forum has a dedicated subforum for anything related to controllers. You might want to repost there... https://forum.dcs.world/forum/70-input-devices/

Sedenion's script turns every button into a DX button by default (see chart_complete.png). Either you need to rewrite MapThrottle.tmh to match it to your current setup or get the DX120 mod and integrate that into your script so you have the 120 DX buttons available for your own profiles and use them where you want them.