Home Fries

I run mostly high, but low textures (doesn't appear to make any difference except for frames), no MSAA or post-processing, and low traffic.

I ran two of the F-14 Instant Action missions on an i5-2500 with a 1060 GTX and 16Gb RAM. 600kias at 500ft AGL was smooth as silk over both Haifa and Beiruit.

I'm in for voice acting as well. If you need a sample, check out The Crew pt 1 which is released today. I'm the lead pilot. I also have a small role in Raven One.

Not bad at all, though the COVID was keeping me really busy for a time. Now I can once again give the cat the attention she deserves! Hit me up if you want the ultimate Tomcat experience: flying with a RIO. That's where the fun really happens, not to mention it really helps with precision A2G. Finally, you of all people know how excited I am for the A-6, even if it is AI only.

The fuel cutoff switches work great, but I get a "Unhandled Proxy Command 3060, val=nil" message when I try to use the bottles. Please add these to the keybindings, as they are impossible to get to in the cockpit without some serious contortioning, and even then it's difficult because the hotspot is slightly offset from the button. And speaking of hard to reach useful buttons, I would like to reiterate my request to map the stopwatch button at the RIO station.

TACAN would be the easiest option to implement, but that would also require that Jester input a waypoint that corresponds with the selected TACAN station. OFC, as AI Jester would know the TACAN L/L, but which waypoint would you want him to use? FP? I suppose you could use the F10 markpoint and assign it to a waypoint using the wheel, but having an automated option would be nice too. The other option is a visual update, where you have a FP already in the flight plan (so it's already entered in the system). If it's a known visual position, you as pilot could fly over it, and Jester being AI (and hopefully aware of his in-game position in the abstract sense) would update the INS position at your closest point of approach. EDIT: This could also work with the F10 markpoint entered using the Jester wheel, so long as Jester AI has positional omnipotence with regard to marking the closest point of approach at overflight.

That's how it works in real life: the pilot says what he wants, and the NFO uses brain-power to make it happen! :smartass: As previously stated, the distance between bombs in a stick is a factor of both intervalometer setting (the ms between drops) and the aircraft ground speed. If you know the delivery groundspeed, you can set the intervalometer to get the spacing you want. There's actually a pretty easy way to figure this out: if you set your groundspeed to a multiple of 60, you can just divide your speed by 60 to figure out the number of nautical miles you travel per minute. This is why flight planning uses numbers like 300, 360, 420, 480, etc. Take your miles per minute, and you just multiply that by 100 to convert the value to feet per second. For example, if you're doing 420kts (therefore 7 nm/min) that means you're traveling 700 ft/sec. (Derivation: 7 nm/min * 6000ft/nm / 60sec/min = 700 ft/sec) Now the intervals themselves require some fudging because in this example, 700 is not an easy number to divide, and even then your intervalometer settings are to the nearest 10ms. You'll need to determine whether you would rather space longer or shorter and adjust accordingly. For example, if you want 150ft spacing, you can round up to 5 drops per second (200ms intervalometer) and your spacing will be 140ft (close enough for a 500lb bomb). Now here's what I'm wondering with Jester: when you tell him the spacing you want, does he calculate the intervalometer based on current groundspeed, or is the intervalometer virtually tweaked to match GS at delivery time?

The Tomcat airframe can take a lot of punishment, but less can be said about its INS. If your violent maneuvering dorked the alignment, you can either deal with it or switch to AHRS and RTB if it's serious enough. Bottom line: it's still better to replace an INU than lose an entire jet, so the price of dodging a missile may just be giving the enemy an M-kill instead of a K-kill.

There may be a number of things in play here: 1) While the WH stick/Cougar TQS combo is coded, it is not officially tested or supported. I tried to code it as best as I could, but there are combinations I may have missed. I need to know which module/profile(s) you are using when this happens. 2) With controllers dropping out, is this after initial script load, after changing profiles (i.e. between modules), or does it just happen inconsistently? Are both controllers affected, or just the stick or TQS? 3) Regarding pushing/releasing S3 (the pinky button), what you describe totally depends on the module selected. That said, I can't think of any time where pressing S3 should return actual keypresses. Please let me know the module/profile in which this happens.

Yeah, I regularly compare the Tomcat module to a religious experience. Being a former backseater IRL (albeit not the cat), and figuring that most people prefer the front seat, I started as RIO and taught 3 other people up to speed on the station. Then I started playing in front and had a blast, although knowing how an NFO should operate I often get frustrated with Jester. Now my comfort level in the front seat is near as good as the back seat, and I enjoyed every minute!

Radar gives you "big picture" items so you can see major points like mountains, cities, water, and sometimes roads (depending on material/prep level and surrounding areas). It's great for navigation and SA, but more difficult for precise targeting. You can find your target area using the AG radar (or even targets if using a doppler mode like GMT), but this gets you into the ballpark for a refined targeting solution using a pod.

I normally like to use the Disable Player Voice option when using VAICOM because I already know what I just said. However, with Supercarrier comms, sometimes the pilot will automatically make a transmission without VAICOM prompting (e.g. "Overhead, angels, fuel state"). For these comms, it can be awkward just to hear the reply from the carrier without having made the call in the first place. I would like to see an option to at least enable player voice during the automated calls like this, while suppressing player voice during actively initiated calls.

