rob10

If you have how many tons of aircraft pushing against that small of boom you really think something isn't going to break/bend even if it's moving slowly against it? Yes it's the A-10 pilots fault. YOU destroyed the tanker by overspeeding into it. As mentioned above the boom as 12 ft of extension in it. If you can't keep your aircraft within that distance of the tanker there is ZERO chance you're ever getting near a tanker, let alone being cleared to take fuel, IRL. I did the math: if you're overtaking at 1 kt, you're moving forward at 1.7 FEET/sec. If the probe was fully extended to 12 ft, it would take you 7 seconds to push it fully back in. At 2 kts it's 3.5 sec. And since it starts at 6 ft you're between 3.5 and 1.25 secs of reaction time (at 1-2 kts). If you can't meet this reaction time, save yourself the aggravation and move on from DCS. As lots of others have said, this is not a DCS problem, it's a problem on your end (either the person behind the stick or hardware fidelity). Stop obsessing about the fact that boom ends up in the cockpit. If it was modelled correctly you'd have been crushed, your aircraft and the tanker both damaged massively and you'd be screaming that you had to keep restarting the mission. The tanker can only move the boom so far up/down/forward/backwards, so NO they CAN'T keep it out of your cockpit. I suspect that IRL before it ever got near going through your cockpit they would be SCREAMING at you, they would be taking radical evasive maneuvers and you'd likely be instantly grounded on RTB.

Honestly, I have no idea what the radio ranges should be IRL so I can't really agree or disagree . I just know the current behaviour in the mission editor causes confusion. To use 151.0 as an example, if it should only be available as FM in the F-18 that's fine and I don't have an issue if ED wants to change it to that, but then have it change to that without the option to change it to AM (which currently exists -- at least change it in the mission editor, no idea how that works IRL in the cockpit either). Maybe it's currently being worked on but incomplete. This isn't you're fault nor under your control, but it's where ED really falls down. If this was a deliberate and intentional change to how the radio's are going to work in the Hornet ADD IT TO THE ........ING CHANGELOG!! The first time it happened took a while to figure out the problem because Hornet could communicate with Hornet but not with Vipers. Except on some frequencies they could communicate with Vipers. And a line in the changelog (if it was intentional) would solve the issue. I'm getting off-topic, but make the changelog as long as it needs to be to document significant changes. So from that, it looks like current behaviour is "more correct" than the old in that 136-155 by default SHOULD be FM. Which I'm good with, but it really makes me spitting mad when ED changes something as fundamental as that and doesn't mention it. I can guarantee (from my own previous experience alone) this is going to cause mission makers unaware of the change grief.

There have been a number of people with a multi-screen setup that have had assorted issues over the years when the "main" DCS monitor wasn't the top left one in Windows. Generally a good idea for DCS to put it top and left.

And that can be important if you land at an airport. If you happen to be in idle when you touch down and don't push throttle ahead a bit and back to idle you'll remain in FLIGHT idle and likely run off the far end of the runway due to the extra thrust provided.

Discovered last night that this bug has reappeared. It was a thing a couple of years ago and got fixed, but apparently has come back. When you first open the radio frequency panel the modulation defaults to AM for all entries. However, if you enter a frequency roughly from 130 to 160 or in the 40's (I haven't tested exact ranges affected) it automatically changes them to FM. It's possible to manually change it back to AM with the box beside it and it will stick as AM so obviously something like 151.0 AM is a valid frequency even though it will switch it to 151.0 FM as soon as you enter 151. This matters because other aircraft in DCS like the F-16 can't use that range in FM (only AM). So you have to either catch it and change it manually in the mission editor or figure out why you don't have comm's with other aircraft types (only your own) which is challenging to troubleshoot if you haven't ran into this before. Attached mission is literally a single player F-18 sitting on the ramp cold at Kobuleti, so you're probably better to just create it yourself, but I include it for testing purposes. F18 freq to FM.miz

In MP it automatically saves the track file. If you fly MP it's actually worth going to the track file folder and deleting occasionally because it builds up pretty quickly due to this.

