CrackerJack Posted January 28, 2020 Share Posted January 28, 2020 I downloaded Tanks Again 1.0 from the files section. It looks like it dates back to 2014. I'd like to get this running in the current version. What's the correct procedure please? 0 Quote Link to comment Share on other sites More sharing options...
Members Ssnake Posted January 28, 2020 Members Share Posted January 28, 2020 Chances are, it will run out of the box. If not, it will provide a (hopefully comprehensive) error message. Depending on which error message you get, the recommended procedure will vary. 0 Quote Link to comment Share on other sites More sharing options...
CrackerJack Posted January 28, 2020 Author Share Posted January 28, 2020 Here is the message I get when I try to open the scenario 0 Quote Link to comment Share on other sites More sharing options...
Administrators Sean Posted January 28, 2020 Administrators Share Posted January 28, 2020 1st thing is to try is to install the legacy maps pack on the esim downloads page if you have not already. Then try again. If that doesn't work, volcano wrote up the directions below. 0 Quote Link to comment Share on other sites More sharing options...
Members Ssnake Posted January 28, 2020 Members Share Posted January 28, 2020 I don't think the legacy map installation will make a big difference. The heightmap "Wolfsburg" has already been converted to the new format. I would recommend in this case to open the Mission Editor with a blank scenario, and then to try and open the Tanks scenario from there. This will bring up a map extraction wizard that you can then use to create a delta map of the Woldsburg package. Afterwards you can then try to load the scenario again and replace the map in it with the new one that you just extracted. That way the conversion will be complete. 0 Quote Link to comment Share on other sites More sharing options...
CrackerJack Posted January 29, 2020 Author Share Posted January 29, 2020 (edited) As you speculated the Legacy map installation did not make a difference. I opened the Mission Editor and then selected Extract Map Pkge and the scenario. Which gave: And then Delta map selected And then this which was where it stopped It seems that I would 59GB! A lot more space than I expected for one map? Which I don't have on that drive but I have enough space on another drive. Any suggestions please and thanks. Edited January 29, 2020 by CrackerJack 0 Quote Link to comment Share on other sites More sharing options...
DarkAngel Posted January 29, 2020 Share Posted January 29, 2020 It stopped because of the ! in the name. It should be a low res data map so only 800mb 0 Quote Link to comment Share on other sites More sharing options...
DarkAngel Posted January 29, 2020 Share Posted January 29, 2020 I think you'll find also that wolfsburg is in the map download 0 Quote Link to comment Share on other sites More sharing options...
Members Ssnake Posted January 29, 2020 Members Share Posted January 29, 2020 But the Wolfsburg map already IS converted into a map package, so it doesn't need to be converted again. 0 Quote Link to comment Share on other sites More sharing options...
Members Ssnake Posted January 29, 2020 Members Share Posted January 29, 2020 8 hours ago, CrackerJack said: It seems that I would 59GB! A lot more space than I expected for one map? Which I don't have on that drive but I have enough space on another drive. Any suggestions please and thanks. The disk space usage is a worst case estimation as the converted map would still be uncompressed until you publish it. The error message is misleading in that the full disk space requirement will not be used until you start leveling roads etc., which all needs high resolution data to work. In that case the full dimensions of the map must be stored in what we call an "HNT" file, and that has full 78cm grid resolution. Most of that will "disappear" again after compression (publishing), but until it's published the file will sit there and hog a lot of disk space. So, if you just convert but don't edit the map with any of the elevation tools, only about 800 MByte will be used as Dark wrote (and even less so after compression). That being said, if you would rather use the other disk, there's two options. Uninstall the map package and Steel Beasts, then install the map packages first and pick the other drive as the map data destination. Then install Steel Beasts. Or, move the entire map packages folder to the new disk. When Steel Beasts starts the next time you will be forced to enter the location of the map data before you can proceed with anything. Once that you confirmed the new location, everything's fine again. 0 Quote Link to comment Share on other sites More sharing options...
CrackerJack Posted January 30, 2020 Author Share Posted January 30, 2020 With your help I was able to get it working. Thank you for your support! 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.