@zlefin If you're using 7621 or later, you can run TripleA from a Command Prompt and have all the console logs output to that window: Open a new Command Prompt window, e.g. via the UI or press Windows+R to bring up the Run dialog and enter cmd. Change to the directory where you installed TripleA, e.g. cd "C:\Program Files\TripleA_1.9.0.0.8304". Start TripleA using the following command: TripleA.exe -console. Then all the output that normally goes to the console will be duplicated in your Command Prompt window and should survive after TripleA crashes. If there's a lot of output, you may have to change the screen buffer size. You can do this by right-clicking the title bar of the Command Prompt window and selecting Properties. When the Properties dialog appears, select the Layout tab. In the Screen Buffer Size group, change Height to a large number like 1,000 or even 10,000.

@prastle oops, is that what that thingy is?

thanks gents went into engine perferences and turn console off ty again

Can you still click on the units and select them?

@redrum thanks for the reply - see attached 0_1515775033666_WW2.tsvg

The eastern continent has some open borders causing connection bugs. However there might another layer of bugs caused by attempts to fix it, by xml. Anyways those borders need to be redrawn in the baseTiles image. And then repair the xml by rerunning connections, and what ever else they changed.

@mattbarnes Thanks, nice and clear feedback. I am aware of that thing. When I uploaded a version to github, an earlier version got partly mixed into it. That's also why the name of Helms Deep is displayed incorrectly. But both are just visual bugs, so I don't feel like releasing a new version just to fix these two. And yes, 6 is the intented attack for axethrowers.

@mario-rafael-herrera-vaca 0_1513023963039_Console.txt

@mario-rafael-herrera-vaca Just meant was that the only TripleA version that you played the game with. I believe there was a bug in 1.9.0.0.7527 which can cause the save game to become corrupted when playing the AI. Please upgrade to the latest version (1.9.0.0.7621): http://triplea-game.org/download/ That won't fix your existing save game but you shouldn't see the error occur in any new games.

@mario-rafael-herrera-vaca Try a Japanese attack from Yakuts to southeastern siberia. Then, whait a couple of turns and you´ll find out that there is a perpetual winter in europe..See attached files for details. Thanks in advance for your attention. Kind regards, 0_1512986631255_eternal_winter_bug.tsvg

@mario-rafael-herrera-vaca try again with mail wgbt@gmx.at normally nobody is rejected

Ah great! Thanks. Downloaden the triple A 1.9.0.0.7652 ^^

I think "Test1" is the "Map Making Tutorial". If it's the old version with the misspelled "attatchment" elements, it was probably downloaded from SourceForge. I believe the one on GitHub has been fixed.

@basil-plant The real test would be to reproduce it with only a battleship under attack. To see if it actually takes two hits. Also what engine are you using?

@william0107 The bug should now be resolved in the current download on the website as well.

@gloriousbattle Yes, I really pushed some boundaries in making Greyhawk Wars and there are some quirks and bugs as a result. But they're mostly minor and don't keep the map from working. Except that it's unplayable in the current TripleA release (1.9.0.0.7378) because of a bug introduced to the TripleA engine 11 days ago (starting with .7374) and affecting casualty selection for battles in neutral territories (the kind of battle that happens all the time in Greyhawk). But that's already been fixed and the latest pre-release version of TripleA runs Greyhawk Wars just fine: https://github.com/triplea-game/triplea/releases Although I don't spend much time on this project anymore I'd love to hear specific information about other bugs. It's nice to know someone's finding enjoyment from Greyhawk Wars and I appreciate all feedback!

Thank you for your replies. The suggestion that I describe the bug to see if anyone might be willing to fix it led me to try it myself, and lo and behold I think I managed it. The problem was that it wasn't letting infantry units move after the first turn in which they moved, and the note that came up said they're unable to blitz. It was like the count of territories they were moving through wasn't being reset. Then in the AAA release notes I saw that for 1.8.0.3 “resetUnitState” was changed to “resetUnitStateAtEnd” and “resetUnitStateAtStart” so I opened the hood and replaced the old string with one of the new ones and it seems to work. Thank you again for your suggestions.

@redrum Yes. It had been preventing the placement of the naval assault marker for reasons I do not recall. It only required a small tweak to the game XML.

@RogerCooper It appears this map was a separate mod of hearts of iron which are no longer supported in 1.9. The reason it doesn't find the images is that its only looking here: Loading resources from the following paths: [C:\maps\hearts_of_iron.zip, C:\Users\ron\Documents\GitHub\triplea\assets] To resolve this you should either do: Merge this into hearts_of_iron (copy game XML and any needed images into it so you have just 1 zip with 2 games) Copy all assets from hearts_of_iron to HeartsofIron_Fatherland so its a standalone map and then update the name property in the game XML so it no longer points to hearts of iron: <property name="mapName" value="Hearts of Iron" editable="false"/>