Wax Savage Posted October 12, 2019 Share Posted October 12, 2019 it’s a given that using the ‘legacy’ scenarios and maps is a dicey proposition. However, even knowing this I still get frustrated when I cannot determine how to open a scenario. Even using my best powers of deduction, I am blunted. There is a scenario under the Single Legacy ‘easy’ category that is a perfect example.., KFORCE PROTECTION by Charlie Zero-Five (circa 2007). When I attempt to open the scenario I get the following message from both vers. 4.161 and 4.023, “Error loading the scenario! It may be incompatible or its artwork (map) resources may be missing. Please see the log for more information.” There is NO option to replace the map file. I’m stuck! The log has the following info… [13:55:26,887] WARN : ------------------------------- [13:55:26,888] WARN : Steel Beasts Log File v4.023 [13:55:26,888] WARN : Sat Oct 12 13:55:26 201 / 4036 [13:55:26,888] WARN : ------------------------------- [13:55:26,888] WARN : +--+ MEMORY USAGE INFO (SteelBeasts START): [13:55:26,888] WARN : | | Process: 235 MB (0 % of 8.0 TB total, 8.0 TB free) 235 MB min/125 MB max [13:55:26,888] WARN : | | Physical: 3.6 GB (22 % of 16.0 GB total, 12.4 GB free) 3.5 GB min/3.6 GB max [13:55:26,888] WARN : +--+ Pagefile: 4.1 GB (12 % of 32.6 GB total, 28.5 GB free) 4.0 GB min/4.1 GB max [13:55:53,599] WARN : +--+ MEMORY USAGE INFO (LoadFileToPlay start): [13:55:53,599] WARN : | | Process: 946 MB (0 % of 8.0 TB total, 8.0 TB free) 235 MB min/946 MB max [13:55:53,599] WARN : | | Physical: 4.2 GB (26 % of 16.0 GB total, 11.8 GB free) 3.5 GB min/4.2 GB max [13:55:53,599] WARN : +--+ Pagefile: 4.8 GB (15 % of 32.6 GB total, 27.8 GB free) 4.0 GB min/4.8 GB max [13:55:56,196] ERROR: Unknown type (0x24). Cannot create unit! [13:55:56,196] ERROR: Invalid formation size 'Size: 1; 0x80024, '! [13:55:56,197] ERROR: CGame::ReadScenarioFromFile failed [13:55:56,197] ERROR: Error setting up new game! Can anyone aid me in getting this scenario to work? If files such as these are of no use, should the SB Forum do a purge of the files that are irrevocably ‘broke’? kforceprotection.zip 0 Quote Link to comment Share on other sites More sharing options...
Gibsonm Posted October 13, 2019 Share Posted October 13, 2019 I tried opening it in 4.023 and received an error about "It maybe incompatible or its artwork (map) resources may be missing". The log provided: [13:45:49,738] WARN : ------------------------------- [13:45:49,738] WARN : Steel Beasts Log File v4.023 [13:45:49,739] WARN : Sun Oct 13 13:45:49 201 / 21484 [13:45:49,739] WARN : ------------------------------- [13:45:49,739] WARN : +--+ MEMORY USAGE INFO (SteelBeasts START): [13:45:49,739] WARN : | | Process: 4.3 GB (0 % of 128.0 TB total, 128.0 TB free) 4.3 GB min/4.2 GB max [13:45:49,739] WARN : | | Physical: 11.6 GB (24 % of 48.0 GB total, 36.3 GB free) 11.6 GB min/11.6 GB max [13:45:49,739] WARN : +--+ Pagefile: 15.6 GB (25 % of 62.0 GB total, 46.3 GB free) 15.5 GB min/15.6 GB max [13:46:00,543] WARN : +--+ MEMORY USAGE INFO (LoadFileInScenarioEditor start): [13:46:00,543] WARN : | | Process: 5.3 GB (0 % of 128.0 TB total, 128.0 TB free) 4.3 GB min/5.3 GB max [13:46:00,543] WARN : | | Physical: 12.3 GB (26 % of 48.0 GB total, 35.6 GB free) 11.6 GB min/12.3 GB max [13:46:00,543] WARN : +--+ Pagefile: 16.6 GB (27 % of 62.0 GB total, 45.4 GB free) 15.5 GB min/16.6 GB max [13:46:09,480] WARN : +--+ MEMORY USAGE INFO (LoadFileInScenarioEditor end): [13:46:09,480] WARN : | | Process: 5.7 GB (0 % of 128.0 TB total, 128.0 TB free) 4.3 GB min/5.7 GB max [13:46:09,480] WARN : | | Physical: 12.8 GB (27 % of 48.0 GB total, 35.2 GB free) 11.6 GB min/12.8 GB max [13:46:09,480] WARN : +--+ Pagefile: 17.0 GB (27 % of 62.0 GB total, 45.0 GB free) 15.5 GB min/17.0 GB max [13:46:46,584] WARN : +--+ MEMORY USAGE INFO (LoadFileInScenarioEditor start): [13:46:46,584] WARN : | | Process: 5.7 GB (0 % of 128.0 TB total, 128.0 TB free) 4.3 GB min/5.7 GB max [13:46:46,584] WARN : | | Physical: 12.8 GB (27 % of 48.0 GB total, 35.2 GB free) 11.6 GB min/12.8 GB max [13:46:46,584] WARN : +--+ Pagefile: 17.0 GB (27 % of 62.0 GB total, 45.0 GB free) 15.5 GB min/17.0 GB max [13:46:50,305] ERROR: Unknown type (0x24). Cannot create unit! [13:46:50,305] ERROR: Invalid formation size 'Size: 1; 0x80024, '! [13:47:04,548] WARN : +--+ MEMORY USAGE INFO (LoadFileInScenarioEditor end): [13:47:04,548] WARN : | | Process: 6.0 GB (0 % of 128.0 TB total, 128.0 TB free) 4.3 GB min/6.0 GB max [13:47:04,548] WARN : | | Physical: 13.0 GB (27 % of 48.0 GB total, 35.0 GB free) 11.6 GB min/13.0 GB max [13:47:04,548] WARN : +--+ Pagefile: 17.2 GB (28 % of 62.0 GB total, 44.8 GB free) 15.5 GB min/17.2 GB max [13:47:39,166] WARN : +--+ MEMORY USAGE INFO (LoadFileToPlay start): [13:47:39,166] WARN : | | Process: 5.9 GB (0 % of 128.0 TB total, 128.0 TB free) 4.3 GB min/6.0 GB max [13:47:39,166] WARN : | | Physical: 12.7 GB (26 % of 48.0 GB total, 35.3 GB free) 11.6 GB min/13.0 GB max [13:47:39,166] WARN : +--+ Pagefile: 16.9 GB (27 % of 62.0 GB total, 45.1 GB free) 15.5 GB min/17.2 GB max [13:47:43,241] ERROR: Unknown type (0x24). Cannot create unit! [13:47:43,241] ERROR: Invalid formation size 'Size: 1; 0x80024, '! [13:47:43,242] ERROR: CGame::ReadScenarioFromFile failed [13:47:43,242] ERROR: Error setting up new game! [13:47:51,487] WARN : +--+ MEMORY USAGE INFO (SteelBeasts END): [13:47:51,487] WARN : | | Process: 5.7 GB (0 % of 128.0 TB total, 128.0 TB free) 4.3 GB min/6.0 GB max [13:47:51,487] WARN : | | Physical: 12.3 GB (26 % of 48.0 GB total, 35.7 GB free) 11.6 GB min/13.0 GB max [13:47:51,487] WARN : +--+ Pagefile: 16.4 GB (26 % of 62.0 GB total, 45.5 GB free) 15.5 GB min/17.2 GB max [13:47:51,552] WARN : Done My guess is that is uses a unit that perhaps no longer exists. Trying to open in it SB Pro 3.3X had the same outcome. I'm afraid my copies of 2.654 and earlier have been archived. 0 Quote Link to comment Share on other sites More sharing options...
Wax Savage Posted October 13, 2019 Author Share Posted October 13, 2019 Thanks for trying to open the scenario, Gibsonm, yeah, if your guess is correct, then a discontinued unit is probably available only on an early version. Sure would be nice to get it open and replace all the units with ones we know were carried forward into the later SB editions. I'd still like to get into it. Anyone have a 2.654 or earlier? 0 Quote Link to comment Share on other sites More sharing options...
Members Ssnake Posted October 13, 2019 Members Share Posted October 13, 2019 It's under investigation, let's see what we'll learn from that. 0 Quote Link to comment Share on other sites More sharing options...
Wax Savage Posted October 15, 2019 Author Share Posted October 15, 2019 (edited) On 10/13/2019 at 1:25 PM, Wax Savage said: Thanks for trying to open the scenario, Gibsonm, yeah, if your guess is correct, then a discontinued unit is probably available only on an early version. Sure would be nice to get it open and replace all the units with ones we know were carried forward into the later SB editions. I'd still like to get into it. Anyone have a 2.654 or earlier? Thanks Ssnake, my guess is 30% of the legacy scenarios don't open in the SB 4.xxx series. As a second example, the Cat.sce scenario by Bluewings (legacy single scenario) gets the same error message in SB 4.xxx Using the hint from Gibsonm, I loaded up old SB ver 1.226 and the KFORCE PROTECTION scenario (legacy single scenario) did open up! Using the 1.226 mission editor I erased the units in the scenario (leaving the route info and any other designer input alone) and re-saved the scenario renaming it "kforforceprotection_bare". I now could open the scenario in the 4.026 mission editor and replaced the units, attaching each unit to it's original route line. The scenario now runs! Using 4.161 I converted the scenario map to 4.1xx use. Edited October 15, 2019 by Wax Savage added 'cat.sce' 0 Quote Link to comment Share on other sites More sharing options...
Members Ssnake Posted October 15, 2019 Members Share Posted October 15, 2019 It seems to be tied to certain vehicles that were available in SB 1.x but not later (Jaguar 2). 0 Quote Link to comment Share on other sites More sharing options...
Jartsev Posted October 16, 2019 Share Posted October 16, 2019 Fixed; fix should be available with the next patch or update 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.