Now that 1.08 is here and a number of missions have been updated

[Oldjim]

Would it be a good idea to completely remove 1.07 and all the games so that the games can be downloaded again thereby picking up all the ones which have been updated for 1.08 or is there an easier way

[Melan]

Oldjim: if I understand you correctly, the answer is no, no and yes.

• You do not have to delete 1.07. 1.08 is a differential update which will automatically make changes to your 1.07, 1.06 or 1.01 installation.
  
• You do not need to delete the missions you have already downloaded. Most of them are unchanged. But check out the in-game downloader under New Missions: it should notify you of mission which have been updated since you last downloaded them.
  
• You should delete your old save games, because they will not work under 1.08. In fact, due to the different way missions are handled, you should use the cleanup option on all installed missions. This will erase unnecessary folders in your doom3 folder and free up HD space.
  

[Bikerdude]

[*]You should delete your old save games, because they will not work under 1.08. In fact, due to the different way missions are handled, you should use the cleanup option on all installed missions. This will erase unnecessary folders in your doom3 folder and free up HD space.

With reference to this, @Jim you obviously need to finish playing any mission under 1.07 before nuking the save game etc.

[lowenz]

Maybe it's a good idea to create a "1.08 compliant & totally tested" mission list?

Edited October 18, 2012 by lowenz

[Melan]

All missions ought to work with 1.08. In fact, I believe they are tested during the release process to see if anything is broken.

[STiFU]

All fm folders under the D3-root directory can be deleted. No need to do it via the clean up function of TDM, that would be quite cumbersome. Just keep four fm-pk4 inside your darkmod/fms directory and you're fine.

 

All missions ought to work with 1.08. In fact, I believe they are tested during the release process to see if anything is broken.

I did test all whether they launched ok, but didn't check if anything else was broken, I also playtested a few FMs to the finish, as some other probably did too, but I doubt we managed to do that with all FMs.

[Springheel]

We attempt to test every mission, though it's not always possible to test everything inside each mission. There were only two significant issues we noticed that needed updates to the mission itself; one is Thief's Den, which should already be fixed, and the other is In Remembrance of Him, where the fix is known about but RPGista hasn't had time to add it yet.

[Bikerdude]

Thief's Den, which should already be fixed

That's done btw, its sitting in my betamapper repo folder.

[Oldjim]

Thanks - as I am going out to a meeting now that is a task for tomorrow

[STiFU]

That's done btw, its sitting in my betamapper repo folder.

Uhm yeah, because Springheel already fixed it. Don't tell me you fixed the fixed version? ;D

[SeriousToni]

All fm folders under the D3-root directory can be deleted. No need to do it via the clean up function of TDM, that would be quite cumbersome. Just keep four fm-pk4 inside your darkmod/fms directory and you're fine.

 

So what do I do exactly with my old FM folder and my WIP stuff then? Should they be put in the "darkmod" folder since it's the new root folder now?

[STiFU]

You can have your WIP folder anywhere inside your D3-folder, I believe. That actually caused quite the issue on the Dark Radiant side of things at first.

 

Your fms should be contained in darkmod fms and they should stay there. But the FM-folders under ".../Doom3/" can be deleted unless you want to backup the screenshots.

[Oldjim]

Now updated

I had a slight problem with adjusting the video settings as the default was totally blurred and I had to do a bit of guessing to get a better picture before setting it to 1680 x 1050

Regarding updated games the new games list doesn't show any updated games from when I originally installed them but checking the fms folder I see that St Lucia and the Training Mission updated as part of the install process and The Creeps was updated on 18th Sept 2012

[7upMan]

I had a slight problem with adjusting the video settings as the default was totally blurred and I had to do a bit of guessing to get a better picture before setting it to 1680 x 1050

 

This. Also, after doing an incremental update to 1.08, when playing a mission (RTTC v2) I found that pressing ESC freezes the entire game so I have to kill it manually. I have just now d/l'ed everything from scratch and hope that this will solve the problem. I'll post an update after making a new attempt.

[STiFU]

Edit: Have you been playing the mission or does the screen already go black during start? If it is the latter, continue reading, if not, ignore the following.

 

This might be an issue specifically with RTTC v2 I ran into myself. By any chance, did you have RTTC installed and updated it to RTTC v2? If so, it is very likely you have a startingmap.txt or something like that inside your "fms/RTTC"-folder, which point to a wrong mapfile. The authors renamed the mapfile between updates, which leads to this problem. You can solve it by simply removing startingmap.txt.

[stumpy]

am likely to go through mine sometime in the future and update them if needed, I've already checked my WIP map and I need to change some lamp models that were lit in 1.07 but now unlit in 1.08

[AluminumHaste]

All missions ought to work with 1.08. In fact, I believe they are tested during the release process to see if anything is broken.

 

Yes they were. It was fun flying through all the missions as fast as possible, but they were all able to be completed for me anyways.

[7upMan]

This might be an issue specifically with RTTC v2 I ran into myself. By any chance, did you have RTTC installed and updated it to RTTC v2? If so, it is very likely you have a startingmap.txt or something like that inside your "fms/RTTC"-folder, which point to a wrong mapfile. The authors renamed the mapfile between updates, which leads to this problem. You can solve it by simply removing startingmap.txt.

 

I found that this might be only an issue when running the modified flyby-version of RTTC v2 that ShadowHide created. I loaded and ran ToSL just fine. I will try and check the normal version of RTTC during the next days, to see whether it's an issue with the modified version only.

 

Another strange thing is that when I enable Vsync, the game freezes instantly. This might be a problem with the driver (ATI on Win7-64/HD6950), so I am going to investigate this further.