LastRifleRound

Radar bombing symbology in bscope is wrong. Should look like a large cross that spans the length of the screen. Instead ppi symbology used. Radar bombing cross is not at 3km and will cause bombs to fall long in both ppi and bscope. Wind correction not working for level mode, appears to be backward for bk90.

The manual is available for free I'd check it out for specific procedures. There's also dozens of excellent youtube videos by laobi, grim reapers, xxjohnxx, leadnap and many others detailing procedures far better than I could in a forum post.

It's great for ships and formations of vehicles and terrible for buildings. Has something to do with DCS wierdness and not really a problem in the real jet. Cool trick: If you want to test the precision of your fixes (the precise center of the waypoint circle isn't obvious) add a waypoint boundary and now you have a line pointing to it. The b scope isn't really useful. It has great resolution but you can't really do anything in that mode. This is true in the real jet supposedly but is an utterly baffling design decision by saab. The radar is absolutely necessary in these conditions: 1. Deployment of bk90 2. Deployment of RB04 3. Deployment of RB15 4. Fixing nav system in the absence or innacuracy of TERNAV data Ternav data may be innaccurate in these conditions: 1. High cruise altitudes (above 600m) 2. Flight over featureless terrain (desert/plains) 3. Flight over the ocean In these cases you need to get a fix from a known location and i find the radar to be superior to the overfly method. Finally the radar is use for ranging in several weapons employment scenarios and is much more accurate than sight triangulation (think various bomb rocket and gun employments).

The radar isn't very precise for picking out smaller landmarks and which buildings/vehicles it will show vs not show is a toss up. The zoomed in mode doesnt allow fixes. However this is all accurate to the real world aircraft. It is an sbsolute joy to fly and the pilot interface and guage layout just make everything easy. The jet doesn't have ins, only a dead reckoning system so you actually need to fix the nav system regularly which is fun and unique. There is a bug in the wind correction. It's 180 degrees off but if you manually enter the wind in the air for your tgt waypoint you can fix this. I have the a10. I got the viggen because i wanted an aircraft with ag radar that you have to use and a nav system that requires a lot of interaction and HB delivered. I wish there were better radar tutorials out there as they upgraded the system not too long ago and many of the existing ones on youtube are out of date. The maps are more complex and offer better quality than before. It's a top notch module from a top notch dev with a mission and methods unique from all the other dcs aircraft. You should get it.

True, but I think I would have drawn that line on the other side of this. The radar is mission critical for this aircraft. Does A2 always center on the selected waypoint? If so you could use it to verify a fix at least. Its so logical I believe you guys had to take the feature out as you found out after the real jet didn't have such a capability.

I love the image I get in mode A2, but without the ability to fix in this mode what is its intended purpose? PPI lacks sufficient resolution for precise fixes. Bscope has sufficient resolution but lacks the ability to fix. Was SAAB trolling their pilots?:megalol:

Is the ground radar impacted by any graphical settings? Not sure if it's normal but I can't make out anything at all over 15km. Once something is within 15km there's virtually no time to set the cursor for a fix. I hardly ever use the radar as a result, really only for anti-ship do I find it useful. Also, I assume it's a bug that I can't set the cursor in b-scope (mode A2), though b-scope is so under-resolution I can't pick anything out on it anyway.

This is true. Issue was I was too fast and slightly high. What I thought was extra symbology was the steering order glued to the bottom of the hud commanding descent. Still feels off to me. I assumed level bombing modes would specialize in giving you commanded steering for targets below your nose. What is your checklist when you run in for a level delivery?

If you choose one of the higher safety altitudes of 400m or 600m or are even slightly fast this isn't possible. The manual indicates this as such and also shows the steering order should be followed at this point

Is it just me or should the horizontal cue and steering order both be present when holding weapon release? After trigger unsafe if weapon release is held the pilot is given a steering order that indicates where vertically the aircraft should be flying ro fly at the safety altitude. When the bombs begin to release a circle on a horizontal bar also appear to help align in that axis. However the bombs are already falling and it's too late to make corrections. It seems like that horizontal indicator should appear when weapon release is held just like the steering order. Thoughts?

