[Lupus]

It seems that NWD's reticle mod is built in by default, that the carrier mod is built in by default. My problem is I don't like the reticle mod. Not anything against NWD or his work, but at least with my rigs setup in game I can't see the whole reticle. I can only see the inner ring and a few hash marks outside that, I can't see the outer ring. As a result my aiming is off.

I don't want the carrier mod either. My squad flies navy planes. We land and takeoff from carriers. Not everyone uses these mods, as a matter of personal taste. As a result, the carrier mod is not something I can use. I'd like to disable it. I can't.

With the old style UI, I could pick and choose which mods I wanted enabled. I could choose to have this one or that one. I didn't have any single mod forced on me. They were all optional. With the HSFX and UP, this is not the case. I have some mods forced on me. For most of them this isn't a problem. However, in the case of these two mods it is a big problem. One that means I will have to find another way to mod my IL-2.

I'd just as soon remove these mods, but I can't. So I'm stuck with loading individual mods and using a mod activator etc. I know it seems odd to ask for a mod to return some functions to stock, but. . . if anyone would consider building a mod I can activate to override these mods with stock behavior I would appreciate it.

I appreciate any help you have to offer.

Here is what I see ingame just fyi:

[/img]

[Checkyersix]

There's a way to turn off the carrier mod on a mission-by-mission basis, by including a line in the [MODS] section of the .mis file.

If you don't want the AI to use the catapult in a particular mission, you can add a [Mods] section to the end of the .mis file (if you don't already have a [Mods] section), and set the CatapultAllowAI parameter equal to 0. It would look like so:

[Mods]
CatapultAllowAI 0

If you don't want the AI to use the catapult in ANY missions, you can add the [Mods] section to the end of your conf.ini file (if you don't already have a [Mods] section), and set the CatapultAllowAI parameter equal to 0. That way you don't have to add it to each mission file. It would look like so:

[Mods]
CatapultAllowAI=0

Notice a slightly different format between the two. In the .mis file the parameter name and value are separated by one or more spaces. In the conf.ini file they're separated by an equal sign (=). Be sure to make a backup of your conf.ini before trying to make any changes.

The README file for the Carrier Takeoff mod explains all the different optional parameters that can go in the [Mods] sections.

Fireball

HSFX 4.1 includes the persistent .mis [MODS] section mod, so you only have to do this once for each .mis file.

[Lupus]

Thanks I'll check that out and give it a shot.