tech_op2000

is this alignment then complete if you load on jdams after aligning the aircraft? for example, I land and rearm.

is the estimated position error always shown now? Anything I can do to reduce the estimated error?

well, i have gotten to being able to drop jdams. i did not know i needed to hold the pickle for a few seconds. The ALN QUAL is still nowhere to be found though.

In the tutorial videos and chucks guide, i would see "ALN QUAL 00 GOOD" when the J82 is powered on. I am not getting that message. and when selecting a target on the ground the pickle button wont release a bomb. Tips on what I might be missing?

Howdy folks, I am in Open Beta. Trying to learn to Drop JDAMS in TOO mode. First, What does GPS EHPE 18FT and GPS EVPE 18FT mean? I cant find any info on these two lines in either chucks guide or the harrier pocket guide. I don't see an alignment starting on the stores page when I select J82. What am I doing wrong?

I have an interesting addition to this. I experience the same tdc stop behavior when trying to go diagonal with the TGP for the A10C 2. Same for the HMCS cursor. But not for the HUD cursor. Very strange, but at least that shows that whatever funny business is going on there is affecting some ED modules as well. Still though, i haven't found any other modules that have my first issue of deadzones not being respected.

From the future. +1 to this. please add laser cooldown.

@RAZBAM_ELMO Hey, since your actively posting here, can you find my bug i accidently posted in the general forums and move it to the appropriate bugs section?

Am I sure? No. What I can tell you is: -The F18 has 2 gun ammo options: "Default" and "No Tracers" -If you fire rounds and spectate them, they just say "20mm HE" -The bullets do very little damage to ground targets. The f16 on the other hand has as ammo choices: HEI-T High Explosive Incendiary-Tracer HEI High Explosive Incendiary AP Armor Piercing TP Target Practice-Tracer SAPHEI High Explosive Armor Piercing PGU TP Target Practice-Tracer PGU - By Default it uses "SAPHEI High Explosive Armor Piercing PGU" - The f16s gun can kill most ground targets with a few gun round hits. I think that info is enough to say with some certainty that the f16 does use SAPHEI. Your welcome to draw your own conclusions about the hornet ammo but for me I don't think the f18 is using SAPHEI by default, or if it is using it, the round is significantly less powerful when used in the simulator's f18s. I stand by my request to have f16 SAPHEI ammo in the f18 since it can and does carry it IRL

+1 from the future. I love the SAPHEI rounds in the f16. They have so much more stopping power. Seeing that the f18 gun has a selector for whether it is using PGU or M50 makes me want them even more. The Hornet Default rounds are listed as 20mm HE if you spectate them. Please ED, Give us the rounds!

As you wish. During this short flight, I am moving my TDC in circles. As it goes to to diagonals, it stops, and only starts again when I either stop slewing or move to a straight up/down or left/right slew. tdcslew.trk

Here is an additional spooky behavior of the TDC Slew. If I begin slewing using a combination of horizontal and or vertical movement then start or stop using one while attempting to maintain the other. the tdc stops. I then have to stop completely and restart slewing. By combinations I mean: vertical only horizontal only horizontal and vertical simultaneously So as an example. I move my axis to the left to begin a horizontal slew. I then also move in the vertical axis to presumably begin a diagonal slew. All Slewing stops.

So, to test your request; I have just tested this with the TPOD and with Mavericks. The behavior is the same. The harrier honors the deadzone for slewing. BUT, does not honor the deadzone to uncage. Same method applies. Same result for TPOD: set TPOD as SOI. NWS twice to re-center TPOD with deadzone set high. move axis less than would be required to pass deadzone. Note that TPOD begins a ground track instead of being slaved. Also note that TPOD does not slew until after passing the defined deadzone. Same worked for mavericks. Though I don't yet know how to Re-Slave the maverick to boresight other than flying too far off of where the seeker is pointed So, it appears that across the board for sensors, the harrier detects raw inputs on an axis for determining if a slew has taken place. but does not actually slew said sensors until a user defined output is detected. I will note here as I did in an earlier post. I solved this problem by setting a deadzone outside of DCS.

That is unfortunate to hear. I just picked the module up in the last sale. I had done a bit of searching of terms to find tdc related threads but had not come across one specifically for this bug. Is razbam at least relatively active squashing harrier bugs otherwise? -on a side note. I was able to work around this problem a bit by setting a joystick deadzone through windows. It works but ideally this would be solvable in game. I had a similar problem with the fa18 hornet when they added grid coord entry. any input on the tdc axis in there would reset the grid selection. That one on the other had was fixable through an in game deadzone. now that i have one in windows I need to go back through all my other modules and remove the in game deadzones.

