Jump to content
Game-Labs Forum

GShock

Civil War Tester
  • Posts

    352
  • Joined

  • Last visited

Everything posted by GShock

  1. Vicksburg capitulated on the same day as Gettysburg after almost 2 months of siege... which means, complete loss of the river, before the capitulation. The only way to win an enemy is to subdue it: The north, with the odds I mentioned would have never surrendered to accept the loss of half its country and in a condition of complete economic, industrial and political supremacy. There simply was no reason to sue for peace, its victory was only a matter of time even if Lee had captured Washington and crushed Meade while taking no losses. The conditions between defense and offense are very different: Lee's situation was desperate under all aspects and, this time, he was attacking.
  2. By the time Gettysburg happened, Vicksburg had been blocked and the Mississippi completely lost to CSA. Confederacy cut in half and no western armies to stop Sherman. Meanwhile, the population was starving as inflation had risen to intolerable levels. No, the war had already been lost to CSA at the capture of Ft. Sumter for the reasons stated above. 1, 10 or even a hundred battles won by CSA can't make any difference when by manpower alone you're facing 1 to 4 odds, when half your population is composed by slaves (who surely aren't sympathetic to your cause) and you have no navy to crack the blockades. I've always thought CSA efforts to be futile and having studied the subject on many books, I only confirmed my prior convinction. By the time Lee was in Gettysburg, almost out of supply and with odds of almost 2 to 1 in manpower and 4 to 1 in artillery, with no knowledge of the enemy, ANY offensive action would have resulted in a defeat; but for the dream of CSA to come true, Meade should have lost his entire army and Lee should have lost none in order to proceed to Washington. I think even capturing Washington wouldn't have made a difference but Lee had to gamble anyway because of that dream. A great propaganda by the CSA politicians sent an entire generation of men slaughtered for a cause that was as wrong as it was impossible to win. The same happened time over time in more recent history and even in contemporary history. It's happening right now as we speak in Europe and in the Middle East.
  3. A map editor, technically speaking, is a feature that allows you to draw a map... and the map is a bit more than just a graphical representation. More than just the modders, it takes map makers but before that, it takes the map editor itself which is probably part of the SDK and I don't think the DEVs would be willing to release it right now after the 1st title with this engine. There's scenarios to be made for future DLCs that map editor would fool. The OOB instead is about building the army and setting units on the field in starting or reinforcing position. That can be done, for fictional battles in Gettysburg... and it probably will be done later on. Your suggestion about the UI is in the cauldron. In due time I am sure it's among the top priorities. YES the DEVs read these pages.
  4. The routing issue is being addressed. I have other ideas about the reinforcements... but your suggestion will surely be put into the cauldron for this feature. Don't know yet what's gonna happen but something with the reinforcements is surely gonna happen. As of the battle editor I don't think this is possible because the map is something too complex to design, the OOB feature would be nice too. It's in the cauldron too. The battle replay is a great idea.
  5. The matter is extremely simple: a small state cannot go up against a large state, that a few cannot oppose many, that the weak cannot contend with the strong. Lee's defeat at Gettysburg was a desperate, futile and completely expected result that only his skill as a tactician had delayed thus far.
  6. The DEVs will identify the issue in the installer, should my wild guess be correct, if it's solved for you it will be solved for everyone through a hotfix pushed via Steam, they won't need to do anything: Steam will propagate the patch to their clients automatically. So... the sooner you try this step, the better for you and for everyone else.
  7. Did you already post about this in the Support forum? Have you already tried to uninstall the game, delete the folder and then reinstall it again? The issues you describe sound like version incompatibility which happens with faulty installations.
  8. For the time being, this much needed patch was released to address major faults and implement some new features (most notably, but not only, the arty limbering). In the future, all the pre-announced new features will be implemented while other bugs and glitches are addressed. At the speed of development we've had, without that freezing issue, UGG would have had a lot more fixes but it was more important to release a stable platform, gather the feedback of all players (which is what you just did) and then put down a new patching plan for the next patch. Rest assured, it's not over yet.
  9. We've been delayed because of a nasty freezing issue that took us almost 2 weeks to identify and solve. We have been testing the release candidate and i have strong feelings about the latest one we've been given. Don't worry, when you see the changelog you'll realize how big this patch impacts gameplay, why it took us so long (solving the freezes AND adding features and fixes at the same time) and you won't be disappointed. Patience, remember: the longer you wait, the bigger the improvements.
  10. Performing multiplayer tests. Don't worry you'll be notified when the patch is out. You'll all know.
  11. I am not at liberty to tell him WHEN or WHY, Myes. I told him all I could.
  12. It's not ready yet, patience, they're working on it.
  13. Only Beta can access the Beta forums. No ETA on release at present stage, the team is working 'round the clock.
  14. Listen to da man, he's the author of the guide!
  15. I had the IOS version test all over me and I am quite satisfied with it. This means it's MONTHS I haven't played the PC version. We've just begun the tests on the latest Beta and hopefully it can be released in a few days. That will put us closer to the tactical aspect satisfaction and then hopefully the IOS version is released and we can move on to the next steps for the PC version. Naturally, everything is perfectible but nothing is ever perfect.
  16. Hold on, we're testing the patch!
  17. The engine has 2 sides: the tactical aspect (the battlefield itself) and the strategic aspect (what happens in the background to move to the next engagement). The team is working on both sides but the 1st side is priority. Once the battle works reasonably close to a real ACW battle, then more focus can be given to the strategic aspects of the engine. In the meanwhile, the team is focused in releasing the IOS version and that comes before anything else. It's all about being a little more patient and all the problems about incoherence between one engagement and the next will be solved. I have proposed a solution that would have all of us involved in addressing this problem, I'd like to know if any of you has different ideas or proposals.
  18. No, not planned and yes, the overall CW campaign would be a set of scenarios but it couldn't be a real campaign because this game only impacts on the individual battles and not politics and economic issues behind the CW. Welcome to the forums.
  19. Publish the changelog before pushing out the patch itself!
  20. Don't worry about that. The game is even too balanced in regards to historicity. When you learn to use troops properly you'll see Wait for the patch, it's bound to come soon and many many things will change.
  21. You've got to learn how to use troops here. The game is a lot harder than it seems and there's a guide that may help you that REB Blunt wrote. IIRC it's in the stickies.
  22. There simply is no way to make everyone happy but the point is: since some people REALLY studied history and know a LOT about the american civil war (most likely more than the DEVs and surely the common knowledge of the community shadows the knowledge of any single person here, no matter how much he knows), since this battle in particular has been analyzed in OOB, strategies and terrain, I see nothing wrong (on the contrary I see it as the perfect solution) to have the community build custom battles that depict exactly what they know, what they think would have happened in case the Prelude had gone differently, in case Little Round Top had been captured by CSA, etc. etc. More in general allow the community to build the way they think the engine should switch from one battle to another and make these community-built scenarios "under evaluation" by the DEVs for implementation into the standard game. We most certainly already have the tools: Scenario setting (Build the briefing, set objectives: how many VP to be held by the end of the scenario; start/end time of the scenario) Map editor (which parts of the map must be used; where, what value and how many VPs must be put into this map) OOB editor (Build starting units [in all details, including their starting morale and condition] and leaders, build reinforcing units and leaders and assign these groups to the scenario) Battle editor (Manage reinforcements from OOB: the time of arrival, the location of their arrival) This stuff is already in the engine. If it is released to the community, people can start building Custom Battles and if these custom battles are historically accurate, the DEVs may put them into the game. This is called modding. Now, not only the quality of modded games is always better than the quality of vanilla games (as far as my humongous experience goes), but we also have the luck to have a person among the DEVs who's been a very talented and successful modder in the Total War engine environment and who knows this statement to be true... and he hopefully will agree. At the light of the fact the game is just out and that at present time the DEVs are entirely focused on the IOS version, I'd say there's no reason for harsh criticism right now (it is ultra-important to state here that I myself am very unsatisfied of many things in the PC version but I just take a different approach). There's reason to report, discuss and help the DEVs improve the game. The reason + the tools guarantee that this will happen. Let the flames, harsh criticism and even "go to hell" things come if at 2.0 the fixes asked haven't come. That's how it should work, in my opinion.
×
×
  • Create New...