Hi stillontheedge, Can you please post your debug.err file so we can take a look at what it says. The file should be located in your /Documents/My Games/Elemental folder. See this post https://forums.elementalgame.com/391297 for more information about posting files. Thank you.
The graphical problems in this thread are being addressed in the 1.19g update (see change log here: https://forums.elementalgame.com/406499 ) I was not able to test with the exact same card as you, but using a similar card I was able to get some graphical "glitching" that I believe is caused by the same thing that is causing the problem with your graphics card. When this update becomes available please install it, a
The bug has been fixed internally. We'll run it through testing and the next update will have the fix. Thanks again.
I'm looking into the mounted units graphical issue, where the character drops down into the mounted creature. It appears to be a new bug caused by some of the changes to save memory in animation data. Thank you for reporting it. I'm working on a solution.
Glad to hear it. Thanks for letting us know; it's very encouraging :)
Is this new with 1.19f or was this present before?
AlLanMandragoran , I loaded up the save game you posted from turn 81, but it doesn't look like your screenshots. I don't see a CariElf unit in the game and the city Huusaplige does not exist. Are you sure it was the right save? The turn 82 save looks like the screenshot and has the other cities, but is
AlLanMandragoran (and others), The save/load leaks are something I've been focusing on. Thank you for your detailed testing. I'm continuing to work on the save/load leaks and that data will be helpful. - CC
I've been killing several units in different ways, tactical, auto-resolve, auto-resolve from tactical units but am unable to reproduce this bug. Does anyone have a saved game that reproduces this issue? Like if you save before the attack? Also, i f anyone has screenshots of the units that are stuck on the map, please submit it. It would be helpful to see what kinds of units are involved. Thank you.
AlLanMandragoran , I need to know a little more about how this happening. Are you killing the units in a tactical battle and they remain on the map when you exit the battle? Are you auto-resolving the battles? Are you hitting auto-resolve from the tactical battle screen? Thanks in advance.
mywhiskey, Can you please post your autosave file that you are loading? It would help us to better see what is going on in your game that is causing it to use so much memory. Thanks in advance, codecritter
Interesting. I will let the art team know, and they will look into it.
harpo99999 and Burningvillage, c an you please post your debug.err files from the 1.19b version please? Thank you.
I noticed this bug is with 1.19. Have you tried updating to 1.19a? If so, does the problem remain in that version as well?
harpo, Can you please provide us with your debug.err file? It should be located in your /documents/my games/Elemental folder. Please p ost the contents here so we can take a look at what it says. For those of you with the "double eyes" issue, please post your debug.err as well. Those of you who posted dxdiags seem to have recent drivers. For the others, if you havent already, please make sure you update your drivers first and see if that
bubb9, Please try the following: 1. Delete all files in the C:\ProgramData\Stardock\Elemental - War of Magic\Screens folder. 2. Restart Elemental. This should cause it to generate the screen files again. There may be a short delay at the splash screen before the game brings you to the main menu. If this does not fix the issue, please let us know. Thank you.
Thank you all for sending in your bug reports. Fixing these memory issues is a HIGH priority for us, and we are working on it. Please continue to send in your reports, the more data we have, the more we can identify what is causing it. Thank you. - CodeCritter
Vandenburg, It appears to have crashed while auto-saving. Would you happen to still have the previous auto-save before that? If so, please email it to [email protected] . It may help us to identify what was using so much memory there. If you don't have the save, that's ok. If it happens again, please let us know and send the previous auto save and auto save files. In the meantime, we'll take
Hmm, that is interesting that it seems to detect shader 3. That data comes into the game directly from the video driver. When the game fails to validate the shader 3 method of rendering, it will default to the shader 2 method (which your card should support). I don't see any error messages about shader 2 method failing to validate, so the game should be using it. It's possible the issue may be resolved by some of the changes that have been made. The new update
Lantros, The graphical bug you saw in tactical is usually caused by a video driver incompatibilty. Also, one of your crashes occured deep in the graphics system (likely a driver issue as well) I checked your debug.err file and noticed your video drivers are from January 2009. Please try updating your video card drivers. You can check for new drivers for your NVidia GeForce 9800 GT at www.nvidia.com/drivers <
There is an auto-move camera feature in tactical battles. You can turn it off in the options screen by disabling the "Auto-move camera in Tactical" opton in the "Gameplay" tab.
Do you have larger versions of the screenshots? The smaller size images are hard to see what's going on. Thank you.
I believe it lets you rename the other players' units in multiplayer, but you only see it on your own machine.
If you don't see Janusk in your game, please post your debug.err file. Maybe we can find a correlation.
[quote quoting="post"]I know that it's not best to put all in one thread but here it goes: 5 - I can, still, rename units that are not mine. That includes the wives of enemy Sovereigns, to just mention one case. Maybe it's a feature and in case of being so, I'd prefer if that was confirmed. [/quote] Yes, being able to rename other player's units is intended. You can call them whatever you want. It's a feature.