Sign in to follow this  
Guest sbdwag

FSD Talon Service Release - watch out!

Recommended Posts

Just a heads-up: the FSD T-38A Service Release installs only to the original folder name - it won't let you install to a temp folder - and will overwrite your aircraft.cfg file. So if you've added lots of repaints, beware. Back up first and copy your entries across afterwards.Wonderful plane - thanks so much, FSD - but how I hate those "no choice" self-installers!Mark "Dark Moment" Beaumonthttp://www.swiremariners.com/cxkaitak.htmlhttp://www.swiremariners.com/cxkaitakv3.jpg

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Hey Mark-No need to do that if your repaints include the paint.cfg file (as they are suppose to).After you install the update, just run the paint scheme manager and it will update the paints in the aircraft.cfg.DO NOT REUSE YOUR OLD AIRCRAFT.CFG in its entirety, since you will loose any of the updates to the aircraft.cfg. Regards,http://home.earthlink.net/~snyders2000/T2.jpg | [LINK:www.airliners.net/search/photo.search?emailsearch=jlsnyder@hdp.com]AIRLINERS.NET PHOTOS][/b

Share this post


Link to post
Share on other sites

It is the service release for the T-38 that FSD released recently. It addresses these issues:1. Insertion of the airbrake indicator on the VC instrument panel.2. New flight model with lower idle;3. Scrape point edit to fix the constant taxi sound anomaly.4. Force feedback entires included now in the Aircraft.cfg file.5. Automatic Yaw Damper to be set ON with gear retraction as opposed to ground contact - to restore rudder function in the pattern.6. Vertical Speed selector/rate fixed.7. Problem with default Windows sound playing on some gauge control clicks fixed.Regards,http://home.earthlink.net/~snyders2000/T2.jpg | [LINK:www.airliners.net/search/photo.search?emailsearch=jlsnyder@hdp.com]AIRLINERS.NET PHOTOS][/b

Share this post


Link to post
Share on other sites

I downloaded the service pack, but cannot install it for some reason. Yes, I am aware that the documentation says that you can only install it if you did not modify the original folder in any way. But what exactly does that mean? I installed the -38 normally into my FS 2002 folder, which is located on the path E:SpieleFS2002 - is that already too much for the updater? Or does that mean that you must not even manually edit the aircraft.cfg file?

Share this post


Link to post
Share on other sites

Thanks, Jeff. I knew I was dumb. However, I still hate self-installers that give no choice of install route. Yours work (of course) but others seem to use them as a kind of status symbol, and the installer can end up overwriting important gauges with 1998 versions, etc. Shudder shudder ...Mark "Dark Moment" Beaumonthttp://www.swiremariners.com/cxkaitak.htmlhttp://www.swiremariners.com/cxkaitakv3.jpg

Share this post


Link to post
Share on other sites

I tried to install the update and it aborted stating I didn't have a "registered" version of the Talon?!?!?!?! register.... its freewareBrian

Share this post


Link to post
Share on other sites

@ Brian:That is the same error message I got...!

Share this post


Link to post
Share on other sites

Strange...I downloaded the update from FSD directly (got it from flightsim.com at first), and now it did work.HTH!

Share this post


Link to post
Share on other sites

I cannot find the update at the FSD site .... anyone got the URL for it?Many thanks !

Share this post


Link to post
Share on other sites

Unzip the update into a folder of your choice. When you run the updater, tell it to install the newer files into a temporary folder and then you do the drag and drop game with the newer files, over writing the older files.The newer files will be in three folders: Aircraft, Sound and Gauges. These folders are also sub folders within your main FS2K2 folder and it is an easy task to simply drag and drop files from one place to the other. Drag and drop only the files, do not drag and drop any folders!An afterthought - you shoud rename your version of the aircraft.cfg file to aircraftORG.cfg before you drag and drop this file. You should then personally edit the new aircraft.cfg file using your changes which are now contained in the aircraftORG.cfg file.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this