wired521

Thanks Heatblur - well worth the wait

I ran into this as well, The issue seems to be Jester gets confused when task switching. What I had to do to fix it was: Jump in the WSO seat Set the radar to A2G manually Set the range to 5M manually Set the TV/Radar video source to radar Manually Once I configured all of these items, he would lock on the ground for me as normal. One other note, when taking just slick bombs and no pave spike he seems fine... I only had todo this when I ran TV guided bombs, a pave spike (for fun), and slicks.

+1

Thanks @gnomechild - even more excited for it now! I wonder if Computer aided bombing will be a feature, although manual bombing has really grown on me.

Wondering this as well, Also, I may have missed it... but what features will the M have over the E? Any chance a set of NVG's will get tossed into the pit?

Hi everyone, Trying out the Mirage F1 EE and looking for depression tables for the SAMP 400; I don't see them in the manual or kneeboard... has anyone built one that includes the 400 yet?

Thanks for sharing the work around - this was driving me crazy

Awesome - I fixed my issue as well. I wasn't lasing long enough for the target data to store (face palm). I haven't tested using the RF Hellfires with a stored target as the acquisition source; hopefully it's possible to pull off indirect fire scenarios as well.

This has been my initial experience as well (from the CPG position); although I could be doing something wrong. I setup a quick engagement against 4 ground targets at the default spacing from the ME and my first 2 shots (LOBL shots) hit the vehicle next to the one I lased. I haven't tried LOAL shots against stored targets yet, will be interested to hear how this is working for everyone.

Cool - love the updates to SCAS (and the FM in general). Thanks guys!

I did a cold start this morning and ran into this issue (laser tracker was in auto and I had no control over the TADS). For context I run both seats. All I had to do was set the laser tracker mode switch to off.

Was headed back to Paphos (Syria map) in pitch black and heavy rain conditions, only to find I was unable to select RW 29 into the wind when using approach mode (I could only select RW 10L and 10R which was... odd to say the least). Luckily there's a tacan station there and I made it work, but just curious if you can manually tune ILS freq's in the JF17. Thanks in advance! I didn't see anything in Chucks guide, or the EA manual.

If you're familiar with the RADAR, and JDAMs, what I found to work the best is to use EXP modes without a target designated. What was causing me problems was I'd lock what I thought was a target in EXP 2, and try to refine my SPI over the target in EXP 3. The issue with that was when a target is locked (or a SPI is set in general), the RADAR will keep it centered and thus it's almost impossible to refine where you want the weapon to go. Instead, go all the way down to EXP 3 and then set your SPI. I'd suggest playing around with the TPOD loaded too - just to see how close you're getting before doing it all with the RADAR (just for practice). Hope that helps - if you find other tips please share!

Hey @IronMike I've had no luck reproducing this after ~10 sorties. Odd that it happened twice in a row, but not the first time I've seen something odd . Feel free to close the thread - thanks for peaking at the log for me.

Thanks for the reply @IronMike, It's a fresh installation of DCS and the Viggen (among other modules), and I haven't had this problem with any other modules. I'll do some additional testing this afternoon to see if I can reproduce it - will also attach the mission file. It seems to happen after configuring for a dive bomb attack with slick bombs (after setting the master mode to anf), but will see if I can confirm that more definitively.

I've had 2 issues today with DCS completely locking up while flying the Viggen (eventually causing the entire process to kill). Both instances occurred when I was near a target area for a fairly simple mission; I've attached my log file for review. One notable observation from the log was: ERROR VIGGEN (Main): HeatBlur: Assert failed: Value out of range. Pitch stabilization. Was -nan(ind). Expected between -180.000000 and 180.000000 There's an entire block in the log with unexpected values (not always null) - please let me know if you need anything else! dcs.log

No, you just need be creative. I'll start-up in the pilot's seat but fly (yes fly, not hand over to George) from the CPG seat. All I use George for is to hold me in a hover, that's it. He can manage that Ok, much better than his half-brother Petrovitch. I wasn't really enjoying the Apache in single player (which is the only way I play) much, until I started just flying the missions in the CPG seat. No, it's not as effective as multiplayer multicrew... but I don't think it will ever be with George AI. And no, it's not how it's done in the RW (but neither is 'single player' with AI anyway... ). Id also suggest turning off the auto-handoff to AI feature if you give this a try; makes it a lot easier to swap seats without George screwing up your control settings. Give it a try, might make it more enjoyable for you as well.

