Ashpire

Thanks to Stardock for the continued refinement of this great game.

Astounding... How can your head not explode? It's terrific to see this level of care and effort go into the game. Thanks very much.

All my Ashes startup problems were fixed by increasing my total page file (virtual memory) size. I now have something like 8GB total page file, on SSDs. (I only have 8GB of physical RAM). BTW, this was done by setting a fixed size on each of the disk I wanted to be used (same value for Max and Min). I don't let Windows manage the page file size.

Here's the DropBox link. Not sure what you mean about posting the email... Just reply here when you've gotten the file. https://www.dropbox.com/s/izu318i41iabwtj/Save%2017.3.27%20EasyDef%20A4%20-%20Replay%20Crashes%20at%2031m.AshesSave?dl=0 The symptom is that at around 32:30 the graphics freeze. The time varies a litt

Win 10 64-bit 8GB w GTX 770 (4GB) - Intel CPU - 12GB page file - Ashes 2.20.26289 on Steam I have a save game that when replayed will always crash at the same place. The NVidia driver (March 20) and Win10 are up-to-date. No apparent hardware problem (temps look fine). --> Do the devs want this 10MB file for troubleshooting? Seems like it would help find something, unless crashes on an 8GB machine are 'not unexpected'. I can't add more RAM.

Bumped 'cause I think it's an Ashes issue.

The MOD hasn't changed in six months and is just an annoyance for me. I'd like a switch to turn it off... Or some mechanism where the message wouldn't repeat until it does change.

Steam / Win10 64-bit NVidia gfx latest drivers. EDIT: I thought this might be a hardware cooling issue but now believe it's the game, since it happens at the same exact point repeatedly. It should be easy for someone else to test this... Set up a skirmish between two "Insane" AIs on the Espana map. Turn Victory Points, neutral creeps, air units, and orbitals off. Zoom all the way out, and run the match at "Fastest" spee

I currently have 4GB of page file on each of two SSDs i.e. 8GB total. So, probably, page file size is not your problem. Though you could try adding more on a separate drive, temporarily. Even if its a mechanical drive and slow, you might learn something. Ashes does not crash for me with any amount of tilt & zoom. Windows 10 64-bit w 8GB RAM. NVidia GTX 770 Gfx w 4GB RAM. Running DX12 (could not do that until I increased my page file to the sett

If by 'fix' you mean technique, you just hold down the shift key while zooming. Then the tilt is maintained. I deleted my post because it was a discussion of how such a feature might be implemented - pointless once I found it was already available in an intuitive way. Crashes of a stable feature in this game are often due to page file size. Check around on that and experiment with making yours bigger.

[quote]advice on how to set up a 'least privileges' arrangement [/quote] HOW TO CHANGE FROM THE WINDOWS DEFAULT ADMINISTRATOR ACCOUNT TO A STANDARD USER Running as a standard user is universally recommended. It's too bad that Windows does not guide you to this, and that clear instructions are hard to find. These steps assume that you installed Windows 10 as a single user, making no effort to avoid being an

Thanks very much for all the updates and refinements! Especially Observer mode, a feature I've been wanting. It's great to see development continuing.

As a relative noob and single-player only, my humble 2 cents is that Ecalation is not too complex. It's easy to outgrow the base Ashes. It's ironic that the people I see asking for the base game to continue are multiplayers, who are no doubt the most skilled. But - there may be a market for the base game and Stardock really wants to have a low-$$ offering. So... You could have one product with both "Ashes Classic" and "Ashes Escalation" choices on the intro scr

Advice on the Steam forum pointed me towards increasing the page file size. Going from 2GB to 6GB cured this graphics problem in both DX11 and DX12.

This really should be fixed (assuming it's a bug) as it seems unnecessary and is very annoying: If I select a unit and then click anywhere near a dreadnought, they automatically form a group! Which I have to disband before I can continue with my original plan. IIRC this also happens if a dread is selected and I click on another unit... I think this has been mentioned before but is one of those things that appears so simple to correct that I have to b

You should absolutely go for the 1440. Your system will easily handle it, at least for Ashes, and the visual advantage over 1080 will far offset any drop in performance. And there are other general benefits to 1440 including much more screen real estate. I wouldn't want to go back even to 1920 x 1200.

Thank you! In UnitTemplates.csv I selected the Pan (currently line 18) and set its HP and Armor to -1. I set its Heal Rate to 99999. This gave me an invulnerable observation unit, as I wanted. I wonder two things further: I'd like to remove its attacking power, but can't find a setting for that. And there appears to be a ceiling on the sight radius - I tried -1 and 99999 but it remains limited. Still, very usable and of course I can make mul

In Escalation single-player skirmish mode, I want to create an "invulnerable" unit for observation use. I'm thinking of a Pan or maybe Brute, that I can send off to the AI camp to watch & learn about development. I know there are other ways to learn, but want to try this. In the Unit Template CSV file, I tried altering the "Armor" value on a Brute AssetID; however, that seemed to have no effect. Can anyone tell me exactly what to change to do this (greatly increase sur

[quote]• Units will longer not not stop moving if their destination region is captured before they arrive. • Typo fixes [/quote] [e digicons]O:)[/e]

Yes, great support for a great product - one of my best software purchases ever. In the "GUI polishing" category let me recap some that I think would be simple: • Add an "everything visible" option for skirmish maps! This would be of great tutorial value and implicitly adds a new difficulty adjustment to complement the existing choices. Major bang for the buck, especially for noobs like me. • Make impassable terrain lines more discernable on the topo map. So,

Thank you, Tictoc. I've now tried the graphics tweaks mentioned there and see little improvement in the cases I was mentioning. So it may be that my basic problem is CPU load, not GPU. Reducing the drone swarm density, especially when there are bunches of dreadnoughts, still seems to make sense in terms of reducing unnecessary load. I leave it to the devs to do what they want.

By your logic we wouldn't request anything that improves performance, and the existing video nerfs would be removed. Then only people with absolute top-end rigs could run the game, and the eligible player base would dwindle to an even tinier percentage. I doubt that's what you really want. I bought this game to play big battles. To maximize my ability to do so, I want to turn off some more of the impressive but (like shadows) totally useless eye-candy e.g. PHC drea

My mouse is set up to zoom several lines of text with each notch of the wheel. That works fine in most apps and I'd like to just leave it at that setting. It works pretty well in Ashes except sometimes when I want a precise zoom level and can't get it. So I suggest assigning the keypad +/- keys, or maybe page up / down, to zoom by single Ashes-interface increments. Then I can use these as a tweak. Thanks

My rig slows to stop on very big battles even with all Video options minimized. I wish I could also turn off drone animations since these are relatively unimportant, and drone flurries (eg when placing a carving turret next to a repair bay) noticeably slow the rendering. I understand that drone effects must still be calculated, so reducing just the GPU burden may not do a lot. Also, Substrate drone hives might have to be excepted, as they seem to hang around areas but with

The panel in the upper-right corner (player / faction ranking ?) can't be hidden (AFAIK). Personally I have no use for it, and would like to dismiss it. Any key combo that would hide it then pop it back up... EDITED: I was more excited about this until I realized that my GUI was running at 130% (maybe the default?). Once I set it to 100% this was much less of an issue. But the request stands and is probably simple to add.