AngryViper.101

From personal experience. I think the problem is that your system was not properly aligned (either use stored alignment, or normal alignment) prior to takeoff.

How do I activate the smoke on the F16, I have included a Red Smoke module to the right wingtip. But now whilst flying, is there a switch hidden in A-G or A-A mode that I must depress to have the smoke come out?

Ok, I noticed I can lock on (boresighted) with Mav H as well as D (so IR and CCD). This through dense clouds, and only if I have exact coordinates that I can point track using TGP... However, force correlation mode does not work.

Hi When I fly a mission with rain and dense clouds I can manage the following. 1. Boresight Maverick H while on runway 2. Fly low and use TGP to Mark a target (Steerpoint 26) 3. Then I fly above the cloud cover, 15,000 ft up 4. Then using TGP I point track Steerpoint 26 which I setup as the active steerpoint and used the CN (cursor zero function) to make sure the TGP is point tracking on the point I marked in Step 2. (At this stage I see nothing but dark grey clouds and lots of rain) 5. I then proceed to fly to around 8 nm of the target , still 15,000 ft up above dense clouds 6. Then I can point track using TGP, handoff to Maverick H (which is in PRE mode) and it locks on! 7. Shoot and it perfectly hits the target . So my question should a CCD Mav H be able to do this, and will it also work with Mav D's the IR variants?

I also recently landed at a neutral airport expecting fuel. But unfortunately neutral airports do not provide fuel when you are on the blue or red coalition side.

Hey DCS Are there any plans for a laser guided version of the Maverick - for the F16?

Hi Also, when you boresight. 1. TGP find a targe to lock on, TMS up, notice that TGP locks on by 'snapping' onto the target with a square (box) on TGP 2. on WPN page, make SOI, slew to same target, TMS up, notice that WPN also 'snaps' onto the target and slightly moves around, BSGT then 3. step with MSL Step button to your other pylon, again (while on WPN page) slew to same target, TMS up, notice that WPN page also 'snaps' onto target, BSGT again 4. Then leave everything as is, return to Nav page, take-off etc. P.S WPN page must 'snap' / lock to a target before you press BSGT, However, the target does not even have to be the same ... as target that was selected in TGP.

Hang on, why is the rounding for the EAST coordinate not rounding up? Check this: I did not touch anything, spawned in a new jet, started the default stored alignment. And on the map it reads E035'17.772, and the alignment DED shows E035'17.7, Should it not be E035'17.8? looks more like they just chop off the last two digits?

Thank you everyone, I think we have a lot of information here and happy to close off this topic. Happy flying!

Thank you for the reply. Okay, so my second test done. I forced a crash landing, fire and tip of right wing missing... (luckily did not die). Then powered down all the darn switches, waited for a repair, then booted up, cold start. Then did the normal alignment using the images above for the coordinates. 1. The good news, armed with JDAMS, and managed to release on my target location (previously / yesterday I could not release INS was messed upcompletely) 2. BUT as you pointed out I missed my target by a few 100 meters +- not sure, had to get out of there darn Stingers! In summary, my issues yesterday, could have been due to the fact, that after an aircraft repair I did not turn off ALL switches and do a full cold boot. Also, at the time I was refueling, and this time I even enable ground jett ... So the aircraft was untouched in my successful run this morning. This leaves us with the one question, when performing a full alignment, how do we input the correct coordinates, given that the input allows for one decimal place? Cheers!

During a normal alignment procedure, which coordinate system must we use to input our coords? I used the F10 map and left ALT + Y and this was the closest coordinate format I could find, however, the F16 alignment DED page does not allow for the last decimal digit?

Good morning, Alright, tested with a new jet, on the same server, and the GPS guided JDAM hit spot on to my input coordinates (verified via TGP). Now, I will also test, after crash landing and waiting for a full normal alignment, perhaps the coordinates were incorrect.

Hi Tom, yes I will definitely keep this post updated. I watched another video just now, apparently, during normal alignment one must actually input the North and East coordinates manually, which I did not do, I simply accepted them as correct and hit enter on both? Is this a fact, that one must manually lookup one's position on the F10 map and input the N and E coordinates again when performing a normal alignment? - I will also try and test this scenario after forcing a crash landing, repair the aircraft, and do what I explained in the paragraph above.

