rob10
-
Posts
3375 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Posts posted by rob10
-
-
54 minutes ago, DarkSideMaster said:
Problem solved
It's great that you came back that you solved it, but it would be much more helpful if you had mentioned HOW you solved it (even if it was something simple that you were missing) to help the next person that runs into this.
-
3
-
-
IIRC ED has indicated they currently have no plans to add land arresting gear (or it's very low priority). That may change down the road, but don't expect it currently.
-
Maybe try some plumbers tape on the threads to tighten things up a bit.
-
1
-
-
A polite suggestion if I may: please look at the forum for an answer before you start a thread asking. The thread about this issue has been in the top 5-6 threads for a while and is labelled "Latest Oculus v63 PTC build crashing DCS when used on Oculus Link" so it should be pretty obvious what it's about.
-
2 hours ago, Flogger23m said:
Is this still an issue with Quest VR headsets, including the Quest 2? Is there anyway to not auto updated Meta VR headsets? Or is it mandatory each time you plug the VR headets in it while having an internet connection? If so seems like a massive oversight.
Yes, No, and see earlier parts of thread to avoid it if it hasn't already automatically updated you.
Unfortunately when it's two unrelated companies and something that only effects a subset of users it's hard to not have hiccups like this. -
As Razor18 said above, you're likely doing a CASE 1 recovery in which case you'll get a different menu (the one you're seeing). Set the mission to night time or really poor weather and you'll get CASE 3 which will give you the menu you're seeing in that menu.
-
Check that thread for solutions other than waiting for the next DCS patch (likely 3-6 weeks away, might come sooner), but there is no easy way to roll back.
-
1
-
-
PTC on/off is no longer relevant, they have pushed the update that breaks DCS to release. See this thread.
-
1
-
-
11 hours ago, Sandman1330 said:
Thanks. To be clear I'm not looking for any assists or tricks - I can AAR, I have always been able to AAR, and have no interest in using autopilots or tricks to do so
My stick is a Virpil Warbrd, so good quality.
I'm just wondering if anyone knows if the flight model is going to stay this way or not (ie was it intended behaviour). It seems you've noticed the change as well, though from my perspective it feels like lag (a delayed response to control inputs), where you don't perceive it that way. It just feels "spongy" now. I don't recall having any delay to fine control inputs during the real formation flying I've done, though it's been awhile to be fair and it wasn't in a hornet
At least I'm not alone in knowing something has changed!
Do you have any curves or deadzone set (I don't)? It's definitely different, but IMHO it's MORE responsive rather than laggy so easier to get into PIO. It also doesn't have the bit of "rebound" (for lack of a better word) that it used to have when you let go.
-
1 hour ago, Qcumber said:
@BIGNEWYAre there any logs I can share which might help solve the issue?
Pretty sure the "fixed internally" tag on this thread means that they have it solved. It's not released yet because they have to test that the fix doesn't break something else, as well as test whatever else was added to the build. It's good to see people who will to try and help out though!
-
2
-
-
Have you tried ticking the "SLIDER" box in the axis tuning?
-
2
-
-
2 hours ago, Dangerzone said:
Not sure where the paranoia is. It would make marketing sense to exclude something that could be included in a release of a module to encourage sales. I'm not saying that's what they're doing - but I'm not saying that it's not a possibility. If anything, I'm being optimistic - not paranoid - because I'd be delighted if we end up with these features with the CH-47 and C-130. That would be far better than the alternative that you're suggesting - that it's not worth the effort for them, and we'd never see it.
Fair enough. I was just meaning that ED typically doesn't withhold new functionality unless it takes a lot time/effort to develop (a la the supercarrier).
-
2
-
-
2 hours ago, BIGNEWY said:
Ok, lets clarify, the team have replied.
In CCIP and Auto when releasing more than pairs the aim / release point should be centre of the target group.
And to clarify your clarification
, that means that 1/2 the released bombs should hit BEFORE your aim point and 1/2 AFTER?
-
23 minutes ago, Dangerzone said:
It may be that ED doesn't want to include general units being able to rearm/refuel/repair aircraft outside of FARP's due to marketing reasons. (ie - they may be planning on having this feature exclusive to the CH-47 to encourage more sales), although this would only really work in MP environments, and the general consensus is that MP is only a fraction of DCS sales, so who knows.
That seems a little paranoid. Theoretically a guy with a backpack could hike 30 miles from the nearest base to fix it depending what the issue was. I really can't see why they would restrict rearm/refuel/repair for marketing reasons. I suspect it's more down to doing it somewhere else being not highly requested minor case so not worth the effort.
-
2
-
-
49 minutes ago, Shrike88 said:
Any update on this bug ? Seems all of my triggers when using delayed activation on the F-10 radio command / Mist script using the Radio are still broken.
What exactly is happening? Most of the trigger bugs were that it was firing immediately when it shouldn't have and that was fixed in the last patch. What you are describing seems to be something different. Throw your mission up and someone may be able to point to your error.
-
3 minutes ago, Doc3908 said:
Had this issue a few weeks ago and switching off PTC on the Oculus app seemed to do the trick then. I was out of town last week and hadn't touched DCS. Just tried to start it today and now the problem is back (even with PTC off). I'm trying to read through the threads, but there doesn't seem to be a universal solution. I'm guessing that the majority of people playing VR use Oculus, so this affects not an insignificant number of DCS players. So, my question is simple: When do we expect a reliable ED fix for this issue?
Since you last used it Oculus pushed the problem version (V63) from PTC to RELEASE version so there is no simple rollback option.
ED have said they will release the fix when they get finished testing it and whatever other changes are in the build. Could be next week, could be 3 weeks from now.
-
3 hours ago, Tea-Pig said:
Does this not defeat the whole point of 2FA, or are we taking the view that hackers wouldn't have DCS installed?
No, because with 2FA disabled they can't do whatever they were doing to run trials multiple times likely. From the way I read it, that post is just about how to disable 2FA.
-
From that pic, you're not assigning it as an AXIS, you're in the keybind section. Where you are searching for "throttle", instead of choosing "search" choose "Axis Commands". It will give you a whole different set of binding options that will allow you to bind it as an AXIS (not a keybind which is the section you're currently in).
As was mentioned above, look for the THRUST binding in AXIS COMMANDS and you'll get what you need.
-
6 hours ago, Raviar said:
for the 1st time since almost 2 years I have recieved warning from Kaspersky which detected trojan "trojan-PSW.Win32.Stealer.calj" in SimAppPro Setup 1.11.6.exe file! I have never recieved it before
If it's Kaspersky detecting it I'd be checking with something else before I believed it was trojan. It seems to have way more false positives than many other AV's. And no, it's not the others missing things. Every once in a while it screws things up for people with DCS updates (and has for many years).
-
1
-
-
1 hour ago, skywalker22 said:
Yes, I could say so. But that ghosting this is way too obvious to use DLSS. I will when is it gonna be fixed.
Out of curiousity, did you try DLAA alone (without DLSS)? It might be a reasonable tradeoff for you. Not sure the ghosting with DLSS will ever be "fixed" as that's apparently a side effect of how it works.
-
1
-
-
1 hour ago, Mikla said:
Yep...ED seems to have snuck this change in as it now says "Attention! After the link is done you will not be able to use your Steam DCS account unless you unbind!" Typical money grap BS. Sorry, ED, uninstalling standalone will limit my future module purchases.
The only way this is a money grab is if you were letting someone else use your Steam account while you were using your standalone or vice versa (so now you'd have to buy a second copy so you could both play). Otherwise I also fail to see how this is a money grab. People doing that is why it was changed to the way it is now. You can use it on EITHER Steam or standalone and you can swap between the two, you just have to jump through a couple of hoops to do so.
-
1
-
-
1 hour ago, evanf117 said:
ah, ive always just used a truck, a Humvee and fuel
This is a really good guide as to what is absolutely necessary for various functions. It also has "current" unit names (which the DCS documentation doesn't currently)
www.digitalcombatsimulator.com/en/files/3318569/
-
1
-
2
-
-
Check this and related threads. Basically Oculus V63 is almost for sure causing your issue.
-
7 hours ago, draconus said:
Your 45fps 80% is not very detailed either. There's always some set of options and mission/place which can put any PC to its knees. Lower the settings and you will get performance back. And I wouldn't expect anything near 100% boost with Vulkan.
People seem to have overblown expectations for Vulkan. ED has publicly said on these forums (BigNewy or NineLine IIRC) that it will be good to have, but it's not going to magically cure all issues people have with FPS. It will be another step forward, not a gigantic leap.
-
1
-
Create Fast Mission, Crashing during mission creation at 9%
in General Bugs
Posted
Interesting. I just had this started happening to me in the last couple of days (at least I noticed it then). Exact same symptoms. I hadn't had time to look into yet because I was just using it to check something in plane rather than actually flying a fast mission. I wonder if a Windows update is causing an issue. Strangely, although it's happening on my gaming computer, it's not happening on my laptop that I use for editing missions