Search the Community
Showing results for tags 'check procedures'.
-
Regularly, the TGP will enter temporarily INR track mode while slewing, then the recent track mode is recommanded once slewing stops. Occasionally, the TGP enters a continuous INR AREA or INR POINT track. This will reliably happen when the TGP is masked. I noticed that during this state, actuating an exit out of AREA or POINT and then CZ is impossible to achieve by the usual 2x TMS aft. Pressing the CZ OSB will reliably return the TGP to the steerpoint, which often is a quick way to exit unintended masking while surveying the area. Only the TMS aft won't do in this case. While in a continuous state of INR AREA or INR POINT, TMS LEFT, FWD and RIGHT will still work normally, so it is still possible to switch TV/WHOT/BHOT and cycle between INR POINT and INR AREA. Only TMS aft is ignored. In the track we see me heading towards steerpoint 1 which is ahead of us. I then switch to steerpoint 2 which is behind us. The TGP following to the new steerpoint is ending up masked and INR AREA or INR POINT are displayed continuously. After applying a bit of slew, I then press all the TMS directions, all do work, only TMS aft is ignored. CZ by OSB does clear the CZ. When in regular POINT, AREA or INR, TMS aft behaves normally and applies CZ/ returns to INR and then applies CZ with 2nd press. 65 seconds track attached. no TMS aft to INR.trk
-
Hello, recently i feel that the rudder trim is much better improved, with much less "overeaction" in many situation, this include low speed hover, cruise etc, those improvement make flying apache much more comfortable However, there is still some situation that still cause rudder trim overreaction. Like during transition from curise to hover close to the ground, the rudder trim would still overreact significantly that could shift the nose to another direction dangerously. the rudder trim and cyclic trim performs comfortably well, expect at this situation. Here is my track file TrIm test transition.miz
-
check procedures Unable to align GBU-38 or 54 on a cold start
Victor3 posted a topic in Bugs and Problems
Recently I started flying on a server that forces cold starts and I noticed that GBU-38 & 54's won't ever align. If I fly on my normal groups servers and do a cold start same issue, but if I do a hot start they are aligned as soon as I spawn. Attached are 2 tracks one cold w/o alignment and one hot with immediate alignment. NEVADA DAYS TRAINING MAP 1.8-20250625-155858.trk NEVADA DAYS TRAINING MAP 1.8-20250625-154354.trk -
Hi there, I got a slight problem I haven't encountered before in about 2 1/2 Years of flying the hornet. On the last 3 cold starts on the carrier I wasn't able to clear a WPNS DEGD advise on the bit page, no matter what I did. On top of that when I wanted to use the radar in A/G or A/A mode I got a flashing X on the hud and radar screen and I suspect both are connected. At first I thought the culprit could be a faulty ins alignment, but it happened 3 times no matter if I used stored hdg or not, and it also didn't matter if I selected ifa or nav after an ok alighnment. After choosing nfa it also showed a different text with rdr at the end on the hsi under the aircraft symbol with a timer counting up. I also never noticed that before. I did the cold starts on Syria and Caucasus Has something changed in the startup procedure that I missed and is it a new feature or just a bug? I attached a picture of the X on the screens and a track file. Weapons degd.trk
-
guys, if i press icp 4 stpt page, then SEQ, it should display mgrs after 3 sec but nothing happens. conversely if i select on icp, list 1 dest, enter mgrs and convert it function ok and then i have stpt in lat/long on stpt page any clue? thanks
-
check procedures SLAM and SLAM-R with abnormal behavior
skypickle posted a topic in Bugs and Problems
In the attached track, both SLAM and SLAM-R are set to PP to destroy a T90 at the following coords. N43 46 00.55 E41 51 02.79 alt 4057 Both are set to fly a high profile. (cruise at 35k feet) Both are released within range The slam tops out at 22K feet . The slam-r at 15 k. Both are well below the high cruise profile. The slam-r hits the target. The slam falls short Any idea what i did wrong? (I dont know why the replay makes it look like my head is having a seizure. I use track ir and i really wasnt looking around that much) SLAMM.trk- 1 reply
-
- 2
-
-
Hey guys, I think this has been reported already, but just in case it hasn't I wanted to get the word out there. Whenever I use HARMs it changes the steerpoint but it never resets. I was on the South Atlantic map in the 4YA server and noticed it's changing SPT 12, 13, 14, 15, 16. I'll try to include pics to show I have a track file, but it's too large to add here. Thanks you in advance! Have a great day!
-
I'm still new to DCS, and I realize there's a 90% (prob higher) chance my issues are user-errors... But, I really struggle to get TWS to behave like the manual and related videos suggest it should. Main issue: I see several Track Targets and from what I read, I should be able to TMS Right to convert all those to System Targets (empty boxes). That does not seem to work any time I've tried. Sometimes a TMS Up with cursor over a Track Target will convert it to Sys Tgt, but not reliably. And I can never TMS Right to cycle thru System Tgts, probably because I never have multiple, even though there are multiple radar contacts. Ad a result, I find myself way behind when I'm in bvr. Couple more questions, including how to achieve DTT, but I'll wait on that. Thx for any help.
-
This is on the Shadow Reaper Syria Modern PvE server. They have pre-uploaded the waypoints for the missions. My waypoint was 108. My INS would bug out after about the 50ish waypoint. This happened with both a cold start or hot start, with or without stores. I attached a trackfile. If this is a bug, do we have a work around? I usually use the waypoints to begin search with TGP. If not, what am I doing wrong? Thanks SRDCModernSyria-20250114-093211.trk
-
So few days ago I reported a bug that in multiplayer cold start fighter to fighter datalink doesn't work: turns out it is not the case. It was two tankers with 6Y and 7Y tacan channels interfering with F18's TNDL. After a night of debugging deleting units one by one I narrowed it down to channel 4,5,6,7Y, but I didn't test with other channels. Attached are two tracks, one with tacan 7Y, notice I have no tacan bearing/range as well as any PPLI. When I switched to 3Y, PPLI returns. I didn't record 4,5,6Y's operation but these 4 channels are what I found out that jams datalink so far. I want you guys to know this is by no means a priority, mission makers can easily avoid these channels. Take your time to fix it and test it. 3YMIDS.trk 7Y_NOMIDS.trk
-
Using the AGM-88C PB codes; entering the code for the EWR-1L13: Code 101, the code is crossed out, Will fire, but does not track to target. Is there any fix for this coming soon? I have also seen that code 102 for the EWR-55G6 is also blocked out with a X in the MFD. sorry if this has been mentioned, but i didn't see this directly mentioned. Aaron aka squatchy
-
After 6 Minutes or so, I marked the SAM. I also placed a steer point right above the SAM, but I can't align the TGP weather to the mark point 26 nor to the steer point. This issue occurs several times to me. I've tried to push the CN button in TGP and HSD but it will not work... Not sure if it's a BUG or if I'm doing something wrong. tgp_defect.trk