Gray_Lensman wrote:bigus:
Unfortunately, your test scenario under v1.15 will not be able to test against the new changes done under the QuickFix for v1.16. The scenario database has unavoidably been reworked requiring scenario regeneration to fix the supply bug issues in and around New Orleans, Ft. Gadsden and even Charleston, S.C. Once we have the kinks worked out, and v1.16 is actually declared to be "official", we'll make the database available as normal.
Interesting about region #349 (next to Ft. Gadsden), the adjacency(s) are there and there is no accidental Land Interdiction JumpLink, so I wouldn't know why supply could not be forwarded into an Ft. Gadsden, the adjacent region, unless you have no end use unit in the Fort to draw the supply to.
Gray_Lensman wrote:Hold on... I'm working up replacement Iberville and Ft.Pike .rgn files. I'll post them in a few and if you have a game going with Naval units to move into New Orleans we'll see if the dual bombardment issue is solved with the Naval Interdiction Jumplink mentioned above...
edit> Here we go... Below (zipped up) are a couple of test .rgn files for the Iberville (716) and Ft. Pike (1121) regions. They belong in the ...ACW/GameData/Regions/... folder replacing files with the same name
.
Gray_Lensman wrote:Game wise... Ft. Pike is a separate region and not within the boundaries of the Iberville region geographically in real life, why should it share harbor values with New Orleans?
GraniteStater wrote:All I know is that if I am in doubt about Supply somewhere, I address the issue. I said "WAD" largely from a modeling viewpoint.
It is December in the Pennsylvania mountains and you will die without a Wagon, 'cuz you're not near a supply source (no Level 3 City or not in a smaller Town with Supply; nor a Fort; nor a Depot). WAD. Bring your food with you, ninny.
You are General Burnside in April of 1862 and the beachhead is going to be wiped out 'cuz the War Dept. hasn't sent you a rasher of bacon or any ammo for six weeks. WAD. Give landings plenty of support.
I land 100,000 men, horses, artillery and auxiliaries in Mobile and eventually have problems keeping a quarter million supplied in the Deep South. Build lotsa TPs and Wagons for a war winning invasion, General - you're gonna need 'em. WAD, IMHO. 1863 is not 1943; the best you can do is moor large vessels and unload at a proper dock or take forever with lighters and skiffs.
Thus an amphibious operation must first seize a major City on the littoral to support operations. Same for riverine attacks. Same for any "Marches to the Sea" or similar plan. Major thrusts need to be supported.
Gray_Lensman wrote:Probably something in the game engine NOT making an exception to the movement of a naval unit moving from one adjacent region to another when one of the regions is a land region. Pocus will have to check into it since I can't find a data problem or a data solution to prevent it. I was hoping that placing a naval interdiction jumplink would override it. No such luck.
edit> thinking about the Naval Interdiction JumpLink NOT stopping naval bombardment of passing fleets... This is WAD with further thought... If Naval Interdiction JumpLinks were to be made to stop Naval Bombardment, it would invalidate most of the bombardment capability of the existing in-game forts
Eliminating the shared border adjacency(s) between those regions would most likely work, BUT then no land movement could take place between Iberville and Ft. Pike. (not desirable)
edit> more reflection... I actually think reworking the border points to eliminate the adjacency between Iberville and Ft. Pike would work since there's already a pre-existing minor river ferry JumpLink for land units to use even if the regions are not adjacent... This will take some minute adjustment of the Iberville (#716) border point to remove the common adjacency but leave the graphics matched up (an overlap effect of the graphics but invisible to the gamer).
Gray_Lensman wrote:I was able to check the land movement using the pre-placed USA units in the 1863 Campaign scenario. The land movement was unaffected as I thought it would be since the Minor River JumpLink provided the movement link. All that remains is for you to check the bombardment behavior in your scenario once more. Crossing fingers and listening to "Jeopardy" tune in the background.
.
Yee Haa wrote:Please what does WAD stand for, I am guessing from context that it in some way refers to factors designed for purely historical aesthetics ie; background. Explanation pls?
Jim-NC wrote:Hello and welcome to the forums.
If the file you are referring to was posted by Gray_Lensman, then it is gone. He deleted his posts a little while ago. So, sorry, no quick fix (unless someone can find it and re-post it).
Return to “AGEod's American Civil War”
Users browsing this forum: No registered users and 12 guests