View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0003117||The Dark Mod||Coding||public||06.05.2012 18:35||20.08.2012 12:03|
|Priority||normal||Severity||major||Reproducibility||have not tried|
|Product Version||TDM 1.08|
|Target Version||TDM 1.08|
|Summary||0003117: Need release plan for old gamex86.dlls|
Players who have previously played missions will have a doom3/[fm name] folder with a gamex86.dll in it. If they try and load that mission under 1.08 it will crash or have serious problems.
We need some method for dealing with that, or we're going to be overrun with complaints from users who won't know why missions don't work.
|Tags||No tags attached.|
The GAME_API_VERSION define was increased from 8 to 108 so if you try to load an outdated DLL with the new exe, you get something along these lines (the error message is inside the old DLL; so the new, better error message is not shown to the user. This cannot be changed!)
found DLL in pak file: /home/te/.doom3/darkmod/tdm_game02.pk4/gamex86.so, extracting to darkmod path
copy gamex86.so to /home/te/.doom3/darkmod/gamex86.so
FATAL: Incorrect game version: required 8, got 108
Ensure the correct Doom 3 patches are installed.
On Windows, it might be that the user does not even see this message, instead TDM just closes. However, this is still better than loading the old DLL, and then later crashing during map load, or just not-really-working in a map.
We still need to come up with some plan on how users can easily and safely upgrade. They probably need to manually remove all "doom3/FMNAME" directories in their d3 path.
Just a afterthought: The support for loading things from "D3BASEDIR/FMNAME" (e.g. /home/te/.doom3/builders_influence/) should probably be removed completely.
That way old things that are left over in this path cannot disturb the game anymore.
|Yeah, that's what I was going to do anyway. After looking at the FS stuff, I think it will be problematic supporting missions in both doom3/darkmod/fms/ as well as doom3/|
|Are the FM searchpath changes sufficient to mark this as resolved?|
|I think this can be resolved.|
|06.05.2012 18:35||Springheel||New Issue|
|06.05.2012 19:04||tels||Relationship added||related to 0003035|
|11.05.2012 14:34||tels||Note Added: 0004570|
|11.05.2012 14:45||tels||Note Added: 0004571|
|11.05.2012 14:45||tels||Relationship added||related to 0003057|
|11.05.2012 14:46||tels||Assigned To||=> taaaki|
|11.05.2012 14:46||tels||Status||new => assigned|
|11.05.2012 14:46||tels||Relationship added||related to 0003125|
|11.05.2012 14:59||taaaki||Note Added: 0004572|
|16.06.2012 19:04||taaaki||Note Added: 0004665|
|20.08.2012 12:03||Springheel||Note Added: 0004770|
|20.08.2012 12:03||Springheel||Status||assigned => resolved|
|20.08.2012 12:03||Springheel||Resolution||open => fixed|