That's a great point - makes sense.

Thanks everyone for the help, here's a recap in case anyone else is having issues with the new KM-2 changes: Petro's settings did seem to work, even though they were off initially I think this is likely because I needed to press and hold the Greben Match button longer. Multiple times during the flight I had to press and hold PU-38 Greben Match (I just bound this to a hotkey) otherwise my HSI would drift Easiest way I found to test the drift from the pilot commander seat is just to bring up the petro menu and see what heading shows up looking straight ahead (F10 map works too) I don't know if this is expected behavior or not Binding the button a key makes life a lot easier, the click spot a little tricky to see unless you're using track IR and don't mind looking down and back a bit. I tested this over a 70NM path (went a little further) and didn't have any issues Also used route mode with the autopilot to keep the path as straight as I could, worked fine One thing to note, if you don't catch the drift early this does seem to increase the drift from the moving map doppler system When I first noticed the issue (Before I realized you need to re-sync in-flight) my doppler map was almost spot-on where I SHOULD have been, not where I actually ended up This doesn't really make sense considering how a doppler system would work, but that's what I observed. Anyway, hope this helps others with the new setup. Maybe Wags will do a deep-dive into this for us .

Thanks @sLYFa I'll give that a shot; assume the correct procedure (after dialing it in) is to press and hold the PU-38 Greben Match button?

Ok one more update, I pushed the Sync button from the pilot-commander's station on the control head to the right of the Engine start/ APU panel. (Its a small button under the latitude adjustment labeled PU-38 Greben Match on the tooltip). After doing this... the HSI slewed to about 339 (only off by 5 degrees now).

Yes, I'm on openbeta (updated this morning) and oddly enough Petro sets the declination to 2.7E (-0000 0027+ on the KM-2 control head), not 16 (0160) like it should be from what was previously posted. Or, is that 1.6 hard to see . Regardless, F10 map (and petro) show my heading should be 334; my HSI shows about 351. My farp is at N28 02'30" E55 52' 32" if that helps at all. I should note, when I say what Petro shows... it's from the AI menu from the pilot-commander seat.

Yes, cold and dark. And yes, the doppler moving map navigation system showed I was roughly in the area I should have been (~60NM from my FARP) however I was about 20 NM away. For perspective, my heading should have been ~349 and where I ended up was as if I left on a heading of ~315 Did any of the doppler navigation features change? I've flown this route multiple times before the patch and never had this issue. My speed was about 250 KPH with a typical altitude of 500-750M AGL. My route of travel was essentially straight and level cruise (no swerving around mountains or maneuvers that would exceed +/- 30 degrees roll). I had the mission on pause and I tried setting the declination to 16 degrees East (shown on the unit as +0160, I assume the last digit is a 10th of a degree). After the change, F10 showed my heading at 268 and the HSI showed ~355 . Will give it another go from a cold & dark start and see if 16 degrees from the beginning makes a difference. Also, thanks for all the help I appreciate it!

Thanks @AeriaGloria - I let Petro set it but ended up waaayy of course (as in, probably 20 NM or more on a 60 NM leg). Moving map thought I was in the right area, but I wasn't. Maybe Petro is hitting the Vodka too hard; lord knows he's all over the place when you let him take the controls. There's the control in the Pilot-commander station that has the 3-way switch, anything to set there? I'll try what @molevitch provided (thanks for that).

Fighting thru a combination of the F10 map heading checks / petrovitch heading checks and lots of trial and error to get from point A to B. Just curious, why don't we have any documentation or content on the correct use of a critical (IMO) change like navigation? The one video I've found is simply 'how to set' the declination, but nowhere can I find where the values should be. It also seems like, at least on the Persian Gulf map, that the declination isn't static (and requires adjustment during flight). -42.4 seemed to get me in the ballpark, but after a 60NM flight it was way off (way off being about 20 degrees between indicated heading and what the F10 map or petrovitch show). Can we please get something (even a forum post) from you ED explaining how this should be used, along with reference values for each map?