Quote:
Originally Posted by daxb
Only if you activate this feature (NoWriteCache). Normally, WHDLoad will save to disk when it exits. Maybe you noticed flashing while saving because the save file doesn't exists already. This happen in the past when slave author forgot to add save files with install. However, after first save to disk there is no flashing if you don't activate NoWriteCache feature.
|
I never have "NoWriteCache" set.
Try "Test Drive", get a highscore and you'll see what I mean... and this is a very mild example.
Quote:
Originally Posted by Solo Kazuki
@DamienD
I'm sure that no one write WHDLoad install for these "maybe over 100 games", because it is without sense. This is rather talk about games which don't have proper "native" (trainers?) installers.
I'm using WHDLoad, but only when it's needed. When game is working properly from HD installed with own installer (or via assigns) I see no sense to use WHDLoad for them*. But there are games which are not working well or not working at all without WHDLoad. And we are talking about real hardware, not emulation when You can have individual configuration for every game.
*Ok, maybe when WHDLoad adds something (more buttons support, saving, fixing bugs...)
|
Which is exactly what I do... and also believe it doesn't always make sense; but I usually get shot down by the WHDLoad zealots though for this comment.
I only use WHDLoad in extreme cases where there are no bug free disks, or native installs available, or some extra feature that's too good not to have.