Identification of spotted TF ,linked to sinking of subs because they do not get moved ? (Full Version)

All Forums >> [Current Games From Matrix.] >> [World War II] >> War In The Pacific - Struggle Against Japan 1941 - 1945



Message


ROSLEY -> Identification of spotted TF ,linked to sinking of subs because they do not get moved ? (5/24/2005 6:37:11 PM)

Hi,
It would be nice if spotted TF had a change of colour( or pulsed ) or something rather than on important turns having to trawl through all the reports , I am surprised this does not happen it would make it much easier to decide what to do with each TF .
I think that this is an issue why so many subs get sunk , I will move an ASW TF to any hex with a spotted sub , I think opponents just forget to move them . I have had a lot of success with this as both Jap and US . In fact I think that ships on ASW of low experience should be peanalised in some way esp when they are in a big TF , as at the moment you can put 10 PC or similar in the TF and just by shear numbers get the sub .

As a side note ... It would have been a nice bit of chrome to add the date a ship was sunk rather than the location ( or both )

Michael





bradfordkay -> RE: Identification of spotted TF ,linked to sinking of subs because they do not get moved ? (5/24/2005 7:02:47 PM)

It sounds like you are a candidate for Bodhi's WITP utility. It keeps track of sightings of enemy TFs, and the next version will keep track of sightings of your TFs. You can find it on Spooky's websight. http://mathubert.free.fr/




ROSLEY -> RE: Identification of spotted TF ,linked to sinking of subs because they do not get moved ? (5/24/2005 7:47:03 PM)

Thanks for this , I cannot see it on thhat site at the moment but iwill look later.
It should really be in the game ...
thanks
Michael




Mr.Frag -> RE: Identification of spotted TF ,linked to sinking of subs because they do not get moved ? (5/24/2005 9:30:54 PM)

It's a game mechanics issue, it will never happen based on how the code was written. The entire turn processing is done without any form of reporting at all based on the original design. Bits and pieces are tagged for recovery after the fact then the reports are created. This is why every single version has slightly different reports. The nature of the beast.

On a side note, this is also why sometimes you get a ship that looks to be sunk sucking up round after round of gunfire in what you see being presented. The reality is the entire naval combat routine is completed and all results calculated before you even see the window pop up to show you the animation. The animation being presented after the fact doesn't know the ship was sunk until it gets to the end of the routine. This may actually not happen until the following turn. [;)]




madflava13 -> RE: Identification of spotted TF ,linked to sinking of subs because they do not get moved ? (5/24/2005 10:27:50 PM)

I watch the replays with a pad and pen in hand just for this - I jot down what subs have been spotted, what CAPs need to be adjusted, etc. I just write down a word or two so that when I am giving my orders, I don't forget something...




bradfordkay -> RE: Identification of spotted TF ,linked to sinking of subs because they do not get moved ? (5/25/2005 7:11:48 AM)

" Thanks for this , I cannot see it on thhat site at the moment but iwill look later. "

My apologies, it is not on Spooky's website (though you should keep that website bookmarked anyway). Flip a couple a pages through this forum and you will see a thread by Bodhi on his utility. You'll like it.




Hartley -> RE: Identification of spotted TF ,linked to sinking of subs because they do not get moved ? (5/25/2005 7:15:42 AM)

I don't bother trying to track my spotted subs.

Way too much boring work.




madflava13 -> RE: Identification of spotted TF ,linked to sinking of subs because they do not get moved ? (5/25/2005 9:33:55 PM)


quote:

ORIGINAL: Hartley

I don't bother trying to track my spotted subs.

Way too much boring work.



I know you're not complaining about ASW being too effective or sub losses too high, so please don't take it this way... But for people who feel the same way as you do and also complain that their subs are taking a-historical losses, they need to think that one through again...

I don't mind keeping track, but then again, I'm a glutton for micromanagement punishment. And my sub losses are always very low...




Hartley -> RE: Identification of spotted TF ,linked to sinking of subs because they do not get moved ? (5/26/2005 2:04:56 AM)

1500 turns to play ,and only 24 hours in a day...


(And why is mission speed the default for sub patrols ? Really annoying changing it every time.)




Charles2222 -> RE: Identification of spotted TF ,linked to sinking of subs because they do not get moved ? (5/26/2005 8:52:05 AM)


quote:

ORIGINAL: Hartley

1500 turns to play ,and only 24 hours in a day...


(And why is mission speed the default for sub patrols ? Really annoying changing it every time.)



So what should it be set on? As the IJN I definitely prefer cruise instead. Is that where you're going? Some people seem to think subs do better at higher speeds, but I'm not exactly sure why they would think that, as higher speeds lead to being detected easier I would think (half empty perspective), and would indicate to me that they're on the surface with a higher speed. I tried a 'small' experiment in the early going with this game and I saw nothing that suggested one way or the other that speed mattered in regards to detecting or being detected, sinking or being sunk.




tsimmonds -> RE: Identification of spotted TF ,linked to sinking of subs because they do not get moved ? (5/26/2005 1:45:56 PM)

Full speed does however consume fuel much faster and it also is 5 times as likely to cause system damage. Go fast now, then go back home sooner and with more damage....




Charles2222 -> RE: Identification of spotted TF ,linked to sinking of subs because they do not get moved ? (5/26/2005 2:24:49 PM)


quote:

ORIGINAL: irrelevant

Full speed does however consume fuel much faster and it also is 5 times as likely to cause system damage. Go fast now, then go back home sooner and with more damage....


Yes, I am trying to save fuel and reduce damage both, but as to whether the higher speeds help gamewise I am doubtful.




Mr.Frag -> RE: Identification of spotted TF ,linked to sinking of subs because they do not get moved ? (5/26/2005 4:59:26 PM)

The routine works like this:

Each ship moves hex by hex. (independant of the speed of the TF it is in)

Each hex entered causes a roll for SYS damage with a small chance of success (SYS increases 1 point).

Each hex entered causes fuel to be deducted.

Each hex entered causes operational points to be added.

Once a ship has moved it's personal cruise speed maximum number of hexes ...

The same process continues BUT the cost of fuel increases dramatically and the odds on that SYS roll increase until the ship completes it's move *OR* runs out of operational points.

So you understand clearly, sticking a DD in with a group of AK's will result in the DD never moving beyond cruise speed as it's cruise speed is still higher then the AK's flank speed. This is why each ship is tracked separately.




bradfordkay -> RE: Identification of spotted TF ,linked to sinking of subs because they do not get moved ? (5/26/2005 6:39:38 PM)

When set to Mission Speed, subs will travel at cruise speed, unless chasing a spotted TF. What's the complaint with that?




Hartley -> RE: Identification of spotted TF ,linked to sinking of subs because they do not get moved ? (5/26/2005 6:55:36 PM)

quote:


When set to Mission Speed, subs will travel at cruise speed, unless chasing a spotted TF.


Odd. They difenitely seem to run out of fuel a lot faster on mission speed, even when stationary.




bradfordkay -> RE: Identification of spotted TF ,linked to sinking of subs because they do not get moved ? (5/26/2005 7:00:17 PM)

All subs will use extra fuel when attacked, by air or TF. Is this what you are noticing?




Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
1.828125