FastCargo

Me too...I'd like a terrain to be able to test out all mission types, including air to air missions that can't be done on the Range. FC

As far as retraction into the nose, you would need some better pics of the actual aircraft nose gear area to determine how the gear retracts. FC

Okay, first thing is I've color coded what parts are what (I'm assuming here): Green - Steering Collar Tan - Lower Shock Strut Red - Upper and Lower Scissors (2 parts) Blue - Upper Shock Strut The heirarchy tree would be: Steering Collar -Upper Shock Strut --Upper Scissors --Lower Shock Strut ---Wheels ---Lower Scissors The Steering Collar would be linked to the rest of the main part of the nose gear. The Upper Scissors, Lower Scissors and Lower Shock Strut would be animated for the 'shock' strut. The Steering Collar is not animated, but moves using the SteeringNode= parameter in the data.ini for the nose gear. That will take care of the 'shock' and nose wheel steering. FC

What is it you want to know? FC

Ed, we're going to need a LOT more info than that my friend. Data.ini entry, which gun, screenshot, how is it not aligned (which axis, and by how much). FC

http://forum.combatace.com/index.php?showtopic=46947 This should answer your questions. FC

Then it doesn't exist for the ThirdWire series. FC

Okay, since there is some question of the stability of a conversion, I decided to run a test to make sure that this was safe. First, some specifications: OS - Vista 32-bit SP2, Home Premium UFU - Version 3.3 Unregistered - http://www.replsoft.com/index.html ANSI2UNI - Freeware - http://www.robinland.com/ SF2 Merged install fully patched. I used a version of the F-16XL for my test as I had not converted it over to SF2. I went through and verified all the ini files were still in ANSI using Notepad. I then resaved 2 of the files in Unicode using Notepad. I verified again that those files were now in Unicode and all the others were in ANSI. I then used UFU's Finder function to find and mark all the ini files in the F-16XL directory, sending them to the 'Basket' (a queue in UFU). Next, I used UFU's Renamer function to take all the files in the 'Basket' and rename them to all CAPITAL letters. I verified that all files had been renamed using Windows Explorer. I then also verified that all the files were still their specific format (ANSI or Unicode)...UFU had not messed with that at all. I closed UFU and started up ANSI2UNI. I selected 1252 in the codepage window, used *.ini in the File mask, selected the F-16XL directory using the 'Select Dir(s)' button, selected 'Unicode (little-endian)' in the unicode window, and checked Recursive (this enables subdirectory searches). I did NOT check Overwrite Old Files. Hit the convert button, whereupon the program asked me which directory again (selected F-16XL again). Duplicates of the files then showed up in the directories...all with '_uniLE' added to the name (ie F-16XL.ini had F-16XL_uniLE.ini as a duplicate). The 'uni_LE' duplicates were each in Unicode, undistorted from the previous version, no matter if it was in ANSI or Unicode originally. I used WinMerge to check the originals and duplicates and it found the files were identical in every way other than the actual coding. Having this success...I deleted the _uniLE files, reset ANSI2UNI to Overwrite, and proceeded to overwrite the files with Unicode versions. After it asking me if I was sure, ANSI2UNI proceeded to overwrite the inis. Again, checking the results, no distortions were noted. Final test, I put the newly changed F-16XL into my Test folder to check. The model immediatedly showed up and was flyable. This was done with NO other changes to make it work in SF2. My opinion, both programs used in tandem are perfectly safe and efficient in converting your ini and lst files to CAPS, then Unicode. I would STRONGLY recommend backing up your stuff first, then using the settings I used in the order I used them for the best results. FC

Woah...I didn't use UFU for Unicode conversion...only for CAPS conversions. I used ANSI2UNI for the Unicode conversions. I'll post my specific settings in a few minutes. FC

Well, considering that in the readme and in the download page it says very specifically that it's for Generation 2 (SF2/V/E/I) sims only...yea, I'd say that's correct. Now, in the Strike Fighters 2 Knowledge Base, there is a specific article dedicated to getting Generation 2 aircraft to work in a Generation 1 install properly. The Knowledge Base is your friend. Do not (virtually) die in ignorance. FC

All T-38s/F-5B/CF-116D downloads updated with proper fuel tank numbers. Includes redoing all inis and lst files to all capital letters and Unicode (or ANSI for the Gen 1 T-38). FC

Alright! Found out that ANSI2UNI does have a subdirectory function. So, using both UFU and ANSI2UNI, you can convert your whole mod folder ini's and lst files to all CAPS and to Unicode in literally a minute. If you do this, backup your mod folder first! FC

Got it back in early 1996, it was shown as a video during a presentation while I was going through Squadron Officer School. Afterwards, I asked the instructor for a copy. It may be the ONLY copy that still exists...at least until I digitized it and put it on YouTube. I haven't seen a better quality version since....and I've looked! Text of the song taken from this website (warning, not for the weak and worthless): http://www.csufresno.edu/folklore/drinkingsongs/html/books-and-manuscripts/1980s/1988-497-TFS-hooters-songbook/index.htm FC

No. FC

FC

With you on that...Turing is notable in helping shape the modern world...an actor is known for being able to lie convincingly. Exceptions of course exist... FC

Well, in the CF-116D, the tip tanks are optional for loading, but with the correct amount of fuel in each of them. I think I just used the wrong number in the internal capacity of the fuselage tank. I'll take a look at all the Northrop 2 seaters and release a hotfix if necessary. Actually, I'll probably just update the uploads. FC

Hah! Never been 'that' guy...but I have come across a few 'pop ups' I didn't know about... FC

.

Hmmm...could have sworn I had put the fuel in KG in the data.ini. FC

Just tried myself 5 minutes ago. Appears normal for me. Now be advised I had some weirdness myself eariler...couldn't get the site to let me post ANYWHERE. But that seems okay now... FC

This would be great...if I had any Stingers left... FC

Of course, you could use the ruler tool....set the ship as an aircraft that always starts airborne. All you care about is coordinates....the ruler tool will help. FC

Well, couple of other questions are if that was changed in the Oct 08 patch or SF2 versions, and does it affect gameplay. I know for a fact that in certain ini files, as long as there aren't duplicate entries, you can have 'gaps' in counts. SystemNames in data.ini files come to mind. Good find anyway...anything that can make it easier to sort through ini files is a boon. FC