jmarso

Valid point.

Something else you can do once your missions are built and ready to be just played rather than tinkered with: Put them in an OvGME mod and install them to the appropriate modules in your main game folder. (Not the Saved Games folder). When there's an update available, they can be uninstalled with a click along with all your other mod files until the update is done, and then re-activated.

Arigato!

Hey, where are these screenshots that everyone is raving about?

Actually, I like this idea as an option separate from the crew contract utility. No so much 'shut up Jester,' which can be handled through the contract utility, but a 'Talk to me, Jester!' command that would sort of be like asking for bogey dope from the AWACS. It could be mode dependent. If the plane is in A/A mode: When the pilot says: 'Talk to me, Jester!', Jester could immediately reply with: 1. BRA to nearest threat / threat group. 2. Type A/C of nearest threat / threat group if known (Via ESM or what not) 3. Closure rate to nearest threat / threat group if he can calculate it 4. Own airspeed. 5. Own angels. After that, he goes back to making his normal AI calls. If the plane is in A/G mode: 1. Bearing / range to the nearest ground threat 2. Bearing / range to the primary target 3. Current weapon setup. (Type, number, interval) 3. Own airspeed. 4. Own angels. If the plane is in any sort of non-combat navigation mode: 1. Bearing / range to home plate (If datalink or TACAN or some mode of guidance is switched on and Jester should reasonably have that information. To a degree, he should ALWAYS have it as the crew navigator.) 2. Ship's BRC, if he could reasonably be expected to know that. 3. Bearing /range to nearest divert. Think variations on TOPGUN: Iceman: "Talk to me, Jester!" Jester: "Nearest bogey is bearing 090 for 40, speed 450, 900 knots closure! We're Angels 20, airspeed 450. Go get him, Ice!" Note that this is a bit different than what some other people are asking for, in terms of intercept vectors if, perhaps, the two aircraft weren't driving straight at each other. A variation on Jester's reply could be: "I've got a bogey bearing 090 for 40, heading 315, speed 450, 675 knots closure with a left bearing drift. We're Angels 20, airspeed 450. Come right heading 135 to take him down the left side, or left 045 to stay nose-on." The last one is getting pretty complicated for Jester AI, although it's mostly math (easy for a computer processor) and recording a crapload of voiceovers to cover a veritable boatload of contingencies. The first example, a simple BRA following by own altitude and speed, is a lot simpler to implement: it shouldn't need any more logic than already exists for getting a bogey dope call from AWACS.

I'm not at home right now so I don't have access to the game or my files. All I can suggest is that you make sure you follow the installation instructions for the required mods according to their own individual README files. As of the latest game update, all of it still works on my machine which indicates the mods themselves shouldn't be broken by DCS itself. If you are getting the 'need modules' message, it points to an incorrect mod install somehow. For whatever reason, DCS can't find the mod files it needs to load the mission.

https://www.digitalcombatsimulator.com/en/files/3304473/ Naval Collection Mod https://www.digitalcombatsimulator.com/en/files/3301580/?sphrase_id=18880259 US Navy Deck Equipment https://www.digitalcombatsimulator.com/en/files/3302670/?sphrase_id=18880265 Civ boats version 1 I think putting the links in a quote may have borked them. Finding and posting these links took me all of one minute on their site, however- probably less time than it took to type the above post about the links being broken.

You don't have to hit Shift-U again, just wait for it. If nothing happens, hit it one more time, and then wait for it. As soon as the cat fires, get that throttle forward!!! :pilotfly:

Okay, fired it up both to play and in the ME, and it loaded fine for me, so the mods themselves aren't broken by the latest updates. The victory cargo module as I used it in the mission build is part of the NAVAL MOD COLLECTION mod (https://www.digitalcombatsimulator.com/en/files/3304473/), not as a separate module, but that's already listed in the README. So I'm not sure what the issue is. My best advice would be to uninstall all those mods and then reinstall them, and give it another whirl. The only time I an error message like that is when a mod is missing. You might also want to check where the mods are installed and make sure they are in the right folders. I use OvGME for mod installs. That's the only other thing I can think of off the top of my head. Just about all the missions use the USN deck crew mod. Are they working okay? Also, try mission 12: Kill the Kilo. That one also needs the naval collection mod. Another possibility: Sometimes updates wipe user-made stuff out of the folders. You might want to check your mod installs and make sure they're still there!

