- moved do_versions stuff for 2.30 release, to also check 2.30 files.

  this is safe initialization only.
  based at report from madprof.. he had a 2.30 file without this
  data correctly initialized... but how it happens? tuhopuu files?

  anyhoo, we might think of splitting do_versions in 2 parts:
  1. do_versions initialization of old variables that changed
     like physics properties that need to be scaled or so
  2. do_init for newly created variables that are not allowed to be zero,
     this can safely be done for each file

1 files changed, 6 insertions, 2 deletions

diff --git a/source/blender/blenloader/intern/readfile.c b/source/blender/blenloader/intern/readfile.c
index ee3dd5b4131..5987f03a198 100644
--- a/source/blender/blenloader/intern/readfile.c
+++ b/source/blender/blenloader/intern/readfile.c
@@ -3902,8 +3902,12 @@ static void do_versions(Main *main)
 			}
 		}
 	}
-	
-	if(main->versionfile <= 229) {
+	/* ton: made this 230 instead of 229, 
+	   to be sure (tuho files) and this is a reliable check anyway
+	   nevertheless, we might need to think over a fitness (initialize) 
+	   check apart from the do_versions() */
+	   
+	if(main->versionfile <= 230) {	
 		bScreen *sc;
 
 		// new variable blockscale, for panels in any area