Stingray 537 Mongo

No worries IronMike. I never expected the dev and a real-world Tomcat driver to chime in so this is practically Christmas for me. The next chance I get to fly I'm going to try out what you both have shared and just do passes by the boat until I get comfortable. It's something I've practiced but I'm beginning to think a lot of it was negative training because I wasn't doing the right thing in the first place. Thank you both for the suggestions and for taking the time. Sent from my Pixel XL using Tapatalk

Thanks IronMike. I do find myself being reactive rather than proactive a lot of the time if I'm being honest about it. The only thing you said that I'm not sure about is pulling the stick back. That's the one thing I found that almost guarantees going for a swim. Given the Tomcat's affinity for loading up the wings at low speed and packing on the AoA, I've ended up either extremely slow or climbing, or both, in almost every case. I'm very conscious of not being aggressive with the stick due to there not being a computer babysitter between the stick operating ape and the control surfaces but is it that I'm still just being too aggressive with the stick in the pattern? Sent from my Pixel XL using Tapatalk

So, it's been 5 months now and I'm still struggling with this. For some reason I cannot seem to keep the Tomcat completely under control in the pattern. I enter the pattern at 3NM, hook down, wings swept, 350kts at 1000ft ASL. Enter the break at 1.0NM past the boat, bring the wings forward, pop the speed brakes, gear down at 200, flaps down at 180, DLC out with the flaps and the thing starts plummetting like a rock. I roll out, apply power and trim like crazy to get on speed, but I normally don't arrest the descent until about 600ft ASL and 1.5NM astern of the boat. I turn in and am able to trap most of the time but it's a 1 or 2 wire every time I do and I'm 29-32 seconds in the groove every time too. I use my rudder pedals to stay coordinated as best I can but it's still pretty dodgy regardless of outcome (trap or swim). Am I missing something in the procedure? Sent from my Pixel XL using Tapatalk

I agree with some of your points but not others. The Tomcat actually seems to be one of the most fragile aircraft in the game. I've been shot down by one Aim-9 before. It seems to always take out the engines, or the hydraulics, or blow a wing off or something. The systems are so well modeled and the internal damage model so well done that a well placed missile or guns burst, even a small one, will doom the jet. Just last night as a matter of fact I got shot down by a snap shot from a Charlie that did nothing but take out the hydraulics. Maybe 5 rounds hit me, but they hit in the right places and I went into the drink. I can't speak to jester because I almost never fly the Cat alone but I can say that the missiles appearing on datalink makes perfect sense due to how far reaching AWACS radar is so it may be a case where other data links in the sim need to be brought up to HB's standard and not the other way around. For ECM, if that's how the actual system is then that's how it should be. If it's OP then either disable ECM in script or don't have the Tomcat in the mission. It's on Mission Makers and Server Admins to balance the game, not the Devs. The Dev's job is to bring us the most accurate and realistic module they possibly can. It's a simulator, not an arcade. Designing in balance at the developer level destroys the spirit and the intent of the program. Sent from my Pixel XL using Tapatalk

Would you mind sharing the copies for those of us who weren't so forward thinking? Even if changing the FM made them less relevant, they're still great reads and provide a decent base line to start from. Sent from my Pixel XL using Tapatalk

If you're flying online, does the server allow external views or do you have that option disabled in the mission editor by mistake? Sent from my Pixel XL using Tapatalk

I've noticed this too but iirc from an interview with a Turkey Driver, you actually couldn't taxi the Tomcat with the canopy up because it would get damaged from the swaying due to it's length and the relatively small size of the lifting mechanism. Sent from my Pixel XL using Tapatalk

I think I saw a response to a post from Heatblur a little while ago that said the development on the -A would start once the -B was feature complete but I could be mistaken. Sent from my Pixel XL using Tapatalk

My RIO and I were flying the GrowlingSidewinder server and there were a lot of lag spikes that we were both observing. When we got airborne we discovered that our INS system was broken and off by over 100NM. When we reviewed our Tacview files, we apparently pulled over 1,000 G's. Is there a way this can be prevented? I can provide a link to the Tacview file as well if needed but I've attached a screenshot from Tacview of the spike for reference. It's worth noting that this occurred during a lag spike from what we can estimate based on the time stamp.

