"C:\Emulators\\Nintendo 64\Project64 2.1\Project64.exe" "G:\Emulators\Games\Nintendo 64\Banjo-Kazooie (Europe) (En,Fr,De).n64" Having said all that, it's very well supported and those for whom it's worked seem to love it.ĬD "C:\Emulators\\Nintendo 64\Project64 2.2"
Also, Ice is a bit picky about special characters and can fill your Steam library with lots of junk if you point it at the wrong directory.
Multiple runs can create duplicates in Steam, which makes adding additional games problematic as you have to delete duplicates one by one. Rather than follow the guide you can just point Ice's config file to your existing ROM folders, but you have to make sure you get it right first time. There's also no guide to the various command line arguments you need for each emulator or which emulators are supported. The online setup guide doesn't prepare you for the variety of issues you can run into, and assumes you're creating your game folders from scratch (which most users probably aren't). The lack of transparency about how Ice works has led to a common misconception that Ice is a front end of sorts, or is in some way responsible for launching the games, when all it does is create the necessary shortcuts within Steam (which can be done manually, as shown in Method 2). There are instructions and FAQs on the website, but they are woefully brief and don't really explain what Ice does, which would probably help when it comes to troubleshooting. Ice has no UI, so it's a manual setup process that requires a fair amount of editing of config files. It sounds simple and in principle, it is. You tell Ice where your emulators live and where your games live and then let it do its thing.
vdf file (which stores all of Steam's shortcut paths for non-Steam games). Ice is a script that directly edits Steam's shortcut.
0 kommentar(er)
