Easy way to take note on capacity of vessels?

[mikmykWS]

ORIGINAL: uncleharpoon

Howdy Mike

Not sure I follow.

There are some folks who sounded like they wanted to bend some Access code, which is great. If they wanted their efforts to be put into the distro, I simply wanted them to contact me before they started changing stuff.

For those who can't code, but have requests, we can start some threads to that effect.

Hi Don!

Thanks for responding. In my first post I suggested using access and my only rationale for the request was the guys seemed to be letting you know the things they'd like to see in a new GUI. Very sorry I didn't articulate that well.

We are about to start a discussion on details of two features currently slated for 3.11:
1. Rev 2 of the Piracy model
2. Rev 1 of a polygon effects model.

We wanted to "test" the intended implementation of new features with the community, and to start getting folks used to our "agile" approach of more frequent, incremental releases.

Rusty will be posting on these as soon as we have the Gold build QA out of the way (we just got the first of the 3 manuals this afternoon).

Sounds great Don and I'm really pulling for Harpoon to do well with next release. You have some great people around the game that really need a win.

[KTCNet1]

2. Rev 1 of a polygon effects model.

Question - What the heck is a polygon effects model?

[Anonymous]

Hi,

ORIGINAL: KTCNet1

2. Rev 1 of a polygon effects model.

Question - What the heck is a polygon effects model?

I think he talks about the ESM uncertainty zones, displayed by dynamic polygons. There´s an issue with this in ANW, which sometimes leads to a cluttered display full of those polygons - can be very annoying.

Don - regarding ESM: Are you adressing the issue with subs detecting and precisely identifying ships over hundreds of miles, too?

[Bucks]

ORIGINAL: KTCNet1

2. Rev 1 of a polygon effects model.

Question - What the heck is a polygon effects model?

Without giving the entire "game" away, the "Polygon Effects Model" has nothing to do with ESM or Sonar. It would hopefully allow for the implementation of an abstracted model for something like Minefields or say interaction with biological contacts based on a predetermined probability.

Using the biological example, the scenario designer might draw a Polygon and assign it a 40% probability of a biological contact existing within the area. When a player's ship(s) entered the "zone" the game engine would check to see if the 40% chance was met and if so, it would "spawn" a biological contact (whales, tuna, prawns (shrimp)) to help mess up the player's ASW efforts.

These "features" are simply being discussed, although if the "Polygon Effects Model" can be implemented successfully, it would add further functionality to the Scenario Editor. It's simply a modification of the game's Exclusion Zones to do a little bit more than they already do.

Cheers

Darren

[Bucks]

ORIGINAL: koelbach

Hi,

I think he talks about the ESM uncertainty zones, displayed by dynamic polygons. There´s an issue with this in ANW, which sometimes leads to a cluttered display full of those polygons - can be very annoying.

Don - regarding ESM: Are you addressing the issue with subs detecting and precisely identifying ships over hundreds of miles, too?

Ralf,

In regard to the sonar issue, I doubt AGSI are able to do much to solve the problem you've mentioned. The new sonar system implemented in 3.10 is much more accurate although it will need DB Editors to do considerable work to get it working accurately in the game.

I've started working on updating the HUD3 to take the changes into account, although I can't promise it will be fully updated prior to the release of ANW 3.10. Part of the new model includes a new geographical feature allowing the sonar conditions to be set to the Scenario's geographical location. Along with the changes in weather effects and increases in platform speed having been updated, I'm going to have to tweak my numbers as we move forward. As stated I doubt this work will be completed before 3.10 and a full HUD3 sonar "overhaul" will probably be on the cards for shortly after 3.10's release.

In this case the "issue" isn't directly related to AGSI's code change as Chris Carlson was heavily involved in the development of the new modeling and this is more a case of DB Editors coming to terms with the changes and implementing an accurate model for their particular database. I'll update the forum as to my progress with the HUD3 as soon as 3.10 has been released.

Cheers

Darren

[Anonymous]

Hi Darren,

thx for the update and - great that you´re back here !