Jump to content

Baldrick33

Members
  • Posts

    1789
  • Joined

  • Last visited

Everything posted by Baldrick33

  1. It didn't really start very well - " No BIG updates on FRIDAYS anymore please -The title says it all." Assertive posts with capitalisation for emphasis to make demands tend to draw assertive responsives from those who may not agree with the premise. I think the rationale for why updates should not be delayed beyond the weekend due to the numbers that will be able to benefit from it and speed up the process for feedback to progress the development have been well stated. I believe it is also understood that mid week updates are the developer's preference just that sometimes that isn't possible. I believe most of us want to see DCS World develop at the fastest possible pace within the bounds of what we might consider acceptable risk. Of course this is also a multiplayer game which has a devoted following for whom an incredible amount of effort goes into organising their time together, which is a great experience. In mine (and others) opinion on this thread that effort would extend to patch management and doesn't seem an unreasonable task. From my personal experience of running in sim racing online leagues for over a decade, the majority of which I was the league admin, I would see that as a necessary and relatively trivial task.
  2. The process is to promote Open Beta to Stable as and when it is considered suitably bug free and performing well enough. This will take a variable amount of time depending upon issues encountered. A major update like 2.7 to 2.8 typically can introduce more aspects to resolve for example VR performance in 2.8. Until these are resolved then it should not be promoted to Stable.
  3. The current stable version was released in October, the sixth release in 2022, so your 12-24 months comment is wildly incorrect. The issue with using Open Beta is it can change more frequently and at times that impacts multiplayer as servers and clients transition and are out of sync. Having a known quantity that changes less frequently and has any show stopper bugs squashed would resolve that. Players will go into multiplayer post open beta patch with no knowledge if changes to say missile systems will affect the balance of aircraft nor if their PC will crash when they hit fire. Whilst stable may not be 100% stable it has gone through the layer of open beta testing before being promoted. Now as stated the desire to have what some consider vital improvements which have been incorporated into open beta are considered worth the risk. Yet there needs to be an understanding and acceptance of those risks. Be it servers being out of sync version wise, or game breaking bugs two hours into a complex multiplayer mission. I think it is generally understood but there will always be those who choose to complain - when running a beta version.
  4. The biggest issue is the fact the vast majority of the multiplayer community has adopted Open Beta as a standard. I am sure there are many historically good reasons but it is in conflict with the whole concept of an open beta where there are frequent updates and stuff regularly gets broken to some degree. Now it seems the multiplayer community have accepted the risks and the benefits of the latest beta version with fixes to imbalances, new features and the latest aircraft updates outweigh using the stable version and they deal with the challenges of version control and occasional "bad" update that needs a hotfix. IMHO the responsibility lays squarely with the multiplayer community to manage their beta installs and the lack of consensus with your post suggests they don't see it as ED's job to bend over backwards for them at the expense of the wider user base.
  5. The risk of a Friday release is always going to be the limited resources over the weekend to fix any real showstoppers. That said rolling back isn't exactly the hardest of challenges, just a bit frustrating and time consuming if it goes horribly wrong The vast majority of DCS players play single player so most would welcome shiny new stuff for the weekend when they typically have the most time to play. Having patches delayed for an Open Beta program for client run multiplayer events makes little sense to me. The server owners have complete control over the version they run and a simple process of go/no go is all that is needed. Heck we did it in online sim racing leagues over two decades ago with Grand Prix Legends and dial up modems!
  6. Not a desktop icon but I typed in Openknee in the Windows search (bottom left task bar) then right clicked on the App in the list and pinned to Taskbar, which was all I wanted.
  7. The change log for Open Beta is pretty substantial. Which always adds potential for new issues to be highlighted as part of the open beta process. How long it might take for these new and as yet unknown issues to be resolved, along with resolving already highlighted issues in 2.8 would seem at best an educated guess. I wouldn't expect an ETA at this stage.
  8. Buying standalone, once logged in it will show the discount. Which seems pretty generous! Not sure if buying through Steam.
  9. Nice one! That must be a relief to find.
  10. It changed after you edited your post, I am sure it was fine when I first read it and replied.
  11. @jonsky7that is a more elegant explanation My original idea of using a redundant control was based on an early collective solution I bodged up. I had a CH Flightstick which I removed the springs from and installed it horizontally to act as a primitive collective. Of course it would drop if I let go of it. So I used a modifier button to "lock in" its position prior to letting it down to free up my left hand. The modifier was used with the Y axis to switch it to an unused camera control, leaving its position as a collective frozen. I would then pick up the collective to roughly the last position and press the modifier again. It worked pretty well. I now have a Virpil collective which of course is much better but my bodged CH stick collective served me well in the interim!
  12. One of the benefits of VR is we can easily break away from location of the PC to some degree. My rudimentary "cockpit" may not be as flash as some but it is away from the desk I am typing this. I don't need or want a conventional mouse for flying in DCS, it is neither convenient nor an immersive solution. The transition from flying at a desk using a keyboard and mouse as an interface to being constricted to a headset where you can't see your controls can seem daunting. The solutions not only work well but IMHO improve the overall experience to the extent using a mouse and keyboard seem rather obsolete.
  13. You can try editing your local files as per my previous post. I don't have the Blackhawk mod so you will need to find the abbreviated name used (try the kneeboard folder)
  14. If you want to have both the twist axis and pedals axis available you can use a modifier (as a switch) to move the twist axis to something you don't use. E.g. map the modifier+twist axis to an unused camera control. When you press the modifier the twist axis will no longer control the rudder and you can use only the pedals. Press the modifier again and the twist axis and pedals are both enabled.
  15. I see. The op describes deliberately losing tracking to reproduce the issue so assumed it must be momentarily losing tracking when it occurs in game.
  16. It may well be. My last experience of losing tracking was due to failing Reverb G1 cable. I never got this issue of the VR centre resetting, just the tracking failing to keep up (which was pretty nauseating!). This was many DCS builds ago so it is of course possible something has crept in. It could also be something different in the way that the Oculus software interfaces with DCS compared to WMR. My experience with losing tracking in any game is that it is horrible, so even if the game assumes you haven't moved your head in the meantime I would be desperate to fix the loss of tracking but any solutions to better cater for it happening would be worth pursuing for sure.
  17. I am not sure how much the application handles tracking but simply hand it over to the headset software. Yes we can reset tracking manually but I would be surprised if DCS is resetting it sporadically, rather that the headset software layers be it Oculus, WMR, SteamVR, OpenXR etc. are updating the tracking info and sending this back to the application (DCS). Of course it could be in the DCS code in which case I will be flat out wrong but my experience with other games has all come down to the headset and how its software copes with not getting a fast enough flow of data for tracking.
  18. Yeh it sounds like it should be working as you want - select axis or buttons as you wish.
  19. By reducing settings I meant simply to see if that fixes the tracking issues. If it does then we need to dig deeper into priorities of resources.
  20. I still think it is load on your PC causing the tracking to not be able to keep up for a split second. 2.8 has increased the load for VR compared with what you were running and maybe tipping it over the edge. You could try reducing some settings and see if it stops the tracking issues? If 2.8 had introduced a tracking reset bug I would expect it would be happening for everyone
  21. I have previously had some tracking issues (Reverb G1) that were resolved with my hardware. USB connection in one case, replacement G1 cable the other. The reason I think it can seem like DCS because it works fine in other sims is the issue is more apparent when the PC is on its limits - the PC reaches a point where it momentarily loses connection to the headset and the tracking resets. In my case I had the same issue with iRacing. One other thing to check is whether you have game mode on in Windows. Whilst this prioritises resources to the game in some cases it can take too much away from the VR software, again causing a temporary loss of connection in heavy usage scenarios.
  22. New to Virpil software so definitely no expert! I just added buttons to the mini stick by using the axis to buttons option like @dburne if you have no axis currently I would guess you have unticked the x and y axis for the mini stick either in the axis screen or calibration. Turning them back on should give you dual function if that is the case.
  23. Most mods I have seen for the Warthog stick are to make it lighter, so it is a little surprising. Is it a stock stick without an extension? You can get a stiffer spring (usually to go with an extension) Springs – Warthog Extensions by Sahaj (warthog-extensions-by-sahaj.com) Also the four small springs underneath the base, offset the big spring. Replacing with lighter springs or even removing them completely will make it stiffer.
  24. Is there a gaze pointer settings option with the Quest 2? I seem to recall an option to select items (equivalent to using the contoller laser pointer and clicking on it) just by gazing at it for a set period of time. Please don't!
  25. You talk as if DCS is devoid of weather effects. One of my quick test missions for setting up helicopter controllers is the Persian Gulf ship landing hard or something similar in the Huey. The conditions are variable and sometimes very stormy making it far more difficult and challenging. I understand you are looking for more specifics but if you want to make it harder with weather effects there is a lot already there at your disposal. You won't likely see it set on the multiplayer servers but that is not down to ED.
×
×
  • Create New...