rob10

Are you using the latest Occulus Beta and Open XR? If you disable OXR you can use the latest Occulus, or you can use an older version of it and OXR. Current known issue on Meta side.

Have you tried RIGHT clicking in the box you want to bind it to and manually selecting the appropriate binding? Since they seem to be working (show in SimAppPro) it seems like DCS isn't recognizing them for binding purposes (which happens occasionally) so you need to bind them manually.

Click on the big red banner at the top of your screen that says "! Authorization issues" and you'll see it's an ED issue that they're working on.

I can completely agree with your contentions about the advantages available in VOLUME manufacturing, BUT I really doubt that any FFB joystick is really going to actually be volume manufacturing. It's a pretty niche market of what's already a niche market ("near replica" controllers).

I think this is the part that trips people up. You can't control the ship if you're in a plane slot, you must be in the AirBoss slot.

Just realized that I ran into this on Green Line campaign. I got the "mission complete" message in game but noticed it hadn't marked the mission as complete when I went to continue the mission. It's possible to continue simply by skipping the mission in the selection screen.

That's a long standing known thing. Track files strictly record the inputs and attempt to recreate what happened (it's a debug tool, not a recording tool). It is NOT and is NOT claimed (by ED) to be replay tool. Because of if conditions during when running the track are even slightly different (i.e. a tiny desync vs original or a random condition that doesn't fire the same way) you can end up with completely different results.

I'm not really familiar with using ground power, but using instructions found on the forum I'm seeing the same: they won't stay on even when held for 3+ seconds in F-18. Tried it on a random cold start mission in Marianas and quick mission on Caucaus and same on both too.

Did you see an explosion? That sounds like a fusing error causing a DUD bomb.

Definitely seems like that's the case. I'd check it in whatever the software is for your stick and see if it's showing multiple inputs.

So if they are axis controls there is no way to bind left rudder and right rudder separately. The rudder axis command needs a middle/centre/neutral point where there is no rudder input. If you had separate left and right what should it do if it was getting input from both axis? I guess if it was getting inputs from both it could just ignore both (I assume that's what it would do with conflicting button inputs). But virtually anyone that's looking to bind it to an axis is only ever going to want to assign it to an axis with a centre point so that's why there is only one available. Fortunately, for the Hornet you really only need the rudder for turning on the ground. I would bind two BUTTONS, one for Aircraft Rudder Left and one for Aircraft Rudder Right to turn with.

That's only true of the exact location of WP0. There is nothing to say that WP0 can't be deeper water than the areas between it and the open sea. The channel between starting point and open sea not being deep enough is very likely the problem. Posting the .miz with this happening would be helpful for troubleshooting.

Check your antivirus and/or Malwarebytes.

Post your logs. There are lots of reports of anti-virus quarantining files that are giving similar symptoms. Also, are you on the beta stream for that? The new version (V68) is still not compatible with DCS (as mentioned in the release notes).

Post your logs. There are lots of reports of anti-virus quarantining files that are giving similar symptoms.

Thanks for that. I didn't really dig back through the post so I didn't catch that.

That is working as intended. If you have a TARGET DESIGNATED it will always keep you in CCRP mode, even if you try to change to CCIP. If you UNDESIGNATE you'll get CCIP targeting option. This should be true with clusters and any GP bombs. I haven't see the video you mention in your 2nd post, but I presume that he undesignated the target as he rolled in and lined up. It would then switch back to CCIP mode.

Post a track and someone may be able to point what (if anything) you're doing wrong.

I don't know that controller but are L2 and R2 actually axis controls or are they buttons? If they're buttons, you DON'T want to bind them as an axis but in the main bindings as Aircraft Rudder Left/Right.

The solution for this needs to come from Malwarebytes. If they have a "submit for inspection" or similar link, send the offending file to them to check. The solution is for Malwarebytes to decide the file is safe and whitelist it. Nothing ED can do.

Someone who is going to stop bothering to try and help you since you apparently aren't willing to try and help yourself. I tried to point you in a direction to look at for what your problem could be but you apparently don't want to try and help figure it out (either by posting a track or in this case any details of the what missions are or a mission file or maybe searching the forums for the issue I suggested to see if it happens to be the same). I worked on creating a mission all of last week in the mission editor and had ZERO issues. I've flown a bunch of missions as well and had ZERO issues with random failures. YOU are the only one currently reporting this issue, so obviously it's not a widespread issue. Good luck figuring it out when you seem to only want to attack anyone that gives you any suggestions.

I agree with that sentiment, but the problem is that it changes that value back each time you RUN SimAppPro, not each time it's updated . There is a check box in the settings that used to stop it from changing that file, but it no longer seems to be working (although I haven't tried unchecking and rechecking it to see if that makes it work again). I wouldn't have read only'ed it if the checkbox was still working.

Yes, the new launcher is bugged and won't save whatever state you set. It's a known bug. The current work around is to disable the launcher then it will save whatever you have them set to.

Back a while ago it used to default to ON when you cold started. It changed in an update and now you have to manually put it on.