Hi Yes, I actually tried it two different ways. 1. Firstly, I manually input the coordinates based on a 'tag' on the map, then cursor zeroed etc. (tried TGP and FCR ground radar) 2. Secondly, I actually used the TGP to create a Markpoint, which I then set as the active steerpoint, and also tried the cursor zero on both TGP and FCR ground radar with no luck I will try again tomorrow, same load out with a newly spawned jet to see if the GPS guided bomb works after creating similar steerpoints ;-( Surely there must be a way to have the jet repaired and then setup alignment correctly? and go off and mark targets correctly for dropping of bombs?

Good evening Need some advice. While playing on one of the Buddy Spike servers (Syria, 80's) I encountered a problem. Situation After crash landing at an airport. I shut down the engine, waited, asked for repairs. After some time the ground crew were happy to repair the Jet. Then I proceeded with a cold start. However, I did not move the jet an inch. In fact I had the parking brakes on. I then performing a 'normal' alignment procedure. 1. turning the knob to the normal alignment position 2. waited for the bearing to correctly adjust, that happens rather quickly 3. click on the enter button to confirm the North, East and elevation 4. Wait .... 5. Then on the HUD the align starts flashing (after counting down to .../10) as per usual 6. Then turn the alignment knob to the Nav position Problem All looks good on the Hud, bearing etc. But, when I reach my target the TGP correctly 'shows' the target picture, but on the Hud the block with the dot points at an incorrect location? This causes me to not be able to use any GPS guided bombs? What could I be doing incorrectly in the procedure above? P.S I actually turned around, landed safely ... and did the Normal alignment procedure again... waiting for the flashing on the HUD after it counted down from .../99 to .../10 .. long wait. and again, same story? Any advice / guidance would be much appreciated. Cheers

Good day Recently purchased the RTX 3060 mobile GPU. Not the 3080... Paired with the faster nvme m2 SSD and 16GB system Ram it works well. DCS caches about 50 GB to the SSD but with the latest SSD read and write speeds it runs DCS smoothly.

Shucks, for almost one year I have been spending hours finding something to lock the TGP on, then looking for the same darn thing via the maverick seeker (WPN) page, locking onto the same thing again before trying to boresight. Tested it yesterday by locking onto different objects and bore sighting, and it works, as long as it actually snaps / locks onto something bore sighting works...

also, partial success on 04th attempt, different approach. please can someone inspect my tracks and tell me what works and why? and what the actual correct procedures are to successfully deploy paveway iiis in different scenarios (altitude, lasing time etc.) thanks payveway iii success attempt 04.trk

Okay, third test success. But I had to follow the tutorial on youtube, changing the release 'cue' to 8,000 nm and also setup the release angle from -30 to -0... And also went up 20,000 feet before trying to release Why did this work? versus prior attempts? payveway iii success attempt 03.trk

Hi, I tried a second time. This time I started firing the laser much later. The Paveway iii picks itself up and just about reaches the target. So does this mean, as with other laser guided bombs, one must not start firing the laser too soon? payveway iii fail attempt 02.trk

Hi What am I doing wrong. Paveway III almost always drops short, please see my track and advise. Thank you payveway iii fail.trk

My two cents worth, that video posted above, "tame your viper" helped me a lot. My checklist prior to landing: 1. drop landing gear 2. trim nose up about 5 notches - key presses ... 3. keep speed between 200 and 240 4. ensure CAT III is selected, not CAT I (shout if you do not know what I am talking about) (this seems to reduce the sensitivity of controls, especially at low speeds?) 5. I always use a tool from github: https://github.com/aronCiucu/DCSTheWay/releases/tag/v1.5.1 5.1 I then pick / create a steering point +- 5 miles from the runway i want to land and autopilot to that point. 5.2 Also pre-create a steering point on the runway number that I want to land on 5.3 I thus auto pilot to the first point 5 nm out and then manually fly toward sthe 2nd steer point on the runway (aiming point, not landing point) 6. Then about 2 / 3 miles out I only drop the landing gear 7. by then the aircraft is pointing towards correct runway and i am about 2,000 - 1,500 feet altitude and also 235 knots speed +- 8. then i land flawlessly even with keyboard - BUT taking note of what was said in the video regarding 11 degrees angle of attack and also putting the flight path marker FPM above the 5 degree line ... let me know if you want a track or more information.

Aha, answered my own question, 20nm is okay for releasing the cb87b (202's). But, when the pipper marches down, you MUST align it to the FPM (flight path marker). If the pipper does not intersect on the FPM then it won't release!

Hi, thank you for the reply. when mobile keyboard and mouse alone.

Good day, What is the maximum altitude that the cb87b may be dropped? I was flying over 20nm and they would not release, however flying much lower I could release?