Tenkom

But you need to designate with the tpod after slaving it to the mark point. If it's not looking at the target, say there's a hill in between, will it change the coordinates? I don't know. will test.

Not an ideal solution but sounds like it should work. Will test when I get home. I'm worried what will happen if the TGP cannot see the target. Thanks.

Is there an efficient way to transfer markpoints to JDAMS? The only way I've found, which is really stupid, is to manually type the markpoint coordinates in the MSN menu for the JDAMS. I know how to use waypoints by turning them into a target point but I'm not able to turn markpoints into target points.

I haven't tested this. But it might work. If you bind button x pressed AND button x released to the afterburner toggle function it should, if my theory holds, get toggled on when you press the switch and then off again when you release. Worth a shot. Edit: I've tried this now and it does sort of work. But you have to hold the button until you are at the spot where you want it(i.e. full AB) and then not move the throttle because after you let go of the button any throttle movement will send you back to full mil.

Be in NAV mode. Create a mark point with your hud or jhmcs near your point of interest. Make that mark point SPI and switch SOI to the tgp. Should be possible to slew it around. You can also just use existing steerpoints ofc.

You only need to do the last 3 steps for the next target. It's no faster in the hornet. Step 3 is the only real difference(apart from pressing different buttons).

Surely the bomb's Coordinates would get synced with plane coordinates while the bomb is attached to the plane? I could be wrong ofc.

The target indicator on the FCR starts flashing when the missile goes pitbull.

Also make sure it is the correct type of tanker. The one with baskets AND probe won't talk to you. At least that was my experience the last I tried.

Ok. So if the bombs didn't have gps they would have the same drift as the plane, presumably the plane would supply the bomb with what it thinks is the current position at drop, and would have hit the target?

Wouldn't an A-G radar designation be a point relative to the aircraft? And if so, as long as the bomb is dropped shortly after said designation, wouldn't the bomb go to that relative location? Assuming the bomb and plane have the same coordinates when you drop the bomb? i.e. It doesn't matter where the plane thinks it is if it knows that the target is x meters north and y meters east of where the plane is and you tell the bomb to go x meters north and y meters east it will hit the target. I am probably completely wrong here but that's how I thought it would work, especially when there is no GPS and it's all inertial navigation.

notselecting9thjdam.trk Track included. Basically if I have 9 gbu-38s loaded and add them all to prog 1 in PACS. When I cycle them in the Smart weapons page one is skipped. After I've dropped some, haven't been able to pinpoint the logic there, it does become available. So in the end i can drop them all but it seems like a bug. Also with unlimited weapons it doesn't seem possible to drop the reloaded ones since they don't show up in the smart weapons menu.

The hornet auto-boxes everything that it can detect. Then you cycle through them with the NWS button. I think the hornet radar is generally more work but also potentially more effective. It has much better detection range for one. But also you have a AZ/EL radar page that helps build SA enormously. You can choose to control scan zone manually or automatically while in TWS where the viper locks scan zone to the active target, the hornet can also do that if you wish. The radar screen can get messy on servers with a large amount of planes and awacs. But you can always distinguish between targets that your radar can and cannot see.

Click Weapons/MODE Switch FWD

If you right click the jfs handle it twists and you can use the second bottle. Then put the throttles to idle and start them normally.

Ok. So I just completely failed at making a post. I had a bunch of images and an explanation but it all got lost. Instead I made a short youtube clip to show what I mean. Please forgive my utter incompetence at making videos. F16 TWS Datalink problem

Good points. Convoys will sometimes drive of the road when off them are hit. Doubt it would save them from a maverick though. But they can definitely be shot down yes.

Ripple fire is when you lock up one maverick, switch to the other, lock that up too and then fire both at once right? I'm curious as to why you would not just fire the first one immediately when acquiring the lock. In my experience mavs are always in range when you get the lock. Am I missing something? I know this is slightly off-topic but the issue seems to be resolved.

https://github.com/the-paid-actor/dcs-dtc This works pretty well.

Did some night flying yesterday. Most in F15 but some in F16. Definitely happens more in the F15. But I did have one such flash in the F16. It's really unnerving. Especially when it happens during SAM evasion.

According to NASA: "A helicopter’s rotor blades are spinning wings." https://www.nasa.gov/learning-resources/for-kids-and-students/what-is-a-helicopter-grades-k-4/ Let's face it. Helicopters are unnatural. They float around on those skinny wings shaking and rattling while planes glide beautifully through the skies.

Hey. Helis have wings. They are just really thin and floppy and mounted in a strange way.

I don't understand. Either your mini stick is analog, in which case you should be able to adjust it using axis tune. Or it is a digital switch in which case the .lua trick would be the way to go. Except it doesn't seem to work with this module so I guess it's a moot point in either case.

No. The OP is using a 4-way hat switch on his stick and is having issues with the cursor being too sensitive. It's not about axis setting. Your fix should work here.

It might be possible to adapt the trick used here: A few posts down you will see how they fixed the slew rate for the antenna elevation on the viper. I've done this and it works quite well. Try finding the line the describes the bind for the TDC slew and change the values there. It gets reset every update so use JSGME or take a back up so you can paste it back in after updates.