The TDC Slew Horizontal and TDC Slew Vertical Axis assignments are not respecting deadzones when determining whether a slewing event has taken place. Steps to reproduce. 1. Assign TDC Slew Horizontal or TDC Slew Vertical to a controller axis. 2. Set Deadzone in axis tune to something ridiculous. For my tests I set it to 80 percent. 3. observe that in axis tune an input of less than that threshold causes and input but no output. 4. select the DMT in flight and cage it to velocity vector 5. Move the TDC axis less than the deadzone set. Note that the DMT will uncage and begin ground tracking. - For me, the DMT will uncage instantly due to any input on the axis. Since it is an axis and is not perfect, this means that for me pressing NWS/Cage will move the DMT to my velocity vector, then it will immediately uncage and begin a ground track. - It can be noted though that with a very high deadzone, the sensor will not slew at all until after that deadzone is reached. - expected behavior: If a deadzone is set to the axis, the dmt and other sensors should not recognize an input and uncage until the stick has been moved past the player defined deadzone. I meant to put this in the bugs section. feel free to move it.

I was referring to the volume knob on the ALR-67 which people often think should turn up and down RWR audio warnings. then again. as you quoted me "volume knob on the ALR-67"

also, in other reports of missiles firing randomly, the cause has been USB issues. Some have had issues with usb hubs, bad ports etc.

also, the volume knob on the alr-67 is nonfunctional. But, there is a volume knob that is functional for the hornet rwr. it is on the back left panel.

there is a bug where loosing lock on a target in TWS-Auto sometimes breaks the radar elevation. While we wait for them to fix it, one workaround is as follows. 1. select a missile, (say AIM-120) 2. TDC Depress on a blank area to begin a rapid search 3. Select a different missile while the rapid search is going on. (aim-9 for this example) after the search ends, you should have elevation control again. (this can also fix the bug where the radar gets locked into a guns scan pattern)

1. for flight height of harpoons and slams. low is 5000ft, med is 15000ft and high is 25000ft. You should be releasing them from above the height that you select. ie. don't release below 15000ft if it is set to medium. At times I have observed that releasing them lower than their programmed height will cause them to attempt a climb to that height and they will stall out. Flight height is the altitude the missile will fly while cruising to its intended search area and while searching. Only after it has a valid target will it attempt to skim the water 2. the seeker setting tells the missile at what distance from the selected target to turn on its seeker. Unfortunately, this does not prevent it from seeking an unintended target once it activates. It is also possible currently for the missile to be to high when the seeker turns on to see the intended target and to continue flying past it either until it detonates or into an unintended target. per the hornet manual for DCS, seeker modes are as follows • SML. 10,000 meters before target location • MED. 20,000 meters before target location • LRG. 30,000 meters before target location so 10km (5.4nm), 20km(10.8nm), and 30km(16.2nm) Once that seeker turns on. It will go after the first ship it sees. 3. Dead ships still exist. Telling the harpoon to go after a target location is only telling it to go to it and start looking. The missile doesn't have any way of knowing that the ship it sees is already dead and sinking. a ship is a ship in its seeker. Harpoons are not designed as precision strike weapons. They were not intended for picking out a target within a group of non targets. For that I would suggest the Walleye, Slam, or laser guided munitions.

Congrats Rooster. @Fri13 The forums wont let you upload a track file if it is too big. But you can upload it to a cloud service like google drive and give us a link to download it. If you know a previous mission where it happened. Upload one or more of those. They should all still be in your DCS track files folder assuming you haven't deleted them. Bonus points if you also tell us a timestamp for about when the pitch occurs.

Great. Now Turn on the controls indicator and see if it is an input into the jet problem or a problem with the system. @rooster7755 It would probably be good for you to start your own thread for this issue. and providing a track file is always helpful

so it isn't just me who is having my tanker on a circle pattern fly in circles magically with no bank or rudder?

I am not getting the F10 Command center option to appear. Any guidance on where to start troubleshooting?

Most of the cases of sudden pitch up, if right after takeoff are likely due to takeoffs with flaps in auto instead of half. Have you checked through all your control bindings to make sure you don't have pitch double bound. If using a HOTAS, it may be wise to unbind the keyboard bindings for pitch/roll etc as well. (I use the arrow keys for SRS instead) The best thing you could do after that is try to make the bug repeatable every time with the exact same steps. Then double check that doing those steps isn't causing an input on your pitch. Turn on controls indicator. "Show Controls Indicator" RCTRL + Enter by default.