Jump to content
Oovee® Games

Legacy versions issue


Recommended Posts

Legacy - build 2015- 01-02 Doesn't start at all:

2019-08-31_094016.png.c8f1f16c66587b8a40dbbc40ec4781a4.png

20190831094046_1.thumb.jpg.b544d349cc9a434c621ff8d2cd3b73bd.jpg

Legacy2 - build 2017-01-27  In this version, auto zoom and as a result the default camera position is too close for E-167:

20190831095304_1.thumb.jpg.29b713605eb2ea0aaf49e2cec10c6712.jpg

Edited by oldman777
Link to post
Share on other sites

LegacyDLC.thumb.jpg.b46b19cd4a8e245ef154b2471102292f.jpg

This warning has been there since release day.
The E167 uses features (petrol smoke effects, engine choke, numerical wheel parameters, easier steering angle for casuals,..) that have been added in the 1.3.6 patch, so it cannot work properly in legacy builds.

  • Thanks 1
Link to post
Share on other sites
2 hours ago, oldman777 said:

I deleting DLC

I assume you just deleted CanyonsDLC.zip, but the DLC modifies other files. To properly remove the DLC, you have to uninstall it from Steam. To do so: in Steam, go to Spintires->properties->DLC->untick the install checkbox. Then let Steam download.

  • Thanks 1
Link to post
Share on other sites
14 minutes ago, Localhost (Oovee) said:

I assume you just deleted CanyonsDLC.zip, but the DLC modifies other files. To properly remove the DLC, you have to uninstall it from Steam. To do so: in Steam, go to Spintires->properties->DLC->untick the install checkbox. Then let Steam download.

Now it works, thanks.

Link to post
Share on other sites
  • 4 weeks later...

Found the cause of errors.  It started after adding new identical ones Config.xml files in both Legacy and Legacy2 builds:

<!-- Last change v1.3.6 -->
<Config Version="20160303">
	<MediaPath Path="Media" />
	<MediaPath Path="Media.zip" />
	<MediaPath Path="TextureCache.zip" DoPrepend="true" />
	<MediaPath Path="MeshCache.zip" DoPrepend="true" />
	<MediaPath Path="CanyonsDLC.zip" DoPrepend="true" />
	
	<System
		Width="1024"
		Height="768"
		Windowed="false"
		Maximized="true"
	/>
</Config>

After launch Legacy - Build 2015-01-02, (CanyonsDLC downloaded or not, it doesn't matter) , an error occurs:

2019-08-31_094016.png.c8f1f16c66587b8a40dbbc40ec4781a4.png.8fac6d261c4b8298a183a929d9d2c216.png

After launch Legacy2 - Build 2017-01-27 without CanyonsDLC downloaded , an error occurs:

2019-10-08_111748.png.f0ba762fc6600beb669b1e862301f085.png

After launch Legacy2 - Build 2017-01-27 with CanyonsDLC downloaded , no error occurs.

============================================================================

I replace in Legacy - Build 2015-01-02 the Config.xml file with the old one:

<?xml version="1.0"?>
<Config Version="20150313">
	<MediaPath Path="Media" />
	<MediaPath Path="Media.zip" />
	<MediaPath Path="Shaders.zip" />
	<MediaPath Path="TexturesCache.zip" DoPrepend="true" />
	<System
		Width="1024"
		Height="768"
		Windowed="false"
		Maximized="true"
	/>
</Config>

After launch Legacy - Build 2015-01-02, (CanyonsDLC downloaded or not, it doesn't matter) , no error occurs.

BUT, if CanyonsDLC is downloaded it not displayed in the game, which in my opinion is reasonable, because it is not compatible with this version. 

And with this old Config.xml, everything is fine. 

I do not know how to fix  Legacy2 so that there CanyonsDLC downloaded or not, are no errors.

-------------------------------------------------------------------------------

And one more request from an old person suffering from perfectionism, please correct, if possible, Build titles for real, which are displayed in game

Legacy - Build 2015-04-13

Legacy2 - Build 2016-03-03

 

Link to post
Share on other sites
  • 3 months later...
  • 1 month later...

Why are you trying to run the legacy version anyway?  Just curious.  I did try recently, maybe a month ago or two, and it ran fine for me.  But I think I did a clean install and moved my current ST folder out of the way.  That way there were no file conflicts.

Link to post
Share on other sites
54 minutes ago, Unster said:

Why are you trying to run the legacy version anyway?  Just curious.  I did try recently, maybe a month ago or two, and it ran fine for me.  But I think I did a clean install and moved my current ST folder out of the way.  That way there were no file conflicts.

Regarding the legacy version: I have a bunch of my personal trucks for this for legacy versions.
The second reason is sunny weather
and excellent visibility at night in legacy versions.

Legacy2 can somehow start, but the Legacy1 cannot start at all. Like already described above.

Edited by oldman777
error
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...