Eclipse

I have noticed this issue, as well. It settles down after some time, but in the meantime frame time spikes and tearing are pretty bad.

I know how development works, thanks. I'm done with this pointless argument. Have a nice day

^ what he said Initially ED only planned for the Black Shark, none of the rest of it existed. There were no other modules. Plans changed, and they developed it into a platform that supported other aircraft as modules. Multiplayer was not included in the beginning, it was single player only. They changed their plan and added multiplayer support. VR did not exist yet, but the changed their plans and added VR support. Also, all third party development is done with ED's support. No third party is developing something ED does not want them to develop. Your argument is invalid, sir. We have late war pretty well covered on both sides. Having a mid-war Bf 109-G to go with the allied mid-war modules like the Spit and eventually the (exciting) La-7 would be a good thing. Having a Bf 109-E or F-2 or something to match up with the I-16 and the Mosquito would be a good thing. If you can't understand that I don't know what to tell you. If you disagree that's fine. But I agree with the OP, a 109-G would be a nice addition.

I'm aware of the recent improvements and the roadmap for future improvements like the General Flight Model, and I'm very much looking forward to all of it. Considering that ED develops the Digital COMBAT Simulator, I think it's fair to say that developing modules that would make the combat more authentic would only benefit the sim. And I am speaking about people who have said the actual words to me "I won't spend the money to go to DCS until they have more planes that "go together" historically", and I've read that same sentiment from others, some who represent some large and well-known groups. Whether that sentiment I've read more than once from more than one source is still accurate I don't know, but I heard the words with my own ears about 2 weeks ago. It's a logical point, whether or not you agree.

I was speaking about those who refuse to try DCS WWII for the reason I mentioned, so yes, necessarily. And no the Sabre and MiG wouldn't see more action, there are many reasons why that doesn't make sense - Korean War interest VS WWII interest, and the known issues with the AI flight modeling that are known to be significant and cause UFO behavior in the AI MiG, to name just a couple.

Most DCS players play single player only. The source for "most play only single player" was ED themselves, though I don't remember the exact context. In my experience people want accuracy and an authentic exoerience. But then again I wouldn't pay much attention to the users you mentioned, maybe there are more of them than I realize Having said that, now is a great time for a G6, and sooner would have been better! I fly with some and have spoken with others that pretty much refuse to buy into DCS WWII until there are more complete "plane sets". For an obvious example, what is an I-16 going to compete with, a K-4 and D-9? Not having pairs or sets of opposing aircraft that match each other in terms of their historical service periods is a big put off to many who would otherwise fly DCS WWII. Filling out the modules set to allow authentic matchups for early, mid, and late war scenarios in different theaters should be a very high priority. Things are coming along very nicely so I hope this is ED's plan!

It would be great if the fuel pump switch was mentioned in the manual. They left it out completely, no mention of it anywhere that I've found, besides the cockpit layout with the tag that identifies it as a fuel pump switch. It should probably be one of the steps in the startup/takeoff sequence... But at least now I know why my engine was cutting out at higher altitudes even after switching the fuel pressure valve on once the low fuel pressure light lit up. Thanks!

The controls setup in DCS isn't completely ideal, but it is miles ahead of some others. The ability to set modifier buttons and the support for multiple simultaneous presses are a big deal that are not present in some other sim products. I think the settings being how they are is partly due to how DCS evolved. Originally, there was only 1 module. In fact, it wasn't even a module, it was simply its own, stand-alone sim product, the Black Shark. Everything else has been "bolted on" to that original engine over the years, and the engine itself has been "bolted onto" a lot. The current efforts underway are I think the first real, from the ground up rewrite of the engine. So far, so good on that front! To address some of your points: First, regarding your points 1 and 2, I agree it would be nice if common features were in some general category that would only have to be mapped once across any aircraft that had those features, but only for VERY general things, like kneeboard, View controls, etc.. And there aren't that many of those things. I like to have my controls set up reasonably close to how they are on the actual HOTAS, and not every aircraft controls the same/similar function in the same way. Even something like wheel brakes or how a bomb is released can be very different. Wouldn't a cockpit user have even more things to consider mapping more closely to how/where the actual controls are in the actual aircraft? Also, if you have to reprogram something every time you switch to a different plane, you are doing something wrong. You of course have to make assignments THE FIRST TIME you fly a different plane, but no more than that. Second, regarding your point 3, yes, by default DCS will assign the same functions to multiple controllers. It isn't tedious to resolve, all you have to do is click the top of the column for each controller (where it has the controller's name) and click Clear Category. This removes all control settings for that controller. Do it once for each controller in "All but axis commands" and once in the "All axis commands" areas, and then you'll have no redundant, nonsense, conflicting default button assignments to contend with. It takes about 30 seconds. I would prefer that there were NO default button assignments at all. They don't make any sense, there are conflicting, redundant assignments, and no one would know what they are unless they looked. And if they looked it takes only seconds to assign it to the button or axis you actually want it on anyway, so why have all those defaults?