For newer aircraft like the F-14 and F/A-18, you'll need to use the name of the airframe under the liveries folder in DCS/CoreMods instead of bazar. For example, if your DCS path to the F/A-18 is DCS World OpenBeta\CoreMods\aircraft\FA-18C\Liveries\FA-18C_hornet then you will need to add the folder \Saved Games\DCS.openbeta\Liveries\FA-18C_hornet.

Are you asking where to install them?

2.48 is now available. Change log: Adds WAV file for station change Fixed bug with delay in airbrake LED F-5E: Added Aileron Limiter Override (S4), Pitch/Yaw Damper toggle, and moved Pitch Damper Cutoff (S3) F-14: Adds context senstitive Cage/AutoThrottle on T6/LTB F-14: Added VR Zoom to S1 (replaced default functions for VR)

Dude, that was seriously uncalled for. There are plenty of simmers out there who are as enthusiastic as we are, but just don't have the time to dedicate to full-switch sims. I know: when I was active duty I was too busy learning my own aircraft to learn another one, so I stuck with MSFS and Flanker 2, and I kept Falcon 4 on the shelf until I went to shore duty. The OP indicated that it was a time issue; someone's sim-relevance should not be judged based on real world responsibilities that limit recreational time.

I just finished it as well. Again, very nicely done. I especially like "GasCan" as your dig at the AI's skill at fuel management. I also like the "pinkie" trap at the end. Not too crazy, but not a Case I either.

Thanks for the quick reply. I'll be sure to download the latest version. Just a thought: to take out a runway, you don't really need to take out the entire runway. As fun as it is to run down the axis of the runway dropping on the entire surface, a big crater in the center will normally prevent all but helos and V/STOL from taking off. Operationally, we would weaponeer exactly this (and for crossing runways we would crater the intersection). Any more hits on the runway would be useful to keep it out of action longer, but that center hit is the most important one. If there's a way to score the weapon damage specific to the more central portions of the runway, this might be a good way to set the mission criteria. Personally, I wouldn't rename the files themselves. The way you have it now, I can just copy over the old files and not interrupt or corrupt my campaign flow. Thanks again for the quick reply. I'll be sure to let you know if anything else comes up.

@SpikeGondorff, I have to say I'm having a blast with your campaign. Add some voice overs to the already great dialogue and you have a commercial quality product. I am confused about one thing, though (poss bug report): on mission 7 (OCA Strike) I line up the runway, drop all 14 snakeyes at 200ft intervals (shredding the runway), and yet the Iranians still launch F-4s and the mission is a failure. I actually doubled back and verified that the bombs hit the runway. There was a bit of wind drift, so not everything is down centerline, but at least 10 bombs marked the runway. Is this a new issue with the ME, or do I need to set a delay fuse as one would IRL to cause cratering? With ED's current modeling of A/G munitions, I'm usually hesitant to arm a delayed fuse. Again, great stuff. I've told all my fellow Tomcat drivers about this campaign. Best, HF EDIT: F14SCEarnestWill_7_OCA.miz dated 7/12/2020.

Guam capsizes once a month. How else do you think they can maintain those golf courses? :D

Since the Pitch Damper Dump is a momentary press and the limiter override is sustained, they have to be on S3 and S4 respectively. For S3 to work as more than a shift function, it has to be an instant press and release. This is global architecture in the profile to allow dual function on S3 without forcing dual function. I have only supported stock SRS functionality to keep things simple. Adding this feature may be possible in the future, but right now the script is at the point where if I add something, I have to take something out (i.e. I'm at the stack limits of TARGET). Not a bad idea. The mapping is there for compatibility with the Cougar, but I like your idea. I may do that for Warthog users in the future once I start CTS 3.0. If you didn't put it in the survey, please do that specifically.

CTS stands for Configurator for TARGET Script, which is really just the GUI/front end for the TARGET script but the name just stuck. CTS applies to all TM Cougar and Warthog controllers, including MFDs. The link is in my signature (the TARGET profile link). CTS is also free, though if you would like to donate I request that any donations be sent to the charity listed in the linked post. EDIT: I see from another post that you're former USN. Ditto here (the wings in my sig are real). Thanks for your service!

I have incorporated this into the next build. I agree that S4 for limiter and S3 short for pitch damper cutoff makes the most sense. What I did with S3+LTB/T6 and S3+SC/T1 is apply them to the Pitch and Yaw Damper switch toggle functions. I wanted to have a way to switch these and there was no room on the MFDs.

I wish we could still rep posts. :thumbup:

@zepher, Since you're willing to make the initial investment, I also recommend the Warthog HOTAS. I have just about every DCS module, and the Warthog is satisfactory for all of them. If you want to go the extra distance, the Thrustmaster line is fully programmable with TARGET, which is essentially programming logic to the controllers using the C programming language. You can see what I have done in the TARGET profile linked in my signature. The Warthog is great, and its widespread acceptance means that it will continue to be supported and even have switch configurations catered to its throttle base. It is robust enough that you are not going to outgrow it like you might with other HOTAS solutions (like you would with the T.16000 stick). I also recommend the Cougar MFDs, though this is less important if you use VR or plan to transition to VR in the near future.