Well, it wouldn't hurt to try this. I have confirmed it on both TGF & MMF for XP machines; its 100% necessary or ANY click game, regardless of how complex it is, will crash randomly. For MMF2, who knows, it might work. For Vista, from what I've discerned it should be exactly the same for TGF & MMF games; they crash at random unless this is activated. For Vista + MMF2, I have absolutely no idea.
One thing I know, is this really only addresses smaller discrepencies and bugs left in from clickteams older work; if your MMF2 application is crashing because of hardware acceleration problems, this will have absolutely no effect. Likewise, if a TGF or MMF game is crashing because you are doing something very nasty with extensions that causes a crash on its own, this should have no effect.
However, I STRESS: You absolutely must tell people to do this after downloading a TGF or MMF game.
DaVince This fool just HAD to have a custom rating
Registered 04/09/2004
Points 7998
6th January, 2008 at 14:22:02 -
Originally Posted by Pixelthief Well, it wouldn't hurt to try this. I have confirmed it on both TGF & MMF for XP machines; its 100% necessary or ANY click game, regardless of how complex it is
Not on most computers though: for me compatibility mode has absolutely no effect whatsoever.
I've tested it out on 6 XP computers so far; many TGF games in particular would experience the wellknown "repeating wav glitch", while MMF games were more stable and prone to simply stopping and crashing. When 95 mode was activated, none of the computers ever crashed once.
So some computers might be more stable environments and won't crash at all, but from what I can tell for a majority of people click games are rather unstable. I highly suggest including instructions for this in downloads.
Ironically, and not trying to start a little riot, but the most stable Windows experience I've had is on my iMac. Click games have never crashed for me here, I can't even think of a time when one has crashed on any of my computers other than working on Tormi.
Originally Posted by Dr. James Ironically, and not trying to start a little riot, but the most stable Windows experience I've had is on my iMac. Click games have never crashed for me here, I can't even think of a time when one has crashed on any of my computers other than working on Tormi.
I get the repeating wav glitch in MMF games very occasionally, TGF games never crash for me but I'll try this out. I'm with James though, Macs seem to run windows well
I think it's just Apple releasing constant and decent drivers.
Anyroad! I used to get the looping sound crash in Steam based games. Some chaps said you should disable DirectX audio acceleration. Didn't work mind but a set of Omega graphic drivers did.
Compatibility Mode doesn't do much more than faking the Windows version and using MSDOS paths (C:/toolo~1.txt) instead of Normal ones.
Also some minor stuff that hardly help.
It does rarely help. More often than not it get you a little further before you crash again.
Like trying to get system shock 2 to work with 64bit Vista.
But i used to get More problems with my first computer which died of old age and got thrown away.
None of my new computers have had any problems. The only click game that hasn't worked on this computer so far is EEWW.
I believe a large chunk of it has to do with what sound card you use, and such, seeing as the vast majority of crashing in this manner is the "Repetitive Wav Glitch", which affects more then just TGF & MMF. I've been testing it on a multitude of computers, mostly with XP and a variety of different old sound and new sound cards, and it seems that it makes a gigantic impact; Without compatibility mode on it crashes after an average of 3 to 5 minutes, while with it I'm not seeing any crashing for non-obvious reasons. I tried playing EEWW on my laptop only to see it get the repetitive sound glitch in the very first level, so I went and activated the 95' mode, and haven't gotten a single crash all the way up to the last boss.
Virtually 9x programs had to use ~1ish names, but displayed the real path in most of cases.
I've tested with the Visual C++ 6 installer. Setting the compatibility mode to Windows 9x made all path names dosish.
Advertisement
Post Reply
.. I predict a riot. I, predict a riot!
!!!
Edited by the Author.