Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: Dysko on April 01, 2007, 11:11:15 am
-
Some days ago I installed TBP. After playing a bit with it, I returned to play standard FS2 Open (latest 3.6.9 build, MediaVPs in the "mediavp" folder etc.). And I got a lot of problems: cutscenes have all the colours messed up and are shown in smaller size, text distortion problems are back, shine maps are too bright etc.
I tried re-installing 3.6.9, but with no effect. What should I do? What can I post to help? :confused:
EDIT: maybe this info may interest you: I downloaded all TBP 3.3 files. FS2_Open and the INF:A standalone build I'm using for beta testing for Woo are messed up, the TBP and BtRL builds are not.
-
Retrace your steps, are you sure you didn't do anything else that might have affected? Driver updates perhaps?
-
No, I updated only the video card drivers before installing 3.6.9 months ago due to some flickering.
I remember also that when some time ago I used TBP, and the FS2_Open build was 3.6.7, I had no problem... maybe some incompatibility between 3.6.7 used by TBP and 3.6.9? (but this wouldn't explain why BtRL works perfectly...)
-
Maybe the registry settings got screwed up.
HKEY_LOCAL_MACHINE\SOFTWARE\Volition\FreeSpace2
This is used by most engines, I'm not sure if the settings being changed by multiple versions would affect it...
Try exporting that key, then deleting *THAT KEY, NOT YOUR WHOLE REGISTRY OR SOFTWARE KEY*, then re-install 3.6.9...
Wait, try merging my registry key, to overwrite yours... that should work, but you'll have to re-configure your settings the way you like them.
[attachment deleted by admin]
-
Isn't TBL standalone?
How the hell can it mess up your FSO when it's installed in a different folder (you did install it in a different folder - did you?)
-
Screwing with the registry as jr suggests is one way it could very easily do that.
-
? If you haven't noticed, every FSO build, regardless of what it's running - a TC mod or FSO - uses the same registry key. The settings for each, I image, are different. BTW, I have fiddled with my registry with no mishaps for quite a few years (well, almost no mishaps; that's why I always backup first). :p
-
Also WCS seems to be quite messed up...
So, what should I do? And yes, FSO, TBP, WCS, BtRL and my beta testing version of INFA are all in separate folder.
-
I tried merging jr2's registry key with mine, and now it works perfectly! (Though I had to uninstall TBP :()
Thanks!
-
I've had a similar problem w\ TBP 3.4 trying to run Infestation and Survior from MAD, But it screws with all the brightness either too dark or bright or it just ctd, and i have to restart. Ran Reg ScrubXP that seemed to work for fso but not TBP.. Oopss add on..and now everything is SSSSLLOOWWW post this in TBP forum too please
-
Alot of this could prolly be avoided if all Launcher version didn't use the same reg key... TBP, BtRL, FSO, WCS, all using the same reg key might not be such a good idea.. I'm sure it's being worked on, though.