Can you post a screenshot and/or a track file? That'll help the devs see the problem first hand. Sent from my Pixel XL using Tapatalk

As can I in either case, but from my normal position I can't glance down and see the HSI without the stick being in the way and I'm interested to know if this was true in the real aircraft as well or if the pilot had to "move around the stick" so to speak, to see the HSI clearly. Sent from my Pixel XL using Tapatalk

I'd be interested to know from an actual Tomcat driver how much the stick occluded the HSI. Sent from my Pixel XL using Tapatalk

You can make Jester silent through the Interaction wheel. It's in Crew Contracts I believe. Sent from my Pixel XL using Tapatalk

I'm doing my part. Loading takes significantly longer than other modules in the Car it seems, but it's not really causing me any grief right now. Intel Gen 8 i7 8700 6 core 3.2GHz, clocked 4.2GHz 24GB DDR4 Ram DCS Installed on 500GB dedicated SSD nVidia GTX1080Ti graphics card Track IR Sent from my Pixel XL using Tapatalk

Hey everyone. Posting here because I couldn't find anything about this through searching. When cold starting, my RIO arms both ejection seats and sets the eject command to both in the Rio pit. The NATOPS says something about a second arming switch on the bottom of the seat but it doesn't seem to be clickable. When. We tried to eject yesterday we weren't able to. For the sake of argument we loaded into a hot start aircraft and we're able to eject no problems (aside from dying immediately). Has anyone else experienced this or are we missing something? Sent from my Pixel XL using Tapatalk

Is anyone else having trouble opening the DDS files to make custom skins?

Will the hot fix be outside the normal Beta update schedule or will it be part of the next OB update on the 27th? I feel like waiting until then might be the better part of valor since you could push a bunch of patches at once but I know how squeaky this community can be over small things. That being said, if I have to update every day or two for patches, I won't say boo. Sent from my Pixel XL using Tapatalk

Same... This feels like the week before Christmas when I was a kid. Sent from my Pixel XL using Tapatalk

Second. Got a RIO that's chomping at the bit too Jabbers. Just saying... Lol Sent from my Pixel XL using Tapatalk

If you practice, you can start the A-10C from C&D to mission ready in about 4.5 minutes with a full alignment. To do the same in the Cat without the help of a preloaded position would take the same amount of time at minimum for a coarse alignment iirc or up to 8 minutes for a fine alignment. To go from C&D to fully aligned FMC without preloading an alignment in the mission editor in the Cat, it will definitely take longer. Sent from my Pixel XL using Tapatalk

I'm using Tacview version 1.7.4 and DCS version 2.5 beta and Tacview hasn't recorded for me since I reinstalled it back in November. TacviewGameGUI.lua is in a folder called hooks in the Scripts directory as above but I still get a 1KB sized file every time. I've verified that Tacview is installed correctly. Anyone else have this problem in 2.5?

Has anyone else run into this problem? I can unmap and remap the controls but they are non-functional in game. I don't know if this is something I did or if it was the update but they are highlighted this wired burgundy color now and don't work. Sent from my Pixel XL using Tapatalk

1KB and yes.

Hey Guys, I've seen this issue with older versions, but I have the current version of Tacview and DCS 2.5 but my flights aren't recording. My friend has the same and his flights record fine, but mine don't. I know it's installed correctly and that the settings in DCS are configured properly but it still doesn't record anything. Is anyone else having this issue, or has had this issue and figured out how to fix it?

I tried posting this on Input/Output but didn't get any help so I'm trying here. Since I'm on Mobile, I'll keep this short. Windows sees the Coolie switch and the left position works fine, but when I load up DCS, DCS doesn't see the switch for some reason. Up, down, and right positions all work but the left doesn't. This started about a month ago and I'm running 2.5 Beta. Any help yould be greatly appreciated. Sent from my Pixel XL using Tapatalk