Not just yet. I'll have to fire it up a little later and see what happens. Hopefully it's not another case of a DCS World update breaking mods.

Clearly, you needed a micronap! ;)

As a player, you can 'help out' the AI sometimes so it's not always chasing you in full burner, eating up gas. 1. After launch / takeoff, make a slow, climbing circle around the field to allow them to get off the deck behind you and join up, without having to run after you in a stern chase as you haul ass off towards the far horizon. 2. When you climb as the lead in a formation, use less than full mil. This gives your wingmen some power surplus to stay in position. If they fall back and you are climbing in full mil, they'll go to burner. 3. When you descend, use slightly more power than flight idle. This gives your wingmen a 'surplus' on the negative side for minor adjustments without having to pop the speed brake and kill their fuel efficiency. 4. If you are holding in any sort of orbit, stack your wingmen to the inside of your turns, not the outside. They'll burn less fuel making that shorter circle on the inside of your turns rather than chasing you on the outside. 5. The more wingmen you have, the more you should 'take it easy' on them maneuvering as a formation. Dash-4 is always left sucking wind when it comes to the fuel ladder. Have a bandit day!

I can't say for certain, but I think it may have something to do with the 'sliding airplane' glitch someone mentioned in another thread, especially when the ship is moving at high speed. You can still get it to launch you when it hangs up- I throttle all the way back to idle, and wait for it. As soon as the cat fires, jam it into burner. The spool-up time on the Tomcat-B is so good that it'll catch you before you come off the end. Not a 'realistic' solution in the slightest, I know, but it works and enables you to launch without having to exit and restart the mission, sometimes multiple times. It's a frustrating glitch.

The mission pack has been out for a while now with over 150 downloads. I'm going to leave this thread here for discussion and feedback, and suggestions on tweaks / improvements for possible future updates to the mission pack. Just as an FYI, I'm not planning version 2.0 until after the new carrier module is released. Below is the text taken from the original README file.

I did the Nyogel trick to my TWCS today. Testify that this fix works like a champ! Basically, it turned this throttle from a solid 6/10 into about an 8/10.

+1. It's absolutely ridiculous.

It's not your imagination, I'm thinking. The first thing I did after updating was hop in the Tomkitty for a lap around the Stennis. Much smoother, it feels like, with less power needed, and much less squirelly with stick inputs. Like it better; still not sure it's as good as when I first bought it. EDIT: Didn't try it after having a heavy stores load at the start. I guess you could gen up a quick mission, load her down, then jettison it all behind the boat and see what happens in the pattern.

I do that in the mission editor. In the mission planner, someone else has already picked the livery and the loadout. If I want to change it, I have to cycle through all the units.

When you are in the mission planner / editor and on the page where you assign ordnance and liveries and such, a check box (button) so that you can automatically assign the same loadout or livery to an entire flight without having to click through each unit separately.

Anyone else have a problem with the throttle detents over time? I found a video for removing them completely, but found I didn't like that solution. The problem is that the detents start to get 'mushy', where you don't really go 'past' them anymore but sort of force the throttle into position (say, AB) and have to hold it there, as if its spring loaded. What I'd like is a way to get the detents working properly again. Anyone have any pointers on how to do that?

Boom. It's a poor craftsman that blames his tools. Not that Jester is a tool... :D

Curious: how is this useful in VR if you have to lift the headset to type into the scratchpad? I suppose some people can type 'blind' like that with no problem; I don't have to be looking at the keyboard to type, but I DO have to at least have it in my FOV not to fat finger everything into unintelligibly. How are you guys utilizing this?

For me, that's been one of the nice things about playing in VR on a Rift-S. I have to wear 'old guy' cheaters looking at a monitor using TrackIR, but in VR I can shuck the readers and just wear the headset. If you have distance vision problems, you'll have to work something out with glasses or contacts or what not.

"I wish Meg Ryan could have seen that 3-wire!" (Or something like that. Love the Meg Ryan references.)

A key troubleshooting point would be whether or not he gets the message about the SAM site being taken out, and the SEAD package calling off target.