I could be completely wrong on this, but since you haven't had other feedback, is DCS not picky about displaying on monitor #1 and it being LEFTMOST monitor in Windows? But that other thread is likely a good spot to start because I'm sure it will be more accurate than I am. I know in Windows I have my main screen on the left and my 3 WW MFD's stacked off the right side (which obviously is not how they physically are IRL on my desk).

Just to check, you're not on STEAM are you? Trials are not available on Steam (even though it may appear to let you start one).

I presume the count of 1073741823 / 0 in the 1st picture is what they are referring to. @DD_FriarIt would be nice if it could display infinity symbol there too, but I'm guessing displaying standard characters is likely easier than displaying a symbol so that's likely why it is how it is currently. Since that's outside of "active" game it really wouldn't matter if it was a tiny performance hit to do a symbol rather than character, but it might require more coding than you'd think.

You didn't mention MP, so my testing was done in SP.

So I double checked since I rarely use the LITENING pod (pretty much always the ATFLIR). Even if you do as you did (just SCS toward pod) and get diamond over it should put the MAV triangle over it. TDC DEPR also works for me.

Are you actually TDC DEPRESSING on the target? Sounds like you're locking the pod to the target but not actually designating the target so the MAV has no idea where to look. You WPDSG, but that desigination is gone when you start slewing the pod around.

In declining order of likelihood, you have a double binding connected your trigger or a messed up bindings file or else your whole install is in need of a repair. That's pretty clearly changing your camera view as soon as you launch the missile.

Don't post a video. Post a TRACK FILE. With a track file someone will be able to see if they get the same result or if you're doing something wrong. You can save a track file from the debrief screen after you quit the mission.

Easy fix for VPC not working (I'm assuming you're getting a fake omnil ight error). Navigate to: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Bazar\shaders\model Duplicate both: fake_omni_lights2.fx and fake_spot_lights2.fx Rename the duplicates: fake_omni_lights.fx and fake_spot_lights.fx respectively.

Do you have any modifiers assigned (especially as switches) that may be interfering?

Because they aren't moving IIRC? GMT is Ground MOVING Target.

"Radio Transmission" should work, but whoever you want to hear it will need to be TUNED to the correct frequency and modulation (AM/FM) (whatever you set it to in the trigger). "Sound to all" literally sends the sounds to everyone connected no matter what they have their radio set to (it doesn't use the radio).

This is why ED is so reluctant to add things. They can't win. How many posts were there begging for addition of water so they could have carrier ops? And how many of those posts said "Just give us the land, it doesn't need any texture or anything"? And how many posts have there already been about how terrible the textures are and begging for them to be improved? I might actually fly from the carrier up occasionally, so it's not like I'm opposed to this addition, but adding any sort of texture (let alone satellite imagery) would bloat what is already a massive map size (and I like big area maps).

People will have a much better idea if you post a (short as possible) track. You can save a track file from the debrief screen after you end the mission.

I completely feel your pain (I was just shy of 24 hrs downloading the update), but as Mr_sukebe said, it would probably cause more issues than it would solve. You're assuming that nothing ever changes in the way the core and the maps interact with each other. It's very possible you might download the core then be back complaining that your DCS was broken because you had mismatched versions of core and map and that might not be obvious to troubleshoot ("I updated and it broke" -- assumption is going to be you updated everything (because that's what 97% of people would do, not just the core). So while in a perfect world we'd be able to split them, that's very likely never going to happen.

Yes, you would need to add any static (i.e. parked) planes or planes actually taking off/landing yourself.

Sorry, but if you're not getting down to speed in the break (at least to <250 kts so you can drop gear and flaps to lose more speed) you're not doing it right. Not sure when last time I used the speed brake in the break. You might want to aim for 1.5 nm. That lets you do a 30 deg turn to the groove.

What the other guys said. Tracks (which were not designed for exact replays but are currently the only way to get any in game replay) do not do well when replayed in a different version because of the way they work. They literally replay the inputs made in game (at something less than 1:1 fidelity or file size would be crazy huge) so when things are changed in a version change you get very different results.

Normally it should repair to the current version. If it went back to a previous version something is not right.