I'm having this issue and I don't even have teamspeak. I have the x-52 (not the PRO version if that makes a difference). When I hold the throttle hat left for the "coolie left" command, instead of the press being registered and held until I release the command, it's like old-school Nintendo turbo mode, acting like I'm pressing the j key repeatedly. I can't even find old drivers for the x52 anymore, and I don't have teamspeak, so I really don't know what to do. I've had this sim for 2 goddamned years and haven't been able to play it right. I finally got a decent PC and a trackIR and I STILL can't do it. This is why I left PC gaming in the first place. I already have a job, I don't need another one that doesn't pay me. Any ideas? I did the old uninstall and reinstall about 67 times already. I'm out of options here and really annoyed. EDIT: I tried making the coolie hat commands in DCS itself, and it works properly. This isn't really a fix though, as I need to use the shift state switch on my controller to get all the proper functions, and the only way to map this is using the SST software. This is clearly an SST vs. DCS issue, and I'm at a loss at how to resolve it. EDIT AGAIN: Nevermind. This is a known Saitek/Windows 10 driver issue. Ridiculous. You spend all this time upgrading everything just to find out you upgraded too much. I don't know how you dedicated PC people do this. It's exhausting. I have to wait until "Early September" for Saitek to fix "all issues". So I guess this sim will be gathering dust for another several weeks.

PLEASE don't tell me to build my own. I would screw it up for sure. Here's the link to what I'm interested in getting, just want it to be good enough to get good FPS on DCS: http://www.newegg.com/Product/Product.aspx?Item=N82E16883227302

ahhh i think i see what you're saying. The fragments are what ordinarily would be scoring the kills, but since there are no fragments, there are no kills. What, then, are we to use the current S8's for? Point blank they can really tear up columns, but other than that i'm having a hard time finding a use for them

I see what you're saying here, but in application, something is wrong. That amount of firepower should level a column of trucks. I think a simple radial damage model would suffice here, no need to model fragments. They must have come up with some sort of workaround, as they are introducing blast/frag rockets in the patch.

Ground moving target just allows a linear lead calculation. If the target isn't moving, no lead will be calculated. I do the same as Viper, I tend to always engage with GMT enabled.

True, but Cachya also has trouble with aspect, camera positioning, etc. if they are chagned you must change all the settings. Probably not a big issue for most people, but I use a laptop for Black Shark, so it's a big deal for me.

I will say if you're thinking about getting Cachya know that it requires a significant investment of time compared to TrackIR to get it working right, but it DOES work. I still plan on getting TrackIR, as with certain light conditions or times of day it is very difficult to get cachya to track efficiently. I will say that I was quite functional without it with my X52 because i had the mini-mouse, and could map many of the functions to my buttons instead of mouse clicking them. SO......I think a good HOTAS is #1. After that, yeah head tracking is pretty sweet

I should think a barrage of 32 of the suckers landing in and around a road formation of trucks should be enough to knock out 1 or 2 of them HEAT or blast frag. However, I will say that you should employ rockets between 1-2km. Ideally 1.5-1.9 seems to be the "sweet spot". I tried my single mission again and employed rockets in this range to much better effect (Knocked out 4 of the trucks with one barrage). So basically, ignore the advice that says employ between 2-3km, you won't hit anything at that range. I forgot they were introducing blast frag rockets in the patch. If they are as devastating as a 105mm shell that is going to be ALOT of fun :)

My favorite in Lock On is flying the standard model Su-25 (not the T). It's really wild operating with no HUD, and the weaponeering is alot of fun in it as the symbology and employment are a lot different than anything I've tried before. There's also a campaign mission that has you landing in thick fog with a low cloud deck, instruments only with no HUD. It took me 3 tries, but when I put that bird down it was one of my most satisfying sim experiences. Not for the faint of heart.

