Hi Guys - To some of you, this will seem like we're beating a dead horse since it's already been discussed, but please bare with the old guy....:clueless: Let's say I love 1.6 (which I do), but I want to be pwn3d in 1.5 sometimes too... I have renamed the 1.5 folder from "WildWest" to "WildWest 1.5" I installed 1.6 and it still "detected and removed a previous version" (I assume all it really did was delete the old "TheWildWest.exe" from the RTCW folder??) If I want to play 1.5, I rename the "WildWest" folder to "Wildwest 1.6", rename "Wildwest 1.5" to "Wildwest"..... Now.. What about the executable in the RTCW folder? Do I need to replace it with the old one from 1.5 ?? :uhoh: I decided to see if I could still remember how to write a batch file to do all of this for me. It took me 45 minutes of playing around to discover that XP doesn't recognize some of the newer commands like "choice" or "rendir".... Hey Bill Gates :moon: See ya' guys! :flag:
What about the executable in the RTCW folder? Do I need to replace it with the old one from 1.5 ??
I dont know the executable but I know its not really needed. just start in commandline with wolfmp.exe +set fs_game WildWest
BTW I got no probs whith keeping both 1.5 and 1.6 in the same WildWest folder - so I just click a server (1.5 or 1.6 anyway) in my external server browser and the game starts. @ developers: its pity that you cant see 1.5 servers in 1.6 server browser anymore
If you are unsure about keeping both in same folder you could write 2 batch files to start 1.5 or 1.6. Unfortunately I dont know the right syntax so I cant help you here. Just a hint: I would use links instead of renaming the folders - so you dont need to check which Version contains your current WildWest folder before starting.
Just keep 2 folders "WildWest-1.5" and "WildWest-1.6"! "WildWest" is just a link to one of them. Then for example the batch file to start WildWest 1.5 just needs to do the following: cd /path/to/wolfenstein remove the link WildWest create a link WildWest ---> WildWest-1.5 wolfmp.exe +set fs_game WildWest
(I dont know the right syntax but should be easy if you know the command to create links)
There is another possibilty to solve the problem without writing scripts or renaming before playing: You dont need any pk3 in the "main" folder for playing WildWest - so you can copy your complete RTCW (without *.pk3s in main) just for using it for 1.5 - and its almost no waste of HD space. If you want to safe even more space then you might use links (in your 2nd RTCW folder) for all files which you got twice (wolfmp.exe, PB-folder, etc.)
I installed 1.6 and it still "detected and removed a previous version" (I assume all it really did was delete the old "TheWildWest.exe" from the RTCW folder??)
If you dont want to assume anything then you should use the the zip-archive to install WildWest instead of the blackbox.exe ;)
Rudi_alias_Rudi @ developers: its pity that you cant see 1.5 servers in 1.6 server browser anymore
THAT S RIGHT...i dont know any game...u dont see the older version in ingame-server browser...hmmmm
would be fantastic if this was possible...
Errr... how about a RtCW, Quake I, Quake II, Quake III, BF1942 etc etc etc.... They all do that. If you run RtCW 1.3 you will not see 1.41 servers. If you run the RtCW MP Demo You don't see 1.3 or 1.4 servers. If you are running 1.41 you don't see demo servers. If you did it would be EXTREMELY annoying. You'd click on the server and would not be able to join. That's one failing of ASE, it shows all version and then you get weird protocol errors when you try to join a server with a different version of the software. Here's a guide to all the different RtCW versions that are out there... Protocol 81 Enemy Territory-Final Protocol 71 Enemy Territory-Test Protocol 61 Version 1.41 - backwards compatible to 1.4 Protocol 60 Version 1.4 - not backwards compatible Protocol 59 Version 1.32 - not backwards compatible Protocol 58 Version 1.3 and 1.31 - not backwards compatible Protocol 57 Version 1.1, supposed to be backwards compatible with 1.0 Protocol 56 Version 1.0 Protocol 50 and 55 Version MP_demo We don't recommend that you both versions from the same directory. You will only cause yourself to have strange errors and bad performance. The best way to have both versions installed and operable is to have two completely seperate RtCW directory structures each with its own WildWest folder there in. Then you can create shortcuts to each version. The install program determines if you have not yet uninstalled installed The WildWest 1.5 by looking for the 1.5 uninstall file in the RtCW directory you have chosen. If that file is there, then you have not run the uninstall and it will launch it for you. Even if the install program does not find the uninstall script, it will remove (by name) all PK3s that we part of the official beta and released versions of The WildWest.
that u cant play 1.4 with 1.3 is clear!
cause 1.4 didnt exist when 1.3 came out...
but downward compatibility is standard...i thought...but i dunno exactly!
Nice examples but AFAIK WildWest 1.5 and 1.6 is using Protocol 61 so you cant compare this.
We are talking about mods! For example I got about 10 etpro mods installed and no probs if I join an older server or a newer server.
I dont understand why you want to destroy 1.5 while publishing 1.6.
If you really want to separate 1.5 and 1.6 then you could easiely using a different mod folder "WildWest-1.6". (you did recompile the maps anyway!) But IMO it would be also safe to keep it backward compatible.
You will only cause yourself to have strange errors and bad performance.
Could you give an example plz?
Allthough I didnt noticed something on client-side (since half year as I installed an early beta!) - I believe that there could be seldom issues - specially if you join 1.5 servers with that double 1.5/1.6 installation. BUT I really dont know why it doesnt shows 1.5 servers in browser. If 1.6 servers are empty then it just would be nice to watch the 1.6 servers - where is the prob?
Another thing I mentioned aleready: Why dont you separate the maps and the fundamental mod-files? You did several changing on maps where we could dispute wheather its better now or not - For example where is the prob to keep "town" like it is and make an additionary town2 istead of just overwriting town1. The time could show which version of town is the better one. Imagine if in RTCW 1.41 they would have added an additionary tunnel on mp_beach!! I think half RTCW gamers would have run amok to Activision!!
well the executable in the top folder will launch any wildwest game in the wildwest folder so the newer .exe will run the 1.5 game. Now for the launch a server button on the gun that may or may not launch a 1.5 server (not sure if it passes any info on or gets it from the wildwest directory) there are several files that share the same name (and purpose) between 1.5 & 1.6 (and yes I believe 1.14a as well) so if an older version of wildwest is attempting to do something that is a feature in 1.6 you may get some strange results. I know for a fact that someone on my beta list had some rather odd happenings when they mixed the 2 in an early state of the beta testing.