CasoDB AMENDED - New Database and scenarios

[Herman Hum]

Next increase in rank will be for Chief Petty Officer after 99 messages.

[aotino]

Next increase in rank will be for Chief Petty Officer after 99 messages.

Okay. I'll probably earn that by the time I'm finished with the entire Indochine Campaign - a while from now.

I am ready to announce the 4th and last scenario, "Falklands Revisited," and that will close out the 2nd battleset of the Indochine series, "The Abyss of War". I have the announcement ready to post as well as an announcement for the end of the battleset. Attached is the scenario - fully tested and functional. When you give me the thumbs up, I'll post the announcements.

Thanks,
Alan

[Herman Hum]

The scenario has been added to the Library installation files and await your signal for release.

[aotino]

The scenario has been added to the Library installation files and await your signal for release.

Will get on it this weekend. Thanks, Herman!

[aotino]

End of 2nd Battleset – “The Abyss of War”

This scenario, “Falklands Revisited”, is the eleventh scenario of the campaign and the last of the second battleset – “The Abyss of War”. The next battleset of the Indochine Campaign is “Too Few Victories”. With luck and some hard work it will come out sometime later this year with a series of 6 scenarios. I hope you check in and play.

Thanks, Alan Caso

****************************************************************************

The 11th NEW Indochine Campaign Scenario!

11 Falklands Revisited

South America/Caribbean/US/Canada:

Argentine surface forces begin strikes on the Falklands. A newly built carrier on lend-lease from China is a knock-off version of the Russian Moskva-class carrier. It carries updated and redesigned Yaks, which have been much improved since the initial Soviet designs. Also aboard are Sea Harriers from India, all of which help embolden Argentina's new power projection. The Argentine military nows feels confident that, with a much-bolstered and built-up military, coupled with the British engaged with commitments elsewhere, an eventual occupation of the Falklands (Malvinas) has a high chance of success.

With their forces stretched thin, the British Government appeals to Chile for assistance. However, the Chilean navy is anticipating trouble with Argentina in the Straits of Magellan, and so is unable to respond. Brazil still hesitates to become involved, preferring to remain neutral.

In the interim, the Royal Navy and Auxillary Forces cobble together a small convoy and escort in an attempt to break through and resupply the Falklands.

Author: Alan Caso

This is the eleventh scenario written for ANW and HUE using the customized CasoDB. The scenario and database are bundled within the PlayersDB installation file due to its phenomenal popularity and ease of use.

Harpoon3.6.3 users can get the Complete PlayersDB Harpoon 3.6.3 Library
Harpoon ANW users can get the Complete PlayersDB Harpoon ANW Library
Harpoon HUE users can get the Complete PlayersDB Harpoon HUE Library

"Harpoon for Dummies" channel

[Herman Hum]

The files have been released.

[aotino]

Hi Herman,

Long time no talk to. Have been enjoying reviewing your latest submissions.

I have been going through a very frustrating test period with my next batch of scenarios. The biggest issue has been getting air-released Harpoons from Vikings, and Exocets from Cougars from striking their designated targets. Almost to a missile, they veer and choose their own target. Its extremely maddening and a waste of time, as the units require 5+ hours to reload before they can be relaunched again - generally half or more of the time required to play an entire scenario. Why do these weapons not attack on target? I'm thinking I have to re-edit my Db to make shorter turn around reload times on some of these weapons because of the time wasted between air launches. Otherwise, there's not a chance of a side effective taking out another side through these weapons. Any idea of why these weaps seem to have a mind of their own?

Thanks. Any tips would be apprecated.

Best, Alan Caso

[Herman Hum]

The behaviour you describe is only found in ANW or HUE versions. In H3, as long as you had a solid contact on your target when the Harpoons launch, they would strike the selected target.

In ANW and HUE, the weapons always go active at a certain distance from the target. When they go active, they will select their own target within their field of view. This does not necessarily mean that they will engage the target you selected for them. There is not much that can be done about this phenomenon. I believe that AGSI does not even consider this a problematic behaviour. I think it is deliberate on their part, even though it may be a bad idea (IMO).

What can be done about it? The easiest solution is to play in the H3 version where this behaviour is not seen. Since CasoDB is only available for ANW or HUE, there are less options. You can try to edit the database so that the sensor on the weapons have a smaller field of view. However, this also makes them less sensitive at the times you may WANT them to have a larger field of view.

You can also artificially add things like communications datalinks to the weapons and launching aircraft. This would make them guided weapons and less susceptible to this abhorrent behaviour. However, these datalinks are not normally found on the weapons and would likely make them more accurate.

[aotino]

Ah, well that would explain it. Oh well, I'll just have to figure a way to work within it. Okay thanks. I should have the first two scenarios of the next group out by the end of October. Best, Alan

[aotino]

Hey Herman,

Am very close to finishing the announcement to the next battleset. Have the first scenario tested and ready to go with the second one very near completed. Wanted to give you a heads up, if you would do the honors of setting it up in the library.

Also, am toying with the idea of shortening the loadout times for AGM's and ASM's in the Caso Db. An average of 6 hours is often too long for reloads in my scenarios, as I try to create games that play somewhat quickly. I'm not committed to this idea yet, and I know it flies in the face of reality - however, there's nothing of reality in my campaign anyway, as you are well aware. I figured I'd approach it in much the same way as I did in my mine edit. I believe after I make the edit, I open all my scenarios in the scenario editor and it updates them. As for the forum, I guess I re-release an updated Db?

