Lange_666

But it does and will do so in the future... and yes, i did read everything.

There's nothing to Wow about that, it is pure reality, like it or not (and i don't either but at least i know what to expect). When i get a new game/rig i start at the lower end of the settings and then i only go up and even then i make sure i have some headroom so i don't have to tickle the settings every patch. If you do it like most people, set everything to max and then have to go lower each time on your settings, dissapointement is your deal. That's my almost 40 years of gaming experience in a nutshell. Maybe but then...you are the one who seems to be dissapointed, not me. And i don't even have half the perfommance you have. I'm still playing....

No you don't but you've become at a point that performance will go down, don't expect it to be the other way around. And, you're still running an "old" 9900 when a 12900 is just around the corner. Time to cash out man, that is how pure capitalism works.

Still: Going back a couple of years: - Intel 950 - GTX480 - 8GB RAM: Oh wow, i can as good as max out everything. Then after some updates sliders and settings needed to come down, step by step, to keep that FPS up and up to point where an update was need ed to keep it running smootly and decent eye candy. - Intel i7 4770K@3.5Ghz - GTX 780 - 16 GB: Oh wow, i can as good as max out everything. Then after some updates sliders and settings needed to come, step by step, down to keep that FPS up and up to point where an update was need ed to keep it running smootly and decent eye candy. - Intel i7 4770K@4.5Ghz - GTX 1080Ti - 32 GB: Oh wow, i can as good as max out everything. Then after some updates sliders and settings needed to come down,step by step, to keep that FPS up and up to point where an update was need ed to keep it running smootly and decent eye candy. If everything should run on old computers i could have kept my Commordore C-64, even my VIC-20 before that. I'm now at the point where i'm thinking about upgrading again to keep up. Problem is this: Just looked at a 3090 in my local store, 2 available, one at 2899€ (inc VAT) and the other at 2999€. And then i can't get by with a 3090 alone because it doesn't fit in my current case. So a total upgrade comes to mind. I made a list with prices a couple of months ago, today i need to cash out around 1000€ extra just to buy the stuff on that list and then it contains "old stuff" like DDR4 RAM and 11 gen CPU. Same goes for a decent motherboard. No way i will cash out that amount of money to get an update. In that other civil sim i'm down to a locked 30FPS to make it run a bit smooth and still have "some" nice graphics. It's happens not just with ED, it happens in every "demanding" game.

Have you ever seen something heavy running decent on a virtual machine?

Well, hasn't it been always like this in the past? If no, then why did i buy a new PC every few years (counting back to early 1980's). I tell you... just to keep up with ever more demanding software. It happened then, and it still happens today and not only on ED's behalf. Only drawback (and holding me back to upgrade) are the superhigh prices of hardware these days.

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.