I would say put it wherever is comfortable. None of us are sitting in a recreated cockpit (OK, so maybe a couple or 3 of us might be, but certainly not me!), so concessions have to be made. Whatever position allows for full range of motion in a comfortable manner while not being a strain on your arm or shoulder during a longer session is a good position. I have the stick in the center, sitting on a keyboard tray that is a drawer with a flip-down front. The throttle sits on a guitar stool next to my (amazing) Secret Lab chair, and my rudder pedals sit on the floor with a wooden backstop I made to keep them from pushing towards the wall, and with the front propped up a few inches to adjust the angle of their travel to better suit having my chair at a good height for comfortably using the stick and throttle. The resting position for my right arm (not pulling or pushing the stick) has my elbow maybe a few inches forward of where it would be if it was hanging completely relaxed at my side, and my forearm is about parallel with the floor. My left arm is able to sit comfortably on my arm rest with the armrest adjusted for use of my throttle, with just about the perfect height and angle. My setup overall isn't 100% ideal, but it is a fairly neutral position with no strain and it is comfortable for long sessions, so replacing my desk and getting specialized mounts for my joystick and throttle isn't a priority over spending that money on upgrading my system and peripherals. Hope that helps

This is still an issue. Also, in addition to the changes made to the UI Layer - VR Motion Controller category not persisting, if I clear the default assignments and save a new profile for the UI Layer - VR Motion Controller category, the file does not get created in the InputUserProfiles folder (with that folder selected as the save location). I just tested with the latest update installed and after repairing my DCS installation (the full, long repair), and here is what I observed: While on the main menu screen: go to the controls menu, select UI Layer, deselect "Foldable view", observe 3 existing, undesirable control assignments in the HP Motion Controller column click the column heading for HP Motion Controller, select clear category, select "yes" to accept the change, then click the green "OK" button to close the menu reopen the controls menu, deselect foldable view, and observe the original 3 control assignments un the VR Motion Controller column have returned While in a mission: go to the "Adjust Controls" menu, select UI layer, and clear the default assignments as above reopen the "Adjust Controls menu, observe the default assignments for VR Motion Controller have not returned exit mission, load another mission, check the "Adjust Controls" menu, observe the default assignments have not returned Close DCS, restart DCS, check the controls menu, and observe that the UI Layer default control assignments have returned again To summarize, changes made to UI Layer - VR Motion Controller assignments do not persist properly, and saving a profile for UI Layer - VR Motion Controller does not create the file in the InputUserProfiles folder. Other control assignment categories work properly, in my experience. Thank you

I've read from multiple sources that the seeker is indeed different. I'm sure there are other differences as well, as you mentioned.

I found that the best way to fix this is to stop using the infrared MAV-F against that type of target. Use the laser-guided MAV-Es for armored vehicles and other small ground targets. I've read that the infrared mavericks were designed more for anti-ship use, not for ground vehicles. My own experience with them suggests the same. It's unreliable and fussy trying to target ground vehicles, and you have to get pretty close (8-10nm or so) to get a lock in my experience, if you get one. You were obviously close enough at 1.5nm distance, so the missile was just not getting a lock. This is from Wikipedia, and it specifically says the seeker is optimized for tracking ships: Maverick F, designed specially for United States Navy, it uses a modified Maverick D infrared guidance system optimized for tracking ships fitted onto a Maverick-E body and warhead. I didn't like the Maverick's until I switched to laser-guided MAV-Es, and now I think they are fantastic. I haven't tested the MAV-F against ships, since so far ships haven't been targets in any mission I've flown. But I bet you would find that the Fs work much better against ships than they do against ground vehicles. Hope that helps

