Lange_666

Using Open Composite is (was) the only option to use some of the shader packages. They didn't work through the Oculus API.

My bad, did read the topic wrong, since i did read "virtual" i thought it handled the problem described in my post.

Has nothing to do with TARGET but with binding conflict in DCS. TARGET is just a powerfull tool, if you know how to push it's buttons. If your scripts fail to compile it means there are errors in them, caused by you, not TARGET (it would be the same if you use any other programming language for whatever so don't blame it on TARGET). Best thing to do is clear the Touch controller bindings and the throttle/collective binding in DCS, restart DCS and bind them again. Problem solved (without touching TARGET).

I guess you have an Oculus headset attached. There's no need to disabling the lua files. Just remove the compromized throttle binding, restart (!) DCS, bind the throttle again and you're good to go.

No no, the regular hand controllers that come standard with the headset.

In the latest beta the Oculus handcontrollers are introduced as inputs. They interphere with the regular throttle binding making the throttle axis (Z-axis) not working even when there is no double binding on the throttle control. Solution: Clearing out all Touch handcontrollers per aircraft and the throttle axis. Reboot the game, then the exclamation mark for the throttle is gone and then re-bind the throttle. Encountered with: UH-1H, KA-50, FW-190-D9, P-51-D, TD-51, Spitfire. (it's possible there are a few more, i don't have every module, looking at the ones i had problems with i guess the Hind, Mi-8, and the FW-190-A8 are also on the suspect list).

Wand-style? What do you mean by that? It are the standard hand controllers.

They put in the Oculus Touch controllers and they show up under axis. Unaware of this, i jumped into the UH-1H, fired it up only to find that the collector didn't respond. Into the controls section i saw a red exclamation mark on the collector input and also a Z-axis on the Touch controllers which was assigned for the collector (which is kinda weird because they don't had batteries in them so they should not show up). Clearing the Touch controllers didn't solve the problem directly, only a restart of DCS after made it work again. Weird thing is that, for the ones that i checked up to now, the Touch controllers didn't mess up any other aircraft.

Thanks for the heads up. Then i stick with the previous version now. I use the scratchpad mostly in VR and then that virtual keyboard comes in handy.

Is that the scratchpad version without keyboard...?

Exactly. But looking that even Intel has no intention for blocking crypto mining in their next video card line up (https://www.guru3d.com/news-story/intel-arc-graphics-cards-will-not-have-a-built-in-crypto-mining-lock.html), i guess more money is made from people buying stuff for mining then there is made from money made by gamers. And let money be the only thing that counts. In the end, something will break.

So i guess then that it's total battlefield data that's behind it, not local (like weapons and equipment on a particular airfield) since the icon stays in focus. Brings up another few questions: - I can't access it, who can? - If I can't access it, why do i get to see it?

What does this icon mean? I have no clue... It stays in the middle of the map when the map is slewed so it's not something at a fixed location.

Yup it roared it's ugly head again (you can bypass it by using Shift-Return) but i don't understand why somebody needs an extra empty line automatically after each return. You can simply press return twice if you need one...

@UPKEEP: Don't let the derailed discussion above keep you from doing multiplayer. Just do your thing. It's fun.

Can't help you with a group but... You can hop on any server without password restriction. - The star icon means the server is in your fav list (they will appear on top of the list when the serverlist is build). - The lock icon means you need a password (you need an invitation or join the group who runs the server). - The shield icon tells you integrity check is enabled which means in general you can't have any mods installed (some stuff passes, most doesn't). - The green dot icon says: Trial-only clients are allowed. it's something new, I have no clue what that means. If you select a server, on the bottom part you get info on what game setting the server is running (right side), in the middle the available aircraft which can hop on with a number behind it telling you how many slots there are for that type of aircraft. If you want to fly the Spit and the server has 4 slots for the Spit and these are all taken by other players you can't select a Spit in game until some other Spit flyer hops off, that Spit then becomes available again. The left part of the info is server info (together with SRS and/or Discord info) and connection info. As example i take the BlueFlag servers (who have a WWII server running). Once you hop on you need to decide if you want to fly either RED or BLUE side (mostly depending on the aircraft) by typing RED or BLUE in ingame chat. Once that is done you always play for your chosen side until the game (the battle can run for days on end) is finished. Then you can switch to the other side if you want (you can ask via Discord to change side while the game is running but this needs to be done by someone who controls the server data). Other servers may vary. Severs always have one player on board which means nobody is playing, the server is also counted as a player. Once the player count reaches 2 it means somebody is on board. Clicking on the map name colom will sort the servers according the map (other coloms will sort differently).

Those (and more) were already announced a few times (first time more then a couple of years ago) but always more important stuff seems to interphere. So just give it a few more waits and perhaps it might happen one day...

I use the regular mouse to do so. Works fine except sometimes for the comms menu depending on where the mouse actually is when you bring it up. If the mouse is to far off it will sometimes not switch from the blue cross (VR headset) to the white mouse dot. Placing the blue cross (with your head) in the vicinity of the comms menu and closing and re-opening again brings up the white dot again which then lets you work the comms menu. Voice Attack can be a big help but for some reason (my accent maybe) i can't get to work decently. Way to many wrong commands to my taste. For taking notes you can use Scratchpad: https://github.com/rkusa/dcs-scratchpad and bind the on/off option to a button on your controller.

It should not rotate at all.

You might get an answer here but best is to check the input / output section of the forum: https://forums.eagle.ru/forum/70-input-and-output/

Yes DCS VR still works, all "unknown sources" stuff works, software downloaded through the Oculus app doesn't work atm.

I was happy with V31 (on Rift S) but then i forgot to block the upgrade and when it upgraded to V32 i had again something... oh crap Oculus...(and no option to roll back) but V33 came quite quickly after that. Now everything is good again like V31 was. This time i blocked further upgrades. I'm gonna stick with V33 for as long as possible. How to block forced Oculus updates: https://forums.oculusvr.com/t5/General/Please-Stop-Forced-Updates/m-p/619275/highlight/true#M305739

Not sure what you mean by emulate here. At least i didn't emulate them into one device manually. That goes automatically once a script runs. Once a script runs it shows up as Thrustmaster Combined in DCS (if no script runs it are 2 separate devices). Other games are the same. If no script runs, it shows as 2 separate devices in TARGET Device Analyzer, if a script runs both separate devices vanishes in they but are not replaced by the virtual combined device. I was just wondering why not... In Windows Device manager, once a script runs a Thrustmaster Devices shows up containing 3 entry's: Once i stop a script, the above disappears again. This is what i believe is normal behaviour. The only thing that it doesn't do is show up in the TARGET Device Analyzer as a combined device. For the rest everything works just fine.

@352nd_Hoss: Thx for the input but that is not what i'm after. I have the TM Combined within DCS (i write and run my own scripts). Both stick and throttle show up as separate devices in the Analyzer (and in DCS) when not running a script but both vanish in the Analyzer when a script is run and are not replaced with a combined device. In DCS it does but not in the Analyzer. The things is that i never saw that combined device come up in the "Target" Device Analyzer and thought it was normal until i saw a picture here in the forum where it showed up as a combined device in the Target Device Analyzer. I have never seen the combined device show up in the Analyzer so i wondered why.

Well, it never showed the combined device in any way (and still doesn't whatever i try). Thought this was normal behavior when a couple of days ago i saw a screenshot with the combined device showing on the analyzer. I then had something like... WTF...