Baaz

^^ This. I find the radar to only be useful for tracking large and slow moving objects (AWACS/REFUEL) at range. Your smaller targets are simply too nimble and will immediately start taking steps to evade as soon as their RWR goes off. To counter this, I use AWACS or GCI to vector me in, and only turn radar on once I get a visual and go into dogfight missile/gun mode. By putting the target in the pipper, the radar autolocks. The radar, at this point, is being used solely for ranging purposes. When the counterclockwise rotating range indicator reaches the diamond, you're within range and and can launch/squeeze off a few rounds. Don't make the mistake I did early on thinking that because you have tone you're within range. After wasting quite a few missiles, I learned that's simply not the case.

After just checking this a moment ago, it's still there for me. I'm using OB. Can't recall if/what it was called in the past, if anything different, but this is what you need to look for: "Button Targeting mode reset"

While I can't speak for your particular card, I can say that I have no issues with my 1070. While each individual instance will cause +/- a few frames, rarely do I ever fall below 55 fps, and usually average somewhere between 65-85 fps at max settings.

I salute my cat as he's sleeping on his blanket on the table next to me. Does that count?

ED wants bug reports. Therefore bugs are being reported. The least ED could do is acknowledge them, and let people know they're aware. You clearly don't want to help, so you're right, you belong on 1.5 stable.

True statement! In FACT, there are dozens, if not hundreds, in DCS overall. Ever look at the crash logs? Can't miss the number of errors listed within them. What you don't see is an error for people who can't stay on taxiways. One or two people who want to be a drama queens over something that 99.999% of the community has no issue with is what needs fixing. If all but two people can do it, the issue is not with the taxiways. PERIOD. This was funny long ago. Now it's just stupid. A moderator seriously needs to put an end to this thread.

:megalol: My thoughts exactly. :thumbup:

Are you stating to cycle the switch after every shot, or to be sure that the IR cool switch is in the up/on position? The only luck I've had so far is to select the Sidearm in the RWR page, but with only partial success as has been stated previously by another. Edit: The IR Cool switch had no effect on the performance of the Sidearm. I tried with it off, then again with on, then cycling after the first shot. I only get a lock on the very first Sidearm. All subsequent missiles fail to lock.

I know I'm a little late to this conversation, and this may have been mentioned earleir, but the problem I have is that if I don't log into the DCS servers, not only am I not able to play multiplayer but the AV-8B module is disabled entirely. It isn't even listed as a module along with all the other buttons at the bottom of the main screen. It's as though the AV-8B doesn't exist within DCS. Is that how it's intended to operate? If so, anyone who can't connect to the internet is out of luck in terms of playing with the AV-8B and any future module under this system.

As I am also experiencing this, I'm just wanting to bump this thread as I notice that this issue is not yet indicated as a known issue. Thank you.

As I've been expanding my Viggen knowledge to include the use of ordnance other than the BK90, I couldn't help but notice that I was getting some poor results when using RB75's. On a recent sortie to strike a rather well defended Vaziani Airbase, I scored only 1 hit out of 4 with RB75's. Unsure as to why, I turned to TacView. As it turns out, my RB75B's were engaged and destroyed by SA-8's and SA-15's respectively. Now, I've fired more Mavs than I care to count from A-10's at these very same targets, and not once did these targets even attempt to engage incoming Mavs. Has anyone else noticed this?? What makes the RB75 so different?? Is this a potential bug?? Is the RB75 appearing larger to these vehicles than it should be, and is therefore being engaged??

Game crashes 4-6 times a day thanks to this bug. It's been said that the bug has been found. Any ETA on when this is going to be fixed?? One would think it would have been a priority fix and out already.

I'm no genius, I admit that, so can you please explain this in a little more detail, please?

+1

+1

Thank you for the correction. That is what I was implying, though I didn't word it properly.

You said it best, and I couldn't agree more. Hopefully, some of that will change when 2.5 comes out; at least the firing through trees part. Highly doubt anything else will change.

Thank you again Razo+r, the keyboard commands work just fine. Honestly not sure why I never tried to use them for the TAD before, especially when I use the same buttons for zooming TGP and other things. I feel like an old fool now for sure.

Thanks for your help Razo+r. I'll jump in game, check it out, and get back to you. Thanks again.

I don't have a HOTAS, so I don't have DMS mapped to the joystick. Instead I have TMS and China Hat mapped. The scale of the TAD has always been adjusted by me via the rocker switch. The setting of SOI is done with the keyboard commands of H, K, and U.

Yes, Sir, I did. It has no effect on the scale of the TAD at all, at least for me.

I noticed this problem pop up just after installing 1.5.6. I figured I'd wait to see if anyone else was reporting it, but it seems I may be the lucky one, or the only one who adjusts the scale of the TAD in this manner. I don't have a HOTAS, so I do a vast majority of my cockpit work with the mouse and keyboard. When looking at the TAD, the long rectangular rocker-button on the top right would adjust the scale of the map. This button is no longer functioning. While not game breaking, it certainly complicates what use to be simple tasks. I haven't changed anything regarding keymapping or anything of the like in nearly 6 months. Whatever changed, was changed with the last patch, and I just want to make this issue known as I haven't seen it mentioned elsewhere.

I tried to sling a HMMV today. Lifted it just fine. Climbed in a hover to 40 meters, and began move forward. At 40 km/h the rope snapped and the 20 meter fall destroyed the crate. A second attempt at a speed of 25 km/h was more successful, but the crate was still damaged even though the decent was painfully slow at about 50m/min. I have to agree with Drexx, sling-loading is much harder now than it use to be, and ropes and crates are far too fragile.