I VOTE FOR... fixing the existing bugs and gameplay issues first. How about some attention to these? https://forums.ashesofthesingularity.com/486065/Replays-crashing-always https://forums.ashesofthesingularity.com/486254/Dreads-wont-target-or-shoot https://forums
Ashpire
I play PHC against AI Substrate in skirmish. My dreadnoughts are idiotically bad in groups. Whether or not I form an army with them, and even though I right-click constantly on an enemy dread, usually only one of them will shoot at it. Often not even that as my dreads *always* prefer small fry and can't be redirected from those. And the one that is shooting must constantly be forced to do that, or it will often just turn away! No other units behave like this.</
Win10 Pro x64, Ryzen 8-core, 64GB, GTX 1060 w 6GB; 16GB pagefile; latest Ashes & Windows updates, and NVidia drivers. Over the past month I've had more and more trouble with Ashes replays crashing. Those do stress the graphics but my cooling is good. The GPU never exceeds 71 degC and the CPU 51 degC. ==> Currently I can't run a replay all the way through. This is true in DX12, DX11, Safe Mode, and at any Replay speed. The crashes almost always oc
I always zoom in and out with the mouse wheel. But that moves in fairly big steps, and I've often wished for finer control. --> Is there any way to zoom completely smoothly i.e. not in resolution steps? --> Is there any way to zoom other than the mouse wheel? Thx
Win10 x64, Ryzen 64GB, GTX 1060 6GB, 2560x1440 w all latest drivers. All Ashes updates via Steam. See attached screencap from a replay; same results at any replay speed. When they've been destroyed, the Barrager and the Oblivion Turret remain as fuzzy yellow blobs, unlike eg the Smarty which just disappears. They look almost the same while building (upgrading). The overall effect is somewhat ugly and certainly confusing. <a href="http://i65.tinypic.com/
I also had this on Win 10 DX11, possibly also on DX12. This and *most* other anomalies ended when I moved to a new machine. I think the most likely relevant hardware difference was a big increase in RAM. I had 8GB and now have 64GB. I kept the same old video card, and doubt the CPU matters to this. So... if you're running 8GB that could be a contributor. Short of adding more, try increasing your paging file. I'd recommend at least 6GB for that
Wonderful support for this most deserving gem of a game. Than you again.
Than you! Yet again, for the great support of this game, and for the continual refinement of its gameplay.
[quote who="Kreyson" reply="5" id="3685062"] Impassible terrain is not so clearly identified [/quote] Yes! I'm glad someone else is asking for this too. Don't tell anyone else, but I like to turtle... and wish I could discern impassable terrain from high up. https://forums.ashesofthesingularity.com/481144
@bb - Thanks for posting your results which, I agree, indicate that my CPU is doing all it can . That's what I really wanted to know. It's interesting to see that your 'average' and 'cpu' framerates are identical, whereas on my system the 'average' is much lower than the 'cpu'. I'm guessing this means that your GPU can meet or exceed the CPU, and mine can't. I ran the bench again with Ashes graphics options adjusted to more closely matc
[quote who="bbc6rgf57ytty5yxyw5gt" reply="2" id="3681563"] Isn't the 770 the bottleneck? [/quote] I don't yet know if I have any problem - waiting to see comparable results in these CPU-focused tests. I *thought* the Ashes CPU-focused tests were designed to remove GPU dependency and just report what the CPU could do. Anybody know about that? If my GPU is the problem I can eventually replace it. But now I'm trying to see if the non-GPU parts are perf
I've got a new AMD R1800X rig but am for now keeping my GTX 770 graphics board. My video is 2560x1440. Asus Crosshair VI Hero mobo, stock clocks, Windows 10. Below are links to the results I'm seeing in the Ashes Escalation "CPU" benchmark. Amazingly, I can't find other web posts with good comparative results. They are all either at 1920x1080, focus on the GPU, or came out much earlier before optimizations etc. If the links aren't viewable, here are the CPU-r
[quote]please stop my medics from going in front of my attacking units. [/quote] Agree completely. When my dreadnought is moving to a defined destination, the medics should not be in front of it. Currently they are always in front and always get slaughtered immediately. (After so many such disasters, you'd think they'd learn, but no...)
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
Stardock - I'm not a good enough player to find fault with any of this amazing list of tweaks and improvements. THANK YOU and GENERAL'S GENTLEMEN for the huge amount of TLC you're giving Ashes. It continually renews my interest in the game, and has justified the cost several times over.
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