Eregos replied to Eregos's topic in Dune 2000 SupportThanks for the replies. I've been borrowing your settings for the past couple weeks, and recording the length of time I've been able to play the game without crashes. In my psychology class I once learned about the situations in which rewards in experiments were the most likely to generate superstitious behavior. When delivery of a treat was delayed by a long time after a specific behavior was performed by the mouse, or was simply random, the mouse would engage in all kinds of superstitious, absurd behaviors in its cage to try and get the treat. In this analogy, I'm the mouse, as I have no real idea what is causing these crashes, so I'm doing a whole bunch of things to get as much stable playtime as possible (the treat). I do think applying FunkyFresh's settings made a major difference (relative to my settings, the game feels 'fluider' and just kinda feels more stable) as delays between crashes increased. Getting an hour of playtime used to be rare; with Funkyfresh's settings it became fairly common. I don't think applying Windows 8 compatibility really matters, but based on the crash times it's hard to tell, would need a bigger sample size. If I weren't so lazy about it, I'd install visual studio or another programming suite, run the Dune 2000 with an attached debugger, and try to isolate the crash like in my programming days. As is, I've just wrapped up the last of the 3 campaigns on hard, next will be the alternate missions & custom maps. Final Ordos mission was cool, fighting the Atreides, Harkonnen and Emperor with Mercenaries helping, had just enough units to take out the Atreides base, expand and stop myself getting spice starved. Greetings to Germany, sorry to hear about Helmut Kohl! Funkyfresh settings but with cutscene resolution change, 1280X720 resolution: 8:15 Funkyfresh settings but with 1280x720: 19:18 Funkyfresh settings pure (forgot to write time, but it wasn't longer than 25:00) (from here on, clip cursor and modal style also disabled but shouldnt matter b/c RunInWindow already disabled) Funkyfresh settings pure 4:07 Funkyfresh 1280X720 Win 8 compatibility: 1:03:06 (clicking on loadgame menu crash. But it was 1 second after loading another game, might not've happened if I'd waited an extra second for the load to settle) Funkyfresh 1280X720 Win 8 compatibility Cutscene res change: 1:03:34 (at least, shut down early) Funkyfresh 1280X720 Win 8 compatibility Cutscene res change: 0:00:56 (clicking savegame menu crash) (around here I start closing the dune launcher after each launch, because it sometimes seems to help) Funkyfresh 1280X720 Win 8 compatibility Cutscene res change: 15:25 (Click save crash again) Funkyfresh 1280X720 Win 8 compatibility Cutscene res change: 1:13:00 (Normal crash) Funkyfresh 1280X720 Win 8 compatibility Cutscene res change: 26:46 (Normal crash) Funkyfresh 1280X720 Win 8 compatibility Cutscene res change: 35:27 (Normal crash) Funkyfresh 1280X720 Win 8 compatibility Cutscene res change: 25:35 (Normal crash) Funkyfresh 1280X720 Win 8 compatibility Cutscene res change: 00:57 (Normal crash) Funkyfresh 1280X720 Win 8 compatibility Cutscene res change: 18:26 (Normal crash) Funkyfresh 1280X720 Win 8 compatibility Cutscene res change: 16:50 (Normal crash) Funkyfresh 1280X720 Win 8 compatibility Cutscene res change: 26:22 (Savegame crash) Funkyfresh 1280X720 Cutscene res change: 28:32 (Immediately after game save) Funkyfresh 1280X720 Cutscene res change: 18:00 Funkyfresh 1280X720 Cutscene res change: 1:01:08 Funkyfresh 1280X720 Cutscene res change: 0:03:18 (didn't close dune launcher before this launch) Funkyfresh 1280X720 Cutscene res change: 2:35:00 (much of the time was with the menu opened, which appears to make the game more stable. When I returned 10 hours later, it had crashed in the menu.) Funkyfresh 1280X720 Cutscene res change: 2:00:00 (some of it in menus) Funkyfresh 1280X720 Cutscene res change: 15:00 Funkyfresh 1280X720 Cutscene res change: 23:22 Funkyfresh 1280X720 Win 8 compatibility Cutscene res change: 03:32 Funkyfresh 1280X720 Win 8 compatibility Cutscene res change: 32:00 (ended session by winning Ordos campaign)
Eregos posted a topic in Dune 2000 SupportDune 2000 Gruntmods v 18.104.22.168 does indeed regularly freeze on Windows 10 64bit (Pro N). As others have reported, the freezes vary in proximity from 1-15 minutes of gametime usually. On a few lucky occasions, I've been able to play as much as 1 hour without a freeze. The freezes are normally accompanied by stuttering of the most recent sound, but not always. The work Gruntlord & Funkyfresh did is excellent, no doubt an astounding number of things had to be fixed to get it working as well as it does in Win 10. I'm still enjoying the singleplayer, but I have to save constantly and it does get frustrating at times to redo segments especially since clicking the save/load button often triggers a freeze. But I'm unusually determined (wouldn't be here otherwise) and I consider the game playable enough. Everything else works wonderfully, HD resolution is awesome and the cutscenes work. I just had to choose the right settings. (In my case it was Videobackbuffer, FPS limiter, Single processor affinity, disable max windowed mode, cutscene change resolution, disable high DPI scaling, and Enable DxWnd) I played C&C95 vanilla on WinXP years ago, and it was even more unstable but I somehow managed to complete it. Since the freezing in Dune 2000 Gruntmod is similar in nature, I have a theory the cause is also the same. The cause for C&C95 was something like the game executable being programmed to attempt to write to memory sectors that are now reserved for the modern OS (resulting in a segmentation fault). The biggest similarity I see in these crashes/freezes is that in both cases, the sound stutters repeatedly at the time of the freeze (it's possible some of the C&C95 freezes might have been sound related) and the freezes happen more frequently on larger maps where there is more going on, which logically increases the likelihood the game will attempt to write to protected memory sectors. I'm kinda assuming Gruntlord/Funkyfresh decompiled the Dune 2000 executable and fixed the vast majority of this protected-memory-sector-read-writing, otherwise I would be shocked the game is as stable as it is and that people were ever able to manage to use the mod for multiplayer stably. Another reason I suspect protected read/writing is the problem is the half the freezes happen when I click save/load in the menu, which maybe causes the game to run some kind of check on the current memory usage, triggering a protected read/write. So in effect, it seems Dune 2000 Gruntmod is effectively running in a doomed state in the seconds prior to these freezes, with the player unable to save their progress. I tried all the suggestions I could find in this forum before posting, the only one I haven't done which seemed to work for someone with a different problem was installing an older version of Gruntmod. I run a number of unusual programs on my system but I already tried shutting down everything that semiregularly causes problems (except maybe nod32, hmm. Maybe I'll try safemode just to eliminate even more implausible possibilities). Also made sure all drivers were up to date, double checked I followed the install instructions. None of it had any impact on the crashes. The crashes used to be even worse (requiring me to create a new desktop to close the application like another person reported) but when I switched to my current exact video options, this stopped and I can now simply alt+esc and forceclose. I started playing Dune 2000 a couple weeks ago. One unrelated apparent bug in Dune 2000 Gruntmod seems to be related to the mechanism Gruntmod uses to limit CPU cycles. Most programs on my system run normally, but I've noticed that after several rounds of freezing & force termination, a few (windows photo viewer, paint.net, even the blizzard entertainment app) run extremely slowly as though the Dune 2000 CPU cycles limitation is somehow being applied to them. I'm 99% sure this is somehow connected to Gruntmod as it never happens otherwise, goes away after PC restarts. I suspect this has to do with some secondary process (maybe a system service?) Gruntmods uses not shutting down properly (I wish I knew what one it was! very hard to pick out from a huge list), but as with all my speculation I could be totally wrong. I have pretty solid system (mostly I play modern games): i7-6700k, 32GB ddr4 ram, Nvidia GTX 1080, SSD's Ok! I just wanted to share my experience so far and speculation in case it might help anyone.