Welcome! Coincidentally, I bought my HOTAS for Star Citizen after pre-ordering a starter ship in 2012, thinking then that it would be released "soon"... a little off target there. No more pre-orders for me! I also played enough War Thunder to pretty quickly want to try something more authentic, so I tried Il-2 Sturmovik Battle of Stalingrad and then DCS, first the free Su-25 and then the P-51. I knew next to nothing about flying and I was excellent at crashing on landing and pretty clueless in combat, but I was hooked, too. And once I went to VR there was no going back for sure. Fast forward 10 years and a ton of reading, research and practice later (which I've thoroughly enjoyed), and DCS is better than ever with a lot more on the horizon. Good luck with the PC build!

Good luck on the journey. Once you go VR you'll wonder how you went without it this long and you'll not want to go back, even if there are some compromises. One thing to add, for controls - I have everything that is on the HOTAS in reality mapped to my controllers, and some other commonly used items or items that are hard or finicky to manipulate in the cockpit. For almost everything else, I use my VR controllers to point and click, flip switches, turn dials, etc. I use the mouse for things in a few cases (like the rearm/refueling window) because it's faster. But for most cockpit controls I use my actual VR controllers. I have one sitting to the left of my throttle and one to the right of my stick, in quick and easy reach. Just wanted to make sure you knew they are an option.

The biggest downsides I experience while using motion reprojection are: "ghosting" contacts that are moving across my field of view, which makes it hard to ID a warbird within visual range. The bogey is quickly, constantly jumping a little forward or backward with each frame as the actual position is updated every other frame. And the propeller artifacts can be a little annoying to track a target through. This seems to be more an issue in certain RPM ranges. I do use reprojection "always on" at this point, because without it the experience is just not smooth. Rolling around in an engagement the framerate hitches pretty badly making it near impossible to keep a tally on something below you. With motion reprojection on, it's MUCH smoother, but then the two issues above are present. But, I'll deal with those issues until VR rendering is sorted out better. And I have no doubt it will be, between squashing bugs in the new mutlithreaded code and new techniques and enhancements that are in the works.

@cfrag You may have just changed my life now that I've discovered DML! I'm once again amazed by the tools developed by the community. Thank you!

Welcome to DCS! The first thing I recommend that you do when setting up any new aircraft is to clear out all the default control assignments. In my experience, they will only cause you problems. They make little sense, and you'll have things duplicated across multiple controllers (in the case of CH gear and the Reverb VR controllers), plus you won't know what the assignments are anyway if you didn't assign them yourself. Save yourself some headaches and clear all the defaults, then assign things as you learn them. To clear a controller's assignments, make sure you have the controls menu set up to see the full list of assignments, and then click the name of each controller at the top of its column in the controls menu and select "clear category". Do this for all button assignments and axis assignments. Once the slate is clean, then set up your axis controls (pitch, roll, yaw, throttle, etc.). Then as you learn the aircraft add the necessary HOTAS commands. Keep in mind you can click (via mouse or VR controller) to interact with buttons and switches in the actual cockpit (except in older, lower fidelity modules), so not everything needs to be bound to the HOTAS. I fly in VR and I only bind things to match the actual HOTAS in the aircraft plus whatever controls I need fast and reliable access to in the heat of an intense situation, especially if they are finicky to operate with the mouse or VR controller. And a cheat sheet helps - I have an Excel document with a picture of my controller and blanks for the buttons and switches that I fill in as I assign or move things. It makes coming back to some modules after a long break much easier. Plus, I can more easily map all the functions that are common to any aircraft the same way in every module as I get new ones. If you decide you need or want some software in between your controllers and DCS, I can't recommend Voice Attack enough. Even if you don't use it for a single voice command, it is easily the most fully featured and capable software out there that I've used, and I've tried Joy2Key, Joystick Gremlin, and others. It's well worth the $10, and I haven't used a single voice command yet. I use it in Il-2 but haven't needed it in DCS thanks their more robust control mapping with assignable modifier buttons (like setting a "shift" button). I hope this helps. Good luck and enjoy!

There are instructions in the multithreading FAQ post that is linked in the changelog. Here is the Multithreading FAQ link they provided.

Maybe try repairing your DCS installation? I updated earlier and the new bin-mt it there (for me, it's "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt"), working as advertised. Type "repair" into the windows search bar, and Repair DCS World Open Beta should come right up. Good luck

Have you tried using SteamVR to see if the you see the same behavior? I don't have a solution for you but testing whether the same thing happens while using SteamVR could help pinpoint a problem. Good luck

I too had ditched the glitchy CH software that is no longer supported long ago. After trying multiple replacement key mapping products, including Joy2key and Joystick Gremlin, I settled on VoiceAttack. I don't even use any voice commands right now, and it is still hands down the best product out there. I use it in Il-2 and have functions grouped to different 4-way hats. A left or right press cycles between the different control functions on that 4-way, and up and down buttons change the value or activate a function. The best part - VoiceAttack speaks the function I switch to as I press the left or right button. This greatly eases how much you need to remember. It was $10 very well spent, I can't recommend it enough!

It was very worthwhile - installing the latest OpenXR Toolkit version FIXED THE ISSUE! I didn't even think to check it since I haven't actually done anything with it. I have no idea why OpenComposite would work but native OpenXR would not, but I successfully joined a server using native OpenXR in 2 of 2 attempts after updating to 1.2.4. THANK YOU! I'll edit the thread title to show it is solved. And thanks again to everyone else on this thread. As usual, the community here did not disappoint. I really appreciate everyone who took the time to try to help!

I just attempted and it's still no good. I started DCS with the OpenXR Toolkit in safe mode, reset to default settings in the Toolkit menu, closed DCS, disabled safe mode, restarted DCS and attempted to join a server. DCS still stopped responding while loading the mission. Thanks again for trying to help

Your problem is different than mine - I never get to the Fly button. DCS stops responding part of the way through loading the mission. I'm just glad OpenComposite still works. If I try rolling back the GPU driver or anything else I'll post the result in case it helps anyone else. Likewise if I try native OpenXR after a system or DCS update and find that it works again. Glad you got your issue sorted out!

I do have the OpenXR Toolkit installed, but everything is set to default. I tinkered with a few things but never saw anything improved both visually and in performance, there was always too much of a tradeoff. So I reverted everything back to default and have tried any more tinkering with it since probably 2 updates ago. Also, I was able to switch from OpenComposite to native OpenXR before without issue, I didn't have to reset anything. And with this issue, I now launch using OpenComposite without a problem, without resetting anything. Maybe I've misunderstood the point of what you suggested, but I don't see how it would apply to my situation. Thanks, though!