|
Post by chris_c on Aug 28, 2013 10:07:34 GMT -5
Milspecsim wrote:
I too have no idea what this means, sorry.
Chris
|
|
|
Post by Maarten on Aug 28, 2013 10:35:37 GMT -5
|
|
|
Post by Tom/CalClassic on Aug 28, 2013 11:15:16 GMT -5
In that case I would install those patches to each installation as I install them, if they depend on the registry. If not, the order is not important.
|
|
|
Post by milspecsim on Aug 28, 2013 13:13:37 GMT -5
Six Default FixesThis fixes two huge holes, and the mesa to the SW of KMEM. A few mistakes made it though the original meshes of FS 2004. I think Silver and Gold wings are full new meshes, so it may not matter. But I have run into another issue, with the FS9.cfg files. Do they just get renamed like the .exe files? FS9.EXE -> FS9.CFG SW.EXE -> SW.CFG GW.EXE -> GW.CFG Is that that is required, aside from renaming the main FS folder?
|
|
|
Post by Tom/CalClassic on Aug 28, 2013 15:47:20 GMT -5
I don't remember - if you do it for Golden Wings you should do it for any other renamed exe file, I would assume.
|
|
|
Post by chris_c on Aug 28, 2013 16:54:47 GMT -5
Six Default FixesThis fixes two huge holes, and the mesa to the SW of KMEM. A few mistakes made it though the original meshes of FS 2004. I think Silver and Gold wings are full new meshes, so it may not matter. But I have run into another issue, with the FS9.cfg files. Do they just get renamed like the .exe files? FS9.EXE -> FS9.CFG SW.EXE -> SW.CFG GW.EXE -> GW.CFG Is that that is required, aside from renaming the main FS folder? Ok, thanks to Milspecsim and Maarten. Am actually quite used to FS9's assorted holes and spires now, particularly that monster in South America so a fix really never seemed necessary. My executables are renamed but I do not recall if it was me or the installers that did the deed. The installers did place the unique *.cfg files in the ...\Documents and Settings\Microsoft\FS9 folder when each version was fired up for the first time. Chris
|
|
|
Post by milspecsim on Aug 29, 2013 7:38:20 GMT -5
AH! So renaming the EXE files BEFORE first execution is the key...
I'll let ya know what happens, I decided to clean out the FS side of my machine (I have 4 HDD's) and this led to a reorganization of the FS storage files... Me and my computer OCD...
|
|
|
Post by milspecsim on Sept 12, 2013 21:42:25 GMT -5
It worked, however I decided to run only one era. The proper one.
|
|
|
Post by Willy on Sept 12, 2013 23:39:22 GMT -5
I've got two installs of FS9 going. My "FS 1954" one with all the CalClassic goodies and a stock one that I use for our online racing.
|
|
|
Post by milspecsim on Sept 20, 2013 22:21:29 GMT -5
Well I went ahead and put a Modern version on my machine, but Ihave no idea how to separate the default flight files or the flight plans. Anyone know how to separate them?
|
|
|
Post by Tom/CalClassic on Sept 21, 2013 9:21:52 GMT -5
You can use my modified language.dll file to do that, if you wish. Note that the technique doesn't seem to work on certain computers, probably due to permissions issues. www.calclassic.com/files/Classic_dll.zipInstructions in the text file. Hope this helps,
|
|
|
Post by dennistisac on Oct 3, 2013 0:22:00 GMT -5
Yes, the default C-172 is going to be needed unless you don't mind having to scour your file looking for the culprit when you get a Cessna piston sound instead of a screaming jet noise Yes I figured out what to do to eliminate this BTW, so I'm not quite the neophyte I used to be:)
|
|