I've had this problem as well, and found it has to do with a number of factors: 1.) Terrain-If your target is in hilly terrain, the vikhr's spiral could cause it to impact the ground short of your target as you saw 2.) Range-2.5km is point-blank as far as vikhr shots are concerned. The spiral is quite pronounced at this range. Try your shots from 4km and out and you'll see better results. This seems to be the most major factor for me on whether or not I score hits. 3.) Static objects, as mentioned earlier, take many more missiles. This may be an issue, or perhaps it simulates a dug-in target. Either way, it takes many more hits to knock out "static" type objects. 4.) Are your targets moving? Make sure you have ground moving target enabled if this is the case to allow lead angle calculations.

That's just the thing, the S8's AREN'T good against infantry. They're not good against anything. Anything less than a direct hit will not destroy whatever it is you're aiming at. This makes them quite a poor choice to use against infantry. 30mm HE is far superior, even vs. large groups in cover.

points well taken here, but to #4, note that it is not that i don't understand how to manever the aircraft, it is just that the control input required to actually receive airframe response is DIFFERENT depending on whether or not you have FD active or the trim button held down. In other words, the stick position required to hold a certain bank angle is not the same when you have the trim button held down, as the AP is actively maneuvering against your input. This took me a LONG time to understand, as it is not immediately apparent, and isn't explained any where, hence the title of this thread. I have since overcome this issues by holding trim down, which, according to the manual and the sticky on "trimiming" in this very forum are considered to be bad ideas. FOr me, I was simply informing new pilots that the method of holding trim, making sure your helo is ABSOLUTELY stable on the exact attitude you desire, then releasing trim, is the only sensible way i've been able to fly.

I know it's been said before on here, but are HE rockets in real life as weak as they are in Black Shark? I've actually gotten really good at strafing and holding the pipper where i want it. I set up a training mission with 5 Ural 375s on road formation, lined up nice and tight, took 4 pods of S80's, selected all hardpoints, lined up perfectly, had the pipper motionles in the middle of the formation, set salvo to the highest setting, and let rip with a barrage I was sure would decimate the column, leaving 1 or 2 survivors. I had them locked in the shkval, and watched as.....1 exploded. 1. I launch another salvo, and watch the rockets explode in and around all the targets, the smoke clears and....nothing. Not one. I was about 2.5 km out, and know i hit the area. I flew the campaign mission "Escort" in the "Deployment" campaign. *SPOILER* When the column is ambushed, i am told to target the foliage. I whip around, aim at the foliage and unleash well-aimed bursts evenly throughout the foliage. I knock a troop or 2 out with the cannon, and the BTR's in the column handle everyone else. I look at the debrief and.....the rockets didn't kill anyone. Now, i'm not too sure what the purpose of rockets are. I've been told they're like a "Shotgun" and that the ideal range to launch is between 3-2km out and i should be on egress after that, but i've got to tell you this just isn't effective and is a big waste of ammo. Why take rockets? The cannon outranges them, is more accurate, and actually seems to have higher splash damage with the HE rounds than the rockets do. Surely this is a bug or unintended design consequence of some sort? Finally, does the Russian army have MPSM-type rockets? Those would be neat to see in action

He likely has the trim button held down there. It's hard to work with the autopilot when it actively adds input contrary to your own. Just try to perform a hammerhead turn with the trim button not held down. You will sidelip a klick before the thing actually begins to yaw.

Man does anybody remember DI's sim "Tornado?" And then Ef-2000.....man those were some fond memories.... To get back on topic though.....I think 2 seat operations could get a bit sketchy, great for MP play, but not sure how you'd fare with AI without "dumbing it down" or frustrating the pilot. In fact, my favorite part of simming is weaponeering. I don't WANT the AI being the CPG, because I enjoy those tasks. However, watching how the AI fles in BS, i don't think I'd have much choice....