It also wouldn't change game play in any significant way in all my previous scenarios, as a faster reload of AGM's ASM's would not alter positively or negatively the player's chance of success.

Anyway, I'm just thinking aloud here. As I stated previously, I'm not committed to this idea yet, until I get some feedback from you.

Cheers, Alan

[Herman Hum]

Also, am toying with the idea of shortening the loadout times for AGM's and ASM's in the Caso Db. An average of 6 hours is often too long for reloads in my scenarios, as I try to create games that play somewhat quickly. I'm not committed to this idea yet, and I know it flies in the face of reality - however, there's nothing of reality in my campaign anyway, as you are well aware. I figured I'd approach it in much the same way as I did in my mine edit. I believe after I make the edit, I open all my scenarios in the scenario editor and it updates them. As for the forum, I guess I re-release an updated Db?

It also wouldn't change game play in any significant way in all my previous scenarios, as a faster reload of AGM's ASM's would not alter positively or negatively the player's chance of success.

There a number of different ways in which you might want to implement your shortened Loadout Ready Times. You could:

1. Do as you suggest and just change the ready time values for each of the aircraft from their current 6 hours. This will change all your previous scenarios that have these same aircraft. Also, one loadout maybe used in many different aircraft. The faster preparation times will increase the tempo of air operations and will probably have a significant effect on any previous scenario. It is not a problem for your previous scenarios as they will be synchronized to use the new information. This option has the most far-reaching effects.
   
2. Create new Loadout entries for the same weapons and add them to the aircraft. This means that a plane might have two ASM Skua loadouts, one for 2 hour ready time and one for 6 hour ready time. If your previous scenario required 6 hours, this will not change since the planes will already have that ready time selected. This option can be confusing for players since they will see the same loadout with different ready times.
   
3. Create new plane entries for the planes you wish to have faster ready times. Then, create entirely new loadout entries with shorter ready times for the new planes. Once the new plane entries are created, remove the 'old planes' from your scenario and replace them with the 'new plane entries'. This is the way the PlayersDB handles changes because it always preserves any older entries and has no effect on previous scenarios. The new entries would only be used in new scenarios.

You are certainly free to chose the option that best fits your needs. Most other DB editors appear to use #1 even though it may have detrimental long-term effects on pre-existing scenarios.

[aotino]

You are certainly free to chose the option that best fits your needs. Most other DB editors appear to use #1 even though it may have detrimental long-term effects on pre-existing scenarios.

Thanks Herman. I'll look into it and see if it's a feasible option for my Db. Much obliged!

[aotino]

Hi Herman,

Well I reviewed the pros and cons of amending my Db by shortening loadout times for aircraft weapons. I went forward with it, doing a major overhaul of most of the loadouts for aircraft. I set up a scenario to test and the results were very satisfactory. I have run all the present existing scenarios in the Indochine campaign by resaving them with the amended Db, and they are all in good shape. I have prepared an announcement for the amended Caso Db, have the headline paragraph ready for the third Battleset prepared, ("Too Few Victories"), and have the first two scenarios tested and ready to go, although I'd like to take your advice and release them one at a time, to spread it out. Let me know when you might be able to set up the new Caso Db for the library and when you could add the third battleset to the game.

Very much obliged.

Best,
Alan

[Herman Hum]

Of course, it is your database and scenarios to do with as you please. However, I think that the shortened times will have a significant effect on some of your scenarios. The shortened ready times will allow aircraft to participate more frequently. The things that do not change are your ships. They will continue to move at the same previous speed. This means that ships and land targets will face a higher rate of attack. This is not a criticism, but simply an observation of cause and consequence.

When your new battleset description is ready, simply attach it to this thread or post it as a message. It is easy to set up the new Too Few Victories.DSD file and sub-folder. If the revised database is also ready to go, please append it to this thread. Let me know if you wish for me to synchronize all your previous scenarios for compatibility with the revised database?

[aotino]

However, I think that the shortened times will have a significant effect on some of your scenarios. The shortened ready times will allow aircraft to participate more frequently.

Yes, that is very true, and I am very appreciative of this warning. The effect on all the previous scenarios I've released is minor as they have not relied on any significant offensive strategy - up to this point the campaign has been defensive. Practically all the weaps loadouts amended have to do with attack and standoff weapons - no AAW weaps at all. It should be fine. More importantly, it will help in my upcoming scenarios, and my ability to design them the way I prefer.

When your new battleset description is ready, simply attach it to this thread or post it as a message. It is easy to set up the new Too Few Victories.DSD file and sub-folder. If the revised database is also ready to go, please append it to this thread. Let me know if you wish for me to synchronize all your previous scenarios for compatibility with the revised database?

I will get everything together and attach the battleset description along with the revised database tomorrow. I do not need you to synchronize the previous scenarios, as I have done that already. But, thanks for offering. Got some fun scenarios coming up. They will irritate all the old hard noses of the forum, but the members who support things outside the box and like to have something fresh and different might enjoy them - like you. Appreciate the encouragement!

Thanks Herman!

Best, Alan