rob10

Not sure what plane that is (obviously not the Hornet) but I'm guessing it gives you that warning because left side probe is putting you dangerously close to the tail wing on the tanker. No idea if that's a bug or if that tanker is incompatible with that aircraft or if you need to only use the right basket with that combo (isn't possible to force that in DCS currently).

And clearly ED doesn't feel the loss of your purchase of the Strike Eagle outweighs the cost to them if they don't protect their IP currently. Maybe over time that calculation will change, but currently not.

Yes, but my speculation was that in order to get a low enough weight to meet that requirement the tradeoff might be a slower explosive. Faster doesn't necessarily mean more powerful, so you might be able to get BIGGER explosive charge from a SLOWER exploding material. But yes, this is hypothetical speculation on my part.

I think most of the audio files are encrypted at this point, so not sure there is an option for doing anything to/with it. While a long time ago it was a little over-zealous in firing that sound (i.e. when it really shouldn't have), I haven't heard it in a quite a while. Just practice a little more and it should go away on it's own (since you won't be triggering it).

The other option would be to use something like AutoHotKey (AHK) which sidesteps the IC issue (at least mostly, not sure if some servers might have an issue with it running) and have it press whatever key sequence you need to set up things as you like. I use it to set up radar and JHMCS reject in the F-18. May need a bit of playing around with delays to make it work consistently (some DCS keypresses seem to need to be held for a small amount of time (milliseconds) rather than just a straight press to register), but it's pretty light performance and does a good job. Also totally independent of DCS so you won't need to replace anything when DCS updates etc.

A track file example of a comparison of both these situations is going to get you a lot more traction than just posting that they are different.

Maybe, but it's probably not that simple. This is way over my head, but the explosive speed of the Aim-120 might be slower (no idea if they're using the same explosive, just playing devil's advocate) explosive to get a higher warhead power with less weight or something, so exploding at the same time/distance one might hit the aircraft, but the other might not push the fragments to the target fast enough to hit the target from the same distance. Just pointing out that (while I'm a fan) "common sense" doesn't always match up with reality.

SimAppPro can have an impact in FPS. IMO, especially if you aren't using the vibration function, you should do the following: In the file \SimAppPro\resources\app.asar.unpacked\Events\wwt\wwtExport.lua CHANGE AT LINE 19 to 0.3: winwing.interval=0.3 -- default is 0.03 Basically this changes how often SimAppPro communicates with DCS. This reduces these calls by a factor of 10 and reduces the load. Back in the early days of SimAppPro this had a bigger effect and WW eventually changed it to this (or similar) by default to reduce the impact. At 0.03 the impact is much less now, but still noticeable. NOTE that you'll need to make that file read only after you change it as SimAppPro will change it back every time you run it. I'd recommend setting it off read only before updating in case something changes in that file during an update, but that's probably not required most of the time.

I would say no. You really need a "night" setting and either "off" or a separate "day" setting for daytime usage for the F-18 and WinWing MFD's.

You should start by removing your mods (looks like you have quite a few) and doing a repair.

A hunting scope that probably looking 500 or maybe 1,000 feet away. Versus a pod that's 10-30,000 feet above PLUS 20-30 nm away? Might be a rational reason for the difference. And realize the tech being simulated in ED is in most cases pushing 20 years old. Things have come a long ways in that time.

If it's going back then likely you have a binding issue somewhere. How do have them bound? Check that you don't have a continuous input of a trim reset.

An individual could do that, but the cascading errors that could happen to others on the boat or joining after you pull the chocks would massively complicate what is already a crazy complicated situation to make work. IMO there is no easy way to be able to reset things if even ONE person manually pulled their chocks on a public server. So if even one did it, everyone else is going to have to. And chances of someone being impatient (or not understanding) and pulling their chocks out of order thus screwing up the whole deck crew for everyone is high.

Was going to suggest that would be the likely error. If you use any of the lights in VPC it causes a crash in the background. Fortunately the fix is very easy. In that folder duplicate the fake_omni_lights2.fx and fake_spot_lights2.fx and rename the copy to take out the 2 and it will work fine. I think something changed in base DCS over time and maybe the mod hasn't been updated. Note that because that's in core files, the copied files will likely get deleted at some point (esp. if you do a repair).

Ya, it's pretty relaxed in terms of the position you need to be in and will move you over if needed. I've rarely had an issue with not ending up in the right place and almost always it would be user error (inattention) and I can tell before I even try and get them to hook me.

Since the 3.8.10 files there are only E and F preset available and IIRC you get F if you set to ULTRA and E if you set to anything else. The tweak hacks earlier in the thread are no longer required (or at least not really useful anymore) as I understand it.

Gotta say, not sure that should be an issue. Mine happen to be alternating screen/ddi buttons and I've never had an issue. Setup videos are here:

In DCS you do a 180 (with NWS on HI you can turn in a verrrrryyyyy tight radius) and go back down the deck and retry. You can safely run over the deck crew without causing issues.

Well I'm glad you asked question because while I knew it was supposed to be gradients of green still, I didn't realize what was actually added and what it was for!

I agree with the theory of that, but if it let you manually unchock that's likely going to break more than it solves. Yes, if you're just flying a mission with your own squadron it wouldn't matter because you could all agree to do that and work around the deck crew. But how would you reset things on an open server? The only real solution is for ED to keep working on it (which they are) and make it work properly.

Checking that displays are set to extended as Mustang Sally suggested is definitely 1st thing to check. It looks very much like those screens are mirroring your main screen.

Glad you got it fixed. Ya, it's a weird one. I know people had problems turning it off, but you're the first I've seen having trouble turning it on.

But have you tried SAVING it again with it enabled in both? If it was initially saved with it turned off in client that saved it, it might not matter that it's on in client now.

As a starting point, maybe some details on your hardware and a log from one of the crashes, then maybe someone could give you some hints. But just because your AV or hardware has been working fine until this point doesn't guarantee something hasn't gone wrong with it.

Could be a reverse issue of new Deck Crew showing up even when disabled in mission. Try making sure you have the new deck crew ENABLED on client machine AND in the mission then resaving it. Currently if you have it turned on in client when saving a mission it ignores the setting disabling in mission.