Father Cool

It's an intermittent fault Mike. When it happens you can move the trim down as far as it will let it go, hold your finger on it until the trim needle on the gauge is several degrees negative and even at that you have to push the stick virtually full forward to even fly level. It hasn't happened much to me tbh but it does it on occasion and when it does its a real pain to get the ac home. I have an X55 throttle and a Virpil VFX stick.

Yes I had a positive hook on 2 bandits dead ahead at 50 miles with 2 more closing from the 1 o'clock but further out. I fired fox 3 but as soon as the Phoenix left the rail the radar clicked over to RWS, the target was dropped and even the previously IFF'd ac switched back to an unknown target and then dropped from the radar altogether. The Phoenix didn't track at all and Jester refused to switch back to TWS or perform any kind of STT lock. I had RWR contacts with the bogies so I had to attempt to get into PAL range and lock them manually which then lead to the loss of my aircraft as by the time they showed up again I was between 4 and 6 miles way from them with them already releasing weapons. At the moment the F14 may as well be a cessna. Even then with the navigation issues that our squadron is currently experiencing with the F14 the cessna would actually be better. Please HB/ED sort these issues, a few months ago the F14 was working almost 100% and it was an experience that brought happiness and joy to my flying nights, currently, as it's the only module that I fly, the experience is of almost dread of what won't work this time.

It isn't a takeoff issue. It happens in straight level flight. The aircraft starts pulling up and regardless of trim position you have to push the stick pretty much full forward to keep the aircraft level. With all due respect we know how to fly our F14, we know how trim works and we have been flying this module for a long time now and pretty much bug free just before 2.5.6 dropped. Since then there has been issue after issue for us and the F14 is fast becoming unenjoyable to fly due to every mission ending up with at least one of our pilots having to log out of the session due to a bug. As this is the only airframe that I fly I say these things with a tear in my eye. I just want a module that works consistently. Not too much to ask I don't think.

Recently our squadron members have been experiencing this. Very frustrating. Is there any news on what is causing this issue?

Yes I never have random system failures on, I expect my plane to work as advertised during missions. There are enough issues with DCS without adding anything extra into the mix. I have the track file of the mission however we had so many issues getting up last night that it was over an hour before I got airbourne and even then I have this issue and some horrible trim problem where the ac was trying to head for the moon constantly unless I trimmed down and pushed forward, no one wants to sit through that track file! Sent from my SM-G950F using Tapatalk

A feature that destroys the whole night's campaign is no feature in my mind. If that's the case there needs to be some way to correct it in flight or not model that issue as it's realism too far. I have had this happen on airfield takeoffs however so I think it may be more than that.

This has been happening on and off for a few months now but last night took the biscuit for me. Normal start up, Jester fine ins alignment on deck of carrier, normal take off and uneventful transition to CAP point approx 160nm away. On the way to the waypoint HUD started to tilt gradually getting worse. When I reached CAP I couldn't actually catch the waypoint as it was actually drifting away from me on the TID as I was trying to head towards it. The nav grid I set up showed the map essentially drifting underneath me, all waypoints and aircraft were shown on the grid except my aircraft was drifting backwards across the map and then off of the edge of the screen. As a result I could not perform any duties as the radar was useless. By this time the HUD was nearing 30° skewed so I headed back to the carrier. By the time I had made it back to the carrier the HUD was over 45° skewed. The whole flight was calm, no heavy maneuvers, nothing that could have knocked out the INS alignment. I had waited for Jester to finish up, ready to taxi etc etc. Screenshot of my HUD after getting back to the carrier.

Thanks Doormouse, glad I am not going mad! Sent from my SM-G950F using Tapatalk

Prior to last night one of our guys said he was getting contacts showing but Jester would not hook them with the TWS or lock with STT so couldn't engage bandits outside of PAL lock range. Currently that was still a better situation than what we saw last night. Currently running a repair and will see what that yields for me, hopefully not lost control binds which was my fate last night after running it! Edit: No issues found with files.

I did further testing last night after the mission, which is what I posted earlier on in the thread with the Mig 29. I have run a repair after the mission last night but before the mig test. I don't have Viacom, I completely rebound all of my keybinds and don't have anything bound that I can see that would interfere with the radar. the WCS switch is a RIO control and I am flying with Jester so I guess it's up to him. I have no binds that would interfere with that. It is not just me though it is everyone in our squadron so there must be something effecting this. I will run a further repair and see what it yields.

Thanks Mike, I do assure you though (and the F14 is the only plane I fly so have a lot of hours in it) the radar is not working for us (me and the rest of the boys in our club). It's not about locks its about not even seeing contacts at all on the radar. Last night in our first mission of our latest campaign there were approx 4 to 6 enemy F14's all within 20 miles of us. We didn't get a single radar trace on any of them. I got some further out earlier on in the flight from the datalink but nothing on the AWG9. I could see one dead ahead due to his con trail heading straight at me, nothing on radar, no response from the PAL (wouldn't even activate the scrolling diamond), he went past my canopy in the merge by about 50 ft and yet I still never got a trace or lock. Currently we are grounded until fixed.

Well thats odd because right now the F14 is unservicable for me. Sent from my SM-G950F using Tapatalk

It is very broken. I have just tested it and I get zero targets on the TID even when the bogies are directly ahead at less than 20 miles. Just a black V as though nothing is there at all apart from my waypoint markers. Datalink ac show up but cant lock them, nothing at all from the AWG 9. Also PAL not always working but does sometimes. When it does it gets a lock but firing missiles bares no relevance to the lock and the missile just goes off wherever it likes. I tested this with a slow moving mig 29, 5 to 10 miles ahead of me. I shot off 4xAIM 54s, 2x Sparrows and then closed in to get sidewinder shots off. All of them missed the Mig and flew right past it. Somethings wrong here and its broken my plane!! Sent from my SM-G950F using Tapatalk

Ok I'm real noob with using scripts for missions in dcs. I feel that i have gotten there but need some extra features that the standard ME doesn't provide. I am looking at country borders and have managed to get GCICAP working with Moose however the CAP doesn't take off unless a blue ac approaches where actually I would like the red ac to patrol CAP from the beginning with GCI backing them up if a blue ac crosses the border. Also I would like the border to activate a flag showing blue ac in red territory so any action against red ac while in red territory will trigger consequences. And also red ac wont engage blue in blue territory. This must be possible using the borders created for GCICAP? Any help would be great Cheers FC Sent from my SM-G950F using Tapatalk

Ok here is a link to a video of my wingman showing the issue with the bombline. Sent from my SM-G950F using Tapatalk

No I don't believe so. I have certainly had it happen when in a mission set later than 1986. Sent from my SM-G950F using Tapatalk

Yep. I generally have my mission IP and ST plus Navgrid to set up after he has finished aligning and tapping in his waypoints etc and says Ready to taxi. So consciously wait for him to finish.

It's as though the whole thing is not aligned even though I've gone through the process if a fine alignment with Jester.

Nope. No excessive launch from the catapult (also happens on land based takeoffs) and nice easy climb, uneventful transfer to target area. Bombline skewed as soon as I switched A/G on once upto transit altitude and wings level.

Yes I am aligning properly using Jester. I have encountered this on land based take offs and on carrier takeoffs. Don't get me wrong it isn't every time but it is enough to make bombing missions a gamble as to whether you are actually going to even be able to drop ordinance with any real purpose. I'm not sure what the wind settings were last night as the mission wasn't mine and was a MP event, could be wind but I thought that the bombline simply slid across a little in that case not skew off as an angle (the other day the bombline was horizontal at the top of the HUD). However last night as soon as I got airbourne and on course to my IP I switched to A/G to find that the bombline was skewed, starting at just left of centre at the top and sloping out to the left so the bottom of it was off of the HUD, in straight level flight. My wingman also had the same issue. It never changed from this. I thought that I would try to work with it but once at the target I was still able to put my CCRP diamond on the target but the bombs wouldn't release when pickled so I switched to CCIP on the next run, no targeting pipper then appeared in the HUD and I ended up guessing when to release which of course missed the target. This skewed bombline has happened many times now and is frustrating as I am trying to convince our group that the F-14 is capable of more than CAP! Regards FC P.S I don't have the track, video or mission however I will record all of those next time it happens.

If thats the only issue you have right now then it must be rosey in your shoes! Haha Sent from my SM-G950F using Tapatalk

Ok I am getting this more and more now and it's really starting to effect the playability of the tomcat in a bombcat role. Which is what my sub squadron specialises in. A lot of the time now when taking off and transversing to the objective the bombline is tilted off at anything from 40° to 90° rendering the HUD useless and bombing impossible. I have not performed any adverse g manuvers to knock the alignment out. In fact the line is skewed off directly after launch. The bombline is so far off that the CCRP refuses to pickle and in CCIP I don't even get a pipper most of the time. Does anyone else have this issue?

https://forums.eagle.ru/showthread.php?t=265062 Thought I would post my issue here to cover the bases. Our squadron runs CAP on our mission nights protecting our bomber squadrons and if we are not confident in our weapons releasing when asked then its a deal breaker I am afraid.

Any news on this. I assumed it was fixed after a friend of mine was talking about firing AIM54s however I still have an issue where they don't fire. The other night I tried firing 4 times, 3 second hold, and nothing. When I let go of the trigger about to give up it fell off the rail and hit the target. What is going on! Sent from my SM-G950F using Tapatalk

Has anyone had an issue with the F14 when using the Lantirn. I have noticed on my machine that when the VDI is switched from TCS to Lantirn the game becomes stuttery/choppy. Worse in PG map. When switching the VDI back to TCS all is butter smooth. Happens whenever Lantirn feed is selected. How can I solve this? Sent from my SM